Page MenuHome

Failed GPU render using 2.81.12
Open, Needs Triage by DeveloperPublic

Description

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86

Blender Version
Broken: version: 2.81 (sub 12), branch: master, commit date: 2019-09-19 20:35, hash: rBc8df6f2cf9df
Worked: Still works in 2.80.75 version.

Short description of error
Attempted to render via GPU with most recent version of 2.81.12, after successfully rendering in 2.80.75
First attempt generated an Error Message:
Cuda error at cuCtxCreate: Illegal Address

I down loaded the most recent NVIDIA Driver, (Studio version) which allowed me to do a CPU render but generated a failed version, mostly white with only the Billboard images rendering??

This is the attached set of renders, with the failed version noted.
I have also uploaded a ZIP file of the packed .blend to my site, but it is 574mgs, so it must be downloaded to view.
It is currently being uploaded, should be available in 15 minutes.

http://www.hartworks.net/blender/herotree_2-80_11.zip

Details

Type
Bug

Event Timeline

I just tested it again, this time with the Default 'Load Factory Settings' with the same results. It will only render the Billboard Image planes, which are the small bushes and the clouds. Everything else is "White??"
Attached is an image of the Screen in the Solid Mode. Oddly, the tree and leaves show up in this view??
Beyond this 'hiccup' I am very pleased with the fine development by the Blender Team.


Just tested it again, with the Cycles setting and Default GPU and get this with the Material Preview Mode

This is the second time that I found and 'odd' anomaly, which Blender 2.81.12 is doing on it's own. I have seen it twice, and corrected it both times.

This is the 'anomalous' node setup that shows up

This is how I correct it in 2.80.75

This is a second view of the Shader Window, with the newer 2.81.12 version.

Just a comment about the mapping node issue (havent looked at the other stuff...):

  • this happens when you open a file saved with the "new" mapping node [rBSbaaa89a0bc5] in a blender version prior to that commit... not much we can do here [it was decided that this compatibility breakage is acceptable]