Quote:
Originally Posted by gap
On a side note, while working with GR2 Editor I have met the following bugs: - starting with v 1_1_442_1, your editor resets the parent bones of all the bones to -1 (world);
- do the following:
- open a GR2 file;
- edit the file;
- click on Window's close button (top right 'x' icon)
- click on the 'cancel' button
the viewport stops working. If you close the model currently in memory (menu 'file', close 'all', and try opening a gr2 file again, you will get a "reference to an object not set to an object instance" exception. Reproduced this bug many times with different versions of your editor
|
v1.1.447.1 released. See post #1
This version fixes the bugs reported above
As far as the parent indexes being reset to -1 in v1.1.446.1 that was throwing me for a loop for the past day. I changed the model's position data to 0 for X and Z thus moving the coastal defense's meshes to the origin. I would save the file and then view it in Granny Viewer - all was well. I would view it in Goblin - only the barrel would show! Couldn't figure out what the hell was going on. Then I finally remembered an option I had in the app to render the bones as a hierarchy. I set that option on and loaded my new coastal defenses loop GR2 file and noticed that all the bones' parents were world. I loaded up the original coastal defense GR2 file and it had the proper hierarchy. It was then that I investigated my app to see why the bones were all getting their parent set to World. I found the error and corrected it (error was introduced when I used multiple threads to read in all the bones). Now looking at my updated coastal defense loop GR2 file it's correct (and renders correctly in Goblin):
