- User Since
- Jul 4 2014, 11:26 PM (151 w, 1 d)
Thu, May 25
This was supposed to be merged into T44674 but phabricator seems to have done something weird... no option to fix it either...
Closing for a few reasons:
Fri, May 19
I cant reproduce this on my hardware. My guess is the scene is too large, but we should probably have a better error message in that case. I'll try to put something together for that later.
Tue, May 16
Might be nice to record more info into system-info output, but not sure theres anything else useful in this patch.
Im unable reproduce here. Please update your drivers and try again with latest master.
Tue, May 9
- Use VLOG only
- Added code to touch cached files are they are used
Wed, May 3
Made requested changes
Tue, May 2
It would be nice to blacklist the older cards, but I havent found a way to do it yet.
Interesting render results. Unfortuantly @Aaron Carlisle (Blendify) is correct, we arnt supporting GCN1 cards anymore.
Mon, May 1
Sat, Apr 29
Fri, Apr 28
- Fixed path termination again
- Removed ifdef around ray flags
- Rebased on master
Closing as these changes are already in master.
Apr 26 2017
Apr 25 2017
Reuploading with context, couldnt see where inline comments where attached to.
- Fixed ifdefs
- Fixed usage of wrong PathRadiance in do_volume and subsurface_scatter after the change in ray_index for loop iteration.
- Fixed logic for path termination
- Rebased on master
Apr 22 2017
Apr 21 2017
@Tom (vejn) Please open new reports for new issues, putting different issues into the same report is quite confusing.
This could be a driver issue with GCN 1 cards as all cards mentioned in this report are that generation. I cant reproduce this with the cards I have available, and if it is a driver bug there's nothing that we can do anyways. There is a new version of the drivers released recently you guys could try, but we may have to drop support for these cards.
Apr 19 2017
Apr 18 2017
Only minor stuff, don't want to be too picky. I think it will be fine to commit, but maybe would be nice if @Sergey Sharybin (sergey) or someone else could test CUDA split first (I would test it but I've been having issues with CUDA lately).
Apr 11 2017
Apr 8 2017
Apr 7 2017
Mar 31 2017
Only did a quick look right now, will look over the rest later. I like the changes to how kernels are handled.
Mar 29 2017
Im fine with this too.
Mar 23 2017
Mar 21 2017
Mar 17 2017
Mar 16 2017
Not entirely happy with how locals are done but not sure theres really a good way to go. Maybe have DEFINE_SPLIT_KERNEL_FUNCTION_LOCALS_$N and have kernel functions like kernel_func(KernelGlobals *kg, ccl_local unsigned int* local_1, unsigned int* local_2, ...)? That way we get errors if the number of locals falls out of sync.
Mar 14 2017
Mar 11 2017
Mar 10 2017
@James W E Bird (3dLuver), thanks for the logs, very interesting results. Will try to get this fixed quickly.
Please run blender with the --debug-cycles option and attach the full output after the tile gets stuck. Also run clinfo and attach the output of that aswell.
Mar 9 2017
Looks fine I guess, would be nice to deduplicate things more but not so important.