Dosent work with: 2.80.44
Fri, Feb 15
Thu, Feb 14
See here the results of this change in terms of node compilation times.
Which exact 2.80 version are you testing (date from the splash screen)?
Script used for this research. Needs to be run blender containing D2264 patch.
Wed, Feb 13
Patch created D4349
Here are the measurements of how much effort it takes to compile a certain node.
Tue, Feb 12
Are there any ways to log those things in blender so u can get further details from users?
I confirmed it works well on an RTX 5000 and GTX 1080, so it indeed seems to be fully resolved. Performance also seems a few % better than 10.0 for me.
on win7 with sm_30 (gtx670) which was one of the problematic ones
Just for convenience, should make no difference which one is tested.
is the bmw scene linked different from the one in our benchmark suite? or was it just linked for convenience?
I have some test builds to verify if this bug is indeed solved with the upcoming CUDA bugfix.
So far we've not found a way to reproduce this yet, tested on multiple computers with different graphics cards.
From my research this issue has been present for more then a year now. Its a pretty big issue, id say. So far devss kept complete radio silence on this issue, or i havent been able to find anywhere where it was anything said about it. Could devs say anything about it like, is it getting fixed at all and when? Why has it been neglected for so long, is this that hard to fix? Considering it has been around for such a long time.
Reproduced this issue in every comitted Blender file, latest blender-2.80.0-git.d3870471edd7-windows64, using my own Shaderstatue for Shader testing. All bakings fail before 10% got actually baked.
No crashes anymore!
Mon, Feb 11
This one was fixed.
Cannot really reproduce this anymore...
I get an assert when I switch between rendered and lookdev mode in this file.
Seems to be some synching issue between Blender and Cycles.
Is this still an issue with the latest build from https://builder.blender.org/download/ ?
Sun, Feb 10
Sat, Feb 9
Ok, I'll close this then. Glag you manage to solve it in the end.
Thank You, Sebastian, for your patience and help again! I think this bug is one more reason to finally go to Linux system! =)
So finaly I managed with crushing. I reinstalled the whole system from scratch. It looks like the problem was in Windows itself.
Fri, Feb 8
I'm unsure if we can help you here. This is nothing suspicious in the output and because your monitor turns black (+that it works with the software dll) I don't think there is much to do here.
Thanks. Tested Fur and prime. It went well
I couldn't check that the bake result is correct. Yesterday's daily build crashes upon clicking the image dropdown menu in Image editor or UV editor. That's an unrelated issue, and I'll wait a day or two before reporting it.
Cool, it seems to be fixed in current daily builds. I close my bug report as resolved.
Thu, Feb 7
Can you remove the .dll file that you dropped in and run blender with:
blender.exe --debug-gpu > output.txt 2>&1 and make it crash?