Panzerlang

Thanks Slughead. Do I need Ultraleap though? If I use my head in VR to point the cursor, can I not activate the function with your gadget?

I was looking at Pointctrl and even submitted an order, before discovering on his Discord that he's currently still fulfilling orders from 2022. Lol. So, Slugmouse. The 'problem' there is Pimax, who couldn't organize a piss-up in a brewery, have been "out of stock" for months of their integrated Ultraleap module and I see no reliable way of attaching the native one to a Crystal headset.

Given that is IS a game I find adopting the role-playing tactic is fruitful. AKA, I'm a pilot with average eyesight and the Hartmanns have a chance to sneak up on me. C'est la guerre. At least I die (or have to bail) in an aesthetically rewarding virtual environment. Lol. I guess I don't really know the actual range at which I can first see an enemy in my Crystal but if I'm lucky enough to do so, at max range, it still allows me a chance to position myself, even if he spotted me first. Otherwise I'd go play tanks.

Which is exactly what ED have done, no? A pixel is a pixel, smaller or bigger on any given panel ("external factors"). If we ever get pixels the size of human retina cells I guess the issue will be solved but until then...

Real pilots didn't have the advantage of playing around with resolution either. They had the eyes they were born with and a good mechanic to keep the canopy clean if they were lucky. A tiny minority had the eyesight of Hartmann (3840x2160), the rest were on average 1080p. Or vice-versa, given how it works in PC-land. Lol. The point being that there was no level playing field for visuals in real life and there isn't one for us gamers either. Assimilate that reality and play around it, like the real guys had to. Personally I'd rather see nothing than a black blob, because the former is more realistic than the latter and I thank ED for it.

It already does that, it's a function of resolution on pixel size and cannot be solved to everyone's liking. Maybe the big pixel on a low-rez screen could be made very pale but it'd still be a big ugly dot. If it's an e-sport advantage thing, get a crap monitor or VR headset. If it's realism that's wanted, get the highest-rez hardware available and sacrifice the competitive edge to aesthetics. The cake is what it is and ED have done the best that can be done with it. And if you can't work an angle with a warning of 10 miles maybe take up tank-simming instead.

Crystal here, I have quadviews ticked in the PimaxXR but DFR de-selected in the Pimax panel, worked fine before the big update and since the hotfix.

Pimax Crystal, Render Quality is set to "Maximum". DCS Pixel Density is set to "1.0" Runtime is Pimax XR. Quadviews. I don't use the tool tray. 13900k 4090 Be aware, the Pimax software is janky. Every now and then I find the image has turned to dogsht and have to jiggle the Render Quality setting to get hi-rez back.

The Crystal software is dogsht unfortunately. Even with me changing nothing in the panel I'll get low-rez image and I have to jiggle the slider to get the setting to reactivate itself. The pass-through likes to turn itself off too. I can get the stutter back by upping the pixel-density in the DCS system settings. At 2.0 I get low-level jerking/stuttering. At 1.0, with the Crystal Render Quality set to "Maximum", it's smooth. But I had to set the Crystal's Render Quality to 2.0 with the custom setting to stop the image from being low-rez crap. Then back to "Maximum", because it didn't like 2.0. Yeah, nice one Pimax. Software that needs to be repeatedly slapped up the back of the head to make it behave itself. Same Museum Relic mission, some planes did the weird lag/warp again but no crash this time (well, not until a helicopter blew me out of my cockpit).

I know it's frustrating, that it worked before but doesn't now with the same settings. So every time you get a suggestion to try something new it kind of makes no sense. But there are a bunch of goalposts and different software providers have a liking for shifting them. Which kind of leaves us unfortunate players effectively trying to score goals with blindfolds on and our shoelaces tied together. VRAM seems to be quite a significant factor and I read that cockpit textures set too high can flood it. It's clearly not a rez issue at least. Next suggestion, go through each graphics setting and reduce it to its lowest and test (start with cockpit textures). If one on its lowest doesn't change the stutter, leave it on lowest and set the next one. Work methodically through each one and hope to find a culprit. NB: With my Crystal I don't need to open XR, quad views or companion, once set they run automatically in the background. All I have visibly running is the Pimax software (if that's not open in the taskbar the Crystal is dead).

Minefield alert. Lol. I've yet to see a single tutorial on this VR resolution stuff, maybe because everyone thinks it's low-tier obvious. Different headsets and runtimes require different solutions obviously. With steamvr and the pimax Crystal with DCS there are THREE resolution settings/systems that conflict and impact. SteamVR has it's own resolution. Crystal has its own. DCS has its own. With openXR only the Crystal and DCS come into play. You have to choose which one you want to operate the rez, though it does no harm to set a secondary LOWER than base. In my case I have the Crystal at max and DCS pixel Density at 1.0 (base). When I was running steamVR I had that at 100% (base) too. I have no idea if one is better than another, just that once stuff is running perfectly I feel no need for further experimentation. Put every rez setting you have to as low as possible and see what happens.

I see no dots, just a very tiny plane at max distances (exactly how I think such things would appear in real life). Any further and I wouldn't expect to be able to see a real one. In my opinion the viewing experience is pretty much full-real. Pimax Crystal.

FWIW, 13900k and 4090 with Crystal and quadviews, I had bad jerking and stuttering looking left-right out the cockpit at trees and buildings at low level. The last big update fixed that, though I thought it was sandboxman's fixed API dll that did it. Original dll back in place and still smooth as silk. I have no idea how you can run DCS VR with a 1080ti though.

For me at least. After the last big update that broke quadviews I used sandboxman's fixed API dll and discovered all the low-level jerks/stutters had gone. My first assumption was the dll had done it but later thought maybe ED had fixed it. I've installed the DCS patch and put the original quadview dll back in and VR is still smooth as silk. Now I can only hope the single-player crashes are fixed too. Last one I was 30 minutes into a mission in the 'Museum Relic' campaign and for the second time the game crashed with "window out of focus" (I had nothing on the desktop). Just prior to the crash I noticed other planes in formation with me started to lag, exactly as one might see in an online session. Fingers crossed.

Google sez 4070.

No, I'm on a Crystal with Pimax_XR.

I also installed that replacement DLL and it totally fixed stuttering of trees/buildings at low level while looking sideways from the cockpit. Or...the update fixed the stuttering and it's just the new DLL has allowed me to actually get the game working and see the ED fix. Either way I'm worried the next patch might lose all the goodness. 4090.

FWIW, my 4090 has 24gb of VRAM. Before the update I frequently had lock-ups using the F10 map. After the update it happened on the first use but not since then. In other news, using Sandboxman's alternate quadview DLL my stutters (looking sideways at low level) totally went away, motion in all aspects is 100% smooth. My conclusion? DCS is a messed-up bag of spanners and what does something for one user will do nothing for another or will even make things worse. It's headless-chicken code imo.

Regarding forum registration, with gmail I never got the confirmation but with protonmail I got it within seconds. I think ED don't like gmail accounts for some reason. I'm using both programs, only issue so far is engine rumble and/or vibrations continue even with the engine shut down. Other than that I regard the software (Haptic and Realistic) as superb. The other major pro is that with Andre's software I had to have my amp volume nearly maxed; with the Simhaptic stuff it's dialled way back.

Thank you M. It'll forever remain a mystery then. Obviously I'll be very leery of installing ED's patch (or replacing the 'fixed' file with the original), although at some point it'll become inevitable.

Hi Mbucchia. First I want to thank you for your passion and dedication to a piece of work you have freely provided that has given so many people so much pleasure. You, sir, are one of those rare individuals who selflessly give. I have a question regarding my use of the Sandboxman's fix-file (XR_APILAYER_MBUCCHIA_quad_views_foveated.dll). With the original file in place (your install of quad view) I had micro jerking/stuttering of ground objects (buildings and trees etc) at low level as I looked left/right as I flew past them. With his replacement file, that micro-jerking totally disappeared. Absolutely smooth and flawless performance. As far as I can try to understand it my guess is the use of OpenXR Toolkit changes the properties of the .dll (XR_APILAYER_MBUCCHIA_quad_views_foveated.dll). Is that correct or is that file immutable (not able to change)? TIA for any insight.

Well, when it's running it's superb. Shame the longest it's run before crashing is 40 minutes (six sessions). Last one (in which I finally got my missiles launched for three kills) it was "window out of focus" but my desktop was clear. Best analogy I can come up with for the current DCS, it's like a Porsche running on shopping-trolley wheels.

I wondered why the camera-mirror was off in the Mig21, I thought I was going to have to hunt down an on/off switch for it (though it was always on before the update). This was the update they delayed to ensure stuff like this didn't happen, right?

As far as I know the toolkit is just a utility that allows you to fine-tune open-XR. Pimax don't help on their website, they give the impression it's required (along with Open Composite, but it's not).

Regarding the breaking of quad-view. I downloaded the file provided by Sandboxcode and swapped it out. I'm on a 13900k and 4090 and previously, with a superb image, I none the less got the micro stuttering/jerking of objects on the ground as I looked out the cockpit left/right at low level. It would be apparent to a diminishing degree as I climbed higher. With the file-fix in place I went into my game, no jerky foveate box (but visibly working), fired up Mig21 Free Flight and...WTF! Not one iota of jerkiness. Smooth as silk, flawless. I don't get it...did ED fix something else while also breaking the other bit? I run the Pimax client, Pimax-OpenXR, Quad View and QV Companion, no XR Toolkit (don't see any need for it). Serendipity in action. Though now I'm scared the fix on its way from ED might bring back the jerkiness. Right now it's pure 100% perfection. FWIW.