kdfw__

for vr users, couple of items with this model: the default vc eyepoint (cameras.cfg) should be modified to [Views] //eyepoint = -8.20, -0.95, 2.18 eyepoint = -7.51, -0.95, 2.31 also, the vc panel light file is LIGHT_CARENADO_Gauge.fx (pa44 is pointing to asobo's global file), the clipping in vr can be fixed by changing to the following (at end of file) [LightAttributes.0] Type=spot Size=0.0 Range=0.165 Intensity=1.2 Softness=0.0 SpotInner=43.7 SpotOuter=79.152 Volumetric=0 ScatDir=0.0 whenever the model gets an update, these changes have to be made again if it was overwritten. separately, for the pa44 model, vc eyepoint for vr is [Views] //eyepoint = -6.75, -0.9, 1.4 eyepoint = -6.0409104, -0.9, 1.53 both are good models for slow and low, would be nice to get a rxp treatment in the future with hsi driven by the gps. carenado should do the c337 and the pc12 next.

the developer didn't QC the VC using VR. they know the light issue exists because i filed a ticket on it for the pa44 a while back. but there's an easy work around so people can enjoy the pretty carenado offerings in VR. i'll get the seneca soon as she's easy on the eyes.

there's a work around for fixing the clipping of the gauge lights in VR. this is due to the small 'range=0.1' from the default asobo's LIGHT_ASOBO_Gauge.fx file. if it is adjusted to 0.165, the clipping disappears: D:\MFS2020\Official\OneStore\fs-base-effects-legacy\effects\LIGHT_ASOBO_Gauge.fx [LightAttributes.0] Type=spot Size=0.0 Range=0.165 Intensity=1.2 Softness=0.0 SpotInner=43.7 SpotOuter=79.152 Volumetric=0 ScatDir=0.0 i sent a tix to carenado about this a while back but they never bothered to fix it.

there's a basic fix (and fix coming) for p3dv5 vr single pass rendering, edit the shader file per Beau's edits: http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=141764

there's a basic fix (and fix coming) for p3dv5 vr single pass rendering: http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=141764

i had the same problem with coherentgtdraw timing blowing up after flying in/around photogram area in the vc view. flying back and forth between EGLC and EGLL, frames would go from the 30s to 10s with coherent draw going crazy. this is what mitigated it on my setup (mainly VR rig): HAGS=on NVCP pwrmgt=max perf thread opt=on VR pre-render=2 it's all pretty smooth now and looks great. however, turning HAGS=on isn't working great for DCS...

Main issue here is CTD when AI is enabled (offline, low settings at 20%) and trying to start sim with carenado’s PA44. Never before after updates.

this gasket works well: https://www.amazon.com/gp/product/B07PQT73YG/ref=ppx_yo_dt_b_asin_title_o04_s00?ie=UTF8&psc=1 along with some hook side velcro.

updated to v1.2, installed twice but hsi/gps/vloc still not working...

installed v1.2 and hsi is still not working. cdi/vloc doesn't do a thing.

It simply allows eye balls to be placed closer to the lens which will increase the fov. The gasket as shipped has too much distance to lens, especially if head shape doesn’t conform to the gasket.

i checked the status of the ticket i filed at carenado, it now says "solved" so maybe we'll get a patched version soon.

i'd agree with the op on the settings, except for me openxr rendering scale=50% and set the rendering in fs to 100% give good image quality. for my old rig to run smoothly, i also lock frames using nvcp to 25 so that looking out the side window is less prone to stuttering. limiting frames also seems to give some headroom for effects so i can set the windows effect at ultimate.

Trackir and vr running concurrently? wut? it should be one or the other.

it's ready. i'm getting decent performance on slow and low airplanes with my setup. runs about the same as p3dv4 or v5 but with much more details. just need to back off on the rendering ss to 70% or below on the g2 hmd or it goes south pretty quick.

just got it and hsi/nav2 is not working, even after reinstall twice: hsi red flag on nav, not slaved to gns530-looking thing no glide slope nav2 obs dial not moving (loc/gs needles seem to deflect ok)

red flag next to NAV in HSI, so GPS/NAV inputs are messed up glide slope is inop (see above) obs knob does not turn dial

No worries, users will make the appropriate flight sim tradeoffs to make vr work for his/her hw.

Although high fps is better than low fps, >20 fps in vr is perfectly acceptable. Just as there are some people get easily sea sick, there are many who don’t so it’s an individual thing. Matter of users making the usual flight sim trade offs, nothing dramatic.

found that p3dv4 at 60hz refresh caused my distorted single-pass vr image. back to 90hz and all was well.

Single pass works fine on p3d4 and 5. If it works using steamVR on one hmd, it should work with g2.

My ipd is also larger than 68mm but the g2 still works fine for me. The only thing is the gasket is for a narrower head and the large standoff distance between the eye and lens which reduces fov. There are mods to allow closer eye placement so eye lashes are barely coming in contact with the lens for a larger fov. At this point the performance is similar to the cv1, g2 set with ss=140%. 25-30 FPS on p3d jets, which is perfectly fine with me. Vr is single pass and it’s working now. I can get >45fps easy with DCS f14 with fairly high settings and it’s a blast. Gazing at objects at the corner of the field of view through the visual sweet spot is not super clear so it means adjusting the head to center the objects to get a better look. But when the objects are in the sweet spot, image quality is like what i see on the flat 4k display, but rendered in 3d. The blacks are black and night flying really looks good. No banding like the cv1 at night. Anyway, now looking forward experiencing fs20 in vr.

g2 uses 2 x 2160 x 2160 lcd panels (4320x2160) so there are lot of pixels. add some supersampling and it can tax the hw. at native resolution, performance is as expected (like driving a 4k monitor) and image quality is still excellent. vr in single pass in wmr+steamvr looks odd so presently running at stereo mode which can almost halves the frame rate. will try to optimize the p3dv4/5 settings to see if performance can be improved for my aging system. but no regret graduating from cv1 to g2.

Received the G2 today but couldn't figure out why SteamVR wasn't working (headset not detected). Fix was simple: along with installing SteamVR, must also install "windows mixed reality for steamVR". Coming from Rift cv1, the G2 display is great, P3Dv4/5/DCS colors are accurate and no screen door effect. Can read gauges nice'n clear as long as in the sweet spot.