Error on X-Plane Startup after FlyInside Install.

[rsantoro37]

Hi Guys,

Trying to get X-Plane and FlyInside installed on my machine to run via Rift. I have successfully installed X-Plane and am able to run that, however once I installed FlyInside I started to receive the attached error and X-Plane no longer works on its own. Any help at getting this resolved would be awesome!

X-Plane 11.0.2.2 - Demo
FlyInside - 1.81

Cheers,
Bob

[Stevil]

What's the error message in xplane you get?

[rsantoro37]

Hi Stevil, I have attached the error I am receiving. This error occurs when I launch via the FlyInside executable as well as the XPlane executable.

I tested XPlane out standalone successfully prior to installing FlyInside. I installed FlyInside and this started appearing and I have not been able to launch since. Have tested with Oculus connected as well as not connected.

**Also noticed, i am currently running Oculus runtime 1.15... and suggested in 1.10. Could this be the source of the issue?

[Stevil]

Hi Stevil, I have attached the error I am receiving. This error occurs when I launch via the FlyInside executable as well as the XPlane executable.

I tested XPlane out standalone successfully prior to installing FlyInside. I installed FlyInside and this started appearing and I have not been able to launch since. Have tested with Oculus connected as well as not connected.

**Also noticed, i am currently running Oculus runtime 1.15... and suggested in 1.10. Could this be the source of the issue?

Can you please edit your signature for more details on your rig?
Why did you cut your logfile to just some bytes? We need the full one!

[admin]

Hi Bob,

First off, the easy part: You can get X-Plane 11 working normally again by going into your X-Plane 11 folder and renaming "opengl32.dll" to "opengl32_disabled.dll". This will turn off FlyInside entirely

For the second issue, Stevil's correct. We'll need a full copy of the logfile to make any headway. If you're running into any issues uploading it, or don't want to post it on a public forum, you can send it to dan@flyinside-fsx.com

Thanks,
Dan

[rsantoro37]

Hi Stevil/Dan, The error log I uploaded is the full log I did not do any editing. I know it does not provide very much info as to what is occurring, is there any way to enable debug/trace level logs? As for the rig I can provide specifics, however it is a machine used for VR application development so I do not believe that is the issue other then the older Oculus runtime.

[Stevil]

Hi Stevil/Dan, The error log I uploaded is the full log I did not do any editing. I know it does not provide very much info as to what is occurring, is there any way to enable debug/trace level logs? As for the rig I can provide specifics, however it is a machine used for VR application development so I do not believe that is the issue other then the older Oculus runtime.

Let me be a bit sarcastic(no offense here!):
If you know that Oculus runtime is the only issue then why do you ask here for help?

Seriously: Please make a signature where your rig, software etc is stated, this will help us a lot. I am wondering why the log is that short...can you please upload another one if the error happens again?

Thanks and best regards
Stephan

[rsantoro37]

Should of been more specific on the Oculus runtime. I am currently running runtime 10.5, spec for fly inside says runtime 10.1 is required. Does fly inside only work with an older version of oculus runtime is the question or is it compatible with the latest runtime.

As for the rig:
CPU - Core I7 7820HQ
GPU - NVIDIA Quadro P5000 Graphics Card ‑ 16 GB GDDR5X ‑ 256‑bit
RAM - 16gb
OS - Windows 10 x64

I have again uploaded the error log. Does not provide much information as it is only 10 lines long. All my error logs are around this length with similar information.

[Stevil]

Should of been more specific on the Oculus runtime. I am currently running runtime 10.5, spec for fly inside says runtime 10.1 is required. Does fly inside only work with an older version of oculus runtime is the question or is it compatible with the latest runtime.

As for the rig:
CPU - Core I7 7820HQ
GPU - NVIDIA Quadro P5000 Graphics Card ‑ 16 GB GDDR5X ‑ 256‑bit
RAM - 16gb
OS - Windows 10 x64

I have again uploaded the error log. Does not provide much information as it is only 10 lines long. All my error logs are around this length with similar information.

I think this is something only the devs can answer. I will get an answer from Dan for you.

Update: Dan said to me that required OR runtime is 10.1 or higher. So 10.5 shouldn't be a problem!

BR
Stephan

[admin]

Hi Bob,

To confirm, Oculus Runtime isn't the issue. The message should really say 10.1 or later, we support the most recent Oculus runtime no problem

Also, at a third glance, your logs are fine. We've just never seen a crash this early in the startup process before, so it looked like they were missing a lot of data. My apologies for that.

There's a particular graphics extension that isn't working properly. I'm trying to figure out if it's an incompatibility with our software and the Quadro P5000, a driver issue, or something else. Do you have both your main monitor, and the Oculus Rift plugged into the P5000, or are you also used integrated graphics or a second GPU?

Thanks,
Dan