Baldrick33

It has taken a long time to get promoted to stable but that feature was added to the WMR for SteamVR beta back in May 2021. So I don’t think it is quite as ground breaking as it may sound given many of us will have been experiencing the beta for many months without noticing it!

Distortion is normal, it is the effect of lens shape up close to your eyes. The compensation is to remove the pincushion effect image seen through the lens to a rectangle by applying distortion to the image on the panel. Supersampling simply improves the quality of image by increasing the pixels to compensate for the stretch the distortion in the centre. My guess is that when the G2 was developed it was considered there would be more computer power allowing HP to up the target resolution and develop lenses accordingly.

You shouldn't see distortion at lower resolutions but a lower image quality as you experienced. The compensation for barrel distortion causes the pixels to be further spaced in the middle. By packing in more pixels it simply reduces the space between them. So you end up with a higher resolution than native to achieve higher quality in the centre. Or something like that!

The explanation for higher than native panel SteamVR 100% figures refers to the barrel distortion of the lenses, to ensure you get the right level of pixels in the centre area (which results in higher numbers around the edges hence higher than native) The typical figure quoted is 1.4 but I assume it must be dependant on the physical lens design. 1.4*2160=3024 so the 100% SteamVR figures are pretty much spot on. The G1 has a 100% SteamVR of around 2160 - its native panel resolution which is more unusual. Whether this is tweaked for performance I am not sure but HP did say the G2 lenses were different (better) and optimised at higher settings from the G1. Having tried both my findings were the G2 has greater clarity at its higher resolution settings than a G1 at the same high resolution, whereas the G1 at the lower (native) resolution looked equal or even better than a G2 at the same resolution, so that proved in my mind at least that the G2 lenses were designed to run at a higher resolution.

You are right in that the early settings for G1s were set low in SteamVR. The "magic" figure was 188% to get native 2160x2160 resolution. Later SteamVR was updated and 100% was 2160x2160 or thereabouts as is now. My understanding was the G2 has different lenses that by design need the uplift you describe to get the optimum image. Having had both G1 and G2 in my experience running at the higher resolution benefited the G2 much greater at the cost of course of performance. I believe although they have similar res panels by design the G2 is optimised to run at the higher resolution as reflected in SteamVR 100% figures. Running a G2 at 50% was less clear than a G1 at 100% although much the same resolution settings in SteamVR. That is why I ended up keeping the G1 as a PC upgrade is some way away!

Thanks @Olmba Yes it worked! The only issue I had was that Voiceattack was then left listening. I needed to add command (and button) to release TX1. If I added release TX1 as a third line to the command you described then the menu popped up and instantly disappeared

The post I linked to refers to the OpenXR Toolkit which includes FSR functionality. I think it is safe to assume you can't run both tools.

I think it just is very subjective. I can't stand anything less than refresh without motion smoothing. The moment it drops below I can see it and for me it kills immersion because it no longer mimics how we see things. I do seem sensitive to these things though. I can tell if a streamed sports game on TV is being processed at a low frame rate (e.g. my LG TV NowTV app compared to a stick in the same TV). Occasionally my G1 displays at 60Hz although it says 90 and restarting fixes it and I can't run at 60. I think VR highlights just how differently our brains are wired

You have to turn your head a lot more in VR regardless as it is 1:1 mapping. Turn that much and you can’t see the monitor! The limited FOV and sweet spot just increases the difference in movement.

I prefer to run with menus off and just use "Options" if I need something not available (e.g. Mosquito prime engines). However, if playing late on headphones and not using voice I would like to be able to just use options to bring up the menu rather than reconfig VAICOM (plus I prefer to control the menus rather than allowing it to pop up) Can I bind a button to the "Options" keyword command?

Just on the off chance but you are checking the slew under axis settings in DCS?

Yes, you don't want to be lifting your headset to navigate the menus

By default Ctrl-F2 opens up the Toolkit in VR, then you move left or right with Ctrl-F1 as left, Ctrl-F3 as right. Ctrl-F2 will take you down and Ctrl-F4 up as I recall. I changed these as they also are used by default with DCS. You can change the menu timeout but of course you need to find it before it times out! Just moving the cursor around with the F keys (or whatever you choose) will keep the menu alive.

Well done for persevering! With my G1 and lesser PC the advantages I have seen are when the frame rates are lower. The Apache strains my system a lot more than yours so maintaining 45fps with MR on is a challenge. OpenXR allows me to have MR at 30fps which appears just as good as 45. It allows me the headroom to run at a higher resolution than I did with SteamVR and the image looks noticeably improved and less washed out (I used reshade with SteamVR to compensate). So for me it is less about getting faster fps but gaining quality by needing less. I have turned off the frame counter and I have no idea if I am running at 45 or 30 and it is really smooth.

You can edit options.lua in your saved games\DCS\config folder and manually change height and width under graphics and try that. Or copy same file from your beta folder in saved games

I too have a 10cm Warthog extension from the same supplier. Mine is bolted to a custom (cheap!) wooden frame, though I also have the Sahaj Green Spring which makes it lighter again which I prefer for helicopters and is fine for aircraft.

Sounds like a good plan. Joystick Gremlin can handle double taps as well as long/short presses.

My apologies I was reading the forum using unread posts and assumed this was another Apache Pilot/CPG controller post!

The CPG has its own section of controls in the controls drop down top left, including its own axis settings

did DCS update when you restarted it? If so you would need to copy the files into the bin folder again

This post goes into detail how to get OpenXR running. It is regularly updated as more knowledge is gained.

The options come up once in DCS when you press Ctrl-F2 (or whatever you change it to in the screen you just posted)

I take it that is an analog axis being mapped to buttons (in zones)? I recall Joystick Gremlin could add a direction the range was being entered from (above or below) so it can only be applied in one direction. That would prevent it being reapplied on the way back in this case.

The two stages are simply two buttons, so you are mapping two different buttons to fire, so it is the same as pressing fire twice. The detents allow you to say laser a target and then fire the weapon if that functionality exists.

Just one thought, have you set up identical curve and saturation settings for axis in both pilot and CPG control settings?