dburne

I cleaned all my software out when I got my Aero just to help make sure I would not have any conflicting issues. It may well be I would not have. But I sold my G2 shortly after getting the Aero anyway.

Going to have to wait for reports from real world users rather than these so called youtube reviewers. The way Pimax drips these things out it may be a while.

Gave it another try earlier today, seems for me still WWII birds are not behaving with ATC, same as before this latest update. Tested both Spit and P-51 in Normandy 2 and The Channel. Behaving exactly same as it was, wingman comms worked fine, no ATC comms working. I made sure to load into each map and do the finish steps procedure to get the new commands in. Then flew the Hornet some in the Persian Gulf, it worked properly as it always has. So in effect absolutely no change for me with this latest Vaicom update.

@mbucchia magic dust... He would be best to answer this as he implemented it , if I had to guess I would say the Varjo Aero having quad view capability has something to do with it.

Occasionally I might get a very quick glimpse but really I would consider it mostly unnoticeable.

You nailed it, that has been my experience with DFR and eye tracking with my Aero. Really pumped my performance and can not tell any difference in image.

No and obviously this is getting beyond my level of understanding - perhaps others can help you out better. Never heard of this api-runtime segregation. I sure would have thought one could run DCS natively with the Oculus runtime like has been done with their previous headsets for years. Best of luck,

Yes I have auto-import theatres selected in the config. I did finish steps but maybe just on the first or last map I loaded can't say for sure, will make another attempt tomorrow and make sure I click on finish steps after each map loads? Do I need to do this procedure for each aircraft when doing this also? Or just the maps? Thanks,

No I was saying you can run Quest Pro natively with Oculus runtime - DCS supports it. No need for Steam VR or Open XR. However regarding this MC that I do not know anything about. That would prevent you from being able to run natively with the Quest Pro?

Ok so I am just going to put this statement here for the Varjo DCS enthusiast. If you are not using @mbucchia Dynamic Foveated Rendering with eye tracking you are really missing out on one very big feature of the Varjo Aero. Thanks to DCS now supporting Open XR and to mbucchia for his work to enable this feature we now have this option available to us. Granted the new Multi Threading capability of DCS increased our performance nicely, however the performance increase from the DFR with Eye Tracking with the Aero is on a whole nother level I wiill say! Probably most if not all in here have already tried it, if anyone hasn't do yourself a big favor and give it a shot. Just be aware if you are also a big fan of mbucchia's Open XR Toolkit, both of these can not be used together. To use DFR with eye tracking one must disable the Open XR Toolkit. Now I am sure there are some that are pretty knees deep in the Toolkit and don't want to lose that capability - all I would say is give it a shot and see if the DFR with eye tracking may be worth it to you. It certainly was to me. https://github.com/mbucchia/Varjo-Foveated

It will be interesting to see what Oculus does going forward. Scuttlebutt seems to suggest a bigger focus on mobile rather than PC-VR. They just took away the custom Oculus Home capability from the PC-VR crowd.

So got mine updated this morning and been flying most of the day today. In the Hornet everything was fine, just like it has been. WWII still giving me issues - namely while wingman comms work fine ATC never gets recognized. At least I get no audio feedback from it. This is in the Spitfire in Normandy 2 Map, P-51 in Normandy 2 Map, and Mossie in The Channel Map. In fact in the Mossie, TX1 does not seem to work at all - I do not get an audible beep or anything when pressing it. TX5 does at least give me the audible beep, but no ATC comms there either. In the WWII planes I tried each channel available to be sure. This was pretty much how my Vaicom was doing prior to this latest update. Procedure I used - I uninstalled Vaicom and installed this latest version. I also went through the Finish Steps process to paste all the keywords back in.

I am a little confused, why Open XR Toolkit with Oculus runtime? And why run Steam VR in the first place as DCS has native support for Oculus? I think currently the MT version of DCS defaults to Open XR runtime, you may need to set parameters for running in Oculus runtime.

Much thanks for all of your hard work on improving Vaicom guys! It is very much appreciated!!

I have not noticed that yet - however have not done any night flights since these updates. I do not notice anything unusual in my normal daylight activities.

@Burt - before installing Aero highly suggest you get rid of all remnants of your WMR and do a clean up of your Steam VR just in case. https://steamcommunity.com/app/250820/discussions/2/1640917625015598552/

Long as I can maintain better than 45 fps it looks very smooth to me. Now I will on some rare occasions get a spike causing a big stutter or two, thankfully that does not happen too frequently. Undstand though everyone's experience can be quite different. What works for one may not work well at all for another. I just spent a large amount of hours testing, adjusting, testing, etc over many days to get it to the level I have it now for me. The two things that absolutely made it possible for me to get this performance at high GFX settings were MT and DFR with eye tracking supplied for the Aero by mbucchia.

Your issue is in the first stage - setting cursor targets. You have to close the two vertical cursors up until they come into view. Can be tricky as you can't see them moving at first so you don't know if you have them moving opposite each other or both moving in same direction. Obviously you want to set it to where they move in opposite directions so they will close up and become visible. It always takes me a little trial and error to get it but I eventually do. Check the documentation on setting targets it will tell you the button that toggles the change in movement of the cursors.

So I have been running DCS-MT at some very high gfx settings since getting the DFR with eye tracking wrapper in - and performance has been outstanding. I settled with Vsync ON and locked at 45 fps. I do not have reprojection on as I do not care for it still. Have been running my MSAA at 2x, increased that to 4x this morning for today's round of flying. My 4090 never even broke a sweat, if there was a performance penalty I sure did not see it as my fps remained a solid 45 fps. I was like oh man I could have been running MSAA at 4x all this time. That is ok I certainly am going forward. This headset really stretches it's legs and shines when using the DFR and eye tracking.

You are most welcome have fun!

Make sure you have the appropriate files saved on your main drive https://github.com/mbucchia/Varjo-Foveated Only use the MT executable for DCS. No need to disable Open VR in Varjo Base, but definiltey have Open XR enabled in Varjo Base. I think you just need to correct nomenclature for your DCS-MT.exe shortcut. Below is mine (installed on my D drive). "D:\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_OpenXR I have my Varjo Foveated files installed on my regular C drive.

Yep you are definitely good to go! IMHO you will have the best headset out there - for quite some time. Especially for DCS.

Assume you got the Lighthouse trackers in there somewhere?

No. Too many complexities, different hardware, systems, settings, configurations, etc. Best is to do your own testing and find what works best and and looks most pleasing to you and stick with it. I have been flying VR for over 6 years now with multiple different headsets and that is how I have always done it - seems to work for me.

Have to have one, two is ideal unless really strapped on the money side. Index/SteamVR/ HTC controllers.