- User Since
- Jul 4 2014, 11:26 PM (138 w, 1 d)
Fri, Feb 24
@Tom (vejn) that is interesting and might point to something we can fix. Its a different issue than the one in this report tho.
Hit the wrong button
Please check you have the correct drivers installed. You say you have an AMD card but the traceback has Nvidia symbols listed? Something must not be right there. If you can please attach the output of clinfo after checking your drivers.
Host memory is system memory, not GPU memory. Either your system ran out of memory or there's a driver bug.
Thu, Feb 23
Unfortunately there's not really anything we can do about your system running out of memory, which is whats happening here.
Out of host memory means your computer ran out of memory, theres no bug here.
Updated to replace pointers to KernelGlobals with pointers to KernelCamera in functions that are needed to be shared for calculating differentials and removed the duplicated versions.
Wed, Feb 22
Tue, Feb 21
Sat, Feb 18
Fri, Feb 17
Sat, Feb 11
Thu, Feb 9
Tue, Feb 7
To anyone having these issues please make sure you are using the latest available drivers.
Please update your drivers and try again.
Sat, Feb 4
Did some more testing with this scene: split-sss-volume.blend
Fri, Feb 3
To change the tile size setting for viewport rendering open the python console editor in blender and enter a line such as bpy.data.scenes['Scene'].cycles.debug_tile_size = 64, changing Scene and 64 as needed.
Your GPU is running out of memory and a driver issue is resulting in incorrect renders, try lowering the tile size and setting the render dice rate to a higher number.
Without being able to reproduce I can only assume this is a driver bug. You should check you have the latest drivers and try lowering the tile size.
This is a known driver problem, AMD is working on a fix. You'll have to use smaller tile sizes for now.
Your GPU is running out of memory because the tile size is too large. Unfortunately the tile size for viewport rendering isn't the same as for final renders and isn't controllable from the UI. To change the tile size for viewport rendering you'll have to use python. Set bpy.data.scenes['Scene'].cycles.debug_tile_size to the desired size.
Tue, Jan 31
Jan 26 2017
Jan 25 2017
Jan 24 2017
Jan 20 2017
Jan 19 2017
Did some quick tests, doesn't seem to be working.
Jan 17 2017
Watertight rendering is failing again, @Sergey Sharybin (sergey) maybe this is for you?
Jan 14 2017
Aside from the viewport tile size there should be no difference for users from this diff, this is mostly for better debugging and as a cleaner foundation for future work.
Jan 13 2017
Jan 6 2017
Issue in origial report has been fixed in master, closing as resolved.
Either your tile size is set too large and your device is running out of memory or this is a driver issue. Try decreasing the tile size and check that you have the latest drivers. Theres not really anything we can do to fix this, so im going to close the report.