WipeUout

I see this clearly using Caucasus in winter time, less elsewhere. Apparently caused by a DCS shader that need fixing, been reported long time ago but still no fix.

Not a huge difference in performance but 552.44 is still better than 560.81 for me. Getting a GPU Frametime increase of 0.15 ms on average with 560.1 compared to 552.44.

Selecting a f-15E slot and then re-arming with dumb bombs such as mk-82/83/84 or Durandals, I can't then select them in armament page to set drop mode, fuse, etc. The plane has to have the loadout from entering the slot, changing after does not work. Or is there a reset somewhere that needs to be done?

A few issues: Getting double A2A kill points. I get notification for points earned when airplane is killed and again when the downed airplane body crashes on the ground. Although nice to get 150 points instead of 75, not sure this is intended nor if related to DML or DCS. Other issue is with stopGap. Although disabled through the config trigger zone, it activates back if I go into slot select, then hit cancel, then re-select blue faction.

Been playing for a couple of hours and all seems good so far.

What you effectively did is decrease your resolution to 50% and then increase it by 289%. The result is a resolution at 144%. What you could simply do is leave your HMD resolution at 100% and increase your PD in DCS to 1.2 and this will result in the same 144% increase, and spare some processing. You can also increase your HMD resolution to 144% and leave DCS PD at 1.0, it will be the same result. You can test both and compare if there are any FPS gain, sometimes processing is done more efficiently by the HMD compared to DCS and vice versa...

Yes it does, there are two options in Pimax play: Native or Upscale. Native has 3 different refresh rate, 60, 75 and 90hz. Upscale has one refresh rate of 110hz. I believe that upscale uses 2.5k images and then upcale to 4k. But my point was abnout getting maybe different refresh rates for the upscale mode. It is nice to have this feature but increasing the refresh rate kind of negate the gain.

Will this feature be available for the 8kX as well?

Anyone noticed a quadviews box in settings? I do use quadviews and see the box is checked but shaded out as well. Any idea what this setting is?

Unfortunately, the original 8K was limited in quality because of the panels and upscaling. If my memory is good, I think they were taking a 2.5k image and upscaling it to 4k which caused lot of loss. The panels were not optimized for VR with too much spacing between pixels. Other issue was that even the 4k panels were not used at 100% but someting like 80% which also does not help. The second iteration of the 8k, the 8k+ was a bit better but still upscaling from a 2.5k image. It is only with the 8kX that the image was native 4k per panel but with a huge cost in processing power. I have a 4090 and it is still not possible to run the 8kX at full potential. Even if you upgrade your GPU, it will not improve much the quality of the image. You might get a more smooth experience with more eye candy like high textures and details but the image will remain lower resolution and require you to use VR zoom to see panel instruments well. But you will still get this wide FOV which provide a better sense of imersion in the 3D world compare to binocular type FOV in the majority of HMD out there.

This is the resolution for the focus area, at 1.2 you are supersampling it at 120% of its native resolution This is the resolution outside the focus area, at .4 you are undersampling it at 40% of its native resolution These are the focus area dimentions as a % of the total screen, horizontal 25% and vertical 35%. if you open your log file within the quadviews appdata folder after running it at least once, you will see the total original pixel count and the resulting pixel count from Quadviews and the estimated ''savings'' you get. The outcome is a significant reduction in image processing and increased FPS.

This for me also.

In general, supersampling means rendering an image at a higher resolution than what your hardware can display (also called native resolution). If you set the focus area at 1.0 then this means you want the images to be rendered at the same resolution as your hardware or 100% resolution. If you set the focus area at 1.2, then you are asking 120% of your hardware resolution which is superior resolution or supersampling. If you set it below 1.0 such as 0.8 then you are undersampling the image at 80% of its native resolution. Without going too much into details, image processing in VR is done with several passes and the images can degrade quite a bit at the end. When you supersample, you gain back some details that were lost during processing but at the cost of giving more work to your system to output the image. If you have a very high resolution, undesampling will reduce the burden on your system by processing less pixels but will increase your FPS but with less quality images, or less resolution. Pimax software has a slider to alter resolution under "games" but it will apply to the whole image, it is better to leave it at 1.0. DCS pixel density is another way to supersample/undersample also but leave it at 1.0 there as well. It is better to use Quadviews to alter resolution since you will have more felxibility as the image is divided in two area than can have different resolution.

No, matching max framerate with your HMD refresh rate will introduce stutters. I leave it at 300 in DCS. MFD readability is very subjective. With my Pimax 8KX and a focus area at 1.5 supersampling, I do not need to use any zoom but if I use DLSS/DLAA then I need to use the zoom sometimes. CAS sharpening should help, do you see a difference in the ouside view? Maybe not much in the cockpit but the outside view should be definitely better. Not sure either, but your config file should look like this: # These settings are for all headsets and applications smoothen_focus_view_edges=0.2 sharpen_focus_view=0.7 turbo_mode=1 [Pimax 8K] # These settings are specific to Pimax 8K. peripheral_multiplier=0.4 focus_multiplier=1.2 horizontal_focus_section=0.25 vertical_focus_section=0.35

You need to create a specific section in the config file for your HMD. I am away from my computer on a business trip now and back home only Thrusday. These two values are not for the focus area but transition from focus to oustide (smoothen_focus_view_edge) and using CAD sharpening (sharpen_focus_view). I suggest leaving the transition to 0.2 and set CAD to 0 and use CAD in OXRTK instead as it is far more efficient there with identical results value for value. Personnaly I use CAS at 100% in OXRTK. If you look at the example in your screeshot that starts with [Oculus] this is the section you have to create with your HMD name. for me it is [Pimax vision 8K X]. I'm not 100% sure but I think you can have also the HMD settings in the section for "all headsets and applications", maybe give it a try. Then you change the exact same settings that you see in the example to something like this: peripheral_multiplier=0.4 focus_multiplier=1.2 horizontal_focus_section=0.25 vertical_focus_section=0.35 ... yes this is fine.

If you have the 8k+ or the very first 8k, then you will need to ease on supersampling. Just to manage expectation, you will never get the same clarity as a G2 in the sweet spot. You are basically giving up some resolution for the widest FOV. You also need to understand that your GPU might not have the hosepower to deliver the best that the 8k can offer. First start by applying render quality "custom" with slider at 1.0 in Pimax play / device setting / Games / Render quality. Ensure OXRTK resolution is also at default and pixel density in DCS at 1.0. Next ensure your HMD refresh rate is a low as can be tolerated. If I remember well, I think you may have something like 72Hz or 90Hz. The lower will be easier to sustain. The aim is to ensure you can keep your FPS at the refresh rate. Use the nomal FOV which is about 140 degrees horizontal and quite good. If you try to use wide FOV, it will be very demanding. Next install Quadviews and follow instruction to create your config file to have you focus view supersampled at 1.2 and the outside of focus at 0.4. Next try to set your focus area of 25% x 35%, it may seems very small but with the wide FOV, it will cover a lot nevertheless. You can then start increasing the focus view over 1.2 and see if you can sustain it. If you want to use sharperning, use CAS in OXRTK, it is the best performance sharpen tool period. You can also use DLSS/DLAA to gain a few more FPS and reduce shimmering at the same time. There are several other approaches but from my experience, this is what gave me the best performance. Finaly, what is a good experience in VR is different from one person to another, try to experiment...

One way to even the playfield would be to base the dot rendering size on apparent PPD in the HMD. I don't know if DCS would have access to all the data required to make that calculation, i.e. what is the HMD's panel pixel size, super/under-sampling rate used, AA or any other factor influencing the apparent PPD.

See attached mission. The player is sitting in a F/A-18C, facing 6 planes (MIG-29) at 1, 2, 4, 8, 12 and 16nm. I start the mssion and press pause immediately. 1 and 2 nm: Shape 4 and 8 nm: Black dot, similar size 12 nm: Smaller black dot 16 nm: Small grey dot difficult to see I use DLSS Balanced and DLAA. This is a static test and when things move, you may have more difficulty to see farther targets because of DLSS. Closer targets are easier to spot because of jet smoke. SPOTTING TEST.miz

HMD Pixel size seems to matter quite a bit here. Low resolution such as the Rift S would have a pixel size between 50 to 60% bigger than a Pimax Crystal. If the bandit is represented as a simple pixel, lower res HMD will have a much better chance to see it unless the higher resolution HMD has the bandit represented by more than one pixel. No easy solution to this, so many different HMD resolution out there...

Yes you are right, it is the other way around. Still, we need some sort of adjustement to ensure everyone see target at similar distances to ensure fairness, and it should be automatic to avoid tempering.

VR vs Pancake and who as an advantage in spotting targets. Pancake use a monitor that has a very good resolution, in most cases over 50 PPD. If you consider that you have a 4k 32'' monitor about 60 cm from your eyes, it would cover about 67 degree of your horitonzal filed of view resulting in a 57 PPD angular resolution. My HMD has a 25 PPD which is less than half of a monitor. To simplify the issue: If we consider a target at a distance that is showing as one pixel in size on the monitor screen, it would need to be at least two pixels in size in the HMD in order to see it. This means that for me (VR user) to be able to see a target at a similar distance as a pancake simmer, I need to have twice the size target to nullify the monitor user advantage. Hense, the case of having adjustable dot size for taking into account resolution. Not all HMD have the same angular resolution and dot size need to be different to account for this. I think that prior to 2.9.6, VR had dots way too big and now it seems smaller but more fair. It is important though to keep in mind that resolution of VR HMDs varies a lot and there need to be different dot sizes, maybe set by DCS automatically?

I use Quadviews with my Pimax 8KX in fixed foveated rendering (FFR) or "without eye tracking" and it is broken as well since latest DCS patch. I get stutters and bad performance. Quadviews in FFR gives a great boost in performance even without eye tracking when compared to Pimax's FFR or OXRTK's FFR. Update: Last patch (2.9.6.58056) corrected the Quadview bug, it is back to awsome fluidity and performance!!! Thansk ED, and thanks again @mbucchia.

It can work, but only if you use SteamVR as your openXR runtime. OpenXR Toolkit is optional. But in any case, it is a huge hit on performance going through SteamVR.

Same, I can't fly DCS without my VR This For the heck of it, I got the old track-IR back up yesterday and could handle it more than 2 minutes... Pancake Simming no more. @mbucchia : Many thanks for your devotion to this community, you should get paid for what you did!!!