beo6 Posted August 27 Share Posted August 27 Dragging and dropping a node with a component into the Flowgraph, looses the Flowgraph component after loading the map again. Reproduce: - Open Map - Add a Component to the Flowgraph via Drag & Drop - Save the Map - Open the Map again - notice that the Flowgraph entry is gone. Video: https://s3.libs.space:9000/share/flowgraph-not-saved-bug.mp4 Also tested with a completely new map. Node with SlidingDoor Component is saved, CameraDolly component is not saved for some reason. Tried it with this component: Quote Link to comment Share on other sites More sharing options...
beo6 Posted August 27 Author Share Posted August 27 Looks like it is another issue with Nodes being a child of another node. When i use the exact same component on the same node type but that node is on root level, it saves correctly. In This screenshot you can see the state right after loading a newly created map. I had added p3 to the flowgraph as well, but since it is a child of the CameraPath node, it was not saved. the `test-root` however was saved and loaded correctly. 2 Quote Link to comment Share on other sites More sharing options...
reepblue Posted August 27 Share Posted August 27 I've had this happen to me and it looks like you beat me to reporting this. Quote Cyclone - Ultra Game System - Component Preprocessor - Tex2TGA - Darkness Awaits Template (Leadwerks) If you like my work, consider supporting me on Patreon! Link to comment Share on other sites More sharing options...
beo6 Posted October 17 Author Share Posted October 17 I tested this again on 0.9.8c Build 1689 and this is still an issue. Quote Link to comment Share on other sites More sharing options...
reepblue Posted October 17 Share Posted October 17 It happens if the component is parented to another entity and is on the Flowgraph chart. Quote Cyclone - Ultra Game System - Component Preprocessor - Tex2TGA - Darkness Awaits Template (Leadwerks) If you like my work, consider supporting me on Patreon! Link to comment Share on other sites More sharing options...
Josh Posted October 30 Share Posted October 30 On 8/26/2024 at 8:12 PM, beo6 said: Looks like it is another issue with Nodes being a child of another node. Confirmed... You guys keep saying "component" when I think you mean "entity". Quote My job is to make tools you love, with the features you want, and performance you can't live without. Link to comment Share on other sites More sharing options...
Solution Josh Posted October 30 Solution Share Posted October 30 Quote My job is to make tools you love, with the features you want, and performance you can't live without. Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.