Issues when booting when in VR

When I try and boot Eltie in VR and sometimes from the desktop I get a pop up stating "object reference not set to instance of an object" how do I fix this???
 
I have this problem too, I haven't found a fix. but for the most part when the launcher crashes the game is still able to start.
 
Locate your Elite Dangerous program folder.

Examine the file "EDLaunch.exe.config" using notepad.

Look for a section called "<startup>"
In there you will probably find two lines starting "<supportedRuntime version=.....". Probably the first one will continue "2.something", and the second "4.something...."
We need to swap those two lines... HOLD FIRE - READ ON, FIRST!!!!!

Take a copy of the "EDLaunch.exe.config" file as a backup (maybe as "EDLaunch.exe.config.backup") and be sure you are confident in your ability to swap that file back in place as the real EDLaunch.exe.config if this all goes wrong!!! - If this breaks you get to keep both pieces - copying the backup file back into place is your "get out of jail free" card.

Use notepad to edit the file EDLaunch.exe.config
Swap the two lines indicated above, so that the 4.something line is higher, and both lines are still between the <startup> and </startup> tags.

You should end up with something like:

.....
<startup>
<supportedRuntime version="v4.0"/>
<supportedRuntime version="v2.0.50727"/>
</startup>
......

Try the game to see if that helps - if so, leave it in place (and make a note how to do this again in future!) otherwise copy the backup copy of the file back into place...

The above steps sorted this issue out for me.
<edited for multiple typos!>
 
Last edited:
seemed to work McKeon, thanks! but the original problem was inconsistent so I don't want to say its 100% proven.

Yes, that is the fix...

 
let me run the game over the course of a month without issues and I'll say "it works perfect thanks." But as it stands how many systems has this been tested on with how many different setups? FD didn't write that code backward just to create issues.
 
Fair enough, you can doubt that it's the fix for that particular issue, but bear in mind that the solution came from FD support, not me fiddling around with stuff. :)

And after applying the fix (back in early January), I haven't had the issue since except when I reinstalled the launcher, which overwrote the edited file... :)
 
Yes, that is the fix...

I've replied to the VA crash thread with a what was for me the issue, and a workaround.
 
I've replied to the VA crash thread with a what was for me the issue, and a workaround.

Hopefully that will help the OP of that thread.

Obviously the two issues are separate (as I acknowledged in the post I linked to - the launcher issue is nothing to do with VA), it just happened that I had recently had the .NET (launcher) issue and it had been resolved by support, so was able to post the fix for that particular issue.
 
Back
Top Bottom