Menu

#26 Crashing when opening saves

None
closed
nobody
Bug (2)
5
2023-02-12
2019-05-09
No

Hey guys, having an issue with opening my save files on my PC from my PS4 displaying the below error:
System.IO.FileFormatException: Input file is not a WSG (platform is Not WSG).
at WillowTree.WillowSaveGame.LoadWSG(String inputFile)
at WillowTree.WillowTreeMain.Open_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at WillowTree.Program.Main()

Any ideas or help?

Thanks :D

Discussion

  • matt911

    matt911 - 2019-05-09

    Are you sure you are trying to open a Borderlands savegame file from the Bordrlands 1 game and not from Borderlands 2 or some other Borderlands game?

    Its possible that there is a different format for the files on the PS4 than on other platforms. The error that is being thrown in your crash message is that the file is "Not a WSG". The way it figures out if a savegame is a Borderlands savegame file is it checks the first three characters of the save file. They should be the characters WSG in a Borderlands 1 savegame on PC or PS3. On the Xbox 360 if the savegame is still inside its Xbox package the characters would be CON, or if it has been extracted from the Xbox package it would also be WSG. Your savegame doesn't start with the letters WSG so WillowTree# does not understand its format.

     
  • Callum Macdonald

    yeah I'm using a ps4 borderlands goty edition save file

     
  • matt911

    matt911 - 2019-05-21

    There exists third party software for the PC to manipulate the signed and encrypted PS4 package files to allow you to extract the data , change the data inside, and re-sign and re-encrypt the PS4 package files. It is called Save Wizard for PS4 Max I think. It is a commercial program that costs $60. I don't own it and I haven't ever used it, so I can't provide you any detailed instructions on its use and I can't tell you for sure whether it will allow you to edit PS4 savegames with WT# or not.

    The same sort of software exists for Xbox 360, but on that platform the programs that can do it are available for free (utilities such as Modio, Horizon, and XTAF Explorer 360 ). I have used those and I can verify that they work to allow you to extract Borderlands classic and enhanced savegame files that are compatible with WillowTree# and they can re-inject the modified save files back into the packages and re-sign them after you have edited it to authenticate the package file to allow it to work on your Xbox 360. WillowTree# actually has code in it to extract from inside Xbox 360 package files and to re-sign them but it doesn't have code to copy the files from the special Xbox 360 formatted USB flash drives, so you still need a tool to do that.

    Borderlands on PS3 did not have any digital signature required to authenticate and verify that a save file had not been modified. It only required a profile for your PS3 to go along with it, so no special software was required to extract the save file.

    I presume that Xbox One and any other modern console that Borderlands is available on would require a similar savegame extraction and re-signing tool. If you don't have such a tool then you probably can't edit your savegames on any current generation console.

    IF you can edit PS4 save files on the PC you would have to extract the data from the save file with Save Wizard for PS4 Max (or some other similar tool), then open that file in WillowTree#. You would then edit the file then use Save Wizardto put the modified data back into the package file on the USB drive and re-sign it so it will be authenticated for your own console. Unfortunately I have no way to test this myself because I don't own Save Wizrd, I don't own a PS4, and I don't own Borderlands Enhanced for the PS4 so unless someone else who owns all three attempts it and reports back I can neither confirm nor deny whether it is possible to edit PS4 savegames with WT#.

    If you attempt to directly open one of the the files you find on your USB drive without using some kind of tool like Save Max PS4, then that is not the save file that WT# needs. It does contain the save file, but its compressed or encrypted in there in some fashion that WT# has no way to use. It needs to be converted to its unencrypted, uncompressed form for WT# to use it. In that case WT will crash and it will tell you that the file is "Not a WSG", since it doesn't begin with three bytes that correspond to the letters "WSG" as a non-ecrypted and non-compressed save file should.

     

    Last edit: matt911 2019-05-26
  • matt911

    matt911 - 2023-02-12
    • status: open --> closed
     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.