dutchili

Am i correct that the currenthill IRIS-T does show on the RDR, but not on the HAD (F-16) and cannot be shot with a HARM as the harm table value is unknown?

Not that i know, but: - remove AWACS / EWR so no data on other objects is available, unless the planes in your group have radar coverage of those units - in the F-16, leave MIDS switch to off (but that also kills the TACAN)

Tracking: starts with jitter (the view moving up and down), then usually ending up outside of the cockpit. No delays. If tracking data is somehow captured, i can send it to you. Just let me know how. I have a high contrast backdrop, acoustic panels. This should make things easy, while it doesn't. But please note, only in DCS, not in Pimax Home.

@Calvin.Pimax Tracking seems improved under artificial light conditions. But still in Pimax home all is good, in DCS tracking can have a hard time when looking over my shoulder. Natural light coming in at an angle (window on my left) is giving tracking issue when looking either left or right over my shoulder, in DCS, not in Pimax home. The new sharpness setting was set at .6. Very noticeable, but also reducing overall performance (missing frames). When changing the sharpness, it is immediately applied. The apply button remains disabled, which breaks with the overall behavior of the application. When I enabled Smart Smoothing while in DCS, the headset went black. I did not press Apply yet. I did not notice any difference with smart smoothing (RTX 5090). Seems that everything is on the right track, but outside in tracking is definitely in need of more improvements.

Cold start with ATP at night Switch AG TV image shows until cycled through WHOT and BHOT back to TV. Than the image is black (as expected).

see 2nd post. There might also be a left to right difference which you can update from the Windows Application.

@BIGNEWY: the Viper manual on the website is still the december 2024 version: https://www.digitalcombatsimulator.com/en/downloads/documentation/filter/aircraft-is-f-16c/apply/

Can't ED implement some kind of 'vr-sync' so we don't have to fool around with settings so much and hope Windows does not assign something else to a 'render core' causing 1 frame 'off'?

well, that could be right as i am heaving DCS crashes where the dcs.log and eventviewer point towards my GPU. Still investigating this with ED. I also read somewhere that the earphones are clipping, setting the volume in windows lower, and higher on the headset could work. Haven't tested it yet.

no voice attack in my case. Also not related to SRS

Nope, the amount of click seems somewhat related to whether the pimax is the default audio device. But I don't have hard evidence. I haven't contacted pimax. Did you?

yes, same here

I think this has to do with how the game engine works. There must be some 'additional processing' that is too much for the CPU to handle.

I tried increasing and decreasing the boost clock with Intel XTU on a i9 13900KF to solve crashes with Pimax OpenXR (Crystal light) and a 4090. Like @shades71 I've noticed that lowering the boost clock actually improves performance. I ended up switching to SteamVR as it doesn't crash (so far) and currently has better performance that Pimax OpenXR. To respond to the core topic: still ground stutters, especially when 'changing direction', such as turning left/right while taxiing, rolling, pulling G below 6000ft AGL.

Things seem better with NVidia driver 576.66 (no need to blame mod's that are known good)

I experience the same thing with Nvidia 576.52. After the latest DCS patch...it's a matter of time, you just don't know how much time. No crash in DCS log, app hangs. When the app is windowed (while playing VR), i can usually sit it out and get control over windows in a few minutes. In full screen mode....automatic reboot (no BSOD).

no stutters, but crashes that are not mentioned in the dcs.log. Here is an example. After about 20 minutes of flying, the video froze, sound continued for a minute, then a full system reboot. Not an incident. dcs.log DxDiag.txt

Major component: SRS for radio communications in Multi-Player. Major component: Tacview for debriefing in both MP and SP Major component: LotATC for air traffic control in MP My discord uses several mods to enhance the visual experience at airfields and target area's.

I bought a Pixel Crystal Light... - i love the resolution, close to 2D experience - switching between game and 'desktop' is instant - sound of non-DMAS speakers is....better buy the DMAS speakers too - tracking is not as good as the quest. I have issues when looking at my F-16 wingtips. Could be due to my background. Besides this position, it is perfect and better 'smoothened' than the quest, which you will notice when aligning the JHMCS in the Viper. - quality upon delivery was not perfect. Had to correct contrast and brightness of the individual panels, throught the normal software, to balance left and right. One dead pixel in the right panel, no response from customer service on these issues for 3 workdays and a weekend. - setup was 'click and play' instead of those Quest 3 unwanted intro's and safety wizards. - wearing comfort is much better than the Quest 3. It is heavier, but feels lighter. - i get the best performance at 72Hz, quadviews FOV rendering, high(est) resolution. Low-level FPS depends on the map and visible distance setting, FL006+ is steady 72 Hz (and perceived as fluent). The 90Hz setting only works for me with Pimax upscaling enabled, but that comes at the cost of less crispy views. - the asferical lenses have a sweet spot. The pancakes from the quest have better 'edge to exge' sharpness. It took some time to learn to turn my head more, than just the eyes. Ther is also more chromatic abberation, comparable to a quest 2. Primarily visible with high contrast and red colors. Summary: not going back to the Quest 3.

@BIGNEWYThis thread can be closed. The root cause was incompatibility between the Nvidia driver (regardless the version) and Windows 11 core isolation.

DLSS is not the same as DLAA.

I have disabled core isolation. Flown more than an hour now on multiple flights (computer shutdown in between).

@sleighzyththanks for the great tips. They are in line with the advised that I got from NVIDIA. I ran lhe log analyzer on the Ed discord and installed a very old graphics driver as advised. Now I can play for about an hour and 15 minutes before I need to reboot to do it again. @BIGNEWYit does not seem to be a DCS specific issue as I get the same issues with flight simulator as soon as I enter VR

dcs.logDxDiag.txt There you go @BIGNEWY. Hope it helps

I frequently get this error message in the log file, since April 25. Currently on the latest released version, yet i still get this. I experience that the VR images freezes, the sound continuous for a while and if i am lucky DCS writes this log entry. Sometimes the PC writes a mindump, sometimes i just reboots. The minidump and eventvwr often point to nvlddmkm and i see event IDs 14 and 153 in the event log. Happens with Quest 3 and Pimax Crystal light. My friend have more crashes while loading / in multiplayer too, with various reaons. Any help @BIGNEWY