Hi, In the 0.7 update, my mods got screwy. Some of the meshs are offset. The jbeams are in the correct positions, and i believe the meshs that got offset are on parts using nodeoffset. The mesh is also in the correct place in the .dae what i have tried re applying loc, rot, scale in blender moving with the flexbody position factor({"pos":{"x":0, "y":0, "z":0}, "rot":{"x":0, "y":0, "z":0}, "scale":{"x":1, "y":1, "z":1}}],) EDIT FIXED thanks to @Dummiesman i had to put {"ignoreNodeOffset":true} at the beginning of the flexbody section and {"ignoreNodeOffset":false} at the end of the flexbody section.
What is your setup? In v0.7 nodeOffset was fixed so that it applies to all child parts, including meshes and jbeams. This is almost universally desirable as far as I can see... Previously it was broken so that in certain circumstances only the nodes/beams moved and not the meshes. In other words they should currently be moving together according to nodeOffset. I know that dummiesman has a special application where he keeps the meshes in place and moves the jbeam around, but it doesn't sound like that's what you are trying to do here.
Well, i node offset the jbeam, but the mesh was already in the correct place. That creates problems i guess. Solved now though(in first post)
I saw that in the first post. Just curious why you need to move the jbeam with nodeOffset and not the mesh. Couldn't you just put the nodes/beams in the correct position to start out with and skip nodeOffset entirely?
In the case of the front radiator support, the jbeam is copied from the moonhawk, so i used node offset to place it.
I understand. Hopefully this won't sound pedantic, but you you know that the NodeBEAM editor can let you apply the same offset permanently for the copy you made, right?
I only recently started using it myself. It has many limitations and shortcomings. ... but using it is way better than not using it. It can translate, rotate, and scale selections of nodes arbitrary amounts.
