Thank you for pointing this out :) setting it to Screenshot or None does solve the issue of long saving times, probably going to use that until the fix gets released. The Screenshot option does…
No, I don't think it was broken in 4.2.
OK, thx
If I am not mistaken, this was broken in GPv2 as well, right?
Updated the "Worked" field (to help gather a list of fixes for the release notes for issues that were also present in prior versions)
Updated the "Worked" field (to help gather a list of fixes for the release notes for issues that were also present in prior versions)
Updated the "Worked" field (to help gather a list of fixes for the release notes for issues that were also present in prior versions)
Updated the "Worked" field (to help gather a list of fixes for the release notes for issues that were also present in prior versions)
Updated the "Worked" field (to help gather a list of fixes for the release notes for issues that were also present in prior versions)
@mont29 : do you want this on the 4.3 milestone?
Can confirm, assume this is also caused by 96198e88e1 (or lets say "exposed")
We have LIB_ID_COPY_NO_PREVIEW
and the flag is actually correct (it is not set), but the following code in…
One more thing I could think of: check the "altered" state when looping by using find_node_by_name
[if we dont find the group, it has been deleted already :) ]. Might not be as performant, also…
Generally fine I think, not sure though if we should mention specific reports (", see #77557") in property descriptions.
We should definitely wait for @ideasman42 to greenlight this.
The slowdown from ada367a0e9 should be resolved by 5358d1b09a585c5cc4e07931bf751ed7e1924933 already.
Thx for the info, we are getting the puzzle pieces together one by one
Documentation and reality are a bit apart afaict.
the manual says "For a node group to be shared as a tool, it…
After that, there was a large performance drop caused by a single commit:
- ada367a0e9278038d76f0aef4fd82d42412b9cbc (14.5fps -> 10.3fps)