NAV1 out of frequency band

[Stephan737]

Small thing: At every loading of the airplane the NAV1 frequency is at 101.09. As soon as I dial it snaps into the known frequency band. NAV2 is not affected by this. Hope this is an easy fix for IXEG.

[Litjan]

I can not reproduce that - on my end the frequency is still the last one I set it to when i shut down X-Plane from the previous session.

[mjrhealth]

While you are on the subject of radios the coms radio always default to 118.0 they dont remember last used freq.

[Litjan]

Ok, I will doublecheck those reports today.

In reality the nav frequencies stay at the last frequency, as they are mechanically moved, and they should not be outside the valid band in any case.

Edited October 22, 2023 by Litjan

[Litjan]

I just tested on my machine and between reloads of X-Plane the frequency of NAV1 stays the same and NAV2 decrements by one "click" for both the megahertz and 25 khz knob.

The nav radios show default X-Plane nav frequency datarefs, so if you see something else you may want to check other aircraft you fly in between or third-party plugins (flywithlua, etc.) that may fiddle with this. Also make sure that you always select the "engine running" option in the X-Plane flight setup GUI, even if you then use the "cold and dark" initialization in the IXEG menu.

The communication VHF radios stay at the same frequency for me.

Edited October 22, 2023 by Litjan

[okernel]

For Stephan737, I have the same situation on NAV1 as you, so I will follow Litjan's advice.  Just didn't want you thinking you are the only one  

[Stephan737]

Attached 2 videos. Fist one showing the sim start and the 2nd one a location change. Both loads reset the frequencies. Tried it in the inibuild A300 as well. The ILS freq. loads at 117.09 which is an impossible frequency as well. All default planes are working fine. i never touched the Flywithlua plugin. I still have the vanilla sim witht he IXEG 737 and the inibuild A300. No scenery, ground service, weather addon or anything else.

https://www.youtube.com/watch?v=zQGU5343W28&ab_channel=Stephan (you can see I ticked the "start with running engines option")

https://www.youtube.com/watch?v=sA5iaYMeJ1U&ab_channel=Stephan

Don't spend too much time on this tiny bug as it doesn't cause any problems. Have a nice weekend everybody.

Edited October 22, 2023 by Stephan737

[Litjan]

Interesting, thanks for the videos! I have no idea what would initialize these frequencies in a different way. We COULD possibly code a way to store the last frequencies or at least default to valid ones, but as you said it is not a huge problem. I would like to understand why this works differently on different computers, first.

If you guys want to, you could post log.txt files from your sessions so I can take a look if there is maybe something you have in common?

Edited October 22, 2023 by Litjan

[Stephan737]

There you go:

Log_ATC.txt Log.txt

[tkyler]

I would recommend we hold these reports until after the next patch, which may resolve this.  In switching to our new GUI, we began switching over to a new preference system, which tracks settings between runs of x-plane.  Because of the depth of our custom programming though, this is a 'piecewise' process we tackle in digestable chunks.    When we released the V12 port, we defaulted to X-Plane's fuel setting GUI and in doing so, we disabled our own code that sets the fuel state at sim start.  Well just so happens this same code also sets all the radio frequencies and some knob positions.   The new "preflight gui" for the next patch "re-enabled" our code to manage fuel and in doing so, this also brings back code that tracks the frequencies.

Regarding Jan's observations, if he's testing on our normal dev build (which is highly possible, dare I say probable)....he wouldn't see the issue since I've fixed it and I slipped it in under his nose with the new GUI.    I do know that I re-instated code that does handle frequency state at startup...so I'd say lets get past this next patch, see if that clears things up and if not, we'll start debugging then.   As of today, Its looking to be within the next 7-14 days for the next patch to release.

-tk

Edited October 22, 2023 by tkyler

[Litjan]

3 hours ago, Stephan737 said:

There you go:

Thank you for the logs - despite what Tom said about possibly secretly "fixing" the frequency problem, what speaks against that narrative is that I have NEVER experienced our frequency to be out of bounds or not set to what it used to be set to previously...

Looking at your log.txt I see that you load SEVERAL aircraft (A300, MD82, C172, 737-800, SR22,...)but never the IXEG?

Here is a snippet from your log:

0:01:10.035 I/FCG: Starting new flight in Aircraft/iniSimulations/iniSimulations A300-600R(F) v2 - Passenger/A300_P_V2.acf at Piste 05
0:01:10.035 D/STM: Transitioning from state state_QuickFlightWizard to state_NormalLoading

0:06:47.236 I/FCG: Starting new flight in Aircraft/Laminar Research/McDonnell Douglas MD-82/MD80.acf at Piste 05
0:06:47.236 D/STM: Transitioning from state state_Normal to state_NormalLoading

0:07:34.371 I/FCG: Starting new flight in Aircraft/Laminar Research/Boeing 737-800/b738.acf at Piste 05
0:07:34.371 D/STM: Transitioning from state state_Normal to state_NormalLoading

...and so on...

It would be interesting to see a log.txt where you actually USE the ixeg (and no other aircraft at all).

Do this, please:

Start Xplane, use the IXEG and set both NAV receivers to 115,00. Then shut down X-Plane.

Now load X-Plane again, using the IXEG and see what the NAV receivers are set to?

 

Edited October 22, 2023 by Litjan

[okernel]

Here are my logs after a flight yesterday morning (Aust time) from YBBN to YPAD.  I rarely fly any other aircraft, and not in XP12 for at least a couple of months. Another (small) aspect of this for me is that prior to setting NAV1 (from out of range 101.09), the left bit of the window is coloured red, at least from the angle of my camera setting.  I will post a picture of this a bit later.

As Stephan737 says, this is no biggie!

Log.txt Log_ATC.txt

Edited October 22, 2023 by okernel

[Litjan]

Thanks for the logs!

[okernel]

This might help:

Start XP12, load IXEG, NAV1=101.09 (Ignore red colour in window, as suspected, just a reflection).

Set both NAV to 115, quit XP12, start XP12, load IXEG, NAV1=101.09, NAV2=114.95

Set IXEG preferences to ready to fly, NAV1=101.09, NAV2= 113.90

Set IXEG preferences to cold and dark, NAV1=101.09, NAV2= 112.85

Set IXEG preferences to ready to fly, NAV1=101.09, NAV2= 111.80

Changing the IXEG preferences in this way reduces the NAV2 reading by 1.05 each time. (sorry, pics came up in reverse order)

 

Edited October 22, 2023 by okernel

[Stephan737]

Hi Jan,

please find attahced pics taken according to your instructions:

 

1st load after dialing in 115.00 on NAV 1 and NAV2 (and VHF 1, STBY1, 2 and STBY2 on sth. different then 118.00MHz).

 

2nd load after XP12 restart.

"Start with running engines" was always enabled in the sim's aircraft selection menu. Logs attached to this post.

Log_ATC.txt Log.txt

Edited October 23, 2023 by Stephan737

[Litjan]

Ok, thanks for taking the time to test this, Stephan. Curious...

One last idea: Is there a button or lever on your hardware maybe assigned to nav radio tuning?

Edited October 23, 2023 by Litjan

[Stephan737]

Hi Jan,

My assignments (keyboard + joystick) look just like yours. I removed the NAV 1 and NAV 2 flip standby assignments that are also visible on your screenshot. No change. My system behaviour equals the one okernel described above. Also tried to switch between panel states. Same result.