Toro

I dont think so. I think all it does is download a binding file and substitutes the games one for the one you just created/run. I've just tried this on the A10C. I've never not had SimAppPro running though. And yes, you need to exit DCS to load a new keybinding but not if you change planes.

Those settings yielded 72fps quite constant with little drops compared to caucasus, but to me the IQ was very poor. Increased middle resolution to 1/2 and was much better but i'd say similar performance to quadviews. In all fairness, quadviews runs typically at 170% on foveated area (15% otherwise) so its not right to compare ( i think?). I upped PD in game quickly to 1.3 and that gave similar, if not beter IQ than I'd get with quadviews and ~65fps to 50fps. I probably can tune that down. My case might be different to other people as quadviews is quite taxing on my not-so-great CPU compared to my GPU.

Ive tried it today before updating the temporary fix so I can use QVFR. I found the IQ to be lower. The transition areas between circles was more noticeable than on QVFR, that only shows a rectangle on very specific situations. Performancewise i would get less fps (5-10fps less in free flight caucasus on the F16c) than with QVFR but the fps achieved dropped less. This is quite likely due to my setup where I sometimes am cpu limited with a 5700x when using QVFR. I am overall happy but if i had to chose right now, I would stick with QVFR.

I've got a second hand 3090 paired to a Quest Pro and it seems to me it is the best bang for buck. I'm extremely happy with it, specially with DFR. Even a second hand 4080 is slightly more expensive and has less VRAM (16gb) though should be sufficient on most occasions. Might work better with DLSS than the 3090. If you only consider buying new, 4080 is the minimum I'd go for. I used to play on a 3060ti and yes, it would work at lower fps (~45fps) but i get so much IQ now with the 3090 and at 72fps that i would find it hard to go back.

Wow, i had exactly the same issue playing the same mission!

Came here to bump this up after spending too many hours trying to fine tune it. TGP works flawlessly. Anyone with a fix or still reporting the same issue?

Thanks all for your answers. It is indeed not complicated and i would say i do it myself half the time because it is just more convinient sometimes. Just wanted to know if i could switch from NORM to STR HDG once NORM alignment has started. From all the messages above I gather its not an issue. Thanks again

I meant the one you get by pressing L_Win+Home before when you don't want to do all startup when starting on the ramp and cold. I can do it manually, actually just did it on a MP sortie, but just find it more convenient when I need to do other things like sortie planning, discuss something, or maybe go for a beer The issue is that the autostart procedure is configured to do a NORM alignment. My question boils down to knowing if its OK to switch to a STOR HDG once the NORM alignment has started. Thanks

Thanks so much but just to be clear: when you say that I can simply rotate the switch to STOR HDG, you mean that I can interrupt the NORM alignment that has already started with thr autostart sequence, right? Many thanks as well for clarifying that I don't need to confirm coordinates, wasn't sure of that!

Hi! Every now and then I use autostart but would like to use storage align instead of full NORM alignment. Until now I wait for the coordinates and altitude to be entered and then I rotate the ins knob to STOR HDG. Is that the right procedure? Should I do it before the coordinates are entered? Does it matter? I have had a few issues in the past and wonder if I should turn it off, wait 10", store align and confirm the coordinates instead? Thanks!

This worked for me! Thanks so much!! Not happy with virtual desktop over cable, let alone wifi, so this worked like a charm Edit: version is Meta Quest Link App Version 63.0.0.216.361 (63.0.0.216.361)

Same. Just tried and v63 is forced. Later paid £16 for Virtual desktop and its so slow compared to my Link version... even using the cable is bad, probably made worse by mot having eye tracked foveated rendering.

As an update... it still does show it as a separate window. I´ve been playing DCS again today and noticed it still tries to scale down the monitor resolution to the DCS resolution. Is there a way to force the monitor resolution to remain constant regardless of DCS´s?

Hi draconus, i cant see them in VR indeed. For some reason it is working now. I dont think i've touched anything bar a computer restart. Happy to close this for now but i'm rather puzzled. Thanks for your help anyway! null

Hello all, I have a 38" ultrawide monitor and would like to use DCS as smaller window. I can set it up for a 1920px width and 1080px height, but when doing so it resizes my desktop to that resolution automatically. Then I need to reset the desktop to the default 3840x1600 resolution and once DCS loades i get the resolution I want as per the screenshot below. Is there any way to not to have to resize manually? The reason why I want this is because I play VR and would like to have SRS, Afterburner, DTC, and other tools on the side. Many thanks null PS. These are my settings nullnull

Hi all - what is the best way to create a preset for triple monitor and another one for VR? I have changed the settings within DCS so under Default profile I can see the correct render window width/heigh. The problem is that when i try to modify one of the settings (3x Monitor H), it doesn't store the render width and height anymore and therefore I can't save two presets to switch between. Is there anything I'm doing wrong here?

Unfortunately I tried all tips on that thread and it didnt work but I think I've fixed the issue. Attached the latest logfile dcs.log before making it work in case it helps devs. In short, I've repaired Oculus using the OculusSetup file ("C:\Program Files\Oculus\OculusSetup.exe") - no luck. Saw the logfile and realised that I used OvGME for some mods. Removed all mods, *deleted the app and I could start DCS funnily enough from Skatezillas DCS Updater but not from the icon. After a bit of playing, I saw that SZ's DCS Updater gave a .NET error so I reinstalled this. Once I've done this, DCS runs well from both desktop shortcut and SZ's app. Frustratingly, I can't exactly pinpoint what caused the issue but so far its working fine. Thanks all!

I can see my desktop without problem and i can actually play with the monitor as 2D if i use the non-VR version of DCS. Also this morning I installed BMS Falcon and it was working, so I fear it's a problem with DCS.

Hello, DCS crashes when I start up on VR but not on the flat screen. Currently using MT 2.9.47168 but have also tried ST and rolled back to the first 2.9 release. This latest version (47168) was working last week but not sure what's causing the issue. Using a Quest 2 on a 3090 gpu, 5700x cpu, 64gb ram, running from a SSD with plenty of storage. Things I've tried: - Re-installing the latest OpenXR version. - Installing latest Oculust and Nvidia drivers - Launch fron Skatezilla's DCS updater and from the shortcut (with MT and ST) - Re-installing DCS after deleting all folders - Increasing virtual memory to 32GB - Resetting to Oculust default settings, and same with Oculust Tray Tool - Installing latest Visual C++ redistributable Attached latest dcs logfile. Many thanks! dcs.log

this did the job for me! you're a star!

Im surprised on how people tolerate artifacts with DLSS. Other planes look poorly defined (like looking through the bottom of a glass), and smeared (as other people mentioned), plus the known bug of the terrain going from lit to unlit whilst doing barrel rolls,and not to mention the cockpit being a mess on mfd,gauges, etc i have tried to enable and disable openxr, with pd 1.0 and pd 1.4, with lower texture settings or high settings, deleting fxo and metashaders, cleaning my dcs install..... nothing gave me a decent quality, let alone better than msaa i see the performance and the potential is there but either im missing something in my config/setup or its just too green for me. MSAA 2x or 4x with lower settings, plus sharpening and openxr fov'eating works much much better in my experience.

I have identical behaviour with 8Gb VRAM. Unfortunately the savings, though substantial, aren't enough for me to avoid stuttering. Guess this was the last nail in the coffin for the 3060ti and will upgrade to the 3090. Offtopic: Love the trees mod by the way! That definitely is a game changer for me, as they know look steady and not flickering as I fly by.