- User Since
- Dec 2 2018, 2:31 AM (37 w, 3 d)
Mon, Aug 19
Thu, Aug 8
Wed, Aug 7
For others with this issue, a workaround is applying a zero-alpha principled BSDF to the surface input of the shader output. Then set Alpha Threshold to zero.
Tue, Aug 6
Thu, Aug 1
Thu, Jul 25
Sure, I will do that next time :)
I will definitely switch to RC3 when it becomes available but please understand that this is a random crash and not observing it is not 100% proof that it is fixed. I really hope that those backtraces can provide some valuable clues.
Wed, Jul 24
Jul 21 2019
Jul 2 2019
Jun 25 2019
Jun 24 2019
Jun 23 2019
Jun 21 2019
I downloaded 2.8 from June 20th and the issue is resolved :)
This may be related to my report on a crash when editing beveled, modifier'd curves: https://developer.blender.org/T65981
Jun 16 2019
This is a duplicate of https://developer.blender.org/T61432, which is an ongoing issue. Hopefully, we can get this fixed soon!
May 23 2019
May 19 2019
May 18 2019
This doesn't seem like a bug report so a developer should decide whether it is valid and remove it if needed.
May 15 2019
Actually, you were right SlyNine. I was able to append the the smoke objects from the 2.8 blend file, bake the simulation in 2.79, and import it back. Still, is this bug/kludge ever going to get fixed?
May 14 2019
For me, I can't use 2.79 because the smoke flow object was created and edited in 2.8 only. The workflow would be a mess. Wouldn't it be better to remove the "totalSubsteps = 1.0f;" and let people use substeps at their own risk?
May 13 2019
May 9 2019
Looks like this isn't a bug. I found the following in /source/blender/blenkernel/intern/smoke.c line 3027 (after about an hour of searching)
I need this unbroken now. My smoke flow, in an animation that is important to me, travels extremely fast and leaves completely disjointed smoke puffs in its path. Why did it get set to low priority? Did you think it will be difficult to fix?
Mar 5 2019
@Sebastian Parborg (zeddb) Deleting .config/blender/2.80 fixed the issue without a reinstall. Now the question is what was wrong about my previous config files that deletes rigid-bodies... :/
Mar 3 2019
I saved this file with 2.8 from March 3. The cube has an active rigid body and the plane has a passive one. When I open it, neither rigid bodies are visible (the objects are visible). The cache doesn't play. When I add back the cube's rigidbody, its movement plays in accordance with cache.
@Sebastian Parborg (zeddb) I just downloaded the latest version and reproduced the issue. Interestingly, after I add back the missing rigid body in the physics panel, the baked simulation plays as it should.
Mar 2 2019
Mar 1 2019
Feb 28 2019
Also, where can I find "design tasks?"
The vector category wouldn't be almost empty if a true "normalize" node was added. The current "normalize" node could be renamed "normalize channel."
Feb 26 2019
@Jacques Lucke (JacquesLucke) Now I'm wondering why this node is in the "Vector" category, and that actually applies to most of the nodes there. This nodes, except vector curves, really stretch the meaning of "vector."
Feb 24 2019
Feb 23 2019
Feb 21 2019
Feb 4 2019
Feb 2 2019
Jan 14 2019
Jan 13 2019
Dec 31 2018
Dec 27 2018
Dec 25 2018
Upon updating to the December 24/25th version of blender 2.8, the problem is fixed in newly made, basic scenes. However, when I start the viewport cycles renderer in one of my old scenes, it won't stop updating. Normally, it would perform several samples and then say "rendering done" but now it just keeps updating the first, lowest resolution sample. Deleting the dupliverts object or disabling dupliverts stops the issue. Is it possible that this is a side affect of the changes and than all new blend files will not be affected?