Jump to content

Recommended Posts

Posted (edited)

Has anyone tried latest nvidia drivers 391.01 in DCS (using oculus VR)??

 

Edit: all is good with me with 391.01

Edited by vracan
Posted

No problems here. Similar performance to 388.71 for me.

Spoiler

W10-x64 | B650E Gigabyte Aorus Master | AMD Ryzen 7 7800X3D | Noctua NH-D15

G.Skill Trident ZS Neo DDR5-6000 64Gb | MSI RTX 3080ti Gaming X

Asus Xonar AE | TM Hotas Warthog

MFG Crosswind pedals | Valve Index

 

Posted

nothing but freeze after freeze for me had to revert back

System:Motherboard Asus ROG Strix Z390-E,Asus ROG GeForce RTX 2080Ti OC, GPU, 32GB Corsair Vengeance DDR4 Ram, Intel i9 9900K @ 5 GHz , cooled by NZXT Kraken X52, Acer XB270HU G-Sinc monitor, Windows 10 Pro, Warthog joystick and throttle with wasy extension, VBK Gunfighter Pro and MCG Pro,MFG Rudder, running on a dedicated 1TB Samsung 970 Pro M2 Nvme , Super Wheel Stand Pro, with a HP Reverb G2

Posted

A Co, 229th AHB, 1st Cav Div

ASUS Prime Z370-A MB, Intel Core i7 8700K 5.0GHz OC'd, RTX 3090, 32GB DDR4, 1TB SSD, Win 10

Samsung 65" 4K Curved Display (Oculus Rift occaisionally), Track IR5, VoiceAttack, Baur's BRD-N Cyclic base/Virpil T-50CM Grip, UH-1h Collective by Microhelis & OE-XAM Pedals. JetSeat & SimShaker for Aviators.

JUST CHOPPERS

 

Posted

Stutters for me. Reverting back.

[sIGPIC][/sIGPIC]

 

 

Intel i9 9900K @ 5.1Ghz HT Disabled, Asus RoG Strix z390E Gaming, 64GB G.Skill Trident Z 3200, Asus RoG Strix RTX2080Ti OC @ 1.9Ghz, 1TB Samsung Evo 970Pro M.2 TM Warthog, CH Pro Pedals, Saitek Pro Rudder Pedals, Samsung 49" Curved Gaming Monitor, Samsung 50" 4KUHD TV, Acer 27" Touch Panel, CV1, Pimax 5K+, Valve Index, FSSB3 Lighting, F-16SGRH, 3 TM Cougar's and a Saitek X36 that I can't bring myself to part with.

Posted

Are we just reporting on the Rift here?

A Co, 229th AHB, 1st Cav Div

ASUS Prime Z370-A MB, Intel Core i7 8700K 5.0GHz OC'd, RTX 3090, 32GB DDR4, 1TB SSD, Win 10

Samsung 65" 4K Curved Display (Oculus Rift occaisionally), Track IR5, VoiceAttack, Baur's BRD-N Cyclic base/Virpil T-50CM Grip, UH-1h Collective by Microhelis & OE-XAM Pedals. JetSeat & SimShaker for Aviators.

JUST CHOPPERS

 

Posted

I am.

[sIGPIC][/sIGPIC]

 

 

Intel i9 9900K @ 5.1Ghz HT Disabled, Asus RoG Strix z390E Gaming, 64GB G.Skill Trident Z 3200, Asus RoG Strix RTX2080Ti OC @ 1.9Ghz, 1TB Samsung Evo 970Pro M.2 TM Warthog, CH Pro Pedals, Saitek Pro Rudder Pedals, Samsung 49" Curved Gaming Monitor, Samsung 50" 4KUHD TV, Acer 27" Touch Panel, CV1, Pimax 5K+, Valve Index, FSSB3 Lighting, F-16SGRH, 3 TM Cougar's and a Saitek X36 that I can't bring myself to part with.

Posted

I just tried the 391.01 drivers but I do not notice a difference between these and 388.59. I still experience ghosting when flying fast or looking at other aircraft flying fast. Are there any particular settings to eliminate/decrease ghosting?

i9 14900k @5.6GHz NZXT Kraken |Asus ROG Strix Z790 A-Gaming | Samsung NVMe m.2 990 Pro 2TB | 64GB DDR5 6400MHz

EVGA RTX 3090 FTW3 Ultra | PiMAX CRYSTAL LIGHT  | HOTAS Warthog | Saitek Flight Pedals

Posted (edited)
Are we just reporting on the Rift here?

 

Oculus itself was reporting an issue with either 390.77 or 390.65, once I updated I couldn’t even use oculus home, it would stutter and restart every 5 secs. Oculus said we had to revert back, so I went back to 388.43, the last working driver I had.

 

I think the question is whether 391.01 solves this? The answer appears to be... maybe. Background on the oculus forums:

 

https://forums.oculusvr.com/community/discussion/62069/black-screen-on-rift-be-sure-to-use-nvidia-driver-388-59

 

It appears the only surefire working driver right now is 388.59 or earlier, but results vary. I may update and see, I can always revert back if necessary.

Edited by Sandman1330

Ryzen 7 5800X3D / Asus Crosshair VI Hero X370 / Corsair H110i / Sapphire Nitro+ 6800XT / 32Gb G.Skill TridentZ 3200 / Samsung 980 Pro M.2 / Virpil Warbrd base + VFX and TM grips / Virpil CM3 Throttle / Saitek Pro Combat pedals / Reverb G2

Posted
Oculus itself was reporting an issue with either 390.77 or 390.65, once I updated I couldn’t even use oculus home, it would stutter and restart every 5 secs. Oculus said we had to revert back, so I went back to 388.43, the last working driver I had.

 

I think the question is whether 391.01 solves this? The answer appears to be... maybe. Background on the oculus forums:

 

https://forums.oculusvr.com/community/discussion/62069/black-screen-on-rift-be-sure-to-use-nvidia-driver-388-59

 

It appears the only surefire working driver right now is 388.59 or earlier, but results vary. I may update and see, I can always revert back if necessary.

 

Odd, at least for me I had no troubles with the latest drivers.

I am running on the Oculus Public Test Channel though...

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Posted
I just tried the 391.01 drivers but I do not notice a difference between these and 388.59. I still experience ghosting when flying fast or looking at other aircraft flying fast. Are there any particular settings to eliminate/decrease ghosting?

 

That is ASW side effects. You can try to disble ASW, which should eliminate that but then probably introduce judder. Your actual source of the problem is probably your graphics and/or cpu bottlenecking.

Posted

I upgraded to 391.01, it solved the problem I was having with 390.77. Seems to work well.

Ryzen 7 5800X3D / Asus Crosshair VI Hero X370 / Corsair H110i / Sapphire Nitro+ 6800XT / 32Gb G.Skill TridentZ 3200 / Samsung 980 Pro M.2 / Virpil Warbrd base + VFX and TM grips / Virpil CM3 Throttle / Saitek Pro Combat pedals / Reverb G2

Posted
That is ASW side effects. You can try to disble ASW, which should eliminate that but then probably introduce judder. Your actual source of the problem is probably your graphics and/or cpu bottlenecking.

I use the Oculus Tray Tool to make sure ASW is off everytime I run DCS. So that can't be the issue. I'll try to lower some settings.

i9 14900k @5.6GHz NZXT Kraken |Asus ROG Strix Z790 A-Gaming | Samsung NVMe m.2 990 Pro 2TB | 64GB DDR5 6400MHz

EVGA RTX 3090 FTW3 Ultra | PiMAX CRYSTAL LIGHT  | HOTAS Warthog | Saitek Flight Pedals

Posted
I use the Oculus Tray Tool to make sure ASW is off everytime I run DCS. So that can't be the issue. I'll try to lower some settings.

 

If your fps are below 90 you get ghosting/double image on the fast moving object - like an airplane. The lower the fps, the worse the problem.

Posted
If your fps are below 90 you get ghosting/double image on the fast moving object - like an airplane. The lower the fps, the worse the problem.

Ah ok. Thats good to know. You'll never hit 90 fps flying DCS. :)

i9 14900k @5.6GHz NZXT Kraken |Asus ROG Strix Z790 A-Gaming | Samsung NVMe m.2 990 Pro 2TB | 64GB DDR5 6400MHz

EVGA RTX 3090 FTW3 Ultra | PiMAX CRYSTAL LIGHT  | HOTAS Warthog | Saitek Flight Pedals

Posted
Ah ok. Thats good to know. You'll never hit 90 fps flying DCS. :)

 

True, but with the nature of modern air combat it is not a huge problem anyway. In IL2 it absolutely is a massive problem, but in DCS I am content with 45fps with ASW :)

Posted

It would appear I spoke too soon.

 

391.01 brings back the bug where Oculus home crashes every 5 seconds.

 

Oculus software has had a very bad track record of late... I've wanted to hold out for CV2 before upgrading to a newer generation headset, but the Samsung Odyssey or Vive Pro are starting to look pretty good...

Ryzen 7 5800X3D / Asus Crosshair VI Hero X370 / Corsair H110i / Sapphire Nitro+ 6800XT / 32Gb G.Skill TridentZ 3200 / Samsung 980 Pro M.2 / Virpil Warbrd base + VFX and TM grips / Virpil CM3 Throttle / Saitek Pro Combat pedals / Reverb G2

Posted (edited)
It would appear I spoke too soon.

 

391.01 brings back the bug where Oculus home crashes every 5 seconds.

 

Oculus software has had a very bad track record of late... I've wanted to hold out for CV2 before upgrading to a newer generation headset, but the Samsung Odyssey or Vive Pro are starting to look pretty good...

 

Ah yes thought I was going mad. Then I am not a lone. Oculus crashes every five seconds indeed.

 

Edit: Looking at the Vive Pro too.

Edited by SpeedStick

"Hard to imagine bigger engine. its got a beautiful face and an arse built like sputnik." - Pikey AKA The Poet, on 37 Viggen.

Posted

I installed 391.01 yesterday. Flew a 2.5 hour mission. No issues. Flew rather smooth.

MSI MAG Z790 Carbon, i9-13900k, NH-D15 cooler, 64 GB CL40 6000mhz RAM, MSI RTX4090, Yamaha 5.1 A/V Receiver, 4x 2TB Samsung 980 Pro NVMe, 1x 2TB Samsung 870 EVO SSD, Win 11 Pro, TM Warthog, Virpil WarBRD, MFG Crosswinds, 43" Samsung 4K TV, 21.5 Acer VT touchscreen, TrackIR, Varjo Aero, Wheel Stand Pro Super Warthog, Phanteks Enthoo Pro2 Full Tower Case, Seasonic GX-1200 ATX3 PSU, PointCTRL, Buttkicker 2, K-51 Helicopter Collective Control

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...