- User Since
- Nov 22 2009, 9:05 AM (482 w, 5 d)
Sun, Feb 3
cycles in default = suicide
only solution is restart windows before opening blend file
thanks for the answers, I have updated the Nvidia drivers but the problem persists. The operating system is very stable, only when I change from eevee to cycles, after waking up, freeze occurs. For now I will remove eevee as the default engine, I see no other solution. If you have any other advice let me know and congratulations for the work you are doing;)
Thu, Jan 31
I had an idea and I managed to replicate the mistake!
windows in 100% of cases freeze when I access windows from "sleep mode" and open the blender and change the render engine.
I have to completely shut down the computer and restart it to no longer have the problem.
Is this a solvable error?
Wed, Jan 30
Jan 19 2019
thanks for the quick reply and we hope it will be resolved in the future
Jan 18 2019
Jan 17 2019
hi, with blender 2.80.41 date: 2019-01-16 21:59, hash: e57ee5934a30 the error persists (win8.1).
we must wait for the new depsgraph to fix this problem or I misunderstood?
Jan 1 2019
Dec 31 2018
Dec 28 2018
Thank you so much for the quick reply. Just replace the "RigidBodyWorld" collection, which does not actually exist in the scene, with the collection containing the RB. It is however strange that if I move the RB without using the M key but dragging with the mouse this problem does not exist
Dec 27 2018
Dec 16 2018
Dec 12 2018
Dec 9 2018
I managed to animate the particle system by registering a key to the mapping \ offset x. This animation is visible in 3dview but in rendering it is inanimate
Dec 7 2018
Dec 6 2018
thank you, you are an exceptional team !!!
Sorry, maybe I did not understand the discussion.
when the version of blender 2.80 is fixed, will I have the same result as a 2.79 blender?
Currently (build 2018-12-06 00:27, hash: 74db65e5424) the result is completely different as you can see from this screenshoot
this is the blend file
tnx in advance
Dec 5 2018
Dec 4 2018
Nov 27 2018
Dec 16 2017
Mar 22 2016
ok tnx for quick answer
I found an alternative solution,
if I use the node transform\nearest the problem disappears
look the blend https://www.dropbox.com/s/od2dzdsvzh...se1.blend?dl=0