Fish

Is it possible you are reaching the FOV limits of the Harm sensor?

Works for me since the unified patch. 2.9.3.51704

Yes there is mark points accessible from the HSI. 10 in all. Just click on the MK button, when you have a designated target point, and it gets saved as that markpoint. You can retrieve it by selecting the markpoint as a waypoint, or making it a target point. (cycle down through the list of waypoints and below zero you get to the markpoints.

Hi all, Getting an intermittent (and very annoying) flickering when the FLIR or the MavF displays in the MFCDs. Like a camera shutter, Tried all the settings for the MFDs, different resolutions, every frame etc. Tried with VR set to 72 and 90hz. Not using upscaling. Tried with SteamVR and openXR directly. Looked at frame times and there's not noticeable lag spikes when this happens. Happening on Sinai, and Nevada, but not tried on other maps. So don't think its map related. I'm running the latest version of DCS beta MT. Anybody seeing this and if yes, is there a fix? Cheers.

Hi I'm a fan of VD, and have tried VDXR and compared with steam While i really the simplicity of the VDXR start up, Steam gives me the experience with least stutter in a direct comparison (I'm not using any super sampling, and i have tried different OpenXR settings with the toolkit). I note that with steam i get CPU bound, (render thread) mostly, where with VDXR I get flickering between Main and Render thread. I've tricked around with Process Lasso, and followed someone's recommendations from YouTube, but not really sure what it does. Would love someone to explain how these threads differ, and what, if anything can be done to configure/optimise the system or DCS to get the most stutter free experience while not degrading the visuals

null

For me this is a backward step. In VR (Pico 4 render resolution 3270), objects appear as large blobs when they fade to a set distance, or come within a set distance. You can see what happens in the video below. The flight of F14's bank left after take-off, so I get a view of them broadside. While the AC fades in the video (due to limited pico recording resolution, I can see a feint object in VR throughout. At 51s you can see the 'popup' of the AC to a black blob, much larger than when it was fading away to that distance. The other ac do the same. Same happens with the ships, and I'm guessing other objects. This is more pronounced in VR than you can see in the 2d, but still obvious in the video. Something is clearly wrong here. Tested the same replay in 2D, and everything looks fine. Maybe its to facilitate lower resolutions, but I would like higher resolutions to be facilitated also, as this is the direction headsets are going. options.lua

Sebastian of MRTV says Pico for PCVR has slightly better resolution, and much better Binocular overlap than Q3. So agree no point in upgrading for PCVR alone.

Not much now on the forums about this headset since the launch of Quest 3. However i believe given the specs of the Q3, its going to behave in a similar way to the Pico 4 for PCVR, and DCS. So I though i'd give my experience with 2.9 and all the new setting options. First I'll give a little context. Up to now I have settled (and am very happy) with 72Hz and with a few settings medium, (MSAA 2x, view distance medium), VD in godlike mode, H.264+ codec and SSW off. This gives me sharp pit, objects, and only very occasionally frame drops below 72, (never below 66, and over very densely populated cities). Note this is only on single player and not too many objects on the map. Also note that I'm using Nvidia 537.58 drivers from 10th Oct, as I experienced some poor quality textures and frame rates with 545.84. Render resolution in steam is set to 3270x3270. So with a pre-recorded scenario, i fired up DCS 2.9, and without changing any of the other in game, or steam VR settings, I did a brief test of each of the new options in turn with 0 and 100% sharpening. My goal was to focus on getting at least as good a quality as I have now, then to establish if I get better FPS with those settings. Conclusion . For the following settings, TAA (had not tried this before), DLAA, DLSS, FSR, NIC, (with both 0 and 1.0 sharpening), I get noticeable degradation in quality, with the overall image looking more blurred, or more jagged lines with some shimmering. I am getting better performance and image using 90Hz, with SSW from VD (though i don't like using this mode, as i get the ghosting). System, RTX 4090, intel 13700k, (throttled to 250w), 32gb 3200Mhz DDR4. VD wireless to Wifi 6 router with fairly solid 1200Mb/sec bandwidth. Would like to hear others experience.

This has been posted above, but here is what works for me, Make sure you have Virtual desktop on the pico and on your computer Copy your DCS shortcut to the C:\ folder. From inside virtual desktop in VR, right click the virtual desktop Icon (orange color) on the taskbar, and choose 'launch game', Click Ok (ignore) to the warning message, Navigate to your shortcut, (mine defaults to the C:\), select it and press OK.

Hi RealDCSPilot, I've come to this thread late, and actually had the Pico 4 purchased before reading this. Having had it for nearly 4 weeks, I agree with your sentiments of of this head set, and coming from a HP VR1000 (G1), its like night and day (once you include the Virtual desktop along with the package!) Visuals are stunning because of the very large pancake lens, and I can see everything clearly in the pit, MFD's etc. Turning you head to see a wingman or enemy in dogfight, the wide lens means you don't have to turn you head to get the target in the center, and you can scan the scene with your eyes for the attacker more easily without having to move your head. Same applies for getting to the back switches in the pit. Tracking is excellent, and no loss of tracking in all my time using it, once the room is adequately illuminated. Does not need windows mixed reality, which i found problematic with the G1, which has very poor tracking. Pass through is amazing, allowing me to quickly find something on my desk quickly, and a double tap on the headset gets me back in the pit. double click of the left controller menu button takes me back to desktop if i need to check/change anything (eg. forgot to start voice attack), Can be done with the controller leaving the mouse with the focus in DCS. Then double click to get back to DCS. Headset is well balanced and light, but not perfectly comfortable for long sessions (there's accessories available to solve this), but much better that the old HP G1. Wonderful headset for other stuff, and virtual desktop is easy to navigate (me (and family) having a blast with Half Life Alyx. Screen door is not gone but to be honest once you can see the MFD stuff, you don't really notice it. Wireless is great, but for simming i'll plug into a USB socket for charging. You will need to monitor it, since even socket charging does not keep up with the power usage. Won't be beaten on price. A year ago cancelled my order for the Varjo, and decided to put my money into a new rig, (from a 8700@5ghz & RTX2090ti, to a 13700K & 4090), I had a punt on this head set as an intermediate headset (as it wont be my last), and at the price it was worth trying out. Well i'm blown away with what it can do, and I havn't been back to 2D since I got it. I can't seem to stop just flying around in DCS, or dogfighting in BMS (where you can get an amazing stutter free experience). And finally a note of caution. It does perform excellent with a very high end system, and will stand up to or be even better than others with the same resolution (Pancake over Fresnel any day), but with systems less than this there's going to be a bit of a dance to get the best from it. But VR has never been quite quite plug and play, so you should expect a little dancing.

Anybody using the original reverb with the 4090? Asking, because I could not get the 3090Ti to work with the HP reverb. Thanks

Few clips from a super ultrawide. Taken from a 5120x1440 monitor, but rendered at 4096x1152 by shadowplay