reported earlier F 86 ADF wrong morse code from 335 NDB in cold start Caucasus

[DF1]

If I do an instant action cold start in the Caucasus and tune my ADF to the outside NDB of the starting airfield, which is 335, the ADF returns the Morse code "BL" when on the map it says 335 should be "BI." If I do an instant action free flight from the Caucasus, this doesn't happen. In instant action free flight the 335 tuning returns the proper morse code listed on the map of "BI."

[DF1]

Bueller...Bueller...Bueller

Did I post this in the wrong section? Or is it just too mundane of an issue since it isn't graphics or weapons!?

[Flappie]

The absence of track does not help. We don't even know which instant action mission you're talking about.

Edited February 17, 2023 by Flappie

[Art-J]

^ Truth to be told, he did write "cold start in the Caucasus", so we do know which mission is allegedly affected.

@DF1 That being said, F-86 module is sort of abandoned in practical terms as far as bugfixing is concerned, so even if Flappie finds and reports the culprit of the issue, don't expect it to be dealt with anytime soon or ever.

[Art-J]

Well, tried that cold start mission myself and something seems to be amiss indeed. Granted, not all NDBs are always "visible" by ADF at low altitudes, because of terrain features and that's OK, but one would expect at least the ones on the approach path to work when I'm standing on a ramp? Unlike fellow DF1, I was unable to receive any signal at 335 kHz, let alone the correct one (and I was using kneeboard to double check the frequency). Strange. Got nothing at all between 323 kHz ("RF") and 341 kHz  ("BP"). 

In freeflight mission all is well, 335 kHz yields clear and loud "BI" as expected.

[Flappie]

Thanks for your help, @Art-J.

It's the usual wind vs. DB issue. For some reason, DBs get disabled depending on wind direction and strength. It seems to be a feature, but nobody is pleased with it. A change was requested internally a while ago, but we have no news so far.

(sorry, Huey tracks, I don't know anything about the Sabre ADF)

 

335 on.trk 335 off.trk

[Art-J]

Ah, didn't know about wind affecting not only ATC directions but also NDBs. Yes, that must be it then.

[DF1]

Thanks for the replies and looking into this. This is my first post, and I saw it had dozens of views but nobody said anything at first.

I suppose I figured taking off in a cold start with instant action and then finding the home field NDB to land would be a very typical practice, so I was surprised no one else noticed this before.

It is extremely odd that this happens in one mission but not another mission with the same module and same map???? It seems to me if it happens in one mission it should happen in the other mission.

@Flappie - is this issue with wind something that is modeled for realism, or is it a bug that wind somehow effects the NDB's (and on top of that I'm not getting the same issue @Art-J talked about where the NDB is totally not functioning)

@Art-J Thank you so much for looking into this and confirming I'm not crazy and also noting that my post was actually clear. I tried to be as clear as possible. That is very odd because we are definitely getting different issues. I get the NDB and the Morse code at 335 (or very close to it. It is impossible to see the exact number on the dial) but it is definitely returning "BL" instead of "BI" and the compass spins around rather than pointing to it. I know the compass should spin if I'm right over the NDB, but it still spins even if I'm far away and with good path to it.  I reproduced this in both Beta and stable.  It is so odd because in instant action free flight I immediately and very easily find it. "BI" on 335 is right there.

[Flappie]

1 hour ago, DF1 said:

@Flappie - is this issue with wind something that is modeled for realism, or is it a bug that wind somehow effects the NDB's

I'm not really sure. I asked for a change about this a while ago and got no answer so far.

It looks like it's done on purpose, though.

[DF1]

Ok. Well thanks again for responding. How does this work now? Do I wait and then eventually (maybe next week maybe 5 years from now) someone from ED will see this post and look into it? Not that is bad. I was just curious if there is something else I should do or just leave the post as is.

I'm excited to get back into this. I basically went from 1996 SU-27 flanker to 27 year gap and now getting DCS a month ago, so its pretty awesome starting there and then getting back in now that so much has happened with the game. 

[Flappie]

19 hours ago, DF1 said:

Ok. Well thanks again for responding. How does this work now? Do I wait and then eventually (maybe next week maybe 5 years from now) someone from ED will see this post and look into it?

Since I requested a change internally, it should be looked at at some point. We just don't know yet how far that point is. The report gets bumped at least once per year.

[DF1]

On 3/1/2023 at 12:34 PM, Flappie said:

Since I requested a change internally, it should be looked at at some point. We just don't know yet how far that point is. The report gets bumped at least once per year.

Thank you. I appreciate it. Even if it never gets addressed because it is so low priority, I appreciate you getting it in the queue.