- User Since
- May 24 2016, 1:39 PM (264 w, 3 h)
May 12 2021
For me it works, so I would say yes :)
May 3 2021
OK, this seems to be "fixed" with this commit: https://developer.blender.org/rB6899dbef77cd26df3588888040887e4e41c1ec43
Quick update: If I link the collection to a scene and use "Make Proxy" instead of "Make Library Override" everything works as expected...
May 2 2021
Apr 21 2021
I just tried to reproduce it and couldn't reproduce the crash anymore. Great work, guys! 👍
This ticket can be closed I guess.
Apr 7 2021
Mar 23 2021
Mar 18 2021
Mar 4 2021
Feb 24 2021
Yes, the build you're testing is older than the release from the Build Bot I mentioned as the last working build. So I would expect that to work as well, as the bug seems to have creeped in at a later time (most likely here I suspect https://developer.blender.org/rBbb2af40ec7dd9a0c41991bc2faaf6eb3f0618016 ). If you're not compiling Blender yourself, you might have to wait a few hours until an updated build is available for download.
Feb 22 2021
Feb 16 2021
Feb 9 2021
Jan 28 2021
Thanks! I can confirm the fix is working for me!
Jan 27 2021
Jan 21 2021
Yeah, right! At first it looked too easy because I didn't notice that Denoising Data was enabled and I could easily reproduce it with an empty scene file (which I assumed was a bit stupid to upload). But in the end it would've helped.
And just to confirm I just downloaded today's Buildbot build and it fails the same way as my own build yesterday. So it's not a CUDA 10 vs 11 thing. ( blender-2.93.0-41a945d7469f-linux64 )
OK, a quick update:
Jan 20 2021
Hmm, I'm using CUDA 11.2 on my side. Maybe that's the problem.
Thanks for testing YAFU. I don't mean progressive refine but normal tiled rendering with GPU+CPU (CUDA+CPU).
The OptiX and progressive part of that bug report comes from the commit that caused the crashes for me ;)
I also build with OptiX 7.2.0
Invalid value in cuMemFree(mem.device_pointer) (device_cuda_impl.cpp:970)
Launch failed in cuMemcpyDtoH( (char *)mem.host_pointer + offset, (CUdeviceptr)mem.device_pointer + offset, size) (device_cuda_impl.cpp:1034)
Jan 15 2021
Jan 11 2021
Dec 16 2020
Dec 14 2020
Dec 8 2020
Thanks a lot! Problem is fixed :D
I close the file browser by clicking on "Cancel" in the lower right corner. I set my file browser to open fullscreen, maybe that might make a difference?
Dec 1 2020
Nov 30 2020
Nov 19 2020
I just gave it another try with the very latest master and the problem still looks the very same. I attached the system-info.txt from this version here.
Nov 18 2020
I applied Lukas' patch and it works perfectly. It just needs to get reviewed and accepted.
Nov 10 2020
Now that NanoVDB is enabled by default, this bug will hopefully be confirmed as soon as the Buildbots are updated tonight.
Nov 8 2020
Nov 5 2020
Nov 4 2020
Thanks for fixing this crash. It was gone after your commit, but now with the latest master it seems to be back :(
Oct 20 2020
Oct 14 2020
Oct 6 2020
I restarted everything of course, not only Blender. Maybe it's hidden somewhere in a GPU cache or whatever. It happens with all kinds of builds (official and my own). At first I thought it might be a problem with me using CUDA 11 to compile blender, but also the official master builds show that problem.
Your setup indeed looks very similar to mine.
Oct 5 2020
Oct 2 2020
Oct 1 2020
Sep 30 2020
Great! Thanks. So far it's looking good. I'll report back as soon as something weird happens.
Sep 28 2020
Sep 14 2020
Sep 9 2020
Sep 3 2020
What caught my eye when giving this scene a try was that your hair rendering geometry was set to:
which is a major difference to 2.83
Just gave this scene a try and it renders without problems here:
Sep 1 2020
Aug 24 2020
Aug 18 2020
Aug 17 2020
Aug 11 2020
Aug 10 2020
Jul 26 2020
Jul 20 2020
Jun 30 2020
Nice! Good to hear that I'm not the only one ;)
Thanks for investigating.
Jun 29 2020
Jun 18 2020
Jun 10 2020
Jun 8 2020
Oh damn, didn't see that one. OK, so I guess I'll have to live with it then.
May 26 2020
May 20 2020
May 19 2020
I have been able to bake normals, if I used Particle Instance modifier on cube, and then baked cube to target, which is essentially what you did, but a bit more procedural. Perhaps this was also a method that worked prior to 2.8?
Sadly no, it seems.
May 18 2020
May 13 2020
Apr 29 2020
Apr 22 2020
Apr 21 2020
@Brecht Van Lommel (brecht) Thanks for taking care of this so quickly.
Ah sorry, you're right. I can confirm the bug with the current master:
version: 2.90 (sub 0), branch: master, commit date: 2020-04-21 16:29, hash: rB8845b27dce89
This functionality was added during the 2.83 alpha phase AFAIK. So no chance to test it in 2.82a.
The bug itself isn't fixed in the latest builds. I'm using the 2.90 alpha right now and it shows the problem.