Jump to content

Recommended Posts

Posted
Why does that screen not match your hardware ? Did you do something funky commissioning the 'puter ? Looks to me like you need to reinstall Windows .
Good point I didn't even realize that. Maybe he's trying to run it on a different PC like a laptop? Not on his PC that is in the signature?

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

Posted
Good point I didn't even realize that. Maybe he's trying to run it on a different PC like a laptop? Not on his PC that is in the signature?

 

hem... no!

Core i5-9600KF - 32GB DDR4 3000 - RTX 2070 Super - Samsung 970 EVO PLUS 250GB & 500GB- HOTAS Warthog - AOC CU34G2X - HP Reverb Pro

Posted

Is it possible that Microsoft site is checking the chipset's graphics card instead of the RTX 2070S?

Core i5-9600KF - 32GB DDR4 3000 - RTX 2070 Super - Samsung 970 EVO PLUS 250GB & 500GB- HOTAS Warthog - AOC CU34G2X - HP Reverb Pro

Posted
hem... no!
Well that screen you posted shows you have Intel graphics and your signature says you have a 2070. So I'm guessing the program that checks if you have the right hardware is bugged?

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

Posted

I have no problems with my HP Reverb in general. But when I had it working and i noticed 3 crashes in a row when entering a multiplayer server i could pinpoint the cause to my excessive qualtiy settings (400% Supersampling). I was out of GPU memory. After reducing no more crashes. I use fpsVR app to monitor GPU/CPU performance and memory to finetune my experience. I recommend this app a lot.

VIC-20@1.108 MHz, onboard GPU, 5KB RAM, μυωπία goggles, Competition Pro HOTAS

Posted
Is it possible that Microsoft site is checking the chipset's graphics card instead of the RTX 2070S?
Another thing to try, go into bios and make sure you have your graphics set to use dedicated GPU not the onboard Intel graphics.

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

Posted

and that it is plugged into the graphics card ... not the motherboard ...

SYSTEM SPECS: Hardware AMD 9800X3D, 64Gb RAM, 4090 FE, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero
SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO

YOUTUBE CHANNEL: @speed-of-heat

1569924735_WildcardsBadgerFAASig.jpg.dbb8c2a337e37c2bfb12855f86d70fd5.jpg

Posted
Well that screen you posted shows you have Intel graphics and your signature says you have a 2070. So I'm guessing the program that checks if you have the right hardware is bugged?

 

 

Maybe the program is only listing the minimum requirements and telling if they are met or not, and it’s not listing my actual ones.

 

This is a screenshot from the GeForce software:

f79f4ed9bd3074790466ee51ed59a510.jpg

 

 

Sent from my iPhone using Tapatalk

Core i5-9600KF - 32GB DDR4 3000 - RTX 2070 Super - Samsung 970 EVO PLUS 250GB & 500GB- HOTAS Warthog - AOC CU34G2X - HP Reverb Pro

Posted
Not sure what you mean?

PC is brand new, like 2 days old.

All drivers updated.

That screen shows u have a 6600 cpu , 8gig mem , and 27 gig disk space

 

Check settings>system>about . If that matches your sig , you're good . Wmr test is bad .

If it shows the same as the wmr test screen , reinstall windows .

 

Edit: sniped !

9700k @ stock , Aorus Pro Z390 wifi , 32gb 3200 mhz CL16 , 1tb EVO 970 , MSI RX 6800XT Gaming X TRIO , Seasonic Prime 850w Gold , Coolermaster H500m , Noctua NH-D15S , CH Pro throttle and T50CM2/WarBrD base on Foxxmounts , CH pedals , Reverb G2v2

Posted

Guys I want to dig a hole and bury myself in it...

 

What I posted was the example from the page which I thought was my actual test.

Awwwwwww, I'm so sorry.

 

Please don't tell anyone ;-)

Core i5-9600KF - 32GB DDR4 3000 - RTX 2070 Super - Samsung 970 EVO PLUS 250GB & 500GB- HOTAS Warthog - AOC CU34G2X - HP Reverb Pro

Posted

Welcome to the wonderful world of WMR :)

9700k @ stock , Aorus Pro Z390 wifi , 32gb 3200 mhz CL16 , 1tb EVO 970 , MSI RX 6800XT Gaming X TRIO , Seasonic Prime 850w Gold , Coolermaster H500m , Noctua NH-D15S , CH Pro throttle and T50CM2/WarBrD base on Foxxmounts , CH pedals , Reverb G2v2

Posted
Welcome to the wonderful world of WMR :)

 

15+ years passed since I last used a PC... I only bought one to play DCS in VR!

 

Anyhow, sorry again, test is passed with all checks in the right place.

Core i5-9600KF - 32GB DDR4 3000 - RTX 2070 Super - Samsung 970 EVO PLUS 250GB & 500GB- HOTAS Warthog - AOC CU34G2X - HP Reverb Pro

Posted

Hi guys, yesterday I set up my new Reverb Pro and had my first VR experience, obviously with DCS.

A few comments and a couple of questions.

 

The experience was indeed very immersive and very smooth and fluid.

I wasn’t impressed by the resolution though, maybe I set my expectations to high after reading many enthusiastic reviews.

The definition is not at the level of the monitor one although the cockpit is perfectly readable even from a distance.

 

Then there is what I consider the most unpleasant effect which I call the glowing surfaces. It seems like every surface is “alive”, like if it was animated by a thousand micro spheres running below the “skin” of every texture.

Sorry I don’t know if this makes any sense to you but I would not know how to describe it otherwise.

Overall the picture from the monitor is far more realistic while obviously what you get from the VR is much more immersive.

 

I also had some problems with the position in the aircraft, meaning that for some reasons I have to sit at angle with the front of my desk in order to be sitting properly in the cockpit.

Also whatever is inside the cockpit looks too small compared to the real world, like if it was a dwarfs F-16...

 

Any comments regarding what I just wrote would be appreciated, just for me to set the right expectations and understand what can be improved and what is just a limit of the technology.

 

NOTE:

I followed some tutorials I found on YouTube in order to setup the Reverb, in particular regarding WMR and Steam VR.

I forced the refresh rate to 90Hz and the resolution upsampling to 100%.

 

 

Sent from my iPad using Tapatalk

Core i5-9600KF - 32GB DDR4 3000 - RTX 2070 Super - Samsung 970 EVO PLUS 250GB & 500GB- HOTAS Warthog - AOC CU34G2X - HP Reverb Pro

Posted (edited)
Then there is what I consider the most unpleasant effect which I call the glowing surfaces. It seems like every surface is “alive”, like if it was animated by a thousand micro spheres running below the “skin” of every texture.

Sorry I don’t know if this makes any sense to you but I would not know how to describe it otherwise.

Overall the picture from the monitor is far more realistic while obviously what you get from the VR is much more immersive.

 

I think your expectation was too high if you were expecting monitor quality fidelity. What you are describing I believe is the Screen door effect. It may be noticeable to you because you just got the headset and you're trying to nitpick it and compare to your monitor. I suggest just fly a mission and concentrate on the mission. Your brain will erase them.

 

It's like when you have a scratch on your iris. You notice the dark spot if you try to look for it. But after awhile, it disappears because your brain erases it.

 

And increase the Pixel density in SteamVR setting as high as you can before you see frame rate drop.

 

As for seat position, use RCtrl + RShift + Numpad Keys to adjust. Numpad / and * moves forward and backward.

 

F16 feeling like it's miniature, I believe that's normal.

Edited by Taz1004
Posted
I think your expectation was too high if you were expecting monitor quality fidelity. What you are describing I believe is the Screen door effect. It may be noticeable to you because you just got the headset and you're trying to nitpick it and compare to your monitor. I suggest just fly a mission and concentrate on the mission. Your brain will erase them.

 

It's like when you have a scratch on your iris. You notice the dark spot if you try to look for it. But after awhile, it disappears because your brain erases it.

 

And increase the Pixel density in SteamVR setting as high as you can before you see frame rate drop.

 

As for seat position, use RCtrl + RShift + Numpad Keys to adjust. Numpad / and * moves forward and backward.

 

F16 feeling like it's miniature, I believe that's normal.

 

 

Thanks a lot!

How can I see the frame rate?

 

 

Sent from my iPad using Tapatalk

Core i5-9600KF - 32GB DDR4 3000 - RTX 2070 Super - Samsung 970 EVO PLUS 250GB & 500GB- HOTAS Warthog - AOC CU34G2X - HP Reverb Pro

Posted
Hi guys, yesterday I set up my new Reverb Pro and had my first VR experience, obviously with DCS.

A few comments and a couple of questions.

 

The experience was indeed very immersive and very smooth and fluid.

I wasn’t impressed by the resolution though, maybe I set my expectations to high after reading many enthusiastic reviews.

The definition is not at the level of the monitor one although the cockpit is perfectly readable even from a distance.

 

Then there is what I consider the most unpleasant effect which I call the glowing surfaces. It seems like every surface is “alive”, like if it was animated by a thousand micro spheres running below the “skin” of every texture.

Sorry I don’t know if this makes any sense to you but I would not know how to describe it otherwise.

Overall the picture from the monitor is far more realistic while obviously what you get from the VR is much more immersive.

 

I also had some problems with the position in the aircraft, meaning that for some reasons I have to sit at angle with the front of my desk in order to be sitting properly in the cockpit.

Also whatever is inside the cockpit looks too small compared to the real world, like if it was a dwarfs F-16...

 

Any comments regarding what I just wrote would be appreciated, just for me to set the right expectations and understand what can be improved and what is just a limit of the technology.

 

NOTE:

I followed some tutorials I found on YouTube in order to setup the Reverb, in particular regarding WMR and Steam VR.

I forced the refresh rate to 90Hz and the resolution upsampling to 100%.

 

 

Sent from my iPad using Tapatalk

 

I have a different take on this than Taz1004.

 

It is almost certain that the 'glowing surfaces' effect you describe is aliasing, and not SDE, which is almost non-existent in the Reverb. The most effective way of dealing with that is the use of MSAA. However, that takes its toll on fps.

 

Regarding seat position, there are a few tools at your disposal. Firstly remember to reset your centre position. I have mine set to numpad 5 as well as a HOTAS button. Secondly, in almost all modules, there is a seat height adjustment, again which I bind to my HOTAS, as well as up/down/forward/back cockpit camera views that you can adjust. Personally, I have seat raise/lower and cockpit forward/back bound to a hat on my HOTAS, but rarely do I ever use forward/back. Seat up/down is of course, a different matter, and that needs adjusting for certain things, like landing, AAR, etc. in some modules.

 

Wiith respect to fps monitoring, although you can get a basic fps in-game with ctrl+pause, the essential tool for fps, frame time and much more, is fpsVR. This utility should be owned by all VR users and is available on Steam for a few pounds.

 

An important thing to do, is to keep the PD in DCS to 1.0, and start varying the Render Resolution (formerly called Super Sampling) in SteamVR. Again, this has a major effect on visual quality, but comes at a price in terms of hardware resources.

 

I use 200%, but your system may not be able to deal with that. Keep an eye on frame times in fpsVR, and just make sure that you are rarely going above 22ms (45fps) and your normal range is 12-20.

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted
I have a different take on this than Taz1004.

 

It is almost certain that the 'glowing surfaces' effect you describe is aliasing, and not SDE, which is almost non-existent in the Reverb. The most effective way of dealing with that is the use of MSAA. However, that takes its toll on fps.

 

Regarding seat position, there are a few tools at your disposal. Firstly remember to reset your centre position. I have mine set to numpad 5 as well as a HOTAS button. Secondly, in almost all modules, there is a seat height adjustment, again which I bind to my HOTAS, as well as up/down/forward/back cockpit camera views that you can adjust. Personally, I have seat raise/lower and cockpit forward/back bound to a hat on my HOTAS, but rarely do I ever use forward/back. Seat up/down is of course, a different matter, and that needs adjusting for certain things, like landing, AAR, etc. in some modules.

 

Wiith respect to fps monitoring, although you can get a basic fps in-game with ctrl+pause, the essential tool for fps, frame time and much more, is fpsVR. This utility should be owned by all VR users and is available on Steam for a few pounds.

 

An important thing to do, is to keep the PD in DCS to 1.0, and start varying the Render Resolution (formerly called Super Sampling) in SteamVR. Again, this has a major effect on visual quality, but comes at a price in terms of hardware resources.

 

I use 200%, but your system may not be able to deal with that. Keep an eye on frame times in fpsVR, and just make sure that you are rarely going above 22ms (45fps) and your normal range is 12-20.

 

 

Thanks, I will play with MSAA and resolution (one at a time) and see how it goes.

 

Another interesting detail is that on Steam Vr settings my standard resolution (100%, no upsampling) is 2212x2164, while in all YouTube tutorials people mention the vertical refresh rate as 2160...

 

 

Sent from my iPad using Tapatalk

Core i5-9600KF - 32GB DDR4 3000 - RTX 2070 Super - Samsung 970 EVO PLUS 250GB & 500GB- HOTAS Warthog - AOC CU34G2X - HP Reverb Pro

Posted
Thanks, I will play with MSAA and resolution (one at a time) and see how it goes.

 

Another interesting detail is that on Steam Vr settings my standard resolution (100%, no upsampling) is 2212x2164, while in all YouTube tutorials people mention the vertical refresh rate as 2160...

 

 

Sent from my iPad using Tapatalk

 

Yes, you can't match it exactly.

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted
Thanks, I will play with MSAA and resolution (one at a time) and see how it goes.

 

Another interesting detail is that on Steam Vr settings my standard resolution (100%, no upsampling) is 2212x2164, while in all YouTube tutorials people mention the vertical refresh rate as 2160...

 

 

Sent from my iPad using Tapatalk

 

I'd like to know what that glowing spheres was. I thought it was screen door since you said it's on every surface but maybe imacken is right as you also said it's under every texture.

 

Anti aliasing vs Pixel density is kind a split based on preference. I personally don't like the MSAA as the performance hit is too great and does not eliminate the shimmering. Rather use that resource to increase the pixel density to make everything sharper.

Posted

HP's Reverb VR Pro Headset

 

I'd like to know what that glowing spheres was. I thought it was screen door since you said it's on every surface but maybe imacken is right as you also said it's under every texture.

 

Anti aliasing vs Pixel density is kind a split based on preference. I personally don't like the MSAA as the performance hit is too great and does not eliminate the shimmering. Rather use that resource to increase the pixel density to make everything sharper.

 

 

I’m trying to do some testing playing with oversampling and MSAA and I will get back to you.

What I noticed so far is three things:

1) I can definitely see what looks like Screen Door effect (very evident to my eyes), like a very thin mesh covering the image if you look with attention. Less visible during the action.

2) the edges of objects being “alive”. Despite the high resolution of the display the edges present some level of aliasing and the zig zag profile is moving, imagine like an escalator moving, even if I pause the game. For some reasons this is accentuated in very bright lighting when everything looks like shiny edges in motion, kind of sparkling.

3) I see two dead pixels, one very small the other bigger, maybe it’s 2 or 3 dead pixels, not one. The position is on the far left so not very annoying but still visible if you look for it.

 

 

Sent from my iPhone using Tapatalk

Core i5-9600KF - 32GB DDR4 3000 - RTX 2070 Super - Samsung 970 EVO PLUS 250GB & 500GB- HOTAS Warthog - AOC CU34G2X - HP Reverb Pro

Posted

If you can make PD work better than MSAA, let me know. Otherwise I dont think it really matters what your PD is; you're still going to get jaggies.

Intel 13900k @ 5.8ghz | 64gb GSkill Trident Z | MSI z790 Meg ACE | Zotac RTX4090 | Asus 1000w psu | Slaw RX Viper 2 pedals | VPForce Rhino/VKB MCE Ultimate + STECS Mk2  MAX / Virpil MongoosT50+ MongoosT50CM | Virpil TCS+/ AH64D grip/custom AH64D TEDAC | Samsung Odyssey G9 + Odyssey Ark | Next Level Racing Flight Seat Pro | WinWing F-18 MIPS | No more VR for this pilot.
 My wallpaper and skins

On today's episode of "Did You Know", Cessna Skyhawk crashes into cemetery; over 800 found dead as workers keep digging.

Posted
If you can make PD work better than MSAA, let me know. Otherwise I dont think it really matters what your PD is; you're still going to get jaggies.

 

That has been my experience, for me I have to run at least 2x MSAA along with PD to get what I consider a good looking image.

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

Someone mentioned PD of 0.9 and SS of 110+%. That gave me smoother performance even on 30fps sometimes.

Ryzen 1700 @ 3.8GHz / 32GB( 4x8 ) @ 3.2GHz / 1TB ADATA NVMe System Drive / 232GB NVMe Samsung 960 / ASUS dual RTX 2080ti / Reverb / Rift CV1 / T-16000M FCS flight pack

 

A10C/M2000C/F5E/SA342/Mi8/UH1H/KA50/AJS-37/FA-18C/AV-8B/F-14/Mig29/CA/SU-27

Posted

Ive been running .9PD and 100% and I get playable results.

Intel 13900k @ 5.8ghz | 64gb GSkill Trident Z | MSI z790 Meg ACE | Zotac RTX4090 | Asus 1000w psu | Slaw RX Viper 2 pedals | VPForce Rhino/VKB MCE Ultimate + STECS Mk2  MAX / Virpil MongoosT50+ MongoosT50CM | Virpil TCS+/ AH64D grip/custom AH64D TEDAC | Samsung Odyssey G9 + Odyssey Ark | Next Level Racing Flight Seat Pro | WinWing F-18 MIPS | No more VR for this pilot.
 My wallpaper and skins

On today's episode of "Did You Know", Cessna Skyhawk crashes into cemetery; over 800 found dead as workers keep digging.

  • Recently Browsing   0 members

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