Hi there!
Very complex title about what might have been a completely different issue. But here goes:
Many orbits ago (well, 3-ish) I built an SLI system with a couple of NVIDIA GTX 980TI cards and a single ultra-wide screen. Elite was beautiful on Ultra and still is. On of the cards was kind enough to fall over within warranty, but also after the 980s were generally not in sale anymore. The store said "sorry, we don't stock those anymore, but here is a 1070 - they are 30% more powerful". "Thanks" I said. "But no thanks. This is an SLI system and I need two of the same.". "OK" they said, and sent me a second 1070.
All was happiness for about 2 years, but I kept hearing ravings about VR and how ED was basically the game for VR. Somewhere out in the Formidine Rift I took the plunge. And lo it was the bee's knees, the cat's pajamas, the duck's nuts. The toy I got was the Rift Touch, with a couple of otherwise rather nice touch controllers gathering dust not far from my HOTAS. The second graphics card also appears to be gathering dust, as VR and SLI don't seem to work together. It is still great for CUDA work such as rendering.
Fast forward until a few weeks ago, when I started to (again) get "Direct3D cannot load a buffer" messages on startup. Eventually I just disconnected the headset and played in flatland again. That was fine for a while - nice to see things in high detail again. But then I got myself a Beluga and I just had to see that bridge in full 3D. So time to troubleshoot:
1) Was it the game? I "repaired" (reinstalled Elite as per directions) - no.
2a) Was it the Oculus drivers? Perhaps, dxdiag indicated an issue with a sound driver for the Rift. So I disabled sound from the Rift and only used external speakers. Result - still failing.
2b) But was it something with the Oculus Rift? I reinstalled the Rift, which removed the .dll isse according to dxdiag. Still no go when starting Elite; damn you ED! My computer does live up to minimum specs, thank you very much!
3) Was it the graphics card? The GPU driver was updated, everything should be fine. Still no good, even with the latest driver version.
4) How about SLI? I turned it off, and the game fired up in VR. Horay!
5) But was it really SLI? I turned it back on and restarted. The game fired up in VR. Twice horay!
Why is it that Windows troubleshooting just feels like wiggling wires until a lamp comes back on? Either way, the Beluga bridge is a marvel in VR. Now where did I mislay my Star Trek uniform?
: D S
Very complex title about what might have been a completely different issue. But here goes:
Many orbits ago (well, 3-ish) I built an SLI system with a couple of NVIDIA GTX 980TI cards and a single ultra-wide screen. Elite was beautiful on Ultra and still is. On of the cards was kind enough to fall over within warranty, but also after the 980s were generally not in sale anymore. The store said "sorry, we don't stock those anymore, but here is a 1070 - they are 30% more powerful". "Thanks" I said. "But no thanks. This is an SLI system and I need two of the same.". "OK" they said, and sent me a second 1070.
All was happiness for about 2 years, but I kept hearing ravings about VR and how ED was basically the game for VR. Somewhere out in the Formidine Rift I took the plunge. And lo it was the bee's knees, the cat's pajamas, the duck's nuts. The toy I got was the Rift Touch, with a couple of otherwise rather nice touch controllers gathering dust not far from my HOTAS. The second graphics card also appears to be gathering dust, as VR and SLI don't seem to work together. It is still great for CUDA work such as rendering.
Fast forward until a few weeks ago, when I started to (again) get "Direct3D cannot load a buffer" messages on startup. Eventually I just disconnected the headset and played in flatland again. That was fine for a while - nice to see things in high detail again. But then I got myself a Beluga and I just had to see that bridge in full 3D. So time to troubleshoot:
1) Was it the game? I "repaired" (reinstalled Elite as per directions) - no.
2a) Was it the Oculus drivers? Perhaps, dxdiag indicated an issue with a sound driver for the Rift. So I disabled sound from the Rift and only used external speakers. Result - still failing.
2b) But was it something with the Oculus Rift? I reinstalled the Rift, which removed the .dll isse according to dxdiag. Still no go when starting Elite; damn you ED! My computer does live up to minimum specs, thank you very much!
3) Was it the graphics card? The GPU driver was updated, everything should be fine. Still no good, even with the latest driver version.
4) How about SLI? I turned it off, and the game fired up in VR. Horay!
5) But was it really SLI? I turned it back on and restarted. The game fired up in VR. Twice horay!
Why is it that Windows troubleshooting just feels like wiggling wires until a lamp comes back on? Either way, the Beluga bridge is a marvel in VR. Now where did I mislay my Star Trek uniform?
: D S
![[VR] Mad Life Crisis](https://forums-cdn.zaonce.net/data/avatars/m/232/232989.jpg?1592151565){kind=avatar}