Quote:
Originally Posted by gap
does it all imply that GR2 files edited with previous versions of your editor are somehow broken or corrupted?  |
Depends. If there was any extendeddata that had a granny_struct_pointer that had a null value then yes. There is an easy way to tell if your file is broken and/or corrupted. Load the file in question with the app. After it's loaded and displayed press F1 to bring up the Sentinel window. Type:
getchainforsection 0 true
Scroll to the very top of the report. If it reports that it found broken chains then your file is broken and/or corrupt
Here is an example using the Augustus.GR2 file:
Augustus_Sentinel>
Augustus_Sentinel>getchainforsection 0 true
Linked list for section 0 (arttoolinfo)
this section's chain is complete
This example shows no broken chains
Quote:
Originally Posted by Targor Avelany
interesting...
It's awesome to hear that GR2EditorViewer is progressing so much! 
Nice job, TDW!
On the gap's post: yeah, it is possible that a lot of them will have to be re-done. I also wonder if the above is the cause for my texture problems. |
It's quite possible that your texture problems can be caused by a broken and/or corrupted GR2 file. Follow the procedure above to see if you have any broken chains.
Quote:
Originally Posted by Ekmek
Great to hear. I guess the Otto Bismarck GR2 is no different than Augustus?
|
Haven't loaded it yet.
Now the good news: Found where the pointers were getting corrupted when any data was written to the Augustus.GR2 file (my error). Due to the duplicate pointers and/or extendeddata that the Augustus.GR2 file contained I was using an incorrect offset for the exporterinfo extendeddata (when I create these new entries in the GR2 file). Changed it to use the correct offset and everything is perfect
The exporterinfo extendeddata was written to the file, file was saved to disk, Granny Viewer was able to open the new file with no problems and so was the app
I've included a little more error checking in this version so load/save times may increase a little. One major error checking during a save is the app will check for any broken chains and if any are found will inform you before saving the file to disk.
Have to do some more testing with this current version to ensure I didn't break anything major. There might be some bugs in this next version I release since I did a major overhaul to it from the bugs/errors found when trying to load the Augustus.GR2 file
