GUIDE: how to improve performance in IL-2 Korea (VR, Quest but not only)

[YoYo]

Basically, since the launch of EA IL-2 Korea (June 2026), I've been having significant performance issues in the IL-2 Korea VR. Sometimes the FPS is quite good, sometimes, for no apparent reason, it can drop for a moment. The CPU load is also quite high, and the bottleneck may be the coding. While it's generally good in the air and over open spaces, the problem is in cities and larger villages, as well as when we have a lot of vehicles and objects on the ground (e.g., Air2Ground campaign missions). There's also a noticeable problem with AI aircraft performance, which is quite interesting, as we often see maximum and stable FPS (for example 72FPS with 72Hz goggles), while the aircraft seem to jump around as if we were watching every other frame. This may indicate ongoing issues with the IL-2 Korea code and the processes the simulator sends to the CPU, especially.

After extensive testing, I've managed to achieve a relatively decent look and performance in the simulator (version 1.003b). It's still not perfect, and the developers at 1CGS still have a lot of work to do, optimizing the simulator for VR, especially (but generally speaking, this also applies to 2D users), improving code performance, data transfer to the CPU, and optimizing graphics for the GPU. But the settings below have—at least for me—significantly helped me achieve a decent FPS level in single player (multiplayer is less load on your system, so you can even increase some of these settings).

I'll also add that I fly without DLSS. I don't like it and believe it ruins the immersion in combat simulators. While I find it acceptable in civilian simulators, it's not for air combat or destroying ground targets where you fly dynamically. A while ago, I even flew Multiplayer and couldn't tell the type of enemy aircraft even with the max zoom (I thought it was an Li-2, but it turned out to be an IL-10). DLSS simply blurred the outlines and created a "phoenix ash effect" despite the M preset. No thanks, it's not for me. Of course, enabling DLSS can result in better FPS, at the expense of sharpness (it's always your choice and this is explained below).

⚠️ Below I present my settings that worked best for me as of August 2026, along with a discussion of the impact based on my experience (each of these options was tested by me separately in exactly the same scenario).

---------------------------------------------------------------------------------------------------------------------------------------------------

👉 Global:

👉 Section Overview:

💬 GRAPHICS SETTINGS - moderate impact on FPS

General Graphics Quality - I have HIGH, you can use BALANCED as well. It doesn't have much of an impact on FPS. The High level affects the quality and sharpness of ground textures (less blurry), and it also expands the scene with trees and other objects and effects (though there's no significant optical difference for effects). The impact on FPS isn't significant if you have a better GPU (4080, 4090, 5070ti, 5080, 5090). If you're having trouble, change it to Balanced; then you'll see less of the area, and you'll see translucent trees more often on mountaintops. Bridges will also appear later (they'll also have the transparency effect). For me, whether High or Balanced, there is no effect on FPS, so I left the higher setting, I don't like these semi-transparent trees. There's also VR Optimalized, but it looks worse than Balanced, and actually produces longer response times than Balanced. I don't recommend this mode.

Screen Resolution - 1920x1080 pxt. It only applies to 2D and the image displayed from the VR on your monitor. Generally, it's best not to use full-screen mode if you're only flying in VR. This always saves some performance, and the CPU and GPU will focus more on VR. However, it's almost irrelevant. The image is set to a lower resolution than the monitor's image. To save power, but also to ensure the monitor displays only one eye in VR, go to startup.cfg and set or_render_eye = 1.

Full Screen - DISABLED. In my opinion, if you're using a lower resolution than your monitor, use frame mode (DISABLE). If you're using full resolution, use full screen. There's no fundamental difference for VR.

Upscaling - DISABLED. As I mentioned above, I don't use it due to artifacts and blurring (although DLAA smooths out DLSS very nicely). In my opinion, DLSS isn't suitable for online play, and it also has a lot of flaws in single-player. As you wish. However, it has a significant impact on FPS, as the image is displayed at a lower resolution than your headset and then artificially upscaled to a higher resolution. This can even provide a significant FPS boost (especially in balanced or performance mode). DLSS Modes - Quality 66.7%, Balanced 58%, Performance 50%, Ultra Performance 33% However, there are downsides to this solution. Enabling DLSS can significantly improve performance in the IL-2 Korea with the settings mentioned in this thread (up to +30 FPS or even more!). This will come at the expense of image sharpness and will add some artifacts. However, if anyone is still experiencing FPS issues, this option is worth enabling after testing with all these settings and then seeing how your IL-2 Korea performs in VR. I recommend setting the DLSS mode to Balanced or Performance. Korea uses the automatic preset M, so you don't need to change it in the NVidia panel.

Enable VR HMD - OPENXR, of course, has better performance and is a newer tool than OpenVR. Provided your headset supports OpenXR.

💬 VISUAL EFFECTS - in most cases, a huge impact on FPS, with some exceptions

Distant Landscape Detail - x2, previously, I used x4, which improves texture blurring but also adds objects, resulting in a noticeable FPS drop. It's not significant, but we're fighting every free frame in VR. However, there's not much visual difference between x2, x3, or x4 in VR, so it's better to stay in the middle.

Horizon Draw Distance - 100km, similar to above. 100km further looks fine, we still have a very long view range. I don't see a significant impact on FPS, and for me, whether it was 30 or 150 FPS, the difference was minimal (if your GPU can handle it). Let's stay closer to the middle. Smaller values cause significant blurring of terrain textures.

Distant Buildings - DISABLED. Enabling it doesn't have a significant impact on FPS, as we only see the lowest LOD of buildings. However, combined with low AA or even no AA, it will cause quite a bit of shimmering. Turning it off always saves power, but it also allows you to see from a distance that a given area is a city thanks to the texture, so there's no annoying shimmering. As you get closer, buildings will appear smoothly, it looks quite ok in IL-2 Korea.

Pilot Body Visibility - DISABLED. The pilot's body looks nice, although some of the controls are obscured. In VR, the pilot's body is quite well-made and creates a nice effect. It would be nice if it could be turned on and off, but in real time (with a key combination), not in the main settings. It doesn't affect FPS. If you like it, turn it on.

Canopy Reflections - OFF. This is where things get weird. Despite being such an unnoticeable feature that works really well in IL-2 GB and competing simulators, IL-2 Korea has a significant impact on FPS, ranging from 4-8 FPS depending on the scene, even on Normal mode. The effect adds dynamic reflections from the interior of the canopy, but it causes significant FPS drops.

Shadows Quality - OFF, we go back to the times of the potato. Even on Low, this significantly impacts FPS. These shadows are cast by the surroundings (cities, trees, objects), as well as those within the cockpit. Unfortunately, shadows significantly reduce FPS and are a major problem at airports or when flying low over cities. The drop is significant, sometimes exceeding 10 FPS over urban areas. It would be useful to separate shadows between those outside the plane and those within the player's plane, but that's not the case, so I suggest disabling it entirely, even though it's a step backward. This also requires in-depth developer work, as something isn't quite right. In competing simulators, including the IL-2, shadows don't generate as much load as in the IL-2 Korea. Optimization is undoubtedly needed here. Unfortunately, without shadows, the world and the cockpit interior look noticeably worse and lack depth, but this is a compromise in favor of FPS.

Clouds Quality - HIGH. You're below Ultra, but your graphical card should be able to handle it without any FPS drops. The clouds look great here, offering a lot of variety and effects.

Grass Quality - OFF. We're back to the Stone Age in simulators again, but it's another FPS killer at the airport. Grass takes 5-8 FPS during the takeoff run at the airport, and can also reduce FPS on low pass, especially near towns or villages, where we experience additional FPS drops for other reasons. Here again, compared to the competition and even the IL-2 GB, the IL-2 Korea performs poorly. The simulator looks simply bad without grass, but this element significantly affects the FPS during runways.

Mirrors - OFF. Another FPS killer. Especially at airports or low passes over cities. The innocent mirror, which has been in simulators for years, in the latest version, 1C, drains a significant amount of FPS. The mirror can reduce FPS by up to 8-12 FPS. Other aircraft visible in the mirror also have a significant impact (e.g., during the airport career). This is another strange element requiring optimization, because whether in the IL-2 GB or in the competition, it works really well without significantly affecting FPS. Here, even setting it to "Simply" already drains FPS and affects the resulting stutter. Of course, if someone flies online, this option should be enabled, even if they fly in single-player, more like a fighter. For now, I have it turned off and we'll see what the future brings. This option drains a lot of FPS, depending on the complexity of the scene and scenery.

💬 ADVANCED SETTINGS - none or moderate impact on FPS

AntiAliasing - Generally, it's up to you. OFF or FXAA is preferred (it simply has the lowest impact on FPS). OFF will give you the sharpest image, but with noticeable jaggies. FXAA will smooth it out a bit; it still might not be perfect, but it won't affect the performance of newer GPUs at all, so you shouldn't see any impact on FPS. This is a compromise, in my opinion, and when paired with higher-resolution VR headsets (above 4K), you'll get an acceptable image with good performance. DLAA looks the best, but it has a huge impact on FPS (without DLSS, no graphics card on the market can currently achieve maximum FPS with DLAA in more demanding scenarios). I haven't tested FSR AA (I have a GeForce). Interestingly, MSAA works quite well here at x2. It's less demanding on the system than DLAA, and the image quality is better between FXAA and DLAA. Sharpness is also preserved. Personally, I sometimes fly with MSAA x2, but in my professional work, I prefer FXAA for performance reasons. MSAA has a greater impact in airports and over cities. FXAA is a compromise between quality and performance.

Antialiasing Rate - x4 if you use FXAA (even x8 is fine, it doesn't affect my FPS but blurs the subtitles/stencils in the cockpit more), and if you use MSAA then x2.

Dynamic Resolution Factor - DISABLED. It does not work properly in VR and may also cause stutter and lag.

Sharpen - ENABLED. No impact on FPS. Depends on your preferences, it will sharpen the entire image, including textures, which is especially cool in VR.

SSAO - DISABLED. It provides better reflections and halo effects on the aircraft. It has a slight impact on FPS, around 2-3 frames. The visual difference is minimal and you usually won't even notice it during combat.

Indirect Lighting - DISABLED. Ray tracing simulation can have a significant impact on FPS depending on the GPU. It adds additional lighting effects and lighting with greater depth and contrast. However, the impact on FPS is there. You can live with simulators without it; it's better to have higher frames in a combat simulator.

Terrain Roughness - HIGH. It improves the ground contact of objects and adds certain effects. My tests show that it has no impact on FPS at all. Whether I had the settings set to Off or High, I got exactly the same FPS, for example, at the airport while taxiing. So I'm leaving it at maximum, why not?

Landscape Filter - SHARP. However, it depends on your preference. The Blurred option will create further textures that will be blurrier. The advantage is that this way you can get rid of shimmering if someone doesn't like it in its current form. Personally, I don't like this option, and the Sharpness option produces sharper textures. It has no effect on FPS.

Lighting HDR - DISABLED. This option is still in development; generally, most goggles don't support HDR, so it should be disabled. It primarily affects 2D flying. You can, of course, test it yourself, so the decision is based on your own experience. No impact on FPS.

Gamma Correction - 1.00. This is the default option, which looks the most appropriate to me. Again, it all depends on your preferences and the displays, how black levels and other lighting effects are displayed. It's your decision; it has no impact on FPS.

Use 4K Textures - ENABLED. It significantly impacts texture quality. Leaving it at 2K can make text unreadable, for example, on the wings from the pilot's position. The difference is quite dramatic. However, it all depends on your GPU. If you have more VRAM, use 4K; if less, disable 4K. I didn't notice any impact on FPS. Moreover, the IL-2 Korea, even at 4K and above the city, was below 11GB of VRAM. This option affects textures primarily for aircraft, but also possibly for buildings and other elements, although some of them have maximum textures of 2K or less. Check Enabled option.

Cities Optimization - FAVOR FPS. Honestly, this option doesn't make a difference in FPS with more RAM. The developers recommend leaving the preference set to prioritizing FPS over cities, so let's do that (unless we have a GPU with a small amount of RAM, e.g., under 8GB).

VR Resolution Factor - 100%. This option will lower your headset resolution and a specific amount. I recommend leaving the default at 100% unless you have high-resolution headsets, like 8K. In that case, it's worth testing lowering these settings, say, to 75%; resolutions around 4-5K (both eyes) should work quite well with these settings. Of course, it can have a significant impact on FPS, especially in the case of high-resolution HMDs. For Quest, leave 100%.

---------------------------------------------------------------------------------------------------------------------------------------------------

👉 Additional settings

💬 Oculus Debug Tool (for Meta users, Quest Link)

Pixels Per Dispaly ... - I use 1.2. This artificially boosts the resolution, creating the impression of better image quality. Depending on your hardware, 0 or 1 is the default resolution for the Meta headset. Try 1.1 first; if it's okay, you're good to go. This affects quality, and with higher resolutions, even AA won't be necessary. However, it does affect FPS, as IL-2 Korea doesn't like high resolutions. If you notice an impact on FPS, return it to 1 or 0.

FOV - Tangent Multiplier - 0.75; 0.75. The image in the headset is generic at full resolution, but the shape of the headset and the gasket mean you can't really see everything. You can therefore reduce the FOV (the displayed image, which you can't see anyway), which in turn has a very positive effect on FPS. While the previous option can negatively impact performance, this one has only a positive effect. Here, you can notice a significant increase in FPS. For me, 0.75 is fine (if it's not enough, try 0.80). I still don't see the black display frame, and there's a significant performance gain. I recommend testing this for yourself. Don't confuse this option with the headset's FOV (for the Quest, for example, around 110°). It doesn't change this setting until you notice it in the headset itself.

(PC) Asynchronous Spacewrap - DISABLED. I don't use any reprojection; it affects online combat, dogfights with AI, and attacking ground targets. If your system allows you to maintain a constant frame rate of 72FPS or 90FPS, don't use reprojection. This will also result in a sharper and smoother image.

BTW. Note that the popular OTT (Oculus Try Tool) program no longer writes data to the ODT. You'll need to manually enter this data each time, or follow my advice below to automatically overwrite these values before each simulator launch.

 💬 Creating the BAT file for ODT

How do I save and use settings to the Oculus Debug Tool (what mentioned above only applies to Meta Quest users if you make the changes above in ODT)? You need to use a BAT file every time you launch the IL-2 Korea and VR. I've included a few automated commands in this file. You'll need to customize them (see the example below). I've also attached a ZIP file with everything: a sample BAT file, a profile loading sound (this will ensure everything is working), and an icon for the VR Korea mode. Place the BAT file wherever you like (e.g., the IL-2 folder), create a desktop shortcut, and place it there. Go to the desktop shortcut properties (right-click), select "Run: Minimized," and specify the icon location (ICO file) for a more attractive appearance (Change Icon tab). Save it by OK.

In the BAT file, set this to your paths (I mark what needs to be changed in blue, the comment in red :

Spoiler

@echo off

:: =========================
:: OCULUS SETTINGS
:: =========================
set PixelPerDisplay=1.20 <<< set the pixel saturation to your preference, like default, delete this item 
set FOVx=0.75 <<< set the FOV you prefer, see description above
set FOVy=0.75 <<< set the FOV you prefer, see description above
set "asw=off" <<< it turns off my ASW every time

(
echo service set-pixels-per-display-pixel-override %PixelPerDisplay%
echo service set-client-fov-tan-angle-multiplier %fovx% %fovy%
echo server:asw.%asw%
echo exit
) | "C:\Program Files\Oculus\Support\oculus-diagnostics\OculusDebugToolCLI.exe" <<< check if this is really the path of your Oculus Debug Tool, probably yes, but make sure

:: =========================
:: LAUNCH Sound
:: =========================

powershell -c "(New-Object Media.SoundPlayer 'C:\Program Files\Oculus\Support\oculus-diagnostics\Sound_yoyo\IL2profileloaded.wav').PlaySync()"  <<< there must be a track for the sound here from ZiP file, folder with "IL2profileloaded"
timeout /t 1 /nobreak

:: =========================
:: LAUNCH IL-2 (VR)
:: =========================
cd /d "S:\IL2Series" <<< path to the main game folder
start "" "launcher.exe"

exit

This means you don't have to use OTT, which no longer works. You also have the peace of mind that ODT won't revert to its initial values, which sometimes happens.

💬 VectorXR

This is excellent software supporting VR users (OpenXR). This tool can improve the World Scale (in the IL-2 Korea, the default cockpits appear underscaled, too small; this option is called Stereo Depth/World Scale, and I have -5.9), as well as the Convergence (few options) and Pivot—which replaces the "neck saver." However, what we should be interested in in terms of FPS is the "Turbo mode" option (known from OpenXR Toolkit's mbucchia). You can create a profile for any game, including the IL-2 Korea for sure. I recommend keeping the Turbo option enabled. This option won't add much FPS (if any), but it will improve rendering time, which will primarily affect the feel of smooth gameplay (less stutter, thanks to direct data pipeline to GPU). The difference isn't huge, but it can be helpful in more complex scenarios or during combat. If you haven't used VectorXR yet, I recommend giving it a try.

You can read about the tool on the IL-2 Korea forum in many threads, but the original one, created by the author, is on the DCS Forum (the software is in development and there are also new noteworthy options, I highly recommend it)::

https://forum.dcs.world/topic/389658-introducing-vectorxr-open-beta-an-openxr-enhancement-suite/#findComment-5789322

---------------------------------------------------------------------------------------------------------------------------------------------------

The above settings allow me to maintain a constant 72FPS at 72Hz for about 95% of the time. The remaining 5% is caused by slight spikes in airports or when attacking a group of targets in single-player career mode. Interestingly, in tests over Seoul, I'm able to achieve 72 frames, which was unattainable for me some time ago, without changing some settings. These settings also helped me enjoy my IL-2 Korea career now, where I previously had quite a performance issue in VR.

How it looks with these settings (unfortunately, OBS always takes some of the power when I record something):

It works very well in multiplayer (some of the processes are handled by the server). Of course, I must add that this isn't the Holy Grail, and there's still work to be done for the developers, as we've clearly fallen behind in development. Optimization is a bit of a stretch, as things like mirrors and shadows were a long time ago, and these and some other basic options have a huge impact on the performance of a simulator like IL-2 Korea. This text can also serve as a guide for developers as to which graphical aspects are worth optimizing.

This was a long post, but I hope it helps you, at least at this stage, get the IL-2 Korea right, especially in VR. I hope I helped someone, if so, let me know below! 

⚠️ If anything changes over time, I'll gladly update this guide, and I sincerely hope that happens and that the developers continue to improve the IL-2 Korea's performance in VR. In the meantime, fly high and get many kills!

Good luck over the sky of IL-2 Korea title! ❤️

IL-2 Korea BAT file.zip

Edited August 16 by YoYo

[OAE]

Thanks ❤️

[OAE]

With Quest 3, 5080, 5800x3d, 64 GB ram this is the best experience I have so far in vr, but I can run with fov at 0 in ODT. Thanks again for the wake up call 😄

[LuftManu]

Great writeup @YoYo!

[Charger]

Some good tips there!

 

The terrifying part is turning the resolution down by 50% in a crystal super to match the performance.

 

I'm really struggling with VR in this game. Last night I fired up Great Battles again and was shocked at how beautiful the image (@1.0 res)was and how smooth the game ran.

 

Can we import the planes from Korea into GB?

[YoYo]

10 minutes ago, Charger said:

Can we import the planes from Korea into GB?

The obvious answer is no (not to mention that they are encrypted and it didn't work in IL-2 GB). Btw. I had a similar phase, after frustrations that were so serious that I started to think that something was wrong with my GPU and CPU, I checked IL-2 GB, which I hadn't used for a while, after this I was in a mental shock  how well this simulator works in VR and gives stable frames with still not bad graphics.

[GiftGruen]

This is a great guide, Yoyo - and you‘ve put a lot of effort into it. Highly appreciated!

I dont share your opinion for each single setting, that’s no surprise because I have another Hardware/ VR setup and also dont play competitive MP.
 

But it‘s a very good starting point and a highly recommended HowTo. We should PIN it !

[Valis]

Interestingly the Landscape Filter is referred to as 'Anisotropic' in the startup.cfg so I guess 'Blurred' is no anisotropic filtering while 'Sharp' is...4 maybe? It's not terribly aggressive - I wish higher values were available.

Also, the 'Terrain Roughness' - I wonder why it's even an option? Like Yoyo I've noticed no difference to FPS whatever the setting. Maybe it's CPU (Load) intensive?

Edited August 16 by Valis

[MajorMagee]

The file filter_settings.inc in the game\data\Graphics folder caps the Anisotropic filtering at 8.

[sandmarken]

Is deleting the startup.config file still a thing, or was that fixed during one of the updates?

[YoYo]

10 minutes ago, sandmarken said:

Is deleting the startup.config file still a thing, or was that fixed during one of the updates?

This doesn't really help, unless you've changed a lot of options yourself and can't remember what. Of course, I checked this once, but it didn't make any difference for me.

[sandmarken]

8 minutes ago, YoYo said:

This doesn't really help, unless you've changed a lot of options yourself and can't remember what. Of course, I checked this once, but it didn't make any difference for me.

Thx! And thx for the guide!

[JG4_Moltke71]

Hey @YoYo, nice summary, Maybe I'll want to try out one or two of the things you suggested

I try to do without anti-aliasing and rely on the high resolution of my Varjo Aero instead.
 

What I did notice, however, is that a setting that was working yesterday is failing again today, kind of weird 🤪

However, I have to say that, due to the shortcomings of IL-2 Korea regarding graphics and gameplay fluidity, I’ve started flying online again.

And I have to say, the game looks completely different from that perspective. It looks really good and runs smoothly (aside from occasional rubber-banding and the fact that targets often render very late).
 

But actually, the fact that the game looks good at times and bad at others—does that offer hope that there is still room for the developers to make improvements.

And so it should be, because I won't play a game that frustrates me for very long 😜

 

[Mark_Krieger]

Thany you very much @YoYo for spending time testing and sharing your experience. I have a 7800 X3D CPU, a 7900 XTX GPU (26.7.1) and 64 Gb of RAM and also Quest 3, and don't have experience with the FSR, so I'm still not sure what to do. 

Doesn't FXAA affect the detection of contacts in the sky? I think contacts detection is one of the aspects that has improved more compared to Great Battles, but precisely in Great Battles I played a lot of years with FXAA while I had a potato PC (1060 GPU) because of the performance untill a friend of my squadron recommended to use MSAA x2 instead of FXAA. Although worse for the fps, MSAA improved detection of contacts A LOT. Perhaps now in Korea with the improvements in contacts detection FXAA can be considered again?

First of all I have to solve some BIOS settings with wrong PCIe mode that limits the performance of my GPU (I've been playing during yeras having a lot of crashes in G B and Korea because of that and I didn't detect it until yesterday 😓), but once I solve that problems I will do some more testing. Your information es very useful. Thank you again!

Edited August 17 by Mark_Krieger

[GiftGruen]

@Mark_Krieger

You should switch on the "show signatures" ( at account settings => signature ) flag then you see YoYos hardware:

I can add that afaik he uses a Quest3.

Me, I am on Pimax and indeed prefer MSAAx2 ... MSAAx4 is a real fps-dropper but x2 works fine for me.

 

Edited August 17 by GiftGruen

[Mark_Krieger]

40 minutes ago, GiftGruen said:

@Mark_Krieger

You should switch on the "show signatures" ( at account settings => signature ) flag then you see YoYos hardware:

I can add that afaik he uses a Quest3.

Me, I am on Pimax and indeed prefer MSAAx2 ... MSAAx4 is a real fps-dropper but x2 works fine for me.

 

Oh yes, I didn't pay attention. It was already there. Thanks! I added mine on the signature too

[WWGeezer]

Does anyone know if you can run VectorXR and Virtual Desktop at the same time or do they conflict with each other?

[Husar]

2 hours ago, WWGeezer said:

Does anyone know if you can run VectorXR and Virtual Desktop at the same time or do they conflict with each other?

Yes you can, without conflict.

[Mrpink7]

Not using dlss is crazy. Use L model at quality it's better than native

[Husar]

1 hour ago, Mrpink7 said:

Not using dlss is crazy. Use L model at quality it's better than native

Not everyone likes it, especially in VR. DLSS uses DLAA as temporal anti-aliasing, so the image is a little softer and there is some minimal ghosting. It’s not as noticeable on a monitor because you’re working with a higher base FPS. Temporal upscaling and super resolution use information from previous frames to reconstruct the image.

 

[=ILS=_Abu_27]

很遗憾 我不能认同你的设置，你这个设置在实战服务器中不适用。

[TenienteDan]

I'm just writing to thank you for the guide.

It is very time consuming to test all the settings and with a 3080 12gb + Quest 3 and using wired Virtual Desktop, you gave me a very solid starting point.
After a few hours testing some settings I have settled with the same you recommended but with shadows on low.

There is definitely a lot of room to improve by 1C studios, because the low performance is not justfified compared to GB. Although I recognize the game looks better.
 

[YoYo]

1 hour ago, TenienteDan said:

Quest 3 and using wired Virtual Desktop

I also plan to test VD, but more on cable I suppose, so I'm waiting for the official Link version to be released. Some people praise VD's performance because the image rendering for headsets is slightly different, which may offer some benefits, perhaps in the form of improved performance:

Quest Link:

• The game renders a frame
• Oculus/Meta runtime executes its part of the pipeline
• The image is encoded
• USB transports data
• Quest decodes

Virtual Desktop:

• The game renders a frame
• VD takes over streaming
• GPU encoder encodes the image
• Ethernet → router → Wi-Fi → Quest
• Quest decodes

However, since I don't have a 5G router with good bandwidth, I'd like to use the Link. This isn't a major concern for me, though, as I believe the biggest performance gains will come from future changes made by the developers. I'm keeping my fingers crossed for that (still ).

[TenienteDan]

2 hours ago, YoYo said:

Virtual Desktop:

• The game renders a frame
• VD takes over streaming
• GPU encoder encodes the image
• Ethernet → router → Wi-Fi → Quest
• Quest decodes

The beta version of VD (Virtual Desktop) now supports USB 3.0 connection (many tutorials in Youtube-Reddit)
I had VD for many years, but always used wired via link with Quest 2. VD had many benefits but I always got a bit better experience using wired (even using a dedicated router for VR streaming).

But VD now with wired is :cheffkiss experience for Sims. That good that I bough a Q3 and its superb. 
Also with VD I didn't have to install ANY of the Meta software in my PC.

Q3, "unfortunately" is incredible value/price because of the specs and the versatility.

[Husar]

I was using USB -C to Ethernet adapter, best solution before  beta USB support.