For some reason I don’t remember seeing the other thread. Strange.
Three were some changes to how things were cloned at some point… I think near one of the last alphas(?). It would be interesting to know if it stopped working at that point or if it was related to some other change.
A lot of times when I notice something breaks and no one seems to know why, I end up having to step through the changes, building JME locally, until I find which commit broke things. Painful to be sure… but it often points to the issue right away. There were enough alphas that maybe you could more easily at least narrow it down that way.
Note: it’s also completely fair to put an issue in the bug tracker if you don’t get a response in a reasonable time… “reasonable” being a judgment call but certainly after a month of nothing is definitely a reasonable amount of time.
If you’ve got more than a few commits between HEAD and a known good build, bisect it.
If there’s a simple scriptable way to test for the bug, you just let the system do its thing. If you need to manually test, git takes care of tracking where you are at in the test process. 1024 commits should take only 10 tests.
It would be good to confirm but my read on it is not the above.
From the explanation so far, my interpretation was that saving a j3o with an attachment node in it never works. But if you load a j3o and then manually grab the attachment node then it works.
The SDK isn’t doing anything special that the code wouldn’t be… neither is the blender loader in this case.
But it’s quite likely that something during load is not getting ‘fixed up’ like it used to and leaving these attachment nodes dangling. The new cloning would be the most obvious potential culprit. Someone could short-circuit a lot of testing just be trying JME before that commit.
This was the commit that started it all:
…though that was back even before alpha4 so there may have been other changes much later that could affect this also I guess. I haven’t really looked at the evolution of attachment nodes at all.
I have what is hopefully a fix committed to the v3.1 branch and to master… the v3.1 commit is here:
I have confirmed that at least in my own testing, cloned animations work at least as well as they did before. In theory, attachment nodes should now also be fixed. Well, at least they have a reasonable chance. There is no way they’d have worked before this change.