Fiztex

There is zero blur with DLAA only, without DLSS, when using J/K. No issues with the spotting dots as well. You would still see some blur with old DLSS profiles though. I've got 4090 now and it allows me to run DLAA with excellent clarity and no artifacts what so ever at 80 Hz. Basically the difference between 4090 and 4070 now is no blur / blur, while the clarity will be almost identical.

Как видите, разница с той же 4070 Super для Quest 3 не с ума сойти какая, и сейчас можно сказать наступил золотой век DCS в VR - летать теперь можно и на средних картах с вполне приличной графикой и быть вполне эффективным в бою в VR. Разница по сути лишь в шлейфах DLSS против чистого DLAA. С 4090 можно уже даже задуматься насчет шлемов покруче, если готовы к шлейфам от DLSS.

Мои настройки для RTX 4090 + Quest 3 80 Hz (без ASW/SSW) + 7800x3d и полетов на A10C2 на Кавказе: DLSS 4 Меняем nvngx_dlss.dll (на 01.02.2025 это v310.2.1): nvngx_dlss.dll Ставим DLSS Profile J/K (кому что нравится больше) через Nvidia Profile Inspector Revamped из архива: NvidiaProfileInspectorRevamped.zip Настройки DCS Ставим в DCS VR pixel density на 1.1. Не смог увидеть разницу с PD 1.2. Настройки ниже по принципу "вижу ли я разницу, и колышет ли она меня за тот фпс который оно стОит". Quad Views (QV) Стоит сразу отметить, что QV жрет процессор и VRAM - имейте это в виду, если читаете этот опус с другим железом. Например, на 8 GB VRAM может толку не быть от слова совсем. Ставим Quad Views и создаем такой %LocalAppData%\Quad-Views-Foveated\settings.cfg: smoothen_focus_view_edges=0.1 sharpen_focus_view=0 horizontal_fixed_section=0.5 vertical_fixed_section=0.6 vertical_fixed_offset=-0.25 peripheral_multiplier=0.20 focus_multiplier=1.0 turbo_mode=1 Если лично Вы такой зоркий, что увидите разницу с PD > 1.1, то ставьте focus_multiplier на 1.1 и больше пока не достигните дзена. Не забываем активировать Quad Views в настройках DCS. Если замечаете границу низкого разрешения, то может быть выгоднее поднять ее разрешение через peripheral_multiplier, чем увеличивать поле обзора. Если всё-таки двигать дальше от центра, то это делается через horizontal_fixed_section или vertical_fixed_section. Опустить/поднять четкое поле по вертикали можно через vertical_fixed_offset - помогает коситься вниз на приборы и не страдать от эффектов QV. После изменения настроек рекомендую считать пиксели, т.к. от этого зависит конечная производительность - см. %LocalAppData%\Quad-Views-Foveated\Quad-Views-Foveated.log: 2025-02-03 20:49:11 +0100: Quad views pixel count is: 6719792 2025-02-03 20:49:11 +0100: Savings: -66.0% У QV vогут быть проблемы совместимости с другими слоями OpenXR. Хотим вкл/выкл слои OpenXR - https://github.com/fredemmott/OpenXR-API-Layers-GUI В целом, настройки в QV делал по принципу "максимальная четкость в бинокулярном перекрытии и чтобы я не замечал границу раздела разрешения в 95% случаев". Если у вас с ними не так - опять же крутите vertical_fixed_section и horizontal_fixed_section пока не станет так - головы у всех разные. Virtual Desktop VDXR + 400 Mbps H264+ по WiFi (по проводу через адаптер ставим 500 Mbps): Хотим больше/меньше "умного" шарпа - лучше крутим шарп DLSS в DCS. 5-10% в VD это более тупой шарп, но он помогает именно с видео потоком в шлем. Но и для него вплоть до 50% с некоторыми настройками может быть оправдано - это большо про то, насколько вы лично любите простой CAS шарп. Итого Четкая картинка и ноль шума на ландшафте и облаках. Но звезды ночью будут жирные, QV c'est la vie. Но вам четкие звезды или +50% к производительности? Хотим летать тяжелые модули - падаем до 72 Гц, снижаем PD до 1.0 либо активируем DLSS - зависит от вашей чувствительности к шлейфам. Учтите, что при использовании DLSS вероятно придется поднять разрешение peripheral_multiplier в Quad Views до значений при которых периферия перестанет шуметь, легко проверять по облакам. Скорее всего получите что-то вроде 0.3 для Quality. Бонус - используемые моды для сингла:

Here is what I ended up with on a 4090 to fly A10C2 in Caucasus: 2025-02-03 20:33:57 +0100: Found option 'smoothen_focus_view_edges=0.1' 2025-02-03 20:33:57 +0100: Found option 'sharpen_focus_view=0' 2025-02-03 20:33:57 +0100: Found option 'horizontal_fixed_section=0.5' 2025-02-03 20:33:57 +0100: Found option 'vertical_fixed_section=0.6' 2025-02-03 20:33:57 +0100: Found option 'vertical_fixed_offset=-0.25' 2025-02-03 20:33:57 +0100: Found option 'peripheral_multiplier=0.20' 2025-02-03 20:33:57 +0100: Found option 'focus_multiplier=1.0' 2025-02-03 20:33:57 +0100: Found option 'turbo_mode=1' 2025-02-03 20:33:57 +0100: Eye tracking is not supported 2025-02-03 20:33:57 +0100: Recommended peripheral resolution: 614x644 (0.200x density) 2025-02-03 20:33:57 +0100: Recommended focus resolution: 1536x1930 (1.000x density) 2025-02-03 20:33:57 +0100: Stereo pixel count was: 19759104 (3072x3216) 2025-02-03 20:33:57 +0100: Quad views pixel count is: 6719792 2025-02-03 20:33:57 +0100: Savings: -66.0% 2025-02-03 20:34:03 +0100: Session is using quad views 2025-02-03 20:34:03 +0100: Edge smoothing: 0.10 2025-02-03 20:34:03 +0100: Sharpening: Disabled 2025-02-03 20:34:03 +0100: Turbo: Enabled Runs Quest 3 at 80 Hz VDXR Godlike, DCS PD 1.1. So as you can see only 6.7 MP + DLAA without DLSS with profile J pretty much maxes out Quest 3 optical resolution capability. I have zero clue why would one need 12 MP on Quest Pro with DFR... Sure if I need to run something heavy I can still drop PD one step, reduce visibility to high and switch to 72 Hz. Or even switch to DLSS with some low flying helicopters. But I definitely don't need ASW/SSW...

That's exactly my point. I have better pixel reduction with Quest 3 than you with Pro, which doesn't make any sense. It should be the opposite - I'd expect you to end up with >70% savings with Pro while I can expect to be around 60-65% with Quest 3 and not perceive the difference as well. You should be able to reduce peripheral multiplier much further down with new DLAA and not perceive the difference, at least in daylight conditions. For starters try 0.3 and see if you can notice ultra clouds shimmer. Also not sure 0.2 smoothening is necessary with new DLAA, I'd try 0.1. And I see in your log that your vertical focus offset is not working even though you set it in the app - that was another point of mine. I've ditched the app and been adjusting the file directly for a long time already, the app is missing parameters for focus offset.

Log says your initial resolution before QV was ~4000x4000. If you take Godlike VDXR and apply 1.2 - 1.3 PD on top of it (e.g. in DCS) then it will be around 4000x4000 as well - I literally suggested you that but you dismissed me just because you didn't like a particular multiplier... And then you can lower periferal till 0.25 and boost focus further to 1.1 with QV and new DLSS 4 J/K. And on top new DLAA will supersample even further. You seem to be doing all that with the link, but now with QV you are still rendering 12.5 MP which is way too many and IMHO can be optimized further, especially for displays of Quest Pro. E.g. my settings in QV for fixed foveated target full resolution in the stereo overlap area of Quest 3 and somehow give reduction of 67% while yours are at 60% with a much smaller focus area. I'm thinking you probably miss out on not using vertical offset and have yor vertical FOV in not optimal position, though maybe it's just perfect by default for Pro, who knows. Definitely not for Quest 3 though, focus view is shifted up a lot there, so I'm just suprised about you not using this. But hell, if you like your settings then this discussion for sure doesn't make much sense, we are not here to convince you to do anything. Repro is worse on VD, so stay off it for sure if you like repro. BTW my 4090 has arrived, will test this all in the evening and see if I can bring everything to ~9-10 MP rendered which by my estimation should be great for a 4090 without repro.

My experience as well but with 4070S and Quest 3, MSAA is basically dead now for DCS. It has transformed the DCS experience (pun intended), new DLAA is excellent with quad views low resolution area denoising as even 0.2-0.25 peripheral multiplier with ultra clouds leads to zero noise which was always distracting previously when in the sky and as such making QV a compromise. Not anymore. Overall DLSS 4 has had a major positive impact on all main VR issues we had in DCS - clouds noise, performance vs image clarity, and even VRAM consumption. It indeed feels like upgrading the GPU by 1 or even 2 generations. IMO those who are still flying crazy PD and MSAA 4x are simply missing out. Yes, there are some artifacts, but they are a joke compared to what you are getting in return. The biggest noticeable one for me are the stars in the night sky, but I don't fly at night very often so I can easily live with that. And you can still see shimmering on fences when parked on the airfield, but again this is nothing compared to what it was like before. Today I'll get the 4090 and see what I can squeeze out of it with new DLAA.

My bad you need to target 3500 resolution before foveating no matter with Link or VD, then on top you'll put DLAA which will supersample further and you would probably end up with a similar PD as you have now but for a fraction of the frame time. You can also go 60 with SSW at 120 Hz which maybe better for your eyes than 45 ASW. I fly 80 full normally and only for really heavy stuff switch to 72. Tomorrow I'll get a 4090 and update my settings. I have no doubt I'm keeping DLAA though, it's excellent with QV.

What are your CPU+GPU and what and where do you fly? I'd say if you want ASW then for sure forget VD as it's much inferior in that regard, but I would be surprised if you actuallly need repro. I.e. I really highly doubt you need reprojection now with DLSS 4 to fly 72 Hz. I don't with my 4070 Super. Unless maybe if I decide to run a Supercarrier with a full deck and shadows, but I think that would drop even a 4090 into lower frames. But that is more about ED "optimization" than settings - IMO no point targeting full frames there if we end up flying with 50% GPU load later... If you've got a 4090 try VDXR Godlike, DCS PD 1.2, DLAA with profile J or K without DLSS. You can find my QV settings in my signature, as well as the rest of instructions. They are in Russian, but screens are in English and I bet a translator will manage to do well for those basic instructions. Or you can also contact biotech so he can make some screens of settings for you - he's flying a Quest Pro with 4090 now with DLSS 4 and VDXR through ethernet adapter: You can save your DCS settings as a template in DCS so you won't loose yours if decide to roll back. And stuff like enable/diable QV and switch between Quest and VD is easy, so should be no problem.

Fair point, I've put that in the spoiler to not overload the thread. Was bored on my way home and typing on a phone, so didn't notice how long that ended up

Well, I disagree with that completely, and I'm not alone, very far from it. To not overload the topic with an off-topic discussion:

Well, if you don't update the software for 2 years I'd say it is abandonware But indeed a couple months ago they suddenly fixed VRAM consumption problem without telling anyone, so maybe they'll fix the rest as well. Will see.

I have a link cable as well and a Quest 3. Link at 900 Mbps looks worse than VDXR godlike at 500 Mbps H264+, even if you bring them both to the same render resolution. Oculus link is practically abandonware, VD became significantly better around mid 2023 and only becomes better. Link had some improvement recently (before it was even worse in performance to VD, a natural VRAM hog), but still not on par. If only Meta updated their encoding profile the case cold have been different, but they don't seem to bother. Hence all that BS with ethernet cable, to squeeze maximum out of Quest...

Sorry, probably 400 is indeed the limit on Pro, 500 is for Quest 3. 400 is still going to be better than Oculus link IMHO.

Unless you use ASW I seriously suggest running VDXR Godlike instead as it is simply superior to whatever you can get through ODT/OTT. You can connect via RJ45 cable as well and avoid WiFi troubles. Use H264+ 500 Mbps. Use 400 Mbps for Quest Pro and 500 Mbps for Quest 3. As for the resolution it indeed doesn't matter how you force the game to render the pixels you need, you just need to do it to not have issues with spotting dots when using temporal AA like DLAA. You should target something like 3500 pixels before foveating and then apply DLAA on top.

Try setting PD 1.2 in DCS and enabling DLAA without DLSS J/K - beats MSAA 4x+MFAA for sure, and 4090 is well capable of that with Quest Pro + VDXR Godlike. QV helps a ton as well if not CPU limited as DLAA is excellent at blending the low res periferal section of QV.

И в самом деле нет. Я был бы один из первых, кто начал бы ругаться, если бы зеркало VR ело хоть сколько-то производительности, встречались такие VR игры.

В больших миссиях на тяжелых картах и онлайне есть, в сингле на Кавказе нет. Я думаю ты сразу поймешь как она закончится, статеры начнутся.

Тот где рядом нужный nvngx_dlss.dll, они идентичны теперь, по крайней мере в OB.

People sensitive to smearing should only use DLAA without downsampling of DLSS, and adjust their render resolution and QV settings till needed performance level vs visual quality balance is reached.

Никак не влияет.

I think you should try for yourself, everything is very subjective. E.g. I'm definitely not going back to old DLSS or MSAA, have no issue with the gameplay whatsoever with new DLAA.

Ну да, только DLAA оставь если максимальное качество хочешь.

All is correct, this is the latest dll.

I'd be happy if ED just whitelisted all Nvidia signed dlls - no cheating like that possible and it's not like the game is super secured anyway.