Jump to content

F-16 Viper Cockpit in VR


Eaglewings

Recommended Posts

  • Replies 194
  • Created
  • Last Reply

Top Posters In This Topic

53 seemed about right to me looking at my stick as a reference to size in Oculus rift S. Just kind of sucks you have to change it everytime you change planes. I wish ED would make it a setting in Special tab for each plane.

Owned Modules: F-18, F-16, F-14, AV-8B, A-10c, Huey, Hip, KA-50, Gazelle, Mig 15, Mig 19, Mig 21, FC3, P-51, BF-109, C-101, L-39, F-5, YAK-52

 

PC Specs- 8700k at 5.1GHz on Asrock z370 Fata1ity k6, EVGA 1080ti SSC2, 32 GB G.Skill TridentZ, 1TB NVMe m.2 Drive for DCS with a 500gb NVMe M.2 boot drive, Oculus Rift S

Link to comment
Share on other sites

Yeah I find the viper a bit mis-scaled compared to other planes too. The F18 looks "right" as does the harrier in terms of "stick size", the Viper stick looks too small by comparison. I'd rather not have to mess with the IPD adjuster between planes.

New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1)

Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).

Link to comment
Share on other sites

Indeed, it would be a great feature to have an IPD setting that can be set specific to the plane.

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

Link to comment
Share on other sites

Yeah I find the viper a bit mis-scaled compared to other planes too. The F18 looks "right" as does the harrier in terms of "stick size", the Viper stick looks too small by comparison. I'd rather not have to mess with the IPD adjuster between planes.
My world scale ipd is set to 63.5 and the other modules look fine. Not sure how that 63.5 got there in the first place. But in the viper cockpit I do feel a bit squished. I also notice that I can't clearly see the warning lights on some of the switches you have to run during startup. This may change when I get the Reverb this week hopefully.

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

Link to comment
Share on other sites

I think it’ll be better once you we get a pilot body. But I don’t think the cockpit is mis-scaled. The F-16 cockpit is tiny. The Hornet is positivity palatial by comparison.

 

maxresdefault.jpg

 

US_Navy_050619-N-6009S-002_Aviation_Structural_Mechanic_2nd_Class_Benedict_Bautista_inspects_the_cockpit_of_an_F-A-18E_Super_Hornet%2C_assigned_to_the_Royal_Maces_of_Strike_Fighter_Squadron_Two_Seven_%28VFA-27%29%2C_in_the_hangar_bay_a.jpg

Proud owner of:

PointCTRL VR : Finger Trackers for VR -- Real Simulator : FSSB R3L Force Sensing Stick. -- Deltasim : Force Sensor WH Slew Upgrade -- Mach3Ti Ring : Real Flown Mach 3 SR-71 Titanium, made into an amazing ring.

 

My Fathers Aviation Memoirs: 50 Years of Flying Fun - From Hunter to Spitfire and back again.

Link to comment
Share on other sites

Number one way to improve readability is setting the iPd to the correct perceived pit size for each of your aircraft. F16 is miniature for me compared to f18c at 55 iPd setting. To get right scale in f16 for me I’m at 45 iPd in dcs world.

 

Shooter dependent aka depend on everyone’s real world iPd and eyes

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

Link to comment
Share on other sites

The force ipd at 55 (think that was preset waiting selection but not remember. Was/is it ? ) is good. I had not realised that the stick at default looked smaller than full size. 55 improves things for the mfds but makes legibility on the side consoles worse. Stick looks right.

Someone said 45 was good for him. Way over size but for sure cures readability issues. Not sharp but readable. HOTAS looks ridiculous.

For the moment ive compromised at 50 which i can live with and does not suffer the side consoles messing up like the 55.

There are so many permutations with vr/dcs. I do wish there were tried and tested settings provided.

 

That zoom view is good as long as i do not move the view about whilst zoomed in. Doing that makes me heave.


Edited by CobaltUK

Windows 7/10 64bit, Intel i7-4770K 3.9GHZ, 32 GB Ram, Gforce GTX 1080Ti, 11GB GDDR5 Valve Index. Force IPD 63 (for the F-16)

Link to comment
Share on other sites

FWIW, I use the default (unchecked) IPD value and am perfectly happy in all cockpits!

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

Link to comment
Share on other sites

Checking world scale is super easy in VR if you have something of scale to work with - I set my DCS scale IPD initially in the F-14 using a 1:1 printout of the front panel/ACM panel etc.

I had to reduce it a fair bit in the Viper by simply lifting my headset and comparing my TM Warthog grip and MFD.s to the in-game items, which seemed quite a bit smaller than my IRL items. I have all these items positioned identically IRL as in the sim relative to my head position.

 

The world scale is also dependant on what type of headset you are using, as when I tried an odyssey+ I had to adjust the in-game scale quite a lot from my Rift. Probably dependant on other things such as prescription inserts etc.


Edited by VampireNZ

Asus Maximus VIII Hero Alpha| i7-6700K @ 4.60GHz | nVidia GTX 1080ti Strix OC 11GB @ 2075MHz| 16GB G.Skill Trident Z RGB 3200Mhz DDR4 CL14 |

Samsung 950 PRO 512GB M.2 SSD | Corsair Force LE 480GB SSD | Windows 10 64-Bit | TM Warthog with FSSB R3 Lighting Base | VKB Gunfighter Pro + MCG | TM MFD's | Oculus Rift S | Jetseat FSE

 

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

I did a very fast test to compare. It looks like IPD 50-55 is good.

What's really needed is a per-plane world scale adjustment slider for us VR folk. This way we can dial in each plane as necessary. Since there are many VR HMDs out there, it is a better solution than the kludgy force IPD hack we're using to do the same thing. QOL :)

Derek "BoxxMann" Speare

derekspearedesigns.com 25,000+ Gaming Enthusiasts Trust DSD Components to Perform!

i7-11700k 4.9g | RTX3080ti (finally!)| 64gb Ram | 2TB NVME PCIE4| Reverb G1 | CH Pro Throt/Fighterstick Pro | 4 DSD Boxes

Falcon XT/AT/3.0/4.0 | LB2 | DCS | LOMAC

Been Flight Simming Since 1988!

Useful VR settings and tips for DCS HERE

Link to comment
Share on other sites

I really don’t understand all this talk about changing the IPD settings per plane. I mean, surely ED will have done a lot of research to make sure the default position for each one is realistic.

Now, that position may not be the users ideal, but it should be realistic.

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

Link to comment
Share on other sites

I really don’t understand all this talk about changing the IPD settings per plane. I mean, surely ED will have done a lot of research to make sure the default position for each one is realistic.

Now, that position may not be the users ideal, but it should be realistic.

 

I think the default number in the box is 64 which is the average IPD according to Oculus and HP lol. Even though we all know that the IPD setting in DCS does not refer to the distance of our pupils but to the size of the pit, I believe someone at DCS did. Why else put a number in the box that corresponds to an average IPD. It's too coincidental to not consider the possibility.

That said, the simple fact is, not all of us see each pit in VR as the same size we perceive it in the real world. For me, the A-10C has never looked right. It's either too big or too small. I could never get all of the HUD symbology to fit within the HUD to where I did not have to drastically sit up or lower my head. I believe this is because the A-10C was pre DCS world as we know it now and before consideration was given to VR.

The IPD of 51 to 55 that works for me in the Viper is HUGE in the 15. While the Hornet looks good to me at about 58. Again the 15 is an FC3 aircraft and pre current DCS world. The only recent module I have that looks odd is the Mirage. I can never get the throttle to line up while keeping everything else ok as well.

Tonight I tried 55 in the Viper and when I first got in the pit it looked to be the right height off the ground. However, when I landed it was back to the height of a golf cart lol. Oh well.

Lastly, I don't check the box to force IPD. When I've tried it, the load screen and GUI ibecame fish eyed. I simply change the number and it works.

[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.

Link to comment
Share on other sites

... Even though we all know that the IPD setting in DCS does not refer to the distance of our pupils but to the size of the pit, I believe someone at DCS did.

 

 

In actuality that is exactly what it is...but it is not your physical IPD, but if you can imagine the IPD of your digital self in the world.

SO by reducing the DCS IPD setting for example - you are effectively moving your digital DCS eyeballs closer together, giving you a smaller digital head so the world looks bigger, and vice versa.

Why it seems different for each aircraft I have no idea! But it is easy to set - just set it too small and look at your 1:1 sidestick in game and at your Warthog grip IRL...looks way too big. Now go the other way and it will look way to small - then just converge the two till you can swap between headset off and on and there is no size difference.

Anything at 1:1 scale works held at the correct position to match in-game, such as a certain display or instrument panel.

If you can't look at two different images and tell if one is different than the other....

Asus Maximus VIII Hero Alpha| i7-6700K @ 4.60GHz | nVidia GTX 1080ti Strix OC 11GB @ 2075MHz| 16GB G.Skill Trident Z RGB 3200Mhz DDR4 CL14 |

Samsung 950 PRO 512GB M.2 SSD | Corsair Force LE 480GB SSD | Windows 10 64-Bit | TM Warthog with FSSB R3 Lighting Base | VKB Gunfighter Pro + MCG | TM MFD's | Oculus Rift S | Jetseat FSE

 

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

I did not know that!

[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.

Link to comment
Share on other sites

FWIW, I use the default (unchecked) IPD value and am perfectly happy in all cockpits!

 

Me too. The stick is right size, F-16 MFD is the right size at 4 inches, my shoulders feel like they're gonna touch the side bars, everything looks like it should from what I've seen on youtube.

Link to comment
Share on other sites

Just to show how "bad" the HUD's and the MFDs' legibility is in VR, this is a Rift CV1 screenshot, obviously taken from the left eye:

 

Wow, that is how the Rift CV1 looks in DCS? I'm glad i bought the Rift S as my first VR Headset, i can see the HUD and MFD's clear and have no problems reading them.

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Here's some other cockpit to compare. HUD is readable. Also, it's actually a bit better to read than it looks on the screenshots, hard to explain. Also, leaning forward makes it easier of course, even without zooming. Except for the HUD since it's projected into infinity. Having paid 250€ for my CV1, I can't really complain though icon_redface.gif

 

attachment.php?attachmentid=218868&stc=1&d=1570544914

 

attachment.php?attachmentid=218870&stc=1&d=1570544978

1115041384_DCS2019-07-0923-46-44-92.thumb.jpg.dae6ff10e15559d6b030b4b9c6450e5c.jpg

531654432_DCS2019-06-2100-54-18-63.thumb.jpg.b82180579498ed452b53166c2bdff4ea.jpg

dcsdashie-hb-ed.jpg

 

Link to comment
Share on other sites

Yea the detail in the f18 seems to be a bit better in the model.

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

Link to comment
Share on other sites

Just to show how "bad" the HUD's and the MFDs' legibility is in VR,

 

Readability in VR using the HP Reverb is top notch; I have zero issues reading the MFDs or the HUD.

 

(I've mentioned it somewhere else before, but my go-to for readability in VR testing is the Christen Eagle II - sitting in its backseat, being able to read the speed indicator well enough means that I can read pretty much everything important in any DCS cockpit - and so far the Reverb has not disappointed).


Edited by rrohde
Clarification

PC: AMD Ryzen 9 5950X | MSI Suprim GeForce 3090 TI | ASUS Prime X570-P | 128GB DDR4 3600 RAM | 2TB Samsung 870 EVO SSD | Win10 Pro 64bit

Gear: HP Reverb G2 | JetPad FSE | VKB Gunfighter Pro Mk.III w/ MCG Ultimate

 

VKBNA_LOGO_SM.png

VKBcontrollers.com

Link to comment
Share on other sites

HP Reverb here, redability is very good, just not quite like Hornet which is great.

Cockpit is a bit too small (flight stick is smaller then Warthog) without lowering "Force IPD" value.

Overall impression is very good.

Link to comment
Share on other sites

I have an Oculus rift s. For me readability of the HUD and displays is much better in the viper than the hornet. I really struggle in the hornet and have to zoom in or lean in to read the text.

Intel i7 8700K @ 5Ghz, Aorus Z370 Gaming5, 32GB Corsair Vengeance RGB Pro 3000MHz, Nvidia 3080Ti FE, Samsung 970 NVME, Samsung 512GB EVO SSD x 2, Thrustmaster Warthog HOTAS, Saitek Rudder Pedals, HP Reverb G2, Windows 11 x64, DCS Modules = FC3, A10c Warthog, F14 Tomcat, F18 Hornet, F16 Viper, Persian Gulf, Syria.

Link to comment
Share on other sites

  • Recently Browsing   0 members

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