derfritz

This is still happening for me. Makes the kiowa impossible to fly at night. I just enable NVG + ODA, then select HSD and it crashes. Her is my logs, maybe it helps. I'm using a pimax crystal and quadviews, which I think might be the culprit. If I remember correctly, disabling quadviews helped, but not really an option for me due to FPS. dcs.log-20250321-140624.zip

Same here, after updating vrem and reshade I get instant crashes. I reinstalled reshade and vrem and still getting the crashes.

this still happening for you guys? I still can't use the kiowa at night properly, it keeps crashing with ODA.

@BIGNEWY Sorry to ping you, but is there any news on this topic? Even with new hardware (Reverb G2 to Pimax Crystal) the issue persists, the IHADDS is just too far up. Same thing with all other HMDs in Hornet Viper and Kiowa. I think this is just due to my specific setup, so way to change HMD position would be highly appreciated.

Same here. Posted it here:

Ah sorry, can somebody move this to the bugs and problems forum?

Reproduce: 1. Load instant action mission (tried syria free flight and syria infiltration challenge) 2. Turn on NVG 3. Turn on ODA Either it crashes already now or 4. Toggle Pilot AI HUD If it still didn't crash, toggle ODA and HUD a couple times. I'm running updated windows 11, good hardware, pimax crystal in openxr, tested without mods, tested after slow repair + extra files, deleted saved games folder. dcs.20240703-115240.crash dcs.20240703-115240.trk

Did some more multicrew testing. If the CPG sets up the Datalink following the complete procedure (set ownship ids, set profiles, set net with wingmen, set freqs, set SC, IDM select), everything syncs to the Pilot fine except: CALLSIGN and ORIG ID. They will stay on default. If the Pilot sets up the Datalink following the complete procedure, everything inputs well. So if the CPG does the datalink setup, double check the values afterwards. Especially make sure Callsign and ORIG ID are correct. On top of that we will make it a habit to hit the swap key on the EUFD a couple times. I'll report back if we find anything else, but this specifically seems to be a pretty obvious desync issue.

Our group just did the same test, we had three apaches that were setting up the datalink completely from scratch (set ownship ids, set profiles, set net with wingmen, set freqs, set SC, IDM select) and it did not work at cold start. With a hot start, and the same procedure it did work. So yeah something weird is going on. Edit: After more testing, we got it working on cold start as well, even without selecting a different preset and switching back. The only different factor in multiple tests were that it was not working when both helicopters were multicrew, and it was working fine when both were only single pilot. Can anybody confirm that?

just FYI I can't see your video

This topic is not about EGI alignment at all, it is also not about how to boresight the IHADSS. This is about the IHADSS showing too high for some specific VR setups, nothing to do with the startup, or the procedures of the module itself. I still do not understand exactly what your issue is, but I strongly recommend you to watch a startup video and see how they boresight the IHADSS and follow along. The reticle has to be on the center yellow dot, and all the yellow circles should be at the same distance from each other and not outside the scope.

I don't think this is connected to this issue. Also I did not understand what the problem is. The yellow circles have to be centered in the scope and your IHADSS center cross has to be on the middle dot. But probably create a different topic, this one is not about boresighting the IHADSS.

Yeah indeed, quite annoying because we had missions planned over the weekend, lots of wasted time for multiple people. I don't know why you would release this patch, they could have released the phantom and patch the apache together with the kiowa in two weeks. Pretty frustrating all around.

Same issue here, the aircraft is basically unflyable in multicrew. The waypoints don't get synced, the FCR did not sync properly (was not scanning for CPG, but scanning fine for pilot) and the acq did not sync.

Same, can anyone comment if it still works for them in the latest version?