- User Since
- Jan 16 2019, 5:05 AM (116 w, 6 d)
Aug 5 2020
Oct 8 2019
Ok, it looks like this bug and another I reported around the same time were due to the Animation Nodes addon being enabled. I'm aware that it's no longer under active development, so I'm guessing it's ok to close this bug report.
Oct 5 2019
Will do, thanks!
Oct 4 2019
On a related note, is there a specific reason 2.8x doesn't display the Rigid-Body bounding box shapes in the viewport? 2.7x did this, and it was very helpful. I'm assuming it's intentional and not a bug.
As far as I know, the cylinder Collision margin box is not ticked by default, resulting in Blender assuming the value to be 0 automatically. If the box is ticked, then the value is explicitly controlled by the user. Is this the case?
Going off a suggestion in a different but related bug report, I tried resetting Blender to factory defaults. After this, things worked fine. I'll try to figure out what the difference was between my settings and the defaults.
Yeah, it looks like it's just a changed default.
Yeah, after loading factory settings, it's working fine. I'll try to figure out what was different about the settings I was using before.
Sometimes you may have to bake, delete the bake, and re-bake a few times before Blender will crash.
It kinda worked for me, but the playback slowed just under 9fps in the viewport with Prefetch enabled.
Jan 29 2019
Dang man. I don't know what to tell you. That's pretty frustrating.
Jan 22 2019
This is a good place to start. Feature ideas should be as fully fleshed out as possible.
Describe the feature, why it would be useful, where it would be in the UI, Ect.
Jan 21 2019
As far as I can tell, this is how it works in 2.79. Can you show more clearly what the problem is?
Jan 20 2019
I opened this with Blender 2.80.0-windows64, hash b0dee09a6d55, 2019-01-19.
Didn't find any issues. The build in the report is almost a week old, so maybe this is already fixed?
Confirmed. Can you try to simplify the scene so that it's just what's needed to see the bug?
Jan 17 2019
I'm not sure if this task is still active, but I just tested it, and there is no problem that I can find. Should this be changed to resolved?
I've had a similar problem sometimes, although not as severe. I think it's an issue with the graphics driver's anti-aliasing conflicting with Blender's own AA settings. I have a GTX 950M.
I opened the file without any issues, using the same Blender build. Can you be more specific about what modifiers are causing the problem, or what you were doing with the file before it crashed?