- User Since
- Mar 9 2013, 6:17 PM (455 w, 2 d)
Fri, Nov 26
Sadly this didn't make it into Blender 3.0.
It will be in the 3.1 release.
Thu, Nov 25
I guess you could include this in the 2.93 LTS release as well?
Tue, Nov 23
Fri, Nov 19
So you are saying that this fix doesn't actually fix the problem?
I can reproduce this issue.
It works with Eevee, not cycles.
Tue, Nov 16
Thu, Nov 11
This is a known issue with depsgraph and the rigidbody simulation system.
Undoing in certain cases will trigger a crash.
Mon, Nov 8
Wed, Nov 3
Other than my nitpicks, LGTM!
Oct 28 2021
Updated with windows related changes.
Also note that I will merge the fix into the 2.93 branch, so this should be in the next 2.93 release.
If that wasn't clear. Thanks again for pointing this out.
The general idea is that you file out one report for all blender versions that are affected.
Thanks for pointing out that I forgot to merge this fix into the 2.93 branch.
Adding Ray as well for the windows part that I haven't changed yet.
Is the install for windows needed here?
Oct 27 2021
Oct 21 2021
If someone else hasn't already reported this issue, then you should report it as an other issue, yes.
I'm saying that the invalid geometry generated by the boolean modifier is an other issue.
You reported that blender crashed when quadriflow was used on bad meshes with zero length edges.
In either case, the issue with generating invalid meshes is an other issue. So the reported crash has been "fixed", so I'll close this.
Did you try the latest 3.0 version?
The latest file you attached works in master as well (because it doesn't have zero length edges).
The model has several zero length edges which quadriflow can't handle.
(Use "merge by distance" to remove these and it will not crash anymore)
Oct 19 2021
Oct 15 2021
Oct 14 2021
Oct 11 2021
This approach looks good to me.
Oct 8 2021
@Clément Foucault (fclem) Could you take a look?
Oct 7 2021
Oct 6 2021
We don't do automatic tool switching in these cases.
It would be very annoying having to reselect the bounding box tool is you by mistake select multiple strips.
Updated patch with the latest feedback.
Oct 5 2021
Oct 4 2021
Oct 3 2021
Forgot to add Campbell.
@Campbell Barton (campbellbarton) does the 2d gizmo drawing changes look good?
I removed the modal calculations in the drawing code as it seems to me that the result there was always overwritten by the "pre draw" callback functions either way.
Oct 1 2021
Sep 29 2021
Sep 28 2021
Sep 27 2021
I've talked to Sybren and Brecht.
Sep 23 2021
Yes, I tested this with upstream libs on my linux machine as well. So I think it is on our end too.
Sep 21 2021
Besides my comments, I want to rename "overshoot" as well.
Basically because I think overshoot is not describing what it happening.
Sep 20 2021
To me this sounds like failing hardware. As per the fedora FAQ about these types of errors: link
We need to do a deep clean/refactor of our rigidbody code to properly fix some other crashing issues that are there because of some very bad design choices in the current code that can't be fixed.
So as Sergey pointed out, I don't either think this will be a high priority issue because of the amount of planning and time this need to be fixed properly.
Sep 16 2021
@Sergey Sharybin (sergey) Do you have any objections to this?
I don't think that a small memory leak when opening the file in older versions is anything to worry about.
Sep 15 2021
I think it looks good to me except a few things that I created a patch for:
Sep 14 2021
Aug 31 2021
I'm on vacation for two weeks, so I'll review and test this when I get back.
Aug 27 2021
Aug 26 2021
Aug 25 2021
Right, I also think that those two points will require a lot of work.
Aug 24 2021
I think we should probably add text outlines to solve this.
A few thoughts:
Aug 21 2021
Nice! Thanks for the heads up :)
Aug 20 2021
Ah, thanks! :)
I'll just tag @Bastien Montagne (mont29) as he wanted to do a double check on the for_each logic