Array of CSGboxes disappears when hitting apply while the array is located in CSG shape. about godot-array-modifier

[miskatonicstudio]

Hi and thank you for reporting this! I just confirmed that the bug can be reproduced:

I'm not sure why would CSGCombiner behave differently than a normal Spatial node. I'll check this and let you know ;)

[miskatonicstudio]

It seems that the problem might be caused by the scene tree structure rather than by node types. Specifically, I discovered that ArrayModifier has to be a direct child of a root node. So,

Spatial => ArrayModifier => MeshInstance

works, but

Spatial => Spatial => ArrayModifier => MeshInstance

doesn't (in the exact way that you described). Perhaps it's a problem with the implementation of add_child_below_node, but maybe there is something wrong with my code. I'll keep you posted ;)

[miskatonicstudio]

I changed the code a bit to add the child nodes to the root instead of the direct parent, and the nodes appeared in the editor. So, this is most likely a bug with the implementation of add_child_below_node. I will ran some extra tests next week, and submit an issue to Godot's team ;)

[TheConceptBoy]

I changed the code a bit to add the child nodes to the root instead of the direct parent, and the nodes appeared in the editor. So, this is most likely a bug with the implementation of add_child_below_node. I will ran some extra tests next week, and submit an issue to Godot's team ;)

Ahh roger. Well that's good to hear at least. Will you be pushing the change to the godot Asset Library plugin or is github going to be the place to get the updated plugin for the time being?

[miskatonicstudio]

OK, I think that using self.owner instead of parent solves the problem :) I've pushed the changes already in 646fc9b (the next commit contains some changes applied automatically by a new version of Godot).

I've also submitted a new version to the Asset Library:
https://godotengine.org/asset-library/asset/edit/6757

While my plugin is waiting for approval, you can use the code from this repository directly (the change is not a big one). Please let me know if this solves your problem, I will keep this issue open until then ;)

[miskatonicstudio]

Hi @TheConceptBoy ! Did you get a chance to test the new version? Does it fix the problem? ;)

[miskatonicstudio]

I am closing this issue. If you still experience problems, please reopen or create a new one ;)

And thank you again for reporting this! It fills me with pride that my tool makes someone's life easier, and every time an issue is spotted, it's a chance to make my code better ;)