New to the forums? Click here to read the "How To" Guide.

Developer? Click here to go to the Developer Forums.

Elite Dangerous launch error in Rift S

CGH001CGH001 Posts: 38
Brain Burst
I've not played ED for a couple of months, although I did let Oculus do the January ED updates. Now, whenever I launch in VR or desktop mode using the Oculus launcher I get 'Unhandled exception: Object reference not set to an instance of an object' whenever the ED sign in screen opens.  It then closes the window and I can't play the game.

Has anyone else got this message please?

I can get it to run using the ED.exe in the games folder (although this seems to give some issues with Voiceattack and HCS  for some reason) and google reveals some debate re the .NET framework which doesn't seem to be an issue on my system.

Thanks.

Comments

  • RattyUKRattyUK Posts: 1,191
    Wintermute
    It is a .NET error (rearing its ugly head once again)
    Microsoft have a FixDotNet app that may fix it most of the time, remember a restart is needed after running it.

    The other solution that may help is to start in desktop mode and wait until the play button pops up, click and play, there is a good chance that, after the mandatory restart, that just starting it that way will cure the issue.
    HTH :)
    PC info: AMD Ryzen 7 2700X, MSI MPG X570 Edge, 16GB Tforce Pro Dark DDR4 3200, KFA2 RTX 2080 Super, Samsung 870 Pro M.2, 2x 240GB SSD, 3TB WD Green HDD & 4 TB Seagate Barracuda HDD, Antec Modular 750w PSU, custom watercooling loop. (Win 10 Pro & Opensuse Leap 15.1 Linux) 32" AOC 4K Monitor.
    Rift S
    Laptop: Aorus X5 V6-CF1 (I7-6820HK, GTX 1070, 2* 256GB M.2 NVME, 1TB 7200 HDD)
  • FrontierSupportFrontierSupport Posts: 123 Oculus Partner

    Hi there, 

    I am sorry to know that you have experienced this issue! This is often related to .NET I'm afraid. You should be able to circumvent the issue by running through the following:

    On C:\Program Files (x86)\Frontier\EDLaunch you should find a file named EDLaunch.exe.config.

    For Steam installs, it should be here: C:\Program Files (x86)\Steam\steamapps\common\Elite Dangerous
    ·         Firstly, make a backup of this file by copying it to another location, such as your desktop.

    ·         Open the EDLaunch.exe.config file with a text editor such as Notepad. You'll see something similar to:

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

    Switch the lines, so they look like this:

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


    Once you have done this, save the file and attempt to start up the launcher. If it's still not working you can just replace the file with the backup you created.

    If you continue to have problems, please submit a ticket so that we can investigate further.

    Thanks,

    CMDR Sputnik

  • RattyUKRattyUK Posts: 1,191
    Wintermute

    Hi there, 

    I am sorry to know that you have experienced this issue! This is often related to .NET I'm afraid. You should be able to circumvent the issue by running through the following:

    On C:\Program Files (x86)\Frontier\EDLaunch you should find a file named EDLaunch.exe.config.

    For Steam installs, it should be here: C:\Program Files (x86)\Steam\steamapps\common\Elite Dangerous
    ·         Firstly, make a backup of this file by copying it to another location, such as your desktop.

    ·         Open the EDLaunch.exe.config file with a text editor such as Notepad. You'll see something similar to:

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

    Switch the lines, so they look like this:

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


    Once you have done this, save the file and attempt to start up the launcher. If it's still not working you can just replace the file with the backup you created.

    If you continue to have problems, please submit a ticket so that we can investigate further.

    Thanks,

    CMDR Sputnik

    Awesome!
    I've copy/pasted your reply into a yellow note!  I don't see the issue often, but any knowledge given is great :D

    PC info: AMD Ryzen 7 2700X, MSI MPG X570 Edge, 16GB Tforce Pro Dark DDR4 3200, KFA2 RTX 2080 Super, Samsung 870 Pro M.2, 2x 240GB SSD, 3TB WD Green HDD & 4 TB Seagate Barracuda HDD, Antec Modular 750w PSU, custom watercooling loop. (Win 10 Pro & Opensuse Leap 15.1 Linux) 32" AOC 4K Monitor.
    Rift S
    Laptop: Aorus X5 V6-CF1 (I7-6820HK, GTX 1070, 2* 256GB M.2 NVME, 1TB 7200 HDD)
  • CGH001CGH001 Posts: 38
    Brain Burst
    RattyUK said:
    It is a .NET error (rearing its ugly head once again)
    Microsoft have a FixDotNet app that may fix it most of the time, remember a restart is needed after running it.

    The other solution that may help is to start in desktop mode and wait until the play button pops up, click and play, there is a good chance that, after the mandatory restart, that just starting it that way will cure the issue.
    HTH :)
    ... thanks for the info. It won't let me start in desktop mode unfortunately as it does the same thing :( 
  • CGH001CGH001 Posts: 38
    Brain Burst

    Hi there, 

    I am sorry to know that you have experienced this issue! This is often related to .NET I'm afraid. You should be able to circumvent the issue by running through the following:

    On C:\Program Files (x86)\Frontier\EDLaunch you should find a file named EDLaunch.exe.config.

    For Steam installs, it should be here: C:\Program Files (x86)\Steam\steamapps\common\Elite Dangerous
    ·         Firstly, make a backup of this file by copying it to another location, such as your desktop.

    ·         Open the EDLaunch.exe.config file with a text editor such as Notepad. You'll see something similar to:

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

    Switch the lines, so they look like this:

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


    Once you have done this, save the file and attempt to start up the launcher. If it's still not working you can just replace the file with the backup you created.

    If you continue to have problems, please submit a ticket so that we can investigate further.

    Thanks,

    CMDR Sputnik

    Yay!! This has fixed it :) Many thanks for your help.
  • ChrisHaleChrisHale Posts: 3
    NerveGear
    I just wanted to report that this error cropped up for me today and I'm using my Oculus Rift CV1. The recommended solution worked for me too. I had tried the other recommended steps in the Elite support forum but only this one worked.
  • MowTinMowTin Posts: 1,943 Valuable Player
    edited April 6
    Wow, Frontier support read this forum? They have their own forum. It's maybe one of the best forums I've been on. Just lots of fellow nerds on there. It takes a certain type of person to obsessively play a space sim. 

    I'm waiting for carriers to get back into ED. 
    i7 9700k 2080ti   CV1, Rift-S, Index
  • SteelArgusSteelArgus Posts: 3
    NerveGear
    I have tried this fix with the EDLaunch.exe.config. and it only made it worse the launcher and the game both will not run but if I revert it back the launcher still crashes but the game itself will continue to play, now if I launch the game in desktop mode the issue does not happen so its only in VR I get the fore mentioned error message
  • FrontierSupportFrontierSupport Posts: 123 Oculus Partner
    Hi there Steel!

    Hmm, it may be time for you to open a ticket with us. From there, we hopefully should be able to get you up and running.

    You can do so here:

    https://support.frontier.co.uk/topic.php

    Please open a ticket, and hopefully we can get you playing!

    - CMDR Zenit
  • waltor64waltor64 Posts: 1
    NerveGear

    Hi there, 

    I am sorry to know that you have experienced this issue! This is often related to .NET I'm afraid. You should be able to circumvent the issue by running through the following:

    On C:\Program Files (x86)\Frontier\EDLaunch you should find a file named EDLaunch.exe.config.

    For Steam installs, it should be here: C:\Program Files (x86)\Steam\steamapps\common\Elite Dangerous
    ·         Firstly, make a backup of this file by copying it to another location, such as your desktop.

    ·         Open the EDLaunch.exe.config file with a text editor such as Notepad. You'll see something similar to:

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

    Switch the lines, so they look like this:

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


    Once you have done this, save the file and attempt to start up the launcher. If it's still not working you can just replace the file with the backup you created.

    If you continue to have problems, please submit a ticket so that we can investigate further.

    Thanks,

    CMDR Sputnik

    Oh my God! I have been trying to resolve this issue since I started Playing ED in December. Everytime I have had to back into the desktop and clear the errors crashing the launcher but keeping the game playable. When I wanted to shift from regular play to the FC Beta I had to fool around with it for hours to get it working without the launcher. Now the launcher works perfectly and I can switch back and forth at will. Can I buy you a beer or something? I have tried every suggestion I have found but yours not only worked it was written in way that could be followed. THANK YOU!!!
  • RattyUKRattyUK Posts: 1,191
    Wintermute
    waltor64 said:

    Hi there, 

    I am sorry to know that you have experienced this issue! This is often related to .NET I'm afraid. You should be able to circumvent the issue by running through the following:

    On C:\Program Files (x86)\Frontier\EDLaunch you should find a file named EDLaunch.exe.config.

    For Steam installs, it should be here: C:\Program Files (x86)\Steam\steamapps\common\Elite Dangerous
    ·         Firstly, make a backup of this file by copying it to another location, such as your desktop.

    ·         Open the EDLaunch.exe.config file with a text editor such as Notepad. You'll see something similar to:

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

    Switch the lines, so they look like this:

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


    Once you have done this, save the file and attempt to start up the launcher. If it's still not working you can just replace the file with the backup you created.

    If you continue to have problems, please submit a ticket so that we can investigate further.

    Thanks,

    CMDR Sputnik

    Oh my God! I have been trying to resolve this issue since I started Playing ED in December. Everytime I have had to back into the desktop and clear the errors crashing the launcher but keeping the game playable. When I wanted to shift from regular play to the FC Beta I had to fool around with it for hours to get it working without the launcher. Now the launcher works perfectly and I can switch back and forth at will. Can I buy you a beer or something? I have tried every suggestion I have found but yours not only worked it was written in way that could be followed. THANK YOU!!!
    Nice when something so simple works so well, isn't it?
    I'd usually do a .net repair and reboot to get around it...  Then this post happened - end of issues.
    o7 CMDR :)
    PC info: AMD Ryzen 7 2700X, MSI MPG X570 Edge, 16GB Tforce Pro Dark DDR4 3200, KFA2 RTX 2080 Super, Samsung 870 Pro M.2, 2x 240GB SSD, 3TB WD Green HDD & 4 TB Seagate Barracuda HDD, Antec Modular 750w PSU, custom watercooling loop. (Win 10 Pro & Opensuse Leap 15.1 Linux) 32" AOC 4K Monitor.
    Rift S
    Laptop: Aorus X5 V6-CF1 (I7-6820HK, GTX 1070, 2* 256GB M.2 NVME, 1TB 7200 HDD)
  • SergioBR1SergioBR1 Posts: 1
    NerveGear
    FrontierSupport said:

    Hi there, 

    I am sorry to know that you have experienced this issue! This is often related to .NET I'm afraid. You should be able to circumvent the issue by running through the following:

    On C:\Program Files (x86)\Frontier\EDLaunch you should find a file named EDLaunch.exe.config.

    For Steam installs, it should be here: C:\Program Files (x86)\Steam\steamapps\common\Elite Dangerous
    ·         Firstly, make a backup of this file by copying it to another location, such as your desktop.

    ·         Open the EDLaunch.exe.config file with a text editor such as Notepad. You'll see something similar to:

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

    Switch the lines, so they look like this:

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


    Once you have done this, save the file and attempt to start up the launcher. If it's still not working you can just replace the file with the backup you created.

    If you continue to have problems, please submit a ticket so that we can investigate further.

    Thanks,

    CMDR Sputnik

    I would like to thank you very much CMDR SPUTNIK, i have been looking for a solution on general sites for months and today i found here, works fine to me.
  • t0mmy0livert0mmy0liver Posts: 1
    NerveGear
    Hi, I'm having the Unhandled exception: Object reference not set to an instance of an object error when trying to play in VR or not (Rift S). I've tried the edit on the EDLaunch and it didn't work I just got an error and couldn't play the game at all and I couldn't get the .NET to update/ fix it's self.
  • FrontierSupportFrontierSupport Posts: 123 Oculus Partner
Sign In or Register to comment.