Unhandled exception: (solved)

[One Eye Jack]

So all you computer geniuses help me out.

I am getting the following error when I start the game.

Unhandled exception: Object reference not set to an instance of an object.

I have already verified my game files.

edit: The game goes ahead and runs after this. It seems to only effect the launcher.

[kwm57]

I just started to get that also.
Thinking it might be associated with launching ED from Oculus home considering I just got a rift s and never used the Oculus software before.
Been using Pimax and ALVR with steam for years and have never seen that message.

[Crimson Echo]

Specs, OS, VR, etc?

[Arc]

Best to fill a bug report or support ticket.

[Laurreth]

Probably a bad or old .Net installation on an ancient Windows version.

[One Eye Jack]

Originally posted by CMDR Crimson Echo:

Specs, OS, VR, etc?

High end computer. Gforce 1080, VR yes, Windows 10.

[One Eye Jack]

Originally posted by Arc:

Best to fill a bug report or support ticket.

Did that. Waiting on an answer.

[One Eye Jack]

Originally posted by Shadowdancer:

Probably a bad or old .Net installation on an ancient Windows version.

No..... recently reformatted Windows 10 on a high end machine. This just started after my game crashed.

[Crimson Echo]

Do you have the latest standalone Nvidia drivers installed? Have you tried starting with VR off and/or disconnected?

If you have the bandwidth a reinstall of the game may be the simplest solution. (it is possible some config file got corrupted that is not located in the game directory, but the user app data. )

[One Eye Jack]

Originally posted by CMDR Crimson Echo:

Do you have the latest standalone Nvidia drivers installed? Have you tried starting with VR off and/or disconnected?

If you have the bandwidth a reinstall of the game may be the simplest solution. (it is possible some config file got corrupted that is not located in the game directory, but the user app data. )

I updated my video drivers and my Oculus driver first off and that didn't help. I just tried your suggestion of starting without VR. But that didn't work either.

I think I will wait until I get a response from Frontier before I try re installing the game. But I expect that is what Frontier is going to tell me as well.

Thanks for the suggestions. I will update when it's fixed in case others are having a similar problem.

[Laurreth]

Tried this? https://support.frontier.co.uk/kb/faq.php?id=64

It's a .Net error, so I doubt it's anything to do with the game proper, but the launcher somehow not harmonising with your system.

Do you get the usual news and ads in the launcher, or is it White Window Syndrome?

[One Eye Jack]

Originally posted by Shadowdancer:

Tried this? https://support.frontier.co.uk/kb/faq.php?id=64

It's a .Net error, so I doubt it's anything to do with the game proper, but the launcher somehow not harmonising with your system.

Do you get the usual news and ads in the launcher, or is it White Window Syndrome?

I just get a window with the error code..... then I get another window saying the launcher has stopped responding and needs to be closed...... so unfortunately I can't do what is suggested in the link you gave me. The launcher won't stay open long enough to do anything.

The odd thing is that the game goes ahead and launches even though the launcher has crashed. And everything seems to play normally. Seems like the launcher crash would not allow the game to start but that isn't the case.

[Laurreth]

Could you check in the installation location if you have something in the "Products" folder that's obviously the single-player stuff and delete or move that? (Don't remember the naming scheme, but it wasn't rocket surgery to see what's what…)

Alternatively, you should have a "pre-Steam" version, at least you've been around long enough IIRC, so you should be able to just run the launcher directly and bypass Steam Magic going straight into the game.

[One Eye Jack]

Originally posted by Shadowdancer:

Could you check in the installation location if you have something in the "Products" folder that's obviously the single-player stuff and delete or move that? (Don't remember the naming scheme, but it wasn't rocket surgery to see what's what…)

Alternatively, you should have a "pre-Steam" version, at least you've been around long enough IIRC, so you should be able to just run the launcher directly and bypass Steam Magic going straight into the game.

OK I did find a combat tutorial demo in the products folder and I deleted it but that didn't help. And I bought the game when it came out on Steam so no pre Steam installation. I also tried launching directly from the Oculus program as well as launching from the launcher directly rather than from the Steam app. I still get the same issue.

Thanks for the suggestions in any case...... I am thinking a reinstall of the game is what it's going to take.....

[One Eye Jack]

Update:

Frontier says this popped up with the latest Oculus runtime. They are in touch with Oculus trying to resolve the problem.

I guess I need to wait.

[Malcolm Reynolds]

Same problem here. It started yesterday, though a couple times I got past it somehow. Today though it won't let me open ED at all.