Gunnergolly

I'm using mbucchia’s QVFR in fixed foveated rendering mode on the Quest 3 and it's performing well. i'm guessing that the eye tracking on the Quest Pro using DFR would allow quiet a performance boost over the Q3 due to only having to render in high res the area where the eyes are actually looking ??.

I’ve been offered a second-hand Quest Pro, my initial thought was to pass on it as i already have a Quest 3.... but the fact that it has eye tracking interests me. I’ve been using a Quest 3 for about three weeks now and with the help of mbucchia’s OpenXR Toolkit, QVFR and using Virtual Desktop with the new VDXR runtime I’m achieving very good results with it.. I’m lucky in that I have a strong intel processor and a 4090 which really allows me to push the pixels through headset and get the best out of it. I find the open design of the Quest Pro appealing as I also use VR for real world practice/training in MSFS2020. I'm thinking that the open design would allow me to easily “peep” under the goggles to look at flight logs, maps and charts. I know that the Quest Pro has a lower resolution, but using eye tracking with QVFR/OpenXR Toolkit I wouldn’t have thought that would be so much of a problem ??.... how does the QP look and perform in DCS with eye tracking enabled ??. I’d only use the Quest Pro for PCVR flight simming and the Quest 3 for other standalone VR gaming. Would i be wasting my money getting the Quest Pro as well ?... what's your thoughts ??..

I've re-read the wiki page, found the section referring to the log file..... looking at the log file it's saying that it cannot locate my configuration file. 2023-11-10 10:25:24 +0000: Trying to locate configuration file at 'C:\Users\username\AppData\Local\Quad-Views-Foveated\settings.cfg'... 2023-11-10 10:25:24 +0000: Not found There's a very slight error in the wiki page instructions or i've misunderstood them as they say to install the new user created settings.cfg in the following location :- %LocalAppData%\Quad-Views-Foveated\settings.cfg The log is saying that it is actually looking in this location:- 'C:\Users\username\AppData\Local\Quad-Views-Foveated\settings.cfg' I've moved my settings file to where the log is looking and it's all working now :).. 2023-11-10 10:36:24 +0000: Trying to locate configuration file at 'C:\Users\username\AppData\Local\Quad-Views-Foveated\settings.cfg'... 2023-11-10 10:36:24 +0000: Found option 'turbo_mode=0' 2023-11-10 10:36:24 +0000: Found option 'focus_multiplier=1.2' Hopefully the above will help somebody in the future...

I created a new settings.cfg file using notepad++ and saved it as as .cfg file in a folder called "Quad-Views-Foverated" in the following location:- C:\Users\myname\AppData\localAppData\Quad-Views-Foveated I'm using a quest 3 and trying to adjust the render resolution of the foveated area using "focus_multiplier=1.5", however it dosen't seem to be having any effect. I've also tried using the two debug commands debug_eye_gaze=1 and debug_focus_view=1 just to confirm that my settings.cfg file is actually working... but once again im not seeing anything change. What's wrong with my settings.cfg file..... where am i going wrong ???.

%LocalAppData%\Quad-Views-Foveated\settings.cfg I created a new settings.cfg file in the above location as per your wiki instructions and pasted the following entry in to said file -----> turbo_mode=0 Tested in game for about 15 minutes in the F-18C quick action mission and held a perfect 72 FPS the whole time, also the menu FPS held stable at 72 as well.... Will do some more testing later when i have more time, but seems to have done the trick...... thanks

VDXR looks sharper when compared to SteamVr and runs extremley well for me , i can even run the Apache Syrian "hot start" instant action mission at a steady 72 FPS when flying over the nearby city (on both the PICO 4 & Q3). ........................ something that i just can't achieve when using the SteamVR runtime. Unfortuanately when using VDXR i'm finding that whenever i have "Emulate quad views foveation support" enabled (in SteamVR settings) i keep having constant frame drops/heavy stuttering when in game....... if i turn it off runs smooth. Fixed QVFV works fine when using the SteamVR runtime. Just wondering is this a known problem that using fixed foveated rendering mode with VDXR causes bad FPS drops/stuttering ... or is it just my system playing up ?. I'm also having FPS instability whenever i'm in the main DCS menu/mission builder screens. Thanks for you efforts mbucchia VDXR is really good...

Have been flying the F-16, the flashes start whenever i turn the TGP on, as soon as i turn it off ....... the flashing stops.

Poor little F-15's

Just mapped one of my throttle hat switches to the Scan Zone up/down keybinds and its working perfectly in game..... i'm sure i tried that last night and it didn't work ????. Nevermind it's working now :).. Thanks...

Do i need to add the above .lua code in to a file somewhere or has it already been included ?. I will fire up DCS soon and try mapping them again....

Never occured to me to press the middle MFD button !!!. I'm going to take RaptorFighters approach and map the keybinds to my throttle hat switch to control the radar elevation. In the "control setup" menu i've already tried mapping my hat switch to the Scan Zone up/down commands.... but that didn't work. When i get the chance i will try mapping my hat switch to the OSB 18, 19 & 20 MFD buttons. on the center display... hopefully that will work. Thanks for the replies and enjoying the F-22 mod

Silly question, but how do you control the radar antenna elevation when using the enhancement mod ?... I can control the default Grinnelli F-22A radars elevation ok using either the OSB 18 or OSB 20 buttons on the center MFD. However since i have installed the "enhancment" mod ...... pressing the OSB 20 button causes the antenna elevation to go fully up..... and pressing the OSB 18 button causes the antenna to go fully down...... nothing in between I have deleted all axis/bindings so there should be no other control conflicts... Any guidance much appreciated .... thanks.

Thanks MAXsenna. I have completed both the MSSR windows voice training exercises where you have to dictate sentences and have also trained all the VIACOM keywords.... with a high recognition success rate. For the most part my computer has no problem understanding me as i am a native english speaker with no real accent. VIACOM works fine when i'm not in a mission, sometimes i have noticed that there can be a three second delay between me speaking and VIACOM responding when it does recognise what i'm saying when playing a mission. Very fustrating as it works perfectly and pretty much understands everything i say when either using VIACOM from my desktop or when i'm in the DCS menus... :cry: ???...

If i run VIACOM just on my desktop or in the DCS menus it recognises pretty much everything i say first time. As soon as start a mission it's very hit and miss, sometimes it works perfectly for a while, however most of time it defaults to "Jiroft Airport" no matter what i say or does not even respond at all..... even though i am getting good MIC levels. I have tried reducing the MIC input levels just in case it was to high causing distortion of my voice. If i then temporary pause the mission and speak it recognisies what i have just said ok. This morning i have tried:- 1) A DCS repair and removed the leftover VIACOM files. 2) Reset the settings, profile and LUA code from the "configuration window". 3) Deleted my export file and also the VIACOM folder from my Saved games "Script" folder. 4) Downloaded a new copy of VIACOM and installed it into my Voice attack "APPS" folder. After i had done the above steps i started DCS up and played two missions and it worked perfectly on the two missions that i tried and then shutdown my computer thinking that i had sorted the problem. Just tried playing another mission this afternoon and it's acting up again ??. Anybody think of anything else i could try. Thanks..

Unfortunately i have managed to knock and snap the LED off on my left FCU !!. I soldered a standard type LED in it's place to see if it would work, unfortunately the HMS now loses tracking of the FCU LED beyond 10cm. Does anybody know what type of LED's the PointCTRL FCU's use so that i can try and source a replacement here in the UK. Thanks....

Thankyou :thumbup:

My SimShaker updated last night to 1.3.9.1 and i am not seeing the JF-17 listed in the "Model" listings and it's not working in game...... any ideas ?. Thanks. edit.... How do i force SimShaker to update to 1.3.9.2 ?

Last night i had no problems maintaing a steady 40 FPS having both the radar display and the IR video feed on whilst i figured out how to use the CR-701IR air to ground missile. After about twenty minutes of playing i started to notice the slowdowns, turned the ground radar off and FPS went back up to 40. Up to now i have been doing mainly air to air stuff and have not noticed any FPS problems with the A/A radar. I'd imagine that the A/G radar will be a performance hog, i will have a play around later with the A/G radar.

I'm playing in VR (valve Index) and experiencing the same thing, smooth for a while and then starts juddering as my FPS drops from 40 to 27. Switching the air to ground radar display off restores the FPS back to 40, so it seems to be related to that.

+1

Please would you consider adding SimShaker support for the newly released JF-17 ?. Thanks ...

Trying to follow the above video using a designated target point to find the targets general location in AUTO mode and then switching to CCIP during the dive. I have PROG 1 set as CCIP as per the video, everything appears to be working, i press the undesignate button and the bombing mode then switches from AUTO to CCIP. My dive angle is about thirty degrees and when the CCIP pipper is over the target i press the weapon release button and the bomb fall line/pipper in the HUD flashes.... but no bomb release ??. I have played the above mission using CCIP mode only and the bombs dropped ok ??. Please could somebody point out why my bombs are not being released when switching from AUTO to CCIP mode ??. Thanks.

Ok thanks. I don't think my motherboard (ASUS Z370-F) even has bluetooth, no mention of it in the manual so will definitely have to purchase a BLE 4 dongle.

Haven't used my FSSB R3 Warthog in about four years now and the recent release of the Viper has rekindled my interest. Will the new F16SGRH grip work ok with my original R3 base, i understand that i will not get all the functionality however i'm only really interested in using the default F-16 assignments. I'm reading that the new F16SGRH uses bluetooth and not the wired USB connector ??.... is this a reliable ??.

Thanks again for your suggestions guys, two days a go I was seriously contemplating buying one of the two cards that I linked in my first post. Having thought about it I'm probably just going to hold off for now and be be patient, i'll wait and see what AMD or Nvidia have to offer next year. The Index is performing well enough with MSAA turned off, the shimmering is irritating at times but just going to have to live with it for now.