Fractal Softworks Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Starsector 0.97a is out! (02/02/24); New blog post: Simulator Enhancements (03/13/24)

Author Topic: Fatal Error after defeating Expedition Fleet  (Read 400 times)

Calica

  • Ensign
  • *
  • Posts: 4
    • View Profile
Fatal Error after defeating Expedition Fleet
« on: January 11, 2020, 09:57:01 PM »

Hello there!

So, this has happened twice now, when a Persean League Fleet retreated from the Battlefield at first and then decided to take another swing at the Battlestation. To make it clear, the fleet retreated during the battle but attacked again without disengaging (aka after the battle i get the message that they turning for another fight, only options are 1. Comms 2. Engage them again). Re-engaging triggers a CTD.

6584836 [Thread-4] ERROR com.fs.starfarer.combat.CombatMain  - java.lang.NullPointerException
java.lang.NullPointerException
   at com.fs.starfarer.combat.CombatFleetManager$O0.getLocation(Unknown Source)
   at com.fs.starfarer.combat.CombatFleetManager.advanceSeenEnemies(Unknown Source)
   at com.fs.starfarer.combat.CombatFleetManager.advance(Unknown Source)
   at com.fs.starfarer.combat.CombatEngine.advanceInner(Unknown Source)
   at com.fs.starfarer.combat.CombatEngine.advance(Unknown Source)
   at com.fs.starfarer.combat.CombatState.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$1.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)

edit: "Fixed it" by winning decisivly and making them run.
« Last Edit: January 11, 2020, 10:19:14 PM by Calica »
Logged

Alex

  • Administrator
  • Admiral
  • *****
  • Posts: 23987
    • View Profile
Re: Fatal Error after defeating Expedition Fleet
« Reply #1 on: January 11, 2020, 10:27:30 PM »

Hi - sorry about that, and thank you for the report! This is fighter-related, should be fairly rare (thankfully!), and fixed for the next release.
Logged