Forum Discussion
Anonymous
9 years agoOculus Home is breaking SLI
Hey guys,
I am running commercial software "Lockheed Martin's Prepar3d V3.4.22.19868" with Nvidia latest drivers 378.66.
As soon as Prepar3d runs, Oculus home client starts up which is fine as Prepar3d has VR support but Prepar3d runs in SLI and Oculus Home flashes the screen during its initialization and kills the SLI.
Even though SLI is enabled in Nvidia Control Panel, but looking at the MSI afterburner graphs it shows the second card is idle and Nvidia's own SLI indicator on the app does not show SLI is enabled.
Now if I disable the Oculus runtime from the Windows 10 Pro Services and then run Prepar3d again (and this time Oculus home does not run). I get full SLI in the Lockheed's application.
Can you please advise on why this happening.
I need to Oculus home client not to disable SLI - is there some registry or some tweak I can do to make it bypass SLI and keep SLI enabled on the workstation.
We need SLI configuration to work as we are building training scenarios. For this particular application which has lots of legacy code (some of it is decades old), SLI is helping in VR but right now Oculus Client is forcing a SLI breakage.
Thanks
Workstation Specs
2 x 980s
i7-5820K
Windows 10 Pro (latest and fully patched)
16 GB Ram
3x512 SSDs
I am running commercial software "Lockheed Martin's Prepar3d V3.4.22.19868" with Nvidia latest drivers 378.66.
As soon as Prepar3d runs, Oculus home client starts up which is fine as Prepar3d has VR support but Prepar3d runs in SLI and Oculus Home flashes the screen during its initialization and kills the SLI.
Even though SLI is enabled in Nvidia Control Panel, but looking at the MSI afterburner graphs it shows the second card is idle and Nvidia's own SLI indicator on the app does not show SLI is enabled.
Now if I disable the Oculus runtime from the Windows 10 Pro Services and then run Prepar3d again (and this time Oculus home does not run). I get full SLI in the Lockheed's application.
Can you please advise on why this happening.
I need to Oculus home client not to disable SLI - is there some registry or some tweak I can do to make it bypass SLI and keep SLI enabled on the workstation.
We need SLI configuration to work as we are building training scenarios. For this particular application which has lots of legacy code (some of it is decades old), SLI is helping in VR but right now Oculus Client is forcing a SLI breakage.
Thanks
Workstation Specs
2 x 980s
i7-5820K
Windows 10 Pro (latest and fully patched)
16 GB Ram
3x512 SSDs
1 Reply
- AnonymousLooks Like I solved the issue
I believe there is a work around - even though Nvidia SLI indicator is
not showing but the graphs in MSI afterburner are showing activity when
the following steps are done in sequence.
1) First run oculus client and do not close it
2) Now run Flyinside for P3D and only then I see activity being used up on the
SLI. (No Nvidia indicator but MSI Afterburner is showing activity usage
on 2 gpus)
But if I run P3D/ or Flyinside first and then it launches Oculus Client - at this stage SLI is broken.
Will report more in the following days about this
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 8 months ago
- 3 years ago
- 2 years ago