Katmandu

VRAM is around 15Gb when flying over plains and around 16GB when flying over the forests. I've used Pimax new tool that came with the 1.43.1 update and it shows my GPU utilisation to be around 80% when flying over the plains and 98-99% when flying over the forests. CPU is at around 30-40%. So it looks like 5090 is not enough after all, not even for the empty Caucasus map This is with Image Quality set to 1.00 in Pimax play and 110% foveal resolution rendering 20% by 25% area in QV, peripheral resolution is set to 5%. What is weird is that I get the same 99% GPU utilisation with potato quality visuals of Image Quality 0.30. Fewer stutters over the forests, but significant stutters nonetheless. I attach my short replay so that you could try it on your PCs. It's Su-25T over Caucasus, so will work for everybody. Press RCtrl+ScrollLock to get the ingame fps and frametime graphs. vr stutter forest.trk

Could it be down to the 8KX using Valve base stations and thus more efficient tracking algos that don't tax the CPU quite as much? E.g., in their own testing Pimax found that the OG Crystal vastly outperformed Crystal Light even when NOT using eye tracking/DFR in DCS. Crystal Light does its tracking on the CPU, while the OG Crystal uses its stand alone snapdragon chipset to do the tracking. (Going forward, this forms a good argument for standalone headsets like the OG as their own CPU will be doing the head AND eye tracking calculations.) @13:45 I have it installed, will need to play around with it as I've never used it before. In my case, the best limit is 90fps. Set at 120 I get saw like frametime even when flying over non-forested terrain.

It's not just Caucasus and it's not just forests I now find. Circling the same patch of desert in Nevada leads to stutters over some patches of terrain, but not the others. This is far away from Vegas, near Groom Lake. The graph is always showing CPU bound, so it does not seem to be related to the resolution of the headset, but to something else that hammers the CPU. I am using Quad Views, the stutters are identical with stock PimaxPlay and Mbucchia. My system is 9800x3d, 64gb, 5090, win11. I've got two different version of DCS, the current latest one and the April 2025 2.9.13 version - the stutters are near identical.

В списке иранских побед выше есть 10 МЛов, вот он еще раз https://en.wikipedia.org/wiki/List_of_Iranian_aerial_victories_during_the_Iran–Iraq_war ЕД вроде тоже от размеров отталкиваются, но на форуме была контр аргументация https://forum.dcs.world/topic/272236-new-flares/#findComment-4901435

Я про "MJU-7 макс сила излучения 20.3-21.8 кВт/ср", в ссылке выше этих чисел нету

My system is 9800x3d, 64gb, 5090, win11. I get stable 90fps when low flying above *normal* land with a few trees, villages, etc. Once I low fly over some forests, my frametime turns into a saw and i get constant stutters. No issues on 4k flat screen of course. DCS Settings: Flat screen over forests: VR over forests (bad graphics appearance due to quad views): VR over normal land with some trees and buildings (solid 90fps, the solitary spike is due to screenshot): What can be done is the question! Could it be Pimax headtracking sapping the CPU? I attach my short replay so that you could try it on your PCs. It's Su-25T over Caucasus, so will work for everybody. Press RCtrl+ScrollLock to get the ingame fps and frametime graphs. vr stutter forest.trk

У Хорнета пишут MJU-8, MJU-7 я не нагуглил инфы, поделись линками Иранский Ф-14 был сбит и МиГ-21ым , но список побед у иранских Ф-14 большой: https://en.wikipedia.org/wiki/List_of_Iranian_aerial_victories_during_the_Iran–Iraq_war А у иракцев против Ф-14 побед мало или я не нашел http://www.acig.info/artman/publish/article_404.shtml Ф-16A был принят на вооружение в 1976м, МиГ-29 - в 1983м-1987м. Ф-16C тоже из 1980х (блок 25-32), блок 50 приняли в 1991. https://raafdocumentary.com/50-years-of-the-f-16/

F-14 стоит как оплеванный https://ordtech-industries.com/mju-8a-b-for-nato-a-c/ Peak Output 1> 40 KW / sr Dispenser AN/ALE-29, AN/ALE-39 Platform F/A-18 Hornet, A-7 Corsair, A-4 Skyhawk

Double tap does not work on mine, I've done finger tap dancing in every possible way and my headset was left unimpressed. i wonder if a new optical engine I've got coming will solve this. The controllerless mode is a nice workaround, this does work - thanks!

Yeah, the setting is there , but nothing happens when I doubletap. Which part do you double tap - the faceplate or the side? Neither side works for me, I've tried light taps, harder taps, slower, quicker... Passthrough does work, but only when I pick up Pimax controllers, go into the menu and select passthrough - way too many steps. null

When I was testing my UW in ROG FOV Test suite in Steam VR, there was one test where you read a bunch of text paragraphs of different font sizes. With PimaxPlay sharpening off I could read the size 12 almost comfortably, 10 and 8 were unreadable. With sharpening set to the default 0.6 I can read size 10 almost comfortably, 8 is still unreadable (I'm looking forward to trying 57ppd). In DCS shimmer is not an issue, rFactor2 has some shimmers regardless of sharpening settings for me.

Glad I'm not the only one. For me, it's mostly the left one. I wonder if the issue is in the fans, perhaps they run in silent mode and one of them is too slow or does not turn on? Hypothesizing of course. I've double tapped all sides of the headset and nothing happened, I assumed the doubletap tickbox in the Play was for the earlier Crystals.

I am very happy with the support so far, although I went through the ticket system, not the chat. I also had to wait for two-three days for every reply which is less then ideal, but the overall quality the responses and my satisfaction of the outcome was pretty much perfect (won't divulge the details to avoid Pimax agents' kindness being gamed ).

Does anyone else have issues with the lenses steaming up when initially putting on the headset? Its screens warm up after a few minutes and the fan kicks too, so stops being an issue, but the early few minutes I have to take off the headset and wipe the lenses at least a couple of times. I wish we could have a setting/button for an earlier fan start. Speaking of buttons, I also wish I could map one of the 3(?) buttons on the super as a video passthrough button. I know that there is a keyboard combo that is configurable in PimaxPlay, but it does not work for me when I am in DCS. Again, quite often I only need to glance at the keyboard or behind me, but have to take off the headset and put it on again. This would save many hundred of unnecessary headstrap hinge operations and save Pimax from quite a few related warranty claims

Thanks, tried the QuadViews+QuadViewsCompanion and you're right, transition thickness is exactly what I wanted in Pimax Play. I did not see any performance gains though and imo Pimax Play 1.43 looks better - apart from the jarring box around the foveal area. Maybe it's something to do with Pimax's own sharpening setting which I have on 0.6, although this could be a placebo.

At the moment we have 2 custom render states in Dynamic Foveated Rendering: the foveal region and the rest of the scene. This is good, but the border between, e.g., 120% resolution and 10% resolution is a bit too jarring and noticeable. Could we have 3 regions: 1) foveal for its 100%+ resolution 2) the intermediate region for 40%+ resolution and 3) the final low resolution area. I know that I cannot even count red lines in my peripheral region on a standard FOV test, so there is no need to render anything beyond 5% of max resolution there. But rendering all but the central foveal area at 5% looks meh.

Read again my original post In DCS version 2.9.13.68180 replays work perfect with no AI desync. The problem only appeared after ED introduced mid mission save states. It's a new bug that I am reporting, not asking for new features. Thanks for the answer! As I've answered above, I think there is some misunderstanding, I am merely pointing to the fact that AI desync in replays started happening after DCS version 2.9.13.68180, so in all versions starting with DCS World RELEASE 2.9.14.8222 03/19/2025 MISSION STATE SAVE, 2 NEW CAMPAIGNS, HOTFIXES Therefore it's a bug, i.e., a conflict of mission save state and replays (specifically AI in replays).

Relative to other VR headsets - perhaps, but relative to RL there is still a fair way to go. Certainly as far as 50ppd goes. I cannot read the top section in the text reading tests in the ROG Fov test in Steam Vr for example. I've got it at 1.6 and tried it even lower, also my general brightness slider for both eyes is set to 90%, and I've tried it with 80 and lower... The screens get dimmer, but the colours are still muted. Not so noticeable on the desert maps, but Caucasus is obviously off and looking bland green. My QLED monitor is much more vivid. But another big selling point for the 57ppd is the distortion profile with much fewer pixels. 50ppd Ultrawide has 6080x7152=43.5Million pixels per eye, 86Million altogether. 57ppd has 4348x4588 = 20Million pixels per eye, 40Million altogether. Steam VR 100% resolution (See the official pimax vid above). A crazy difference! My 9800x3d and 5090 struggle with Super Ultrawide in DCS when flying through the weeds in Caucasus, even with quad views and DLSS.

I am actually in the other boat, I'm in the trial period with the Ultrawide and thinking of switching to the 57ppd. I want more clarity (distance is still blurry, eg 100, 200, 300m markers in racing games; distant hills and villages in DCS too), the 134deg FOV does not feel that wide after all, and 57ppd uses a different distortion profile to the 50ppd that results in 30% fewer pixels rendered and thus 30% more FPS: @7:31 My UW has good enough sweetspot after the nightmare sweetspot that was PSVR2, but it also has CA fringing just like the OP's 57ppd, and some mura (this I'm not sure if it's borderline ok or borderline fail on my UW). The colours are washed out even during day time as well.

New version, same issue: simple Single player 1v1 guns only vs AI and it desyncs very quickly. Here are the tracks for the flight and for the replay. desync AI p51 ver2.9.21updated replay1.trk desync AI p51 ver2.9.21updated flight1.trk

Will there be a "Lab Mode" - software profile that extends the field of view - for Super UltraWide, like there is one for the Super Standard? Ultrawide is not scratching my wide FOV itch atm, it feels only slightly wider than any other headset.

Like you, I would love to PAY for a working replay system! My current workaround is to stay on version 2.9.13.68180 - the last version before mission state save was introduced and the last version that had good replays. All subsequent versions have severely crippled replay, as I've described here:

Have you tried the solution of Aries144 below?

С RWR F-14 что-то пытались изобразить https://forum.dcs.world/topic/201135-no-bug-rwr-jester-picking-up-launches-on-other-aircraft/#comment-3821581