I'm tying to convert my saved file from my PC to the 360 format so I can import it into Borderlands 2 and unlock whatever it is I unlock, but it keeps telling me "This save game contains raw data that could not be parsed so it cannot be exported to a different machine byte order." When I try this, I open my save game file like normal and then click the willowtree icon in the top left corner, then change save format, then click 360. The game isn't open, Steam isn't even open. Any thoughts or is it just a bug in the system?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Its not a bug, but rather a design safeguard to make sure that WT# doesn't convert a savegame unless it understands all the bytes in it. The bytes have to be rewritten in a different byte order to switch from PC to Xbox 360, but if WT# doesn't know the exact size and type of each piece of data it can't do that. It would inevitably end up scrambling the data into the wrong order.
In this case the problem is that the PC-Steam version of Borderlands writes an additional data section into the savegame that is not present on PC-DVD, Xbox 360, or PS3 versions. WT# doesn't have the faintest idea what the data section contains so it keeps a hands-off approach and just preserves the data exactly as it is. It can be preserved without knowing the byte order, but it can't be converted. WT# 2.2.1.102 has no way to remove the raw data so that means it can never convert a Steam PC savegame to Xbox 360 or PS3.
I never knew about this Steam raw data problem preventing any Steam saves from being converted until recently because I used the PC DVD version which doesn't have it. Once someone reported the problem to me I added a feature to the experimental revision to ask you if you want to discard the raw data so that people can convert their Steam PC savegames to Xbox 360 and PS3 with it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2012-09-21
Alright matt911, thank you for explaining that to me. Tried converting it after I downloaded 2.2.263 version, now it wants me to copy a saved file from my 360 so it can associate the converted file to my gamer tag. Last question I promise; do I need an original Borderlands file or just any sort of saved game file from any game as long as it is saved under my gamer tag?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It needs to be an Xbox 360 CON type package file, but it doesn't have to be a Borderlands savegame. Probably many or most other games also use the CON file format for save data. If you open an appropriate file with a text editor the first three letters of the file should say CON (the rest will be scrambled junk).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm tying to convert my saved file from my PC to the 360 format so I can import it into Borderlands 2 and unlock whatever it is I unlock, but it keeps telling me "This save game contains raw data that could not be parsed so it cannot be exported to a different machine byte order." When I try this, I open my save game file like normal and then click the willowtree icon in the top left corner, then change save format, then click 360. The game isn't open, Steam isn't even open. Any thoughts or is it just a bug in the system?
Try the lastest WillowTree version:
WillowTree#-2.2.263-experimental.zip
https://sourceforge.net/projects/willowtree/files/experimental/
Its not a bug, but rather a design safeguard to make sure that WT# doesn't convert a savegame unless it understands all the bytes in it. The bytes have to be rewritten in a different byte order to switch from PC to Xbox 360, but if WT# doesn't know the exact size and type of each piece of data it can't do that. It would inevitably end up scrambling the data into the wrong order.
In this case the problem is that the PC-Steam version of Borderlands writes an additional data section into the savegame that is not present on PC-DVD, Xbox 360, or PS3 versions. WT# doesn't have the faintest idea what the data section contains so it keeps a hands-off approach and just preserves the data exactly as it is. It can be preserved without knowing the byte order, but it can't be converted. WT# 2.2.1.102 has no way to remove the raw data so that means it can never convert a Steam PC savegame to Xbox 360 or PS3.
I never knew about this Steam raw data problem preventing any Steam saves from being converted until recently because I used the PC DVD version which doesn't have it. Once someone reported the problem to me I added a feature to the experimental revision to ask you if you want to discard the raw data so that people can convert their Steam PC savegames to Xbox 360 and PS3 with it.
Alright matt911, thank you for explaining that to me. Tried converting it after I downloaded 2.2.263 version, now it wants me to copy a saved file from my 360 so it can associate the converted file to my gamer tag. Last question I promise; do I need an original Borderlands file or just any sort of saved game file from any game as long as it is saved under my gamer tag?
It needs to be an Xbox 360 CON type package file, but it doesn't have to be a Borderlands savegame. Probably many or most other games also use the CON file format for save data. If you open an appropriate file with a text editor the first three letters of the file should say CON (the rest will be scrambled junk).