Dominik96

Hi @Rudel_chw, It seems you are doing a Heading Memory alignment, not Gyrocompassing, that's why there is no steady light but the blinking one indicating HDG MEM has finished. To perform a GYRO COMP or BATH alignment, make sure the INS Alignment mode switch is in the GYRO COMP position (not HDG MEM as in the video) BEFORE turning the INS knob from OFF to STBY. null

Tracked Thank you

@Kreutzberg thank you for the track, that is indeed a bug (TACAN is showing the correct one), will be addressed immediately. Re the NBS's, as mentioned above, there is no equipment in the F-4 that can read them. You can use the ADF through radio frequencies, the steering will be available when tuned to a station that is currently transmitting- e.g. tanker, ground station transmitting a looped message, etc. See below: https://f4.manuals.heatblur.se/dcs/mission_editor.html?highlight=ADF#radio-options

@xarann, are you using easy communication? If yes, there was a bug causing the last knob to be rotated improperly, already fixed locally. BTW, good find!

Hey! Thanks you @Hawkeye_UK for the tracks. I found 2 bugs- one causing VOR/ILS problems when flying AWAY from the course selected (reason why you could not get proper steering to fly over the VOR station and possible the reason for your problem @Oesau) and another one- causing problems at some frequencies when switching between VOR and ILS (reason why the ILS did not work in the 2nd track). Will be in the patch, hopefully that fixes most VOR/ILS issues (besides that known DCS wind problem). And many thanks again for the tracks- without them it would be much harder to track these issues.

@ThorBrasil, I checked your mission and the reason ILS does not work is the Mission Editor wind. For some reason DCS disables the ILS in some wind cases. For me it helped either disabling the wind entirely or making sure the wind is aligned with the runway and strong enough (people report around 8kts headwind is required). See this or other threads: null First screen is your setting, the second one is what worked on my side but try disabling wind fully first to exclude it from other possible reasons. Here also a related thread:

Good point! I applied the spring-loaded switches changes. The IFF code number rollers and TACAN knobs position require some art changes so that will come later.

Thank you!!! That was very helpful as such edge cases are difficult to recreate. I found the reason and fixed it. If anything similar happens after the next patch please feel encouraged to save and send the track. Cheers!

It seems the damage passed from the ED SKD does not necessarily match the damage animation. I asked for the animation calculation model in a JIRA. Temporarily I'll lower the threshold in the code a bit.

Good point. I made it faster.

Hey @treg12 It's known and already fixed- coming public with the soonest DCS update.

Nav Comp failure when doing over-G is intentional. However, we will raise the damage threshold a bit so it won't be affected below 10G (currently 9G).

The ADF mode indeed allows for both navigational data (direction finding to steer the aircraft) and audio reception. The audio from the ADF frequency is played through the system in this mode, so you can listen to radio transmissions while receiving navigation data simultaneously. If you're confused about which knob positions do not seem to make sense, please provide more details, and I'll be happy to clarify further.

Hi @Tarres, Yes, you are still able to hear on the 'ADF' positions. It's not either hear or receive steering but you select the steering on top of the radio transmissions, that's correct.

He should never eject at such altitude unless taken very heavy damage, like wing off. Unfortunately, such things are very difficult to track. If you managed to save a replay that would be super helpful. BTW I added logs with a note of the reason of Jester ejection but they will be public in the next build so not possible to check for it this way yet..

Hi @some1! The HSI in the F-4E is the AF/A24J-1 type. Here is a clip from the military specification describing the device (MIL-H-27269A). It clearly states the indicator shows whole (not decimal) miles up to 1999nm (so not that high as 9999nm).

But are the gyros still wobbling or just some alignment issue? There are many possible reasons for a troublesome alignment.

Could be related to this Jester problem with doing BATH alignment when HDG MEM alignment was available. If that was it (but not sure here), it'll be fixed in the todays patch.

@MicMic, did you wait long enough so the blue LAT and LONG lights went off while holding the switch at FIX? Updating the coords may take a bit, depending how far the new coords are from your current ones. Also, do you use the reduced tick rate mode in Special Options?

Hi! The track would be very useful. Or if you could recreate it in a short-one even better, would help a lot to catch the issue. Currently I cannot tell much- it could be a bug, map or DCS issue, failure or user error. The ILS in DCS seems to rely on the Mission Editor wind also a lot, so better to make sure it's aligned with runway heading or even better to turn it off t as it could be caused by this too.

Hi, I already fixed locally the bug with HSI and ADI heading oscillating when on low tick rate mode. That fluctuation was making it impossible to align the INS. @IvanK, anytime the steady green light is on when doing BATH or GYRO COMP alignment it's possible to go into NAV (you'll have lower accuracy than when performed full Gyrocompassing though). Probable reason why you could not reach full alignment are these fluctuations. They made the BATH heading way off the true one, that's why the BATH alignment was possible but probably very inaccurate. When syncing the compass panel, magnetic heading from the flux valve is taken as a reference, that's why the heading on the instruments matched the expected one but the INS platform still could be way off. Re Jester falling asleep after turning to STBY, normally once you occupy the back seat Jester is disabled so he won't move anything in the cockpit. But it's possible to force him to do it by previously selecting Crew Contract/Jester Presence/Enable in the Jester menu

Hi @Oldcrow Jr. 62, I have a few questions that would help me to track the issue. Were you already in the landing config- gear down, flaps down? And also, what runway were you planning to land on? Right or left pattern? Have you saved the log? Thanks for the report!