mbucchia Posted January 3 Author Posted January 3 8 hours ago, FupDuck said: While I have you here, is it possible to use the QVFR tool only for turbo mode? I've heard you can disable it for certain programs using the config file, but this doesn't work for DCS. It's that still the case? I replied in the other thread. I wasn't banned, but this account is mostly inactive and not monitored.
jnr4817 Posted January 4 Posted January 4 15 hours ago, FupDuck said: To answer your question @mbucchia, the eye tracking check box doesn't seem to do anything. I have a Quest Pro, and eye tracking stays enabled whether this box is checked or not (as long as it's enabled in the headset and link software). I tested it using the debug feature, and just by looking at the sun in game. It's very easy to tell when eye tracking is enabled. The other box for QVFR must be checked in order for your software to work. Without this checked, it's the same as if QVFR is not installed. I hope this is helpful info for your edits to the wiki. While I have you here, is it possible to use the QVFR tool only for turbo mode? I've heard you can disable it for certain programs using the config file, but this doesn't work for DCS. It's that still the case? Thanks! Why are we wanting to use turbo mode all of the time? What is it doing that helps so much? Is it hardware dependent. I have top grade system 9800x3d,4090, 64g, ssd, etc and find turbo mode causes me stutters. 14 hours ago, sleighzy said: Update to my earlier comment: The Quad Views Companion app v1.0.14 added support for configuring the height and width of the focal area for fixed foveated rendering (non-eye tracked headsets) a few days ago. https://github.com/TallyMouse/QuadViewsCompanion/releases Can you post a pic of your config file so I can see what was added to the QV companion? I am running a G2 right now and added my own lined for the fixed regions. I'll be getting a crystal light tomorrow, god willing UPS doesn't mess things up. Attached is my config, I added the lines 6-9, which weren't present when I installed QV a few months ago. I also dont remember seeing them in the companion app. 9800x3d|64 GB 6200|4090|m.2 x2 http://www.blacksharkden.com/ Come join us!
FupDuck Posted January 4 Posted January 4 8 hours ago, mbucchia said: I replied in the other thread. Sorry, which thread do you mean? 1 hour ago, jnr4817 said: Why are we wanting to use turbo mode all of the time? What is it doing that helps so much? Is it hardware dependent. I have top grade system 9800x3d,4090, 64g, ssd, etc and find turbo mode causes me stutters For me, I get microstutters when I don't have turbo mode enabled. This is basically the main reason I still use OpenXR toolkit. "...Iiiiiiiiiii just wanna fly; put your arms around me baby, put your arms around me baby" - Sugar Ray RTX 3090, Ryzen 7 5800X3D, MSI MPG B550 Gaming mobo, 64 GB DDR4 RAM, 970 EVO Plus NVMe M.2 SSD 2TB game drive, VKB STECS Standard throttle, Winwing Ursa Minor Fighter stick, Oculus Quest Pro via ersatz link cable, Standalone DCS. VR only.
Thanatos31 Posted January 5 Posted January 5 Hi team, I have a frustrating issue with DCS , Pimax Crystal and Dynamic Foveated Rendering / Quadviews & Eye tracking. My problems started after a recent patch after which I noticed that Quadviews/Eyetracking wasnt working anymore. Everything was rendered and performance was low. I had the typical setup: Pimax XR , OpenXR tools ( disabled) , Quad Views and Quad View Companion. After watching a video about how Quadviews are now native in the Pimax Play app (PP) I switched to the Pimax OpenXR playtime via PP and used the integrated DFR - While it worked , the quality was really not what I was looking for ( rendered area too small, outside area to low resolution being very distracting) THIS is where my problems started - I wanted to get back to the initial setup PXR,QV,QVC. Following problems: Sometimes eye tracking works, sometimes it doesnt. I cannot consitently properly recreate the steps to make it work - one consistent thing is that the Calibration via PP doesnt work ( it takes me through the circles, but it can save / identify my pupils) The frustrating thing is - it sees my pupils due to IDP settings, and it works...randomly after clicking around like the primate that I am and somehow it works (combinations of turning everything off, restarting PP, etc.) The layers are checked and are in the right order with the Layer tool. I've deleted the PIMAX folder in local/appdata without it working. What am I missing? I think somehwere there's a config that has some sort of false ID and doenst start up the right software.... Is there a log I can post or anything I can share with you that could solve this and make me have dynamic eytracking and foveated rendering ?! Come fly with us : https://discord.gg/tawdcs TAW CJTF 13 - EU TZ MilSim Squadron Ryzen 5 5600X | 32GB DDR4 3733| ASUS Radeon RX 6700 XT | ASrock B550 Phantom Gaming 4 | HP Reverb G2 | Thrustmaster Warthog Throttle , F16 & F18 grips , TFRP Rudders | Win 10
Panzerlang Posted January 5 Posted January 5 2 hours ago, Thanatos31 said: Hi team, I have a frustrating issue with DCS , Pimax Crystal and Dynamic Foveated Rendering / Quadviews & Eye tracking. My problems started after a recent patch after which I noticed that Quadviews/Eyetracking wasnt working anymore. Everything was rendered and performance was low. I had the typical setup: Pimax XR , OpenXR tools ( disabled) , Quad Views and Quad View Companion. After watching a video about how Quadviews are now native in the Pimax Play app (PP) I switched to the Pimax OpenXR playtime via PP and used the integrated DFR - While it worked , the quality was really not what I was looking for ( rendered area too small, outside area to low resolution being very distracting) THIS is where my problems started - I wanted to get back to the initial setup PXR,QV,QVC. Following problems: Sometimes eye tracking works, sometimes it doesnt. I cannot consitently properly recreate the steps to make it work - one consistent thing is that the Calibration via PP doesnt work ( it takes me through the circles, but it can save / identify my pupils) The frustrating thing is - it sees my pupils due to IDP settings, and it works...randomly after clicking around like the primate that I am and somehow it works (combinations of turning everything off, restarting PP, etc.) The layers are checked and are in the right order with the Layer tool. I've deleted the PIMAX folder in local/appdata without it working. What am I missing? I think somehwere there's a config that has some sort of false ID and doenst start up the right software.... Is there a log I can post or anything I can share with you that could solve this and make me have dynamic eytracking and foveated rendering ?! I had similar grief with the eye-tracking calibration, in my case it turned out to be the USB connections being inserted directly into the mobo. Once I redid everything using the powered Pimax hub it all worked correctly. I've read conflicting reports however...some people have the opposite experience. I have zero idea why that would be, other than mixing up blue and red slots on different brands and versions of mobos with different USB specs and even incorrectly coloured USB slots or simple user error. So, try the Pimax hub, investigate your mobo's slots and what priority is given to each and etc.
Thanatos31 Posted January 6 Posted January 6 thanks! I believe we found the solution - It was a conflict with tobii software Come fly with us : https://discord.gg/tawdcs TAW CJTF 13 - EU TZ MilSim Squadron Ryzen 5 5600X | 32GB DDR4 3733| ASUS Radeon RX 6700 XT | ASrock B550 Phantom Gaming 4 | HP Reverb G2 | Thrustmaster Warthog Throttle , F16 & F18 grips , TFRP Rudders | Win 10
eFirehawk Posted January 14 Posted January 14 On 1/6/2025 at 8:29 AM, Thanatos31 said: thanks! I believe we found the solution - It was a conflict with tobii software @Thanatos31 Same here... updated Pimax Play and quad views in DCS is dead. What conflict was that exactly? How did you solve it? I tried disabling Tobii in the Windows Services to no avail. Pentium II 233Mhz | 16MB RAM | 14.4kb Modem | 1.44MB Floppy Disk Drive | Windows 3.1 with TM Warthog & TrackIR 5
subroutine Posted January 15 Posted January 15 Does anyone know how to set up quad views for turbo mode only? Openxr toolkit turbo mode crashes DCS when removing the headset, which is well known and quad views itself returns lower fps when enabled on my system.
slughead Posted January 15 Posted January 15 There used to be a way by unadvertising DCS in the QV config file. Scroll up to find details. But I am told this no longer works. The other option is to switch to Virtual Desktop and go wireless, which is great, and that solves the headset removal problem; plus, you can still use OpenXR Toolkit with it. Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
milit Posted January 16 Posted January 16 (edited) 17 часов назад, subroutine сказал: Does anyone know how to set up quad views for turbo mode only? Openxr toolkit turbo mode crashes DCS when removing the headset, which is well known and quad views itself returns lower fps when enabled on my system. Read here https://github.com/mbucchia/Quad-Views-Foveated/wiki/Advanced-Configuration Shortly: u have to create config file in location mentioned in link and set turbo_mode = 1 in it. With Oculus Quest 3 it works fine. With OXRToolkit uninstalled. Edited January 16 by milit =WRAG=345 R7 5800X @ 4,8 GHz; DDR4 64Gb RAM (+32Gb swap); Radeon RX 6800 16Gb; 3840x2160; Oculus Quest 3; Win10-64
gonvise Posted January 16 Posted January 16 19 hours ago, subroutine said: Does anyone know how to set up quad views for turbo mode only? Openxr toolkit turbo mode crashes DCS when removing the headset, which is well known and quad views itself returns lower fps when enabled on my system. You can prevent DCS from closing when removing the glasses by covering the sensor, I have it like this and without any problem.
subroutine Posted January 17 Posted January 17 (edited) Thanks for your replies. I couldn't get turbo mode working with quad views unless it was active but with these settings- turbo_mode=1 # Fixed Foveated rendering settings for fallback when eye tracker is not available. #0.5 0.45 horizontal_fixed_section=0.5 vertical_fixed_section=0.7 [Oculus] #0.4 1.1 peripheral_multiplier=0.6 focus_multiplier=1.1 it actually runs much better then when I last tried it and the image transition isn't too obvious . Stuttering is almost gone and fps are higher. That's with a 5800x and 3080ti. Edited January 17 by subroutine
milit Posted January 17 Posted January 17 @subroutine, try debug_focus_view = 1 and u ll be able to tune fixed sections and smoothen_focus_view_edges precisely. Also my config eats focus_multiplier=1.2 without fps loss. Set debug_focus_view to 0 after tuning. =WRAG=345 R7 5800X @ 4,8 GHz; DDR4 64Gb RAM (+32Gb swap); Radeon RX 6800 16Gb; 3840x2160; Oculus Quest 3; Win10-64
subroutine Posted January 17 Posted January 17 Increasing that multiplier lowers the FPS too much on my system. turbo_mode=1 [exe:DCS] unadvertise=1 The above does work if Quad Views is enabled in the DCS VR settings to activate turbo mode only.
FupDuck Posted January 20 Posted January 20 On 1/17/2025 at 11:35 AM, subroutine said: Increasing that multiplier lowers the FPS too much on my system. turbo_mode=1 [exe:DCS] unadvertise=1 The above does work if Quad Views is enabled in the DCS VR settings to activate turbo mode only. Really? That would be interesting, because the FAQ that mbucchia wrote said it doesn't work with DCS. He also did say he hadn't tried in a while though... "...Iiiiiiiiiii just wanna fly; put your arms around me baby, put your arms around me baby" - Sugar Ray RTX 3090, Ryzen 7 5800X3D, MSI MPG B550 Gaming mobo, 64 GB DDR4 RAM, 970 EVO Plus NVMe M.2 SSD 2TB game drive, VKB STECS Standard throttle, Winwing Ursa Minor Fighter stick, Oculus Quest Pro via ersatz link cable, Standalone DCS. VR only.
slughead Posted January 20 Posted January 20 4 minutes ago, subroutine said: It definitely works on my system. I'm almost tempted to reinstall it on my machine to confirm. Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
FupDuck Posted January 20 Posted January 20 2 hours ago, slughead said: I'm almost tempted to reinstall it on my machine to confirm. Same here. Maybe I'll give it a go at the weekend.... "...Iiiiiiiiiii just wanna fly; put your arms around me baby, put your arms around me baby" - Sugar Ray RTX 3090, Ryzen 7 5800X3D, MSI MPG B550 Gaming mobo, 64 GB DDR4 RAM, 970 EVO Plus NVMe M.2 SSD 2TB game drive, VKB STECS Standard throttle, Winwing Ursa Minor Fighter stick, Oculus Quest Pro via ersatz link cable, Standalone DCS. VR only.
ry-ballz Posted February 6 Posted February 6 If I check the Use Quad View setting in DCS I get a black screen loading into any mission. This started today out of nowhere and I have no idea how to fix it. Pimax Crystal. Previously I was using the openXR toolkit and pimaxXR which I did following a Pimax guide when I got the headset in 2023. But I do not have any of that installed any more. In the Pimax software I've got pimax openXR Quadviews and pimax central priority rendering checked. OpenXR Runtime shows Pimax OpenXR. I literally used the headset earlier today. Hopped on tonight to try out something quick and wasn't able to load into any missions. Black screen and when I alt-tabbed I got a DCS has crashed message. I've played around with a bunch of settings, but the only thing that seems to work is unchecking the Use Quad View settings. But I definitely feel like I've lost frames.
Dentedend10 Posted February 6 Posted February 6 5 hours ago, ry-ballz said: If I check the Use Quad View setting in DCS I get a black screen loading into any mission. This started today out of nowhere and I have no idea how to fix it. Pimax Crystal. Previously I was using the openXR toolkit and pimaxXR which I did following a Pimax guide when I got the headset in 2023. But I do not have any of that installed any more. In the Pimax software I've got pimax openXR Quadviews and pimax central priority rendering checked. OpenXR Runtime shows Pimax OpenXR. I literally used the headset earlier today. Hopped on tonight to try out something quick and wasn't able to load into any missions. Black screen and when I alt-tabbed I got a DCS has crashed message. I've played around with a bunch of settings, but the only thing that seems to work is unchecking the Use Quad View settings. But I definitely feel like I've lost frames. PimaxXR has not worked for me in any sim yet (DCS - black screen or ACEvo - view rotated 180 degrees). I’ve always had to return to mbucchia’s Pimax OpenXR Alienware Aurora R10, Ryzen 5800X3D, RTX4080, 32GB RAM, Pimax Crystal, Winwing F18 throttle, VKB Gunfighter F14 Stick, VKB Modern Combat Grip, Logitech Rudder pedals, DOF Reality H3
sleighzy Posted February 6 Posted February 6 (edited) 14 hours ago, ry-ballz said: If I check the Use Quad View setting in DCS I get a black screen loading into any mission. This started today out of nowhere and I have no idea how to fix it. Pimax Crystal. Previously I was using the openXR toolkit and pimaxXR which I did following a Pimax guide when I got the headset in 2023. But I do not have any of that installed any more. In the Pimax software I've got pimax openXR Quadviews and pimax central priority rendering checked. OpenXR Runtime shows Pimax OpenXR. I literally used the headset earlier today. Hopped on tonight to try out something quick and wasn't able to load into any missions. Black screen and when I alt-tabbed I got a DCS has crashed message. I've played around with a bunch of settings, but the only thing that seems to work is unchecking the Use Quad View settings. But I definitely feel like I've lost frames. Are you still using the OpenXR Toolkit? If so then disable it. It doesn't work with PimaxPlay Quad Views as the OpenXR Toolkit expects 2 views, but will be getting 4. EDIT: I see you've said you've uninstalled the OpenXR Toolkit, worth double checking though as this was definitely a cause of black screens based on your description. You can also install https://github.com/fredemmott/OpenXR-API-Layers-GUI to see if it's still there, or are any other API layers that could be causing problems. If the game is crashing then create a new post along with your DCS log file as that is unrelated to this post. Edited February 7 by sleighzy AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
mbucchia Posted February 7 Author Posted February 7 This is all explained here: 1 I wasn't banned, but this account is mostly inactive and not monitored.
ry-ballz Posted February 7 Posted February 7 5 hours ago, sleighzy said: Are you still using the OpenXR Toolkit? If so then disable it. It doesn't work with PimaxPlay Quad Views as the OpenXR Toolkit expects 2 views, but will be getting 4. EDIT: I see you've said you've uninstalled the OpenXR Toolkit, worth double checking though as this was definitely a cause of black screens based on your description. You can also install https://github.com/fredemmott/OpenXR-API-Layers-GUI to see if it's still there, or are any other API layers that could be causing problems. If the game is crashing then create a new post along with your DCS log file as that is unrelated to this post. I don't have it installed any more. I ran that tool and nothing shows up at all
sleighzy Posted February 7 Posted February 7 32 minutes ago, ry-ballz said: I don't have it installed any more. I ran that tool and nothing shows up at all Raise a new post and attach your DCS log to that after replicating this again. Folk can have a look into reasons why and help troubleshoot. AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
Rufuz64 Posted February 8 Posted February 8 Uninstall is not enough. I had to reset to dafault and then uninstall! AMD Ryzen 5800X3D / Nvidia RTX 4090 / 64 GB RAM / Pimax Crystal QLED OFS openflightschool.de
Recommended Posts