Thanks for the brilliant video, even though i'm nearly a year late! Just installed and tested on my quest3 last night and wow, what a difference in stable performance! Thanks for this bud! (using the fixed FOV)
Thank you for your very kind words. I am happy to hear that I was able to help you out! There’s so much out there and it seems like it changes monthly! Happy flying.
Great video ! I’ve been waiting on this I think this kind of video is needed because a lot folks aren’t tech savvy like myself we just want to play the sim and enjoy our hardware. I went back to Dfr/fvr from QVFR because I felt like my eye tracking wasn’t keeping up or felling to perform right. I think folks mentioned that in the Varjo discord a few days ago. DFR seems to work better on my rig but as you showed in this video that QVFR is better between the too. I’m gonna go back to QVFR and try this again. I have read over the wiki so many times but prefer tutorial videos like yours I’m just scared I’m gonna mess something up. A few Varjo folks are having issues and have to rollback DCS versions to get it running and I don’t want to be in that group. Thanks Str][ker !
Hi! First of all thank you for your kind words. I'm happy to hear that I was able to help you out. I've bene much the same.. videos can be more helpful at times than reading a wiki or instructions. One important thing to note is that the QVFR is very much a beta for the Varjo headsets and if you don't need it because you have something which is working, then there's no need to install it. There are other headsets now supported and I wanted to make a new video so that people aren't landing on the old video all the time if they are looking for installation help. In your situation, it may be worthwhile waiting for a more stable and tested release. I actually ran into an issue with it (which you may have seen on the Varjo Discord). We seem to have identified the cause but not yet a solution to the issue. What I and a couple of the other people have noticed is that the Varjo headset is not passing the eye tracking to the software which mbucchia wrote and so we are not getting eye tracking plus we are getting a lower resolution so the display looks pretty bad in the headset. The workaround is to exit DCS, restart it, and hope it loads correctly. Sometimes I have had to do this a few times until it works. The older Varjo Foveated software works flawlessly but you don't get to use Open XR Toolkit and a few other configurations which would be nice to have (but they aren't essential). I'm going to roll back to Varjo Foveated for daily use until we can come up with a solution. I'll still use QVFR to help troubleshoot the current issue. The good thing is that it's all super easy to install and uninstall (I've done this several times so far). If you do go back to VFR, make sure you disable DCS in the Open XR toolkit via the desktop companion app! There is that other issue which you mentioned and that's something odd which I don't think anyone has been able to nail down. It seems limited to a couple people so far and they need to roll back to older DCS versions to get things working which is not really a solution in the end if you play online or need the updates and fixes to aircraft for single player.
@@StrIIker-TV - I appreciate your knowledge and troubleshooting skills and helping the community. Your right it is easy switching between the two thank god for that and mbucchia. I think today I will just stick to VFR because it seems to work better, I just want to fly the sim today. But, I plan to switch back to QVFR and play around with the Config. settings, thanks so much for showing the process in the video it really helped me gasp it better. Have a Great sunday and Thanks again !
Hi, using a Quest Pro in 2024, I can tell that there is some sort of fixed foveated rendering happening, (there is a clear border near the bottom of my vision), but definitely not eye-tracked. Followed all the steps, although I will say that in 2024 some of the Oculus interfaces are different. Any clue why I might not be getting eye tracking? I turned on, calibrated and tested eye tracking successfully in the headset, but the foveated rendering is fixed in DCS. Thanks!
Hmm, I am not sure why it would not be working. I assume that you are using the multi-threaded version of DCS and XR Toolkit? Also, I have heard of some issue with the quest software and DCS not working properly. I am not sure if this is what your challenge is but Meta made some kind of changes to their software for XR implementation and DCS needs to make a few changes for it to work again. Failing that, you should be able to track down mbucchia on Discord or the DCS Forums to see if he has any insight.
Thank you great video! Quick question , you shown with and without quad view, how do you activate/ deactivate it? Is only by launching/ or not open vr tool kit before dcs?
Hi! Thank you for the compliment. For the video, I just uninstalled the quad view software. There is another way to disable it in the OpenXR stack via steam. You can click into steam and it shows all XR software loaded ( can't recall the exact path but I can grab it if you want). You can disable it there instead of uninstalling it. There is a tool to also see the layers loaded and you can disable them with it and you can change the order in which they load (important for some XR stuff to work) github.com/fredemmott/OpenXR-API-Layers-GUI
Top, hope your comment will help other users. As for me, I am not using Steam but I found how to disable quad view in openxr tool kit menu ( viewed only through the lenses of the headset ). I followed all the step, was working as advertised but when launching dcs this morning... it doesn't in VR. If I disable openxr tool kit it does. If I launch in safe mode it does too. I will have to investigate what in openxrtoolkit prevents dcs to launch in VR mode...
I’m happy that this helped out! Hopefully we continue to see more headsets include eye tracking which would encourage more games to support eye tracking.
thanks for the video! how should be setted the % in quad views, I mean the center and the peripheral view.. It's not really clear to me how this % works and if there is a "ratio ule" that should be followed.. thanks! :)
Hmm, the quad views peripheral / focus setting numbers are different from the Varjo Foveated software (I use the Varjo Foveated because of issues which the Quad Views has with the Varjo Aero). I know it has been discussed a lot on the Varjo Discord in the past but I don't recall what people liked to use. The default should generally be fine but you can always hop onto the Varjo Discord and ask in the DCSWorld Channel for suggestions even if you don't have a Varjo headset. Make sure you have a look at the QuadViews Wiki as Mbucchia discusses it there as well. Here's the specific page for the config. github.com/mbucchia/Quad-Views-Foveated/wiki/Advanced-Configuration
Hmm, after re-installing windows and DCs again, I can't get the FOVeated to work anymore for some reason. Installed Open XR first and then Foveated. but no changes in the headset.
Does anyone experiencing the same after the last quest pro update? I have my foveated rendering "windows" shifted down. Is there any way to reset it to the moddle of the screen?
Quad view is not working. I installed it afyer OpenXR toolkit but it is complayning about OpenXR toolkit. I installed it after OpenXR toolkit but still gives me an error. Not sure why.
Is your headset compatible with Quad View? Did you clear the settings in OpenXR Toolkit by enabling safe mode? There are instructions specific to each headset in the Wiki. Did you follow those instructions to the letter? There are troubleshooting steps mentioned in the wiki as well. Have a look and check the log file to see what kind of error you are getting and see if there is a resolution to it. github.com/mbucchia/Quad-Views-Foveated/wiki
@@StrIIker-TV I followed the video. Is Quad View supposed to give you an interface when running? On another video, you can turn a debug mode that blacks out everything except what you are looking at. I turned on debug mode, went to DCS, hit default on OpenXR, came out, turned debug off, installed Quad View but other than give me a warning about Open XR, it does nothing I can tell. Crystal Sim looks great still. I just xant seem to run it in that mode.
Per the compatibility list on the Quad Views Foveated Wiki, yes, the Quest Pro is supported for Dynamic Foveated Rendering.. github.com/mbucchia/Quad-Views-Foveated/wiki You can use it without the Open XR Toolkit if you wish. The OXRTK adds functions such as post render shading enhancements. Quad Views Foveated Rendering and Open XR Tool Kit are two separate things and can be used together or separately.
Could I first ask which headset you are using? I would also like to confirm that you have a supported headset from the list on the Wiki. Secondly, ensure that eye tracking on the headset itself is enabled (for example on the Varjo Aero and PiMax Crystal and others, you need to enable it within the headset software) and then in any other secondary software (Pimax XR Runtime for example). Make sure that you did follow the Wiki instructions AND the headset specific instructions. Lastly, if I'm not sufficiently helpful here, you can hit up the OpenXR ToolKit Discord channel and get some expert help there! discord.gg/WXFshwMnke
The Pimax Crystal. When following the instructions I am directed to tick the eye tracking box, but none is available. I suspect I might need a Beta version of the software which I don’t have and don’t know where to download it
You are correct I think regarding the Beta software. I had found some reddit posts from about 30 days ago pointing out that eye tracking on the Crystal was in Beta. I was going to mention this in my response but deleted it as I figured should be ready by now. Let me see if I can find out more for ya. There are some Crystal users on the Varjo discord. I'll ask there.
So first off.. I just noticed that you mentioned which headset you have in your comment and then I go and ask what headset you have.. LOL.. My brain didn't process that for whatever reason! Secondly, I did look this up and it looks like you will have to wait as the Pimax software is in closed beta. I did ask others about the availability and will update here if I hear back. The last update was over a month ago (June 30) on the Pimax website... pimax.com/crystal-notice/ Eye Tracking/Auto-IPD/DFR Firmware Release: We recently released the beta version of our firmware to our beta group and a few KOLs. The feedback we received indicates that the firmware has delivered significant performance increase. However, during this testing phase, we discovered a minor issue with the eye-tracking feature, which is causing glitches. Our main objective is to enhance the accuracy of this feature before making it accessible to the general public. We expect to release the improved version shortly.
Unfortunately the Quest 3 does not have eye tracking and therefore the dynamic foveated rendering will not work in it. I think the pro line has the eye tracking though.
I tried this with a Quest Pro and DCS does not load in VR mode. Only the 2D version loads. And the headset only displays the "DCS Loading" logo and not loading in VR mode. Any ideas? I followed the procedure to the letter and I have tried it multiple times with the same results. Once I uninstall the Quad-view app, then DCS is back to normal and loads in VR mode.
I have asked about this issue on the OpenXR Toolkit Discord channel for ya. Quick question while I wait to hear back.. Can you confirm that you are running the DCS multi-threaded executable (this issue sounds similar to what happens when you are not using the multi threaded exe)? For my DCS shortcut properties, here's my Target The focus being the path to DCS.exe as if you don't see bin-mt then you are on the wrong executable..: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR. and Here's my Start In: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt" EDIT: Also the log file might help identify the issue.. Check the Troubleshooting part of the Wiki and see if the log file helps
I heard from mbucchia and he is suspects “Their issues is probably they don't have the vc_redist installed. These are all instructions on the website”. I know you said you followed the instructions. Could you double check this? If not, your best bet will be to hop onto the Discord and see about getting some assistance there. He and the others do a great job helping. discord.gg/x74n8TCB
@@StrIIker-TV Thank you so much for looking into this. I appreciate the help a lot. I did install the VC_redist. I am running the multi-threaded version of DCS. I will post at the discord you linked. Thanks again.
@@StrIIker-TV I finally got it to work. At least I can now start DCS in VR mode with the Quad-Views installed. Now I have another question if it's ok with you, How do I know that Quad-Views DFR is actually working? My monitor mirror display only shows a single view of the game and not four. I also can't tell inside the VR headset (quest Pro) in DCS if it's working. Meaning I don't see any pixelation on the side or anything like that. I am sure I followed all instruction to the T. Any advice? Thanks.
@@emvill4520That's great news! A VERY simple way is to sit in the cockpit in a busy area where your frame rate is not maxed out. Pull up the in game FPS counter (I think the default key binding is . Stare straight ahead and see the FPS line stabilize.. Now glance with your eyes only down into the cockpit. Stare for two seconds or so and then look back up.. you will see that FPS graph change while your gaze was in the cockpit. See this video here for a demonstration (Linked to the proper timestamp). ruclips.net/video/8G_gW4DK154/видео.html That is a clear indication that the eye tracking is working with foveation. There are also log files which you can look at. Also refer to this page and note the location of the log file for the quad view foveated and see if the log file shows what it should.. github.com/mbucchia/Quad-Views-Foveated/wiki/Troubleshooting I personally like to see in game demonstrations that the eye tracking and foveation is working so I always use the method in the cockpit.
On the G2 FFR makes all the peripheral views look extremely aliased (Jaggy). Is it because it isnt a eye tracking headset? I wouldn't even try your graphics settings they are so bad. Those look like what I did 6 years ago when I was just guessing, lol. The VR settings that DCS gives you are a much better place to start. Many of the higher setting you use dont actually make the game look any better in VR. Simply wasting a lot of resources. Making it artificially dark doesn't make it look better, lol. DCS tells us to use 2.2 for a reason. You can get 90fps with your rig why on earth would you bother with reprojection? You need to do less video making until you know what you're doing. People that watch this video are going backwards.
Hi! Yes on the G2 FFR will make the peripheral look lower resolution. The intent on FFR is to keep the sweet spot and area around it looking good while lowering the peripheral resolution to give a performance bump. I tried FFR on my Reverb G2 but never really felt that it helped too much. I didn't notice much image degradation though so probably the peripheral multiplier was not too low. In my opinion, foveated rendering is really only useful for headsets with eye tracking for the very reason you mentioned. You could try adding the settings.cfg and adjust the peripheral multiplier so that it's not reducing the resolution so much. The graphics settings I use were really just me trying to push my system to get to a performance level which I am happy with. When I bought my new CPU and graphics card, I decided to max it all out to see how things looked. It wasn't too bad to be honest but I ran into some issues with DCS swapping to/from the page file (hence the medium textures). It was a far cry better than what I was experiencing on my 5 year on Intel CPU and 3090ti GPU. Part of the issue is that if I drop settings too much, the game mirror (which I use to record videos) will look worse. I am trying to strike a balance for producing a nice video and getting what for me is acceptable performance in the headset. If I wasn't shooting video, I could drop MSAA down (and probably will set it to 2x which I thought I had already). The clouds I could certainly drop from Ultra because that's pointless to have maxed etc. I honestly don't feel the difference between 90 FPS and 70 or 60 FPS. If I focus on it I may be able to but it's honestly not the goal for me. So, it's a combination of what works for me personally and what I need for video recording. I'm also not making anything artificially dark. I have used a lower gamma because the panels in the Varjo are not anywhere as good as the HP Reverb G2 when it comes to blacks. So, if I run at 2.2 all the time, when I hop into a night mission, it looks horrible to me. It's like I am in a fog. It was a big shock and disappointment for me coming from the G2 when I fly night missions. I should probably just create preset with different gamma and other settings I guess but I know that would probably forget to switch before each mission type and have to drop out to switch. I make most of the videos first and foremost for myself. I like to watch them while on the treadmill and see what I did wrong or relive some fights etc. I make the instructional videos to help people out because I've been in their spot before, full of questions and looking for answers. I think that the videos are generally helpful, if not the best looking so I'm happy with them. I don't beg people to like or subscribe because I'm not after numbers or anything like that (plus at this point in RUclips's life, everyone knows about liking and subscribing but that's another story). I do appreciate your feedback, even though some of it was phrased in such a way to be on the meaner side but to each their own. Feel free to set RUclips to never recommend my channel and you will probably be happier not seeing recommendations for my videos. Regardless, go have fun in DCS! It's a great Sim! Edit: I have noticed also that the DCS mirror appears to be darker than what I see in the game. This was a somewhat recent change (I mainly noticed it when I started using v0.2.0 of the Varjo Foveated software) I may consider adjusting this slightly in post production to see if it lifts the overall video up.
Hey! I took your advice and adjusted the gamma. I must have stuck it down to 1.5 when I was doing a lot of night missions and forgot to change it back (derp). I can't believe I was wondering why my videos were suddenly so dark when I was editing them and didn't think of the gamma. I think it's because I so rarely touch that setting and I just forgot about it. I'm also playing with the detail factors to see what I need to do to get to 90 FPS the majority of the time. It's very much situational though but I am seeing performance improvements and not really missing the lost detail. I'm going to continue to play around with the settings.
![Str][kerTV](http://yt3.ggpht.com/nyCYJbLzftuzWPvnp7dFMOMFarXh9PS7OWoCGe3BGT_LOIXeV1ZEnnjx303oClLp4yIOSbqXfb0=s48-c-k-c0x00ffffff-no-rj)
This has doubled my fps and halved my frame time. Absolutely amazing 👏
Awesome! That's what I love to hear! It's such a huge improvement!
Thanks for the brilliant video, even though i'm nearly a year late! Just installed and tested on my quest3 last night and wow, what a difference in stable performance! Thanks for this bud! (using the fixed FOV)
Thank you for your very kind words. I am happy to hear that I was able to help you out! There’s so much out there and it seems like it changes monthly! Happy flying.
Great video ! I’ve been waiting on this I think this kind of video is needed because a lot folks aren’t tech savvy like myself we just want to play the sim and enjoy our hardware. I went back to Dfr/fvr from QVFR because I felt like my eye tracking wasn’t keeping up or felling to perform right. I think folks mentioned that in the Varjo discord a few days ago. DFR seems to work better on my rig but as you showed in this video that QVFR is better between the too. I’m gonna go back to QVFR and try this again. I have read over the wiki so many times but prefer tutorial videos like yours I’m just scared I’m gonna mess something up. A few Varjo folks are having issues and have to rollback DCS versions to get it running and I don’t want to be in that group. Thanks Str][ker !
Hi! First of all thank you for your kind words. I'm happy to hear that I was able to help you out. I've bene much the same.. videos can be more helpful at times than reading a wiki or instructions. One important thing to note is that the QVFR is very much a beta for the Varjo headsets and if you don't need it because you have something which is working, then there's no need to install it. There are other headsets now supported and I wanted to make a new video so that people aren't landing on the old video all the time if they are looking for installation help. In your situation, it may be worthwhile waiting for a more stable and tested release. I actually ran into an issue with it (which you may have seen on the Varjo Discord). We seem to have identified the cause but not yet a solution to the issue. What I and a couple of the other people have noticed is that the Varjo headset is not passing the eye tracking to the software which mbucchia wrote and so we are not getting eye tracking plus we are getting a lower resolution so the display looks pretty bad in the headset. The workaround is to exit DCS, restart it, and hope it loads correctly. Sometimes I have had to do this a few times until it works. The older Varjo Foveated software works flawlessly but you don't get to use Open XR Toolkit and a few other configurations which would be nice to have (but they aren't essential).
I'm going to roll back to Varjo Foveated for daily use until we can come up with a solution. I'll still use QVFR to help troubleshoot the current issue. The good thing is that it's all super easy to install and uninstall (I've done this several times so far). If you do go back to VFR, make sure you disable DCS in the Open XR toolkit via the desktop companion app!
There is that other issue which you mentioned and that's something odd which I don't think anyone has been able to nail down. It seems limited to a couple people so far and they need to roll back to older DCS versions to get things working which is not really a solution in the end if you play online or need the updates and fixes to aircraft for single player.
@@StrIIker-TV - I appreciate your knowledge and troubleshooting skills and helping the community. Your right it is easy switching between the two thank god for that and mbucchia. I think today I will just stick to VFR because it seems to work better, I just want to fly the sim today. But, I plan to switch back
to QVFR and play around with the Config. settings, thanks so much for showing the process in the video it really helped me gasp it better. Have a Great sunday and Thanks again !
Thank you Striker for your video!
My pleasure! I hope it helped out!
fantastic tutorial. Thank you for sharing!
Thank you! I hope that it was helpful. I've been helped many times by video tutorials.
Hi, using a Quest Pro in 2024, I can tell that there is some sort of fixed foveated rendering happening, (there is a clear border near the bottom of my vision), but definitely not eye-tracked. Followed all the steps, although I will say that in 2024 some of the Oculus interfaces are different.
Any clue why I might not be getting eye tracking? I turned on, calibrated and tested eye tracking successfully in the headset, but the foveated rendering is fixed in DCS. Thanks!
Hmm, I am not sure why it would not be working. I assume that you are using the multi-threaded version of DCS and XR Toolkit? Also, I have heard of some issue with the quest software and DCS not working properly. I am not sure if this is what your challenge is but Meta made some kind of changes to their software for XR implementation and DCS needs to make a few changes for it to work again. Failing that, you should be able to track down mbucchia on Discord or the DCS Forums to see if he has any insight.
Great help! Thanks.
Thank you. I am happy to hear that this was helpful.
Nice video!
Much appreciated from a fellow video maker such as yourself!
Guess who, thanks again !
Heh! Guess who... well, I suck at that but thanks for your thanks! :P
Thank you great video! Quick question , you shown with and without quad view, how do you activate/ deactivate it? Is only by launching/ or not open vr tool kit before dcs?
Hi! Thank you for the compliment. For the video, I just uninstalled the quad view software. There is another way to disable it in the OpenXR stack via steam. You can click into steam and it shows all XR software loaded ( can't recall the exact path but I can grab it if you want). You can disable it there instead of uninstalling it. There is a tool to also see the layers loaded and you can disable them with it and you can change the order in which they load (important for some XR stuff to work) github.com/fredemmott/OpenXR-API-Layers-GUI
Also, I made a "stress test" video to demonstrate eye tracking benefits.. ruclips.net/video/8G_gW4DK154/видео.htmlsi=WYlcU3bRIH1bdDsb
Top, hope your comment will help other users. As for me, I am not using Steam but I found how to disable quad view in openxr tool kit menu ( viewed only through the lenses of the headset ). I followed all the step, was working as advertised but when launching dcs this morning... it doesn't in VR. If I disable openxr tool kit it does. If I launch in safe mode it does too. I will have to investigate what in openxrtoolkit prevents dcs to launch in VR mode...
@@damn8445 you don’t need to be using steam (I don’t) but if you have it installed, you can play around with the XR stuff.
A very helpful video thank you
I’m happy that this helped out! Hopefully we continue to see more headsets include eye tracking which would encourage more games to support eye tracking.
Great video 🔥
Thank you! I of course think of something else worth mentioning after it’s posted but I think it is enough to get people rolling.
thanks for the video! how should be setted the % in quad views, I mean the center and the peripheral view.. It's not really clear to me how this % works and if there is a "ratio
ule" that should be followed.. thanks! :)
Hmm, the quad views peripheral / focus setting numbers are different from the Varjo Foveated software (I use the Varjo Foveated because of issues which the Quad Views has with the Varjo Aero). I know it has been discussed a lot on the Varjo Discord in the past but I don't recall what people liked to use. The default should generally be fine but you can always hop onto the Varjo Discord and ask in the DCSWorld Channel for suggestions even if you don't have a Varjo headset. Make sure you have a look at the QuadViews Wiki as Mbucchia discusses it there as well. Here's the specific page for the config. github.com/mbucchia/Quad-Views-Foveated/wiki/Advanced-Configuration
@@StrIIker-TV thank you
Hmm, after re-installing windows and DCs again, I can't get the FOVeated to work anymore for some reason. Installed Open XR first and then Foveated. but no changes in the headset.
Which headset is this for? There was an issue with quest headsets after a recent oculus update.
@@StrIIker-TV Oh damn no way, It's a Quest 3, so I guess that's what broke it! Thanks dude!
Does anyone experiencing the same after the last quest pro update? I have my foveated rendering "windows" shifted down. Is there any way to reset it to the moddle of the screen?
Is it possible that this was an issue with the DCS update or was it specific to the Quest Pro? Did you ever get this resolved?
Quad view is not working. I installed it afyer OpenXR toolkit but it is complayning about OpenXR toolkit.
I installed it after OpenXR toolkit but still gives me an error. Not sure why.
Is your headset compatible with Quad View? Did you clear the settings in OpenXR Toolkit by enabling safe mode?
There are instructions specific to each headset in the Wiki. Did you follow those instructions to the letter? There are troubleshooting steps mentioned in the wiki as well. Have a look and check the log file to see what kind of error you are getting and see if there is a resolution to it.
github.com/mbucchia/Quad-Views-Foveated/wiki
@@StrIIker-TV I followed the video. Is Quad View supposed to give you an interface when running? On another video, you can turn a debug mode that blacks out everything except what you are looking at.
I turned on debug mode, went to DCS, hit default on OpenXR, came out, turned debug off, installed Quad View but other than give me a warning about Open XR, it does
nothing I can tell.
Crystal Sim looks great still. I just xant seem to run it in that mode.
Tnx for the video much appreciated. Does this work on QP without OpenXr Toolkit? QP supports openxr out of the box anyways...
Per the compatibility list on the Quad Views Foveated Wiki, yes, the Quest Pro is supported for Dynamic Foveated Rendering.. github.com/mbucchia/Quad-Views-Foveated/wiki You can use it without the Open XR Toolkit if you wish. The OXRTK adds functions such as post render shading enhancements. Quad Views Foveated Rendering and Open XR Tool Kit are two separate things and can be used together or separately.
I have followed the instructions but in Pimax Client the option to tick the eye tracking box is not offered- what am I doing wrong? Thanks in advance
Could I first ask which headset you are using? I would also like to confirm that you have a supported headset from the list on the Wiki. Secondly, ensure that eye tracking on the headset itself is enabled (for example on the Varjo Aero and PiMax Crystal and others, you need to enable it within the headset software) and then in any other secondary software (Pimax XR Runtime for example). Make sure that you did follow the Wiki instructions AND the headset specific instructions.
Lastly, if I'm not sufficiently helpful here, you can hit up the OpenXR ToolKit Discord channel and get some expert help there! discord.gg/WXFshwMnke
The Pimax Crystal. When following the instructions I am directed to tick the eye tracking box, but none is available. I suspect I might need a Beta version of the software which I don’t have and don’t know where to download it
You are correct I think regarding the Beta software. I had found some reddit posts from about 30 days ago pointing out that eye tracking on the Crystal was in Beta. I was going to mention this in my response but deleted it as I figured should be ready by now. Let me see if I can find out more for ya. There are some Crystal users on the Varjo discord. I'll ask there.
So first off.. I just noticed that you mentioned which headset you have in your comment and then I go and ask what headset you have.. LOL.. My brain didn't process that for whatever reason! Secondly, I did look this up and it looks like you will have to wait as the Pimax software is in closed beta. I did ask others about the availability and will update here if I hear back. The last update was over a month ago (June 30) on the Pimax website...
pimax.com/crystal-notice/
Eye Tracking/Auto-IPD/DFR Firmware Release:
We recently released the beta version of our firmware to our beta group and a few KOLs. The feedback we received indicates that the firmware has delivered significant performance increase. However, during this testing phase, we discovered a minor issue with the eye-tracking feature, which is causing glitches. Our main objective is to enhance the accuracy of this feature before making it accessible to the general public. We expect to release the improved version shortly.
@@StrIIker-TV thank you. I guess we will just have to wait. Fingers crossed it won’t be long. 👍
Can you add the links to the description?
Oops! How did I miss that?! Also I meant to add indexes to main parts of the video! Adding the links now!
does this work for quest 3? the wiki doesn't mention it.
Unfortunately the Quest 3 does not have eye tracking and therefore the dynamic foveated rendering will not work in it. I think the pro line has the eye tracking though.
@@StrIIker-TV ok thanks for the info.
I tried this with a Quest Pro and DCS does not load in VR mode. Only the 2D version loads. And the headset only displays the "DCS Loading" logo and not loading in VR mode. Any ideas? I followed the procedure to the letter and I have tried it multiple times with the same results. Once I uninstall the Quad-view app, then DCS is back to normal and loads in VR mode.
I have asked about this issue on the OpenXR Toolkit Discord channel for ya. Quick question while I wait to hear back.. Can you confirm that you are running the DCS multi-threaded executable (this issue sounds similar to what happens when you are not using the multi threaded exe)? For my DCS shortcut properties, here's my Target The focus being the path to DCS.exe as if you don't see bin-mt then you are on the wrong executable..: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR. and Here's my Start In: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt"
EDIT: Also the log file might help identify the issue.. Check the Troubleshooting part of the Wiki and see if the log file helps
I heard from mbucchia and he is suspects “Their issues is probably they don't have the vc_redist installed. These are all instructions on the website”. I know you said you followed the instructions. Could you double check this? If not, your best bet will be to hop onto the Discord and see about getting some assistance there. He and the others do a great job helping. discord.gg/x74n8TCB
@@StrIIker-TV Thank you so much for looking into this. I appreciate the help a lot. I did install the VC_redist. I am running the multi-threaded version of DCS. I will post at the discord you linked. Thanks again.
@@StrIIker-TV I finally got it to work. At least I can now start DCS in VR mode with the Quad-Views installed. Now I have another question if it's ok with you, How do I know that Quad-Views DFR is actually working? My monitor mirror display only shows a single view of the game and not four. I also can't tell inside the VR headset (quest Pro) in DCS if it's working. Meaning I don't see any pixelation on the side or anything like that. I am sure I followed all instruction to the T. Any advice? Thanks.
@@emvill4520That's great news! A VERY simple way is to sit in the cockpit in a busy area where your frame rate is not maxed out. Pull up the in game FPS counter (I think the default key binding is . Stare straight ahead and see the FPS line stabilize.. Now glance with your eyes only down into the cockpit. Stare for two seconds or so and then look back up.. you will see that FPS graph change while your gaze was in the cockpit. See this video here for a demonstration (Linked to the proper timestamp). ruclips.net/video/8G_gW4DK154/видео.html That is a clear indication that the eye tracking is working with foveation. There are also log files which you can look at. Also refer to this page and note the location of the log file for the quad view foveated and see if the log file shows what it should.. github.com/mbucchia/Quad-Views-Foveated/wiki/Troubleshooting I personally like to see in game demonstrations that the eye tracking and foveation is working so I always use the method in the cockpit.
On the G2 FFR makes all the peripheral views look extremely aliased (Jaggy). Is it because it isnt a eye tracking headset?
I wouldn't even try your graphics settings they are so bad. Those look like what I did 6 years ago when I was just guessing, lol. The VR settings that DCS gives you are a much better place to start. Many of the higher setting you use dont actually make the game look any better in VR. Simply wasting a lot of resources. Making it artificially dark doesn't make it look better, lol. DCS tells us to use 2.2 for a reason. You can get 90fps with your rig why on earth would you bother with reprojection? You need to do less video making until you know what you're doing. People that watch this video are going backwards.
Hi! Yes on the G2 FFR will make the peripheral look lower resolution. The intent on FFR is to keep the sweet spot and area around it looking good while lowering the peripheral resolution to give a performance bump. I tried FFR on my Reverb G2 but never really felt that it helped too much. I didn't notice much image degradation though so probably the peripheral multiplier was not too low. In my opinion, foveated rendering is really only useful for headsets with eye tracking for the very reason you mentioned. You could try adding the settings.cfg and adjust the peripheral multiplier so that it's not reducing the resolution so much.
The graphics settings I use were really just me trying to push my system to get to a performance level which I am happy with. When I bought my new CPU and graphics card, I decided to max it all out to see how things looked. It wasn't too bad to be honest but I ran into some issues with DCS swapping to/from the page file (hence the medium textures). It was a far cry better than what I was experiencing on my 5 year on Intel CPU and 3090ti GPU. Part of the issue is that if I drop settings too much, the game mirror (which I use to record videos) will look worse. I am trying to strike a balance for producing a nice video and getting what for me is acceptable performance in the headset. If I wasn't shooting video, I could drop MSAA down (and probably will set it to 2x which I thought I had already). The clouds I could certainly drop from Ultra because that's pointless to have maxed etc. I honestly don't feel the difference between 90 FPS and 70 or 60 FPS. If I focus on it I may be able to but it's honestly not the goal for me. So, it's a combination of what works for me personally and what I need for video recording.
I'm also not making anything artificially dark. I have used a lower gamma because the panels in the Varjo are not anywhere as good as the HP Reverb G2 when it comes to blacks. So, if I run at 2.2 all the time, when I hop into a night mission, it looks horrible to me. It's like I am in a fog. It was a big shock and disappointment for me coming from the G2 when I fly night missions. I should probably just create preset with different gamma and other settings I guess but I know that would probably forget to switch before each mission type and have to drop out to switch.
I make most of the videos first and foremost for myself. I like to watch them while on the treadmill and see what I did wrong or relive some fights etc. I make the instructional videos to help people out because I've been in their spot before, full of questions and looking for answers. I think that the videos are generally helpful, if not the best looking so I'm happy with them. I don't beg people to like or subscribe because I'm not after numbers or anything like that (plus at this point in RUclips's life, everyone knows about liking and subscribing but that's another story).
I do appreciate your feedback, even though some of it was phrased in such a way to be on the meaner side but to each their own. Feel free to set RUclips to never recommend my channel and you will probably be happier not seeing recommendations for my videos. Regardless, go have fun in DCS! It's a great Sim!
Edit: I have noticed also that the DCS mirror appears to be darker than what I see in the game. This was a somewhat recent change (I mainly noticed it when I started using v0.2.0 of the Varjo Foveated software) I may consider adjusting this slightly in post production to see if it lifts the overall video up.
Hey! I took your advice and adjusted the gamma. I must have stuck it down to 1.5 when I was doing a lot of night missions and forgot to change it back (derp). I can't believe I was wondering why my videos were suddenly so dark when I was editing them and didn't think of the gamma. I think it's because I so rarely touch that setting and I just forgot about it. I'm also playing with the detail factors to see what I need to do to get to 90 FPS the majority of the time. It's very much situational though but I am seeing performance improvements and not really missing the lost detail. I'm going to continue to play around with the settings.
@@StrIIker-TV Great news mate. Getting to 90 most of the time is the best you can really hope for even with a 4090/13900k in VR.