Quote:
Originally Posted by gap
So correct me if I misunderstood you: you simply changed bone position data; you did not edit mesh position in Blender. Is that correct?
|
I did, but that's not when this happens. After I edit mesh position in Blender and import the mesh back, everything is ok and both Goblin and GR2 editor show the same result. However, when I change bone position (regardless if mesh was earlier edited with Blender or not), this happens:
On first image, my current Heavy Bomber's rudder: bone position was earlier moved to have rudder's rotation center in right place.
On second image, the same plane after editing rudder bone position again.
I did not export/import anything between these images - just edited bone position data. In GR2 Editor this didn't result in moving the mesh, but in Goblin mesh itself has moved with the bone.
So, it's not as I initially thought that Goblin doesn't recognize moving bones, it just moves meshes along with them (except, apparently, in opposite direction?)