You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a problem with the latest titledumper 4.
If you do not use a full path for the game folder, it corrupts the \code folder and you get the dreaded 160-2203 error when running in loadiine.
eg. "titledumper /vol ./gameName" works, but "titledumper /vol gameName" corrupts.
meta, save, content, aoc and the fake .xmls are all generated correctly with either format.
All other files in \code are corrupt when you do not use "./"
The corruption follows a pattern. The 8 bytes at xxxFF0:07 - 0F are all bad.
eg 0FF0:07-0F; 1FF0:07-0F; 2FF0:07-0F etc
Sometimes a few extra bytes may be correct. eg corruption starts at 0FF0:0B-0F; 1FF0:0B-0F; 2FF0:0B-0F
The text was updated successfully, but these errors were encountered:
titledumper can be compiled through CodeBlocks. Get the version with MinGW, open titledumper/titledumper.cbp with it and click build. I tried building it with MinGW before, but it was easier with the IDE.
There is a problem with the latest titledumper 4.
If you do not use a full path for the game folder, it corrupts the \code folder and you get the dreaded 160-2203 error when running in loadiine.
eg. "titledumper /vol ./gameName" works, but "titledumper /vol gameName" corrupts.
meta, save, content, aoc and the fake .xmls are all generated correctly with either format.
All other files in \code are corrupt when you do not use "./"
The corruption follows a pattern. The 8 bytes at xxxFF0:07 - 0F are all bad.
eg 0FF0:07-0F; 1FF0:07-0F; 2FF0:07-0F etc
Sometimes a few extra bytes may be correct. eg corruption starts at 0FF0:0B-0F; 1FF0:0B-0F; 2FF0:0B-0F
The text was updated successfully, but these errors were encountered: