Willdass

Uncage with LG down to declutter the lower part of the HUD & remove ILS info. Useful on short final.

Know a few guys who had similar issues and they got a new units. You might hurry up though because the Aero is now discontinued, so who knows how many spares they have..

@BIGNEWY @NineLine Hi guys, can you please take a look at this? Hopefully a quick fix to revert back to 2.9 NVGs. Thanks!

This patch seems to have reverted back to the old NVGs in VR for me... Last patch it worked fine, but now I have a squared box with the NVG inside following my eye tracking (same as before 2.9). Running Varjo Aero with Varjo Foveated Rendering. Please hotfix this.

Same issue for me. Gross weight 34000lbs, afterburner detent special setting "Always OFF" and can't launch without burner.

I aswell get high fps and stutters in multiplayer, much more noticable on other aircraft when flying formation.. No upscaling, DLAA and sharpening 0.5. Other than that no change in settings compared to 2.8, where I had some stutters but nothing like this. Ping on both me and my FL was about 35

Yes, both windows and GPU driver is up to date. Performed a clean up and repair, same error. Will do.

@Flappie @BIGNEWY Tried a full reinstall of DCS, and Standalone version this time. So I could test with a clean Saved games folder and install path, no mods, no modules installed. Game booted both in VR and 2D. Changed graphics settings to what I had tried with steam version (DLAA on). Game restarted and worked (both in 2d and VR). So I thought I had solved it, thought it was a Steam version bug... But, I closed the game, powered of my HMD to start the game again and install my modules in 2D mode. Now the same error pops up as with Steam version, and I cannot get into the game. See attached for logs. Game crashes both in ST and MT mode. Errors I get: 2023-10-23 10:00:22.682 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{LAU_SNEB68G}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/rockets.lua" 2023-10-23 10:00:22.682 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{LAU_SNEB68_WP}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/rockets.lua" dcs.log-20231023-100139.zip

@Flappie Tested some more. If I apply DLAA and remove it before I close the game, I'm able to start the game back up again (VR and 2D). But if I leave DLAA ON when I close the game, I have to "options.lua.bak" and have to apply all settings again. Tried all your tips under "A" in your linked post, nothing else worked.

dcs.logdcs.log-20231020-114342.zip Tried to change the script lua, did not work. So I tried again with options.lua.bak, game launched. Then I tried to reapply my settings from 2.8 and the game automatically restarted and worked. Then I tried to only apply DLAA and performed a manual game restart, this resulted in a crash. This time though, I did get a crash message and was able to send the report. See attached

Thanks, will try this tomorrow. I should note that I was able to start the game the first time after the update. Though it took like 10-15minutes to get to the main menu (30sec before update). And I did test some of the new settings. I think I exited the game with and just changed DLAA, 0.5 sharpening, from my 2.8 settings. So it maybe a Steam+ DLAA issue? edit: typo

dcs.log dcs.log.old

Thanks, It did work yes (partially). But when I tried to reapply my graphic settings (every setting was reset back to default) my game restarts and wont boot back up.

Hi After updating to 2.9 my game won't start. It's just loading in the taskbar, no game window appears. Been loading for 15minutes and nothing. Have repaired DCS, disabled all mods, rebooted PC, tried both VR (Varjo) and 2D. Game wont start. Any tips? edit: Running MT version.

hmm. My game has loaded for 10+min now and nothing. Maybe the problem lies with Steam version. When I loaded in the first time it took about 10mins, but mission loads were very quick, much quicker than before.

Anyone else have insanly long load time when starting the game? Took me about 10minutes to get into the main menu. When ingame the missions load a lot faster than before though. Tried restarting now to see if it got better after first start, no change. DLAA looked amazing though! Very excited about this update

Yes, but this was before we had DFR. Aero ran much better on my system. I got a lot of ghosting with the QP and I did not get along well with Oculus debug tool and tray tools. Settings should apply automatically but rarely did. Would be cool to test the QP again with DFR now though.

I tested the QP for two weeks, before I got the Aero. Horizontal FOV was very similar and was not noticable to me, but the vertical FOV was a fair bit smaller. The FOV felt like an oval shape in the QP vs the Aero which is more like a rectangular box. But, to gain that vertical FOV I had to positon the QP on my head in a way that was not very comfortable to me (the Aero is much more comfortable over longer sorties). The difference in vertical FOV in practice, is that you have to move your head an inch or two down to see the HSI in the F16. Not a very big deal imho and I quickly got used to that, and the reduced FOV is greatly overshadowed by the boost in clarity. Everything outside the cockpit is noticable sharper and you can pick out airframes at longer distances. Inside the cockpit is also sharper. So, if you don't want to trade for clarity/details at the cost of a bit of FOV, keep the QP. If you miss a bit of detail/clarity, you won't be dissapointed with the Aero. If both headsets were priced the same, I would pick the Aero every single time.

I also just use one base station, no controllers needed. Varjo Base opens a virtual desktop and you use your mouse and keyboard as normal

If you now have QVFR: Save your QVFR settings in case you want to change back Uninstall QVFR Disable OXRTK Install VFR https://github.com/mbucchia/Varjo-Foveated/releases Done Only thing you need to do in Varjo Base is to enable Open XR and Eye tracking. Which you also must do to use QVFR. I use the default settings in VFR. I have 4090 and 5800x3d and above 3-5k ft I'm almost always at 85-90fps, regardless of what is going on. Pretty much every setting maxed, except for: 2x MSAA, and lens effects OFF, SSLR OFF, SSAA OFF. Below 3-5k ft I'm mostly at 60+ with the occasional dip below to 45-60 if there is a lot going on below 3-5k feet. My biggest performance hit comes from Flares. If I'm in a dogfight very close to the bandit and the bandit is spamming flares over a longer period (which the AI does), it hurts my system a lot.

I'm in the same camp as @dburne. VFR just works, and easier to set up. Did not really notice the smoother transition from peripheral to focus area with QVFR ( set to max 0.5), which was my main reason for trying it. Was able to tune QVFR to have similar visuals as VFR but the latter was performing better on my end. F-16 instant action cold start on Caucasus gave me 79-83 fps with QVFR and 88-90 with VFR. I think I could get it more even if I reduced the focus area a bit on QVFR, as it does seem bigger than VFR if left unaltered.

And @TimSell75 if you guys have not found a solution yet, try this, as I had the same problem: Export your settings to another folder or desktop, reset settings database in the settings tab, then reimport your settings. Before I did this the HF8 only gave me G forces and 1 sec gun bursts, after doing this all my settings from previous Jetpad was working. GL

Yes, I like both but the Ultra a fair bit more. Once I got used to the extra movement it is just amazing. Maneuvers like four point rolls and knife edge passes became much more intuitive to do.

@Sile Yeah I had a Kuject cable that solved that problem. But I returned the QP in favor of the Aero. This was back when the Aero was on discount and the QP was at it’s original price. Main reasons for the swap were the reduced clarity on far away objects, the high amount of ghosting. Also having to verify OTT settings at each DCS startup was so annoying (OTT was rarely applying settings automatically for me). Miss the panels and FOV though:)