Crashing when leaving hyperspace

kiliki

K
My game appears to crash when entering certain areas (stations, asteroid belts, etc). It doesn't apply to every station, but it happens consistently at those where it does crash.
This only happens in non-legacy modes, in both solo and open play. Combat training works without a hitch.

I've logged a ticket but given the 5 day response time I'm hoping someone here can help.

Specs:
  • i9-9900k
  • RTX 2080 Super
  • 32GB RAM
  • Windows 10 Pro
  • Running through Steam
I've tried the following:
  • Verify integrity (steam)
  • Clean install graphics drivers
  • Restart PC
  • Disconnect HOTAS
  • Downgrade graphics to low
  • Kill all background processes
  • Delete GpuWorkTable.xml
Additional info:
  • Haven't played since just before Odyssey launched
  • Original crash occurred in Gliese 868 10 A Ring (last logout location)
  • Used "unstuck" tool to get out of the asteroid belt, which stopped it crashing
  • Docking worked fine in Braun Station (Coriolis, Gliese 868)
  • Jumped to Deneb Algedi
  • Dropping out next to Burke Port caused another crash (Coriolis, Deneb Algedi)
  • Logging in after this point failed until using the unstuck tool
 

STRONTIUM DOG

STRONTIUM DOG
the fact that it occurs in some areas not others may just point to the notoriously bad servers atm
so bear that in mind other threads about no mission boards either ect in some places not others
 

BadBogey

BadBogey
kiliki said:
My game appears to crash when entering certain areas (stations, asteroid belts, etc). It doesn't apply to every station, but it happens consistently at those where it does crash.
This only happens in non-legacy modes, in both solo and open play. Combat training works without a hitch.

I've logged a ticket but given the 5 day response time I'm hoping someone here can help.

Specs:
  • i9-9900k
  • RTX 2080 Super
  • 32GB RAM
  • Windows 10 Pro
  • Running through Steam
I've tried the following:
  • Verify integrity (steam)
  • Clean install graphics drivers
  • Restart PC
  • Disconnect HOTAS
  • Downgrade graphics to low
  • Kill all background processes
  • Delete GpuWorkTable.xml
Additional info:
  • Haven't played since just before Odyssey launched
  • Original crash occurred in Gliese 868 10 A Ring (last logout location)
  • Used "unstuck" tool to get out of the asteroid belt, which stopped it crashing
  • Docking worked fine in Braun Station (Coriolis, Gliese 868)
  • Jumped to Deneb Algedi
  • Dropping out next to Burke Port caused another crash (Coriolis, Deneb Algedi)
  • Logging in after this point failed until using the unstuck tool
Click to expand...
How you getting on, any better? I have similar issues.
 

kiliki

K
The support team responded and had me do a clean install (removing appdata folders etc), which has solved the problem for me. Their instructions were as follows:
When we have location specific issues like you are, usually it's an installation issue of some kind. So to build on that, we want a clean reinstall of the game itself.

  • First uninstall the launcher from your computer using 'Programs and Features' (or Steam's built-in uninstaller).
  • Remove (delete) any left over files from where the launcher was installed. (Please be aware that this will mean you may have to download all game files again)
  • Find your game folder, you can find this here- Delete it
  • If "C:\Users\%USERNAME%\AppData\Local\Frontier_Developments" exists - Delete it
  • If "C:\Users\%USERNAME%\AppData\Local\Frontier Developments" exists - Rename this folder to back up your user settings

Once completed, please restart your PC to clean up and leftover files. You can now re-install Elite Dangerous as normal and hopefully you will find this issue no longer appears.
Click to expand...
After taking these steps I was able to copy over my Bindings folder to keep my binds, but trying to copy the entire Options folder caused the crash to come back, probably something related to old options. Hopefully this works for you too.
 

Esteban

E
I'd say the fact that you have (apparently, I know it's one datapoint) localized it to something in/about the Options folder is perhaps quite useful troubleshooting information. If it's something there that can avoid a full re-install, I'd say that would be a very appealing alternative.

Glad to hear that you appear to be back in business.
 
You must log in or register to reply here.
Back
Top Bottom