AstroEma Posted June 25, 2016 Share Posted June 25, 2016 Hi all, just a quick note that I do not see any noticeable improvement in the pixel density setting. I tried 1.5 and 2.0 but the gauges are still not readable. Using the Vive here on DCS 1.5.4 Anyone can confirm? Cheers, e/ Kaby Lake @ 4.6Ghz - Gigabyte Z170-D3H - 16Gb DDR4 - Gigabyte GTX 1080 G1 OC - Samsung EVO 250Gb SSD - Seagate 1 Tb HDD - HTC Vive - Rift CV1 Link to comment Share on other sites More sharing options...
illuzian Posted June 25, 2016 Share Posted June 25, 2016 I'm personally not seeing any improvement either but it could just be me. Tried in density 2.0 and 2.5 DCS Dream Wishlist: 1. Better VR Performance/Performance Overall 2. Dynamic Campaign, 3. Fully Modelled: F16, F18, F14, F15, AH64, AH1, MI24, SU27, MIG29, EF Typhoon 4. Better ATC Link to comment Share on other sites More sharing options...
Fab Posted June 25, 2016 Share Posted June 25, 2016 It seems like there is a bug, so your settings arent saved, perhaps thats why... 2. I dont know if this works on Vive or just Rift... Intel Core i7-6700K Cpu 4.00 GHz OC 4.8 GHz Water Cooled|32 GB DDR4 ram OC| Nvidia RTX 2080Ti| TrustMaster Warthog|Saitek Battle Pro Pedals | Logitec G13| Oculus Rift S :joystick: I´m in for a ride, a VR ride:pilotfly: https://www.youtube.com/channel/UCBX_-Hml7_7s1dggit_vGpA?view_as=public Link to comment Share on other sites More sharing options...
illuzian Posted June 25, 2016 Share Posted June 25, 2016 I've checked my options.lua file and it's definitely got the density set as 2.5. I mean I could be expecting too much but I'm not seeing any improvements. Rift guys says when they increased it through their SDK they could read the HUD, I literally can't see any difference and it's still unreadable as before. DCS Dream Wishlist: 1. Better VR Performance/Performance Overall 2. Dynamic Campaign, 3. Fully Modelled: F16, F18, F14, F15, AH64, AH1, MI24, SU27, MIG29, EF Typhoon 4. Better ATC Link to comment Share on other sites More sharing options...
hansangb Posted June 25, 2016 Share Posted June 25, 2016 It seems like there is a bug, so your settings arent saved, perhaps thats why... 2. I dont know if this works on Vive or just Rift... I think #2 is what needs to be confirmed. 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 Link to comment Share on other sites More sharing options...
funkyfranky Posted June 25, 2016 Share Posted June 25, 2016 I wanted to ask the same question. Tried pixel densities from 0.5 to 2.5 and did not see any effect. Are there maybe other settings (Nvidia Control panel?) that can interfere with PD? A warrior's mission is to foster the success of others. i9-12900K | MSI RTX 3080Ti Suprim X | 128 GB Ram 3200 MHz DDR-4 | MSI MPG Edge Z690 | Samung EVO 980 Pro SSD | Virpil Stick, Throttle and Collective | MFG Crosswind | HP Reverb G2 RAT - On the Range - Rescue Helo - Recovery Tanker - Warehouse - Airboss Link to comment Share on other sites More sharing options...
SkateZilla Posted June 25, 2016 Share Posted June 25, 2016 (edited) I think the Pixel Density Setting is Specific to rift, since it's part of rift's runtimes, i dont see any mention of Vive Software having it's own Pixel Density option in their tools. Will confirm. Edited June 25, 2016 by SkateZilla Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2), ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9) 3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs Link to comment Share on other sites More sharing options...
funkyfranky Posted June 26, 2016 Share Posted June 26, 2016 ^^^ :thumbup: Just supported your request. A warrior's mission is to foster the success of others. i9-12900K | MSI RTX 3080Ti Suprim X | 128 GB Ram 3200 MHz DDR-4 | MSI MPG Edge Z690 | Samung EVO 980 Pro SSD | Virpil Stick, Throttle and Collective | MFG Crosswind | HP Reverb G2 RAT - On the Range - Rescue Helo - Recovery Tanker - Warehouse - Airboss Link to comment Share on other sites More sharing options...
uri_ba Posted June 26, 2016 Share Posted June 26, 2016 (edited) I don't think the steamVR implementation matters. openVR API (assuming ED use it for the vive) reads renderTargetMultiplier value using it's steamVR driver. However, the API should allow you to set runtime value when initializing the HMD. Which doesn't seem to be the case. -- Update -- Not a real coder, but I peeked in the OpenVR a little more... it seems that there is an option to override it (but it's not very well documented). seems like the vr::IVRSettings namespace has a "SetFloat" function that takes a key and a value. so in theory you can override the "k_pch_SteamVR_RenderTargetMultiplier_Float" value... I'll just leave it here for someone that actually knows what he is doing :) Edited June 26, 2016 by uri_ba Creator of Hound ELINT script My pit building blog Few DIY projects on Github: DIY Cougar throttle Standalone USB controller | DIY FCC3 Standalone USB Controller Link to comment Share on other sites More sharing options...
M1Combat Posted June 26, 2016 Share Posted June 26, 2016 There is a setting in the steamvr.vrsettings file... See http://forums.eagle.ru/showthread.php?t=169141 for details. Any discussion of the setting not working should probably be kept here but any discussion of pixel density should probably move to that one so we can have one thread :). Nvidia RTX3080 (HP Reverb), AMD 3800x Asus Prime X570P, 64GB G-Skill RipJaw 3600 Saitek X-65F and Fanatec Club-Sport Pedals (Using VJoy and Gremlin to remap Throttle and Clutch into a Rudder axis) Link to comment Share on other sites More sharing options...
j0nx Posted June 27, 2016 Share Posted June 27, 2016 I don't see any difference at all when using the setting in DCS but with the rift SDK the change is quite noticeable. I think there may be some issues for some people with the PD slider in DCS even for those of us with a rift. ROTORCRAFT RULE GB Aorus Ultra Z390| 8700K @ 4.9GHz | 32 GB DDR4 3000 | MSI GTX 1080ti | Corsair 1000HX | Silverstone FT02-WRI | Nvidia 3D Vision Surround | Windows 10 Professional X64 Volair Sim Cockpit, Rift S, Saitek X-55 HOTAS, Saitek Pro Flight Rudder Pedals, Microsoft FF2, OE-XAM Bell 206 Collective, C-Tek anti-torque pedals UH-1, SA342, Mi-8, KA50, AV8B, P-51D, A-10C, L39, F86, Yak, NS-430, Nevada, Normandy, Persian Gulf Link to comment Share on other sites More sharing options...
Recommended Posts