The Home of FlyInside Flight Simulator FFS FSX P3D and X-PLANE Message Board

Background
--------------
Which version of Fly Inside P3D do you use? -- FLYINSIDE_P3D4_PRO_1.97_OVR_1300.exe
Which version of P3D do you use? -- 4.4.16.27077
What P3D plugins do you use? -- all removed / unselected
Do you use reshaders ? -- No
Please upload the log file. -- As attached
Sometimes it also makes sense to upload the log file from P3D. -- Na
Are your drivers up to date? -- Yes
Are you running our software on a laptop? -- No , on a Desktop
Is your HMD plugged directly into the HDMI-port of the accelerated GFX-card? -- Oculus Rift plugged into HDMI on the 1080Ti

Specs
------
Processer - Intel i5-8600K CPU @ 3.60GHz
Memory - 16.00 GB
System - 64 bit Windows 10
P3D - FlyInside P3D4 Pro 1.97
VR - Oculus Rift CV1
Graphics Card - GeForce GTX 1080 Ti (Driver version 417.35)

Symptoms
------------
- Start Flyinside
- Oculus Home starts
- I can see Prepar3D in the Task Manager attempting to start
- CPU usage goes up for Prepar3D process and then goes back down again. Ultimately "Suspended" and disappears from the Task Manager

I check the Log.txt and it appears that Flyinside has failed - last 2 lines are:

Code: Select all

6.75044      VRSLI\SLIManager.cpp      58      Creating multi-GPU mask
6.75066      VRSLI\SLIManager.cpp      92      Failed to create MultiGPUDevice

NOTE:
- All 3 Monitors and Oculus are plugged into the 1080ti graphics card
- I have just upgraded to P3D 4.4 and this is when everything started to go wrong.
- I had no problems with P3D 4.3
- If I stop the Oculus VR Runtime Service, the P3D starts OK - Obviously without the VR - but indicates that P3D installation is OK.
- I have ORBX components and Add-On scenery - I have uninstalled all of these and retried - but some issue. Currently they are installed again, but all are deselected right now.

OK - following the steps in this post seems to have fixed this issue...

https://www.prepar3d.com/forum/viewtopi ... 2&t=123246

OK - a bit premature there...

This is what actually made the difference from that post ..

"...
5) Remove your generated files.

Delete the files in these locations, Copy the TEXT below and paste them into the windows search bar
Delete the following generated folders/files. This will result in any add-ons being removed/disabled.
%PROGRAMDATA%\Lockheed Martin\Prepar3D v4
%LOCALAPPDATA%\Lockheed Martin\Prepar3D v4
%APPDATA%\Lockheed Martin\Prepar3D v4 ..."

In particular , the removal of this file allowed FI to load correctly
- C:\Users\Nik\AppData\Roaming\Lockheed Martin\Prepar3D v4\dll.xml

Which was GREAT .. Until I tried to load the VRS Tacpack and Superbug for P3D..
The VRS superbug would not load in the game with the error "Incomplete Gauge Load".

And here are the steps that I followed to reproduce the error:

* Uninstall Tacpack and Superbug

* Remove following folders:

Code: Select all

C:\Users\<name>\AppData\Roaming\Lockheed Martin\Prepar3D v4
C:\Users\<name>\AppData\Local\Lockheed Martin\Prepar3D v4
C:\ProgramData\Lockheed Martin\Prepar3D v4

* Start Flyinside - works fine

* Install Tacpack - Admin mode
Start and activate

* Install Superbug - Admin mode
Start and activate

* Start Flyinside - the following file is created..

Code: Select all

C:\Users\<name>\AppData\Roaming\Lockheed Martin\Prepar3D v4\dll.xml

The following code stops Flyinside from launching... but it is required for the Superbug to load

Code: Select all

  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
       <Name>VRS_TacPack</Name>
       <Disabled>False</Disabled>
       <ManualLoad>False</ManualLoad>
       <Path>Modules\VRS_TacPack\VRS_TacPack.dll</Path>
   </Launch.Addon>


If I remove this text from the XML file, then FI loads OK, but the Superbug will not run.

Any ideas?

None from me I'll check with Dan for you mate.

Great thanks..
I'll also add that I when I upgraded to P3D4.4, I had to upgrade VRS Superbug and Tacpack to match. The new versions were
- VRS_TacPack_P3D_1.5.0.5_x64
- VRS_Superbug_P3D_1.5.0.5_x64

So I have new versions of P3D / VRS / Flyinside
- P3D + Flyinside = OK
- P3D + VRS = OK
- P3D + VRS + Flyinside = ERROR

Hi guys

Any luck with this?

Thanks

OK and here is the culprit - For some reason I now have to disable DirectX video features.

This allows P3D to start, just not sure what I'm about to lose with this turned off...

No we had zero luck. Never heard of that before??? Does things work as they did before mate ??

I'll keep testing and keep you posted ...