Jump to content

Recommended Posts

Posted

Not correct, with the odyssey set PD to 1.4 or above and you will see a significant improvement compared to The rift. This tech seems to be person and their eyes dependent.

I7-8700 @5GHZ, 32GB 3000MHZ RAM, 1080TI, Rift S, ODYSSEY +. SSD DRIVES, WIN10

Posted

It is person (and how old you are! :)) dependent. But theoretically, you shouldn't have to jack up the PD as much with Odyssey (compared to Vive/Rift). But as Sniper175 points out, give it a shot since it is very much a personal preference.

hsb

HW Spec in Spoiler

---

 

i7-10700K Direct-To-Die/OC'ed to 5.1GHz, MSI Z490 MB, 32GB DDR4 3200MHz, EVGA 2080 Ti FTW3, NVMe+SSD, Win 10 x64 Pro, MFG, Warthog, TM MFDs, Komodo Huey set, Rverbe G1

 

Posted
Actually Pixel Desnity adjustment in the VR Tab only works for the Rift, not the Vive.

 

To adjust pixel desnity on the Vive you need to edit the VRSetting file in the Steam folder.

 

What, is this for real? I want a confirmation from the developers.

Posted

We can also draw a parallel for those who want to determine if their PC will run DCS well with VR. Say "Misha Mignichnik" has a three screen setup and he wants to know if his PC will "run DCS in VR". He can easily run test flights in various locations, conditions and aircraft while running a framerate test on each one. If he has frame rates running at ~90 or more all the time then he knows with ease that he can - should - run DCS with VR; e.g.:

 

Misha runs three screes at 1920x1080 x 3 => 5760x1080 resolution = 6,220,800 pixels generated. If Misha can run that then he "should" have a good VR experience as his PC has enough power to do it.

 

I hope this helps folks understand the relationship between Pixel Density, Screen Resolution and expected pixels per frame more clearly.

 

NB: You can also see that if you're running a PD of 150 and generating a total of 5,832,000 pixels per frame cycle, then if you're getting 90fps you're generating a whopping 524,880,000 pixels per second! WOW!

 

Wrong, What Misha and Derek don't have into account is that on a flat screen the game only render the scene one time per frame but in VR the game needs to render the scene two times (two eyes, two cameras) as best case the fps will be a 30% lower in VR. We need ED to implement the single pass rendering algorithm for ones. If ED implements this, we are going to see a 30% performance improvement in the worst case.

Posted
What, is this for real? I want a confirmation from the developers.

 

 

It was for rift only originally..

However it also works with steamVR since at least 1.5.6... no need for manual override in steamVR, which, BTW, added it as a slider in the steamVR setting a long long time ago.. so regardless, no need for Config file editing anymore.

Posted
It was for rift only originally..

However it also works with steamVR since at least 1.5.6... no need for manual override in steamVR, which, BTW, added it as a slider in the steamVR setting a long long time ago.. so regardless, no need for Config file editing anymore.

 

Thanks for the information:thumbup:.

Posted
I have PD adjustment in Oculus Tray Tool and in the DCS VR tab. If both do the same thing, which should I be using and what do I set the other to?

 

Only use one. If you set PD to say 1.5 in both then you are compounding them. DCS will apply 1.5 to the 1.5 you are already running.

 

I don't know if either one is better than the other.

"It takes a big man to admit he is wrong...I'm not a big man" Chevy Chase, Fletch Lives

 

5800X3D - 64gb ram - RTX3080 - Windows 11

Posted
Only use one. If you set PD to say 1.5 in both then you are compounding them. DCS will apply 1.5 to the 1.5 you are already running.

 

I don't know if either one is better than the other.

 

 

If for example I set one to 1.5 PD do I set the other to 1.0 PD?

Posted
Does a higher PD make for more readable text/HUD/instruments?

 

 

 

It helps quite lot. 1.0 and 2xMsaa hard to read.

 

1.1 (only) and 2xMsaa = much more clear even with minimal PD rise.

 

 

Sent from my iPhone using Tapatalk

Oculus CV1, Odyssey, Pimax 5k+ (i5 8400, 24gb ddr4 3000mhz, 1080Ti OC )

 

 

[sIGPIC][/sIGPIC]

Posted
What’s the point in this feature if it’s already available via oculus software?

 

Just gives another way to set it, via the in game GUI rather than through the HMD software.

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

As a noob to VR I'd appreciate a run down on the best settings at which to begin.

There are settings available in the Nvidia Control Panel, Oculus Settings and DCS.

Can I set Msaa, Fxaa, PD etc in Nvidia and have it control everything with the others being on default?

I'm enjoying the VR experience but can't obtain a crisp picture even with 75 - 80 fps in SP.

Asus ROG Maximus Hero Z690-E, i9-13900KF, RTX 4090, Trident Z Neo 64Gb (4x16) DDR5 6600 C32, EVO 980 Pro 2Tb M.2 Nvme SSD, HP Reverb G2, VKB Gunfighter Modern Combat Pro, MFG Crosswind pedals, Virpil MongoosT-50 throttle, Corsair 7000D Airflow Case, 1200W Asus Platinum G+ PSU, Win10 Pro 64 bit

Posted
As a noob to VR I'd appreciate a run down on the best settings at which to begin.

There are settings available in the Nvidia Control Panel, Oculus Settings and DCS.

Can I set Msaa, Fxaa, PD etc in Nvidia and have it control everything with the others being on default?

I'm enjoying the VR experience but can't obtain a crisp picture even with 75 - 80 fps in SP.

 

About all you can do in Nvidia control panel when in VR is set power mgmt to "prefer max performance".

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

Thanks, dburne

So do I also go with default settings for everything else in Nvidia Control panel Msaa, Fxaa etc?

Asus ROG Maximus Hero Z690-E, i9-13900KF, RTX 4090, Trident Z Neo 64Gb (4x16) DDR5 6600 C32, EVO 980 Pro 2Tb M.2 Nvme SSD, HP Reverb G2, VKB Gunfighter Modern Combat Pro, MFG Crosswind pedals, Virpil MongoosT-50 throttle, Corsair 7000D Airflow Case, 1200W Asus Platinum G+ PSU, Win10 Pro 64 bit

Posted
Thanks, dburne

So do I also go with default settings for everything else in Nvidia Control panel Msaa, Fxaa etc?

 

Yeah, I think you maybe can inject some FXAA through it, I gave it a try and really could not tell much from it so left it at default as well.

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

Thanks again, dburne.

I think part of the transition to VR requires getting over the initial feeling of groping around in the dark for control buttons, keyboard etc. Comfort will come with time and experience.

Cheers

Asus ROG Maximus Hero Z690-E, i9-13900KF, RTX 4090, Trident Z Neo 64Gb (4x16) DDR5 6600 C32, EVO 980 Pro 2Tb M.2 Nvme SSD, HP Reverb G2, VKB Gunfighter Modern Combat Pro, MFG Crosswind pedals, Virpil MongoosT-50 throttle, Corsair 7000D Airflow Case, 1200W Asus Platinum G+ PSU, Win10 Pro 64 bit

Posted
Thanks again, dburne.

I think part of the transition to VR requires getting over the initial feeling of groping around in the dark for control buttons, keyboard etc. Comfort will come with time and experience.

Cheers

 

You are most welcome.

 

Lol yep, luckily for me I had already had pretty good memory of my controller buttons and how I had them assigned even before getting into VR, so in that regard the transition was not too tough on me.

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|

  • 5 months later...
Posted

OK, dumb question.

 

I use OTT and have SS set to 1.3. I also have PD set to 1.5 in game. So am I doubvle dipping and costing myself performance without any real increase?

----------------

AKA_Clutter

 

Win 10 Pro, Intel i7 12700k @4.6 GHz, EVGA RTX 3080  FTW, Ultra 64 GB G.Skill DDR4 3600 RAM, Acer 27" flat screen, HP Reverb G2, TM Warthog HOTAS with Virpil warBRD base, MFG Rudder Pedals, Virpil TCS Rotor Base with AH-64Dcollective, TrackIR 5 Pro w/Vector Expansion, PointCTRL.

Posted
OK, dumb question.

 

I use OTT and have SS set to 1.3. I also have PD set to 1.5 in game. So am I doubvle dipping and costing myself performance without any real increase?

 

Yes could be, best to set it on one or the other , not both.

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 would think it more likely that one takes precedence over the other.

 

Suggest setting them to something like 1, 2 and then vice versa. Should make it pretty clear in terms of performance and image quality if only one setting is used. If they both are, you should get similar results in each case.

Asus Z690 Hero | 12900K | 64GB G.Skill 6000 | 4090FE | Reverb G2 | VPC MongoosT-50CM2 + TM Grips  | Winwing Orion2 Throttle | MFG Crosswind Pedals

  • 1 year later...
Posted
It helps quite lot. 1.0 and 2xMsaa hard to read.

 

1.1 (only) and 2xMsaa = much more clear even with minimal PD rise.

 

 

Curious, can anyone else verify this?

"You see, IronHand is my thing"

My specs:  W10 Pro, I5/11600K o/c to 4800 @1.32v, 64 GB 3200 XML RAM, Red Dragon 7800XT/16GB.

  • 3 years later...
Posted

So I find myself still struggling with understanding the details around the following:

Does anyone know if there's a difference between downscaling with OpenXR Custom Render Scale or using in-game Pixel Density?
Is there a quality or performance difference between them, especially when used in conjuction with the new DLSS setting?

GPU: PALIT NVIDIA RTX 3080 10GB | CPU: Intel Core i7-9700K 4,9GHz | RAM: 64GB DDR4 3000MHz
VR: HP Reverb G2 | HOTAS: TM Warthog Throttle and Stick
OS: Windows 10 22H2

  • Recently Browsing   0 members

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