VR experiences IL-2 Korea

[Jade_Monkey]

Any Pimax users tried the Sboys3 drivers? 

 

I'm going to try it with my Dream Air Slam tonight when I get back to my rig.

 

Not expecting a drastic improvement but anything that can help will be welcome.

[huligan]

who knows what is in the startup.cfg ?

or_rpm_max = 155

...

this I set to old real propeller (like in IL-2 GB)

prop_blur_max_rpm_for_vr = -1

 

Edited June 29 by huligan

[Blitzen]

After applying most of the advice that I can figure out found here I am getting a fairly steady 35FPS. This was about the same when I started playing GB and BoS years ago but now lower by far than either, but playable..🙃

BTW - How do iget the following info added to my profile:

Computer Specifications
CPU: i7-14700F
RAM: iBuyPower 2x16GB 5200MT/s
SSD: WD Green SN 3000 1TB NVMe
GPU: Nvidia RTX 5060

Edited June 29 by Blitzen

[YoYo]

55 minutes ago, huligan said:

who knows what is in the startup.cfg ?

or_rpm_max = 155

...

this I set to old real propeller (like in IL-2 GB)

prop_blur_max_rpm_for_vr = -1

I don't think I have the same problem as in IL-2 BoX/FC. There was indeed some slowdown there. Now I fly the Mustang a lot, haven't touched anything, and the animations of propeller in VR are fine for me.

[OAE]

Discovered something strange. started up oculus performance tool in Q3 to get an overview of "headroom performance" "...regardless of what graphics settings I only had minus 5% to plus 8% headroom, and...constant 72 fps.

What's happening? restarted the game between new settings but same lousy headroom. Now playing with everything on max without AA and upscaling.

BUT, if I fly low over houses/buildings it collapses with up to minus 200% in headroom and 20 in fps.

But why is there no difference between FSR/Dlss vs MSAAx4 in performance?  

RTX 5080

5800x3d 

64GB

Ps. The two single missions is just a mess. I test jusing task editor missions i make.

Edited June 29 by OAE

[brickcommander]

16 minutes ago, OAE said:

Discovered something strange. started up oculus performance tool in Q3 to get an overview of "headroom performance" "...regardless of what graphics settings I only had minus 5 to plus 8 headroom, and...constant 72 fps.

What's happening? restarted the game between new settings but same lousy headroom. Now playing with everything on max without AA and upscaling.

BUT, if I fly low over houses/buildings it collapses with up to minus 200 in headroom and 20 in fps.

But why is there no difference between FSR/Dlss vs MSAAx4 in performance?  

RTX 5080

5800x3d 

64GB

Ps. The two single missions is just a mess. I test jusing task editor missions i make.

For the same reason as everyone- your GPU is doing fine, yoy are cpu limited so changing graphics settings won't make any difference.

[huligan]

42 минуты назад, YoYo сказал:

and the animations of propeller in VR are fine for me.

with defolt prop_blur_max_rpm_for_vr = 155 there just translucent circle instead of a real propeller !!!(((

Only if "-1" propeller is real!

Edited June 29 by huligan

[OAE]

12 minutes ago, brickcommander said:

For the same reason as everyone- your GPU is doing fine, yoy are cpu limited so changing graphics settings won't make any difference.

Yes, I've noticed that, but when the CPU is not under pressure it should make a difference. Something is completely wrong. ( in the Main menu Page 2% headroom , in dcs 80% )

Edited June 29 by OAE

[YoYo]

6 minutes ago, huligan said:

with defolt prop_blur_max_rpm_for_vr = 155 there just translucent circle instead of a real propeller !!!(((

Only if "-1" propeller is real!

Ok, I'll check it out, but like I said, it looks fine to me as it currently is in VR. In the IL-2 BoX/FC, there was indeed a noticeable problem with animations.

[brickcommander]

23 minutes ago, OAE said:

Yes, I've noticed that, but when the CPU is not under pressure it should make a difference. Something is completely wrong. ( in the Main menu Page 2% headroom , in dcs 80% )

Do you have the ray tracing thingy enabled (i forgot how that is called). That is the setting that is killing you in the menu. And probably everywhere else.

[AEthelraedUnraed]

11 hours ago, brickcommander said:

It has a major influence on frame rate!! In great battles as well. And until recently in DCS. It is the reason that frame rate crashes over cities and with AI units in the air but is smooth as butter in the sky in a duel or small skirmish.

11 hours ago, OAE said:

Yes, it has a lot to do with fps when the CPU is throttling.

It's pretty easy to test. If the graphics engine is CPU-bottlenecked, you'd expect that:

1. The CPU load goes up in graphics-intensive scenes (especially those with lots of objects).
2. With a high CPU load, the FPS goes down.

When testing, it's important that you change only one thing; e.g. comparing normal flight with attacking a formation of 30 bombers doesn't work since you cannot (easily) differentiate between the CPU usage of the rendering pipeline and AI/physics. I've therefore done the following tests:

1. No dynamic objects except the player aircraft; looking down in external view; comparing Seoul with the empty countryside 20km onwards. Results:
   Performance over Seoul:
   CPU load 10-12% (min/max), framerate around 45 fps average.
   Performance over the countryside:
   CPU load 9-12% (min/max), framerate around 90 fps average.
2. Flying over the countryside, looking up from within the cockpit (to minimise the amount of rendering). After 30s, 48 MiGs, Sabres and B-29s are spawned on the other side of the map, outside of rendering distance (but physics/AI calculations are still done). Results:
   Performance before other aircraft spawn:
   CPU load around 10%, framerate 107-124 fps (min/max).
   Performance after other aircraft spawn:
   CPU load around 170% (and heavy time dilation), framerate 103-117 fps (min/max).
3. A combination of the above experiments. Circling over Seoul, looking down, after 30s other aircraft spawn to overload the CPU. I've waited 1 full circle to sample at approximately the same point over the city.
   Performance before other aircraft spawn:
   CPU load around 7-11%, framerate 52-56 fps (min/max).
   Performance after other aircraft spawn:
   CPU load 170-180% (and heavy time dilation), framerate 49-52 fps (min/max).

In the first experiment, there was a very minor increase in CPU load in graphically intensive scenes, of which I doubt it's statistically significant (cf. experiment 3). The CPU load stays quite low even above Seoul, although the framerate halves. In the second experiment, the framerate drops by about 5% after the CPU is overloaded. The third experiment corroborates the results, showing a small framerate drop of around 6.5%.

Note that a part of the rendering pipeline happens on the CPU, so a small drop in framerate is to be expected if the CPU is overloaded (which is indeed what we see). These experiments do not point however to the CPU being a particular bottleneck on the graphics, nor to the CPU having a major influence on the frame rate.

Overall, IL2 is certainly CPU limited as you see major time dilation in large battles. The CPU specifically limiting graphics however, is not something consistent with these experimental results.

Edited June 29 by AEthelraedUnraed

[Dash,Polder]

4 hours ago, huligan said:

who knows what is in the startup.cfg ?

or_rpm_max = 155

...

this I set to old real propeller (like in IL-2 GB)

prop_blur_max_rpm_for_vr = -1

 

Thanks for that, completely fixed the watery wave in the prop caused by running Smart Smoothing on my Pimax.  The prop was the only place it was visible.

[huligan]

3 часа назад, YoYo сказал:

In the IL-2 BoX/FC, there was indeed a noticeable problem with animations.

if you set real prop,use prop_blur_max_rpm_for_vr = -1

but don't disabled ASW(SSW in VD) you'll may see broken picture through the propeller in cocpit. Because of this developers add in game  this setting(prop_blur_max_rpm_for_vr = 155) for stupid VR users,who doesn't turn off ASW(oculus link) or SSW(VD)

 

[Panzerlang]

Running the regular EA version. Pimax Super at 0.8 render. Black Thursday mission. With the settings shown in the image I was around 85% highest CPU load. Lowest FPS was mid forties. Highs of over 70. The B29s did display a bit of stutteriness on occasion but it was all playable.

[=ILS=_Abu_27]

13 hours ago, Jade_Monkey said:

有没有Pimax用户试过Sboys3驱动？

 

今晚回到装备后，我打算用Dream Air Slam试试。

 

我不指望会有明显改善，但任何能帮到我的东西我都非常欢迎。

我测试了包含sy3的 evoapp ， 出现了不稳定跳动bug，闻讯过厂家，他们说是和5090 有些兼容性的问题，建议回退版本。

[=ILS=_Abu_27]

4小时前，Panzerlang说：

我用的是普通的EA版本。Pimax Super渲染0.8。黑色星期四任务。在图片显示的设置下，我的CPU负载最高大约是85%。最低帧率只有四十多。最高气温超过70度。B29偶尔会有些卡顿，但都能正常使用。

你可以把vr改成72帧，然后按照我的设置，你可以基本做到 全程72帧，且流畅不会出现重影延迟之类，且画质优美

Edited June 30 by =ILS=_Abu_27
更新设置图片

[Panzerlang]

I can't, I'm unfortunately one of those who can see the flicker at 72hz.

[=ILS=_Abu_27]

我也曾经以为我是，在bos里面我一直是选择90hz。 但是在korea里面卡顿延迟面前，我发现我似乎看不出72的闪烁了。 试试吧朋友~ ~ 等到他们优化好了，再恢复成90hz更有收获感。

[Panzerlang]

3 minutes ago, =ILS=_Abu_27 said:

I used to think I was the one who always chose 90Hz in the Boss system. But in Korea, when facing lag and delay, I found that I couldn't seem to notice the 72 flicker at all. Give it a try, my friend~ ~ Once they've optimized it, restoring it to 90Hz will give you a better sense of success.

I tried it accidentally yesterday, Pimax Play had an update and I did a clean install. That defaulted the settings to 72hz and I noticed it immediately in the game; it was aweful.

[=ILS=_Abu_27]

Just now, Panzerlang said:

我昨天不小心试了一下，Pimax Play有更新，我做了干净安装。这样设置默认为72Hz，我在游戏中立刻注意到了;那真是太糟糕了。

建议不要更新最新的版本app，有些人会发生跳动闪烁，以及丢失定位的问题，特别是5090的用户。

[Panzerlang]

22 minutes ago, =ILS=_Abu_27 said:

It is recommended not to update the latest version of the app; some people may experience flickering or location loss, especially for users with 5090 devices.

Working fine for me at 90hz.

[=ILS=_Abu_27]

7 minutes ago, Panzerlang said:

我在90Hz下工作正常。

那恭喜你，注意到了你的是水晶super 不是 dreamair，所以没有这个问题很好。

[robzerg]

17 hours ago, MrWound said:

Try different resolutions at the same settings page: the support for upscaling is somehow (bug?) tied to those. 

OMG this worked - thank you so much!!! For some reason setting the screen resolution relatively low (as I always did in GB as it didn't affect VR) disabled upscaling.  I'm now able to get a playable 50-60 fps, and was able to turn some of the eye candy back up - apart from over cities or the black thursday mission!

[Gunfreak]

20 hours ago, brickcommander said:

Dcs doesn't calculate real physics on ai aircraft. They all are ufos (or uap in the new parlance). 

And in IL2 they do lazy left turns. Both are terrible. But at least DCS runs well

[Mephisto]

Did some test and ended up with below, maybe it will be found helpful:

**Hardware**
CPU: Intel(R) Core(TM) i7-14700K
GPU: NVIDIA GeForce RTX 5080 with 16GB 
RAM: 32 GB
VR: Meta Quest 3 via Link cable
 

**Nvidia Control Panel**
- Power Management: Prefer Maximum Performance
- Low Latency Mode: Off
- Vertical Sync: Off
- Max Frame Rate: Off
- Texture Filtering – Quality: High Performance
- Texture Filtering – Negative LOD Bias: Clamp
- Texture Filtering – Anisotropic Sample Optimization: On
- Threaded Optimization: On
- Shader Cache Size: Unlimited
- Antialiasing – Mode: Application-Controlled
- FXAA: Off
- Image Sharpening: Off
- VR Pre-Rendered Frames: 1

**Meta Horizon**
- Render Resolution: 1.4×
- Refresh Rate: 72 Hz
 

**Oculus Debug Tool**
- Video Codec: H.264
- Encode Bitrate: 700 Mbps
- Encode Dynamic Bitrate: Disabled
- Sliced Encoding: On
- Encode Resolution Width: 0
- Link Sharpening: Enabled
- Local Dimming: Enabled
- Distortion Curvature: Low
- Asynchronous Spacewarp: Disabled

**Windows**
- HDR: Off
- USB Selective Suspend: Disabled
 

**OpenXR Toolkit**
Unfortunately I needed to fully disable it as the game would crash very quickly with it. After disabling no single crash. Current pita is that there is no adjustment for world scale and the cockpits look very small...

**IL-2 Korea — In-Game Graphics**
- General Graphics Quality: High
- Full Screen: Disabled
- Upscaling: Disabled
- Enable VR HMD: OpenXR
- Distant Landscape Detail: x4
- Horizon Draw Distance: 150 km
- Distant Buildings: Disabled
- Pilot Body Visibility: Disabled
- Canopy Reflections: Off
- Shadows Quality: Low
- Clouds Quality: High
- Grass Quality: Off
- Mirrors: Off
- AntiAliasing: MSAA 2×
- Dynamic Resolution Factor: Disabled
- Sharpen: Enabled
- SSAO: Enabled
- Indirect Lighting: Disabled
- Terrain Roughness: High
- Landscape Filter: Sharp
- Lighting HDR: Enabled
- Use 4K Textures: Enabled
- Cities Optimization: Favor FPS
- VR Resolution Factor: 100%

**startup.cfg**
- fps_limit = 0
- bloom_enable = 0

This now runs 72 fps for me most of the scenarios I tested with a good overall picture quality…