Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Umbra Eterna]

I just recently reinstalled Starsector and allocated 6GB of RAM to the game. The game can load fine to the main menu and I can click on new game, but clicking on Load Game causes a CTD.
I get this error in the starsector.log:

Spoiler

ERROR com.fs.starfarer.combat.CombatMain  - java.lang.NullPointerException
java.lang.NullPointerException
   at java.io.File.<init>(Unknown Source)
   at com.fs.starfarer.campaign.save.CampaignGameManager.return(Unknown Source)
   at com.fs.starfarer.campaign.save.LoadGameDialog.<init>(Unknown Source)
   at com.fs.starfarer.title.TitleScreenState.showLoadGameDialog(Unknown Source)
   at com.fs.starfarer.title.TitleScreenState.menuItemSelected(Unknown Source)
   at com.fs.starfarer.title.Object.actionPerformed(Unknown Source)
   at com.fs.starfarer.ui.h.o00000(Unknown Source)
   at com.fs.starfarer.ui.null.processInput(Unknown Source)
   at com.fs.starfarer.ui.U.o00000(Unknown Source)
   at com.fs.starfarer.BaseGameState.traverse(Unknown Source)
   at com.fs.state.AppDriver.begin(Unknown Source)
   at com.fs.starfarer.combat.CombatMain.main(Unknown Source)
   at com.fs.starfarer.StarfarerLauncher$2.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)

[close]

I have these mods installed:

Spoiler

Autosave
LazyLib
Leading Pip
ShaderLib
UpgradedRotaryWeapons
Version Checker

[close]

[Alex]

This is really odd. Can you clear out the contents of your save directory and try again?

Does it crash without the mods enabled?
Are you sure all of the mods have been updated for 0.7a?

[Umbra Eterna]

huh. So if I remove the saves from the saves folder, restart the game to check it fixes it. Re-adding the saves then starting Starsector up again allows me to load saved games.
All of the mods are updated to their latest versions and are compatible.
i did the removing and re-adding of the saves all with the mods enabled.

[Alex]

Interesting. Yeah, this looked like some kind of filesystem issue, judging from the stack trace. As in, something possibly got corrupted. Haven't seen anything quite like this before.