dutchili

Could this issue relate to HOTAS inputs too? (perhaps ED can answer from a code-level conclusion)

ATP cross disappears.trkATP cross disappears.trknull Expected: cross remains visible after locking a target / setting area track and then switching to N-XR. When N-XR is achieved, the cross disappaear and no bounding box is shown.

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.