Supplement the case of scene instantiation for "Editable Children"#81530
Conversation
e5d0d2e to
cea3ff6
Compare
|
What does it fix exactly? |
cea3ff6 to
216ec91
Compare
|
When Editable Children is enabled, due to copying nodes or specifying the same resource instance for different nodes in batches, the same resource entries will be recorded when saving. When opened again, resources with A test project is provided here. Before opening the scene, please check the text of 0.mp4 |
216ec91 to
f7d0c23
Compare
|
In the case in #81530 (comment), there may be multiple resource instances with the same |
f7d0c23 to
439317f
Compare
KoBeWi
left a comment
There was a problem hiding this comment.
Can't say I fully understand the code changes, but it does fix a bug. I'm not familiar enough with using editable children/local to scene to tell if there are any obvious regressions.
|
PackedScene changes at this stage seem risky (4.2 RC imminent), so moving to the next milestone. |
6692acc to
a037a67
Compare
This is a follow-up to godotengine#65011. For scenes with **Editable Children** enabled, the main scene will record more information and resource mapping will be valid for multiple nodes.
a037a67 to
1b4f116
Compare
This is a follow-up to #65011.
For scenes with Editable Children enabled, the main scene will record more information and resource mapping will be valid for multiple nodes. See #64487 (comment).