COM/NAV issues
-
@n293wk It appears you are assuming these issues are caused by the COM volumes state saving and that you are also assuming they cannot be fixed without affecting the COM volumes state saving.
What evidence do you have for any that? And why not just ask if they can be fixed?
Addressing each of your points in turn:
-
Agreed, the NAV radios only work if the associated COM radio is working (which was not the case in previous versions). It's very simple to just turn the COM radios on (which is a perfectly normal thing to do anyway), so I don't understand how that affects the whole flight as you claim.
-
Agreed, in the latest versions of the Arrow III and Turbo Arrow the DME frequency mode does not read distance unless COM1 and NAV1 are on (which was not the case in v0.9.0 and v0.4.0 respectively). Again, it's very simple to just turn COM1 and NAV1 on (which is a perfectly normal thing to do anyway), so again I don't understand how that affects the whole flight as you claim. This did work previously, so it seems reasonable to think that can be fixed.
-
Your issue with the sound of the GNS knobs is the same as it was in previous versions (v0.9.0 of the Arrow III and v0.4.0 of the Turbo Arrow), so I don't understand how you associate that with COM state saving? Yes, I do still have those versions as well and I have checked them both.
-
The clunk and "State Saving Disabled" voice when starting the flight doesn't appear to have any adverse effect and certainly doesn't affect the whole flight as you claim. JF have already said they are investigating this anyway.
-
-
It appears you are assuming these issues are caused by the COM volumes state saving and that you are also assuming they cannot be fixed without affecting the COM volumes state saving.
Indeed, I am. Hence the phrases "I'm not sure" and "I'm fairly sure."
What evidence do you have for any that? And why not just ask if they can be fixed?
https://community.justflight.com/post/13287
I would be glad to be corrected if my understanding is incorrect, but given the list of changes in the changelog, the only thing that's affecting this area is the state saving changes.
I don't understand how that affects the whole flight as you claim
Having to have the COM radios on during the entire flight while they are not being used is what I mean.
Your issue with the sound of the GNS knobs is the same as it was in previous versions
It definitely was not like that. To be specific, this is really two separate issues:
- For each increment of the COM knob, I hear 2-3 clicks whereas before there was one click per visual increment.
- When turning the NAV volume from 0 to the first position, I hear a lot of clicks, as though the NAV radios are being turned all the way up. Turning the NAV volume anywhere from there to full makes no sound.
I've probably been flying this plane more in the past 2 months than ever, and I've never heard these before. After the update I immediately noticed the almost ear-piercing buzzing of the NAV volume being turned up on the first click. The only other thing I can think of is a SU7 issue as I can't recall if I flew after updating the arrow but before updating to SU7.
The clunk and "State Saving Disabled" voice when starting the flight doesn't appear to have any adverse effect and certainly doesn't affect the whole flight as you claim.
Fair enough. My comment about affecting the whole flight was more about the other points, I added the last point after writing that and neglected to update the wording.
-
@n293wk said in COM/NAV issues:
Even if any of what you're saying is related to the COM volume state saving, that doesn't automatically mean it can't be fixed and still keep COM volume state saving.
Your issue with the sound of the GNS knobs is the same as it was in previous versions
It definitely was not like that. To be specific, this is really two separate issues:
- For each increment of the COM knob, I hear 2-3 clicks whereas before there was one click per visual increment.
- When turning the NAV volume from 0 to the first position, I hear a lot of clicks, as though the NAV radios are being turned all the way up. Turning the NAV volume anywhere from there to full makes no sound.
I've checked again, with the engine and fuel pump off to be sure:
- I only hear one click per visual movement of the COM knob or NAV knob (using v0.5.1).
- Are you saying that from how you remember v0.4.0 or have you gone back to v0.4.0 to check? I hear the same as you on the NAV volume in v0.5.1 but I also hear exactly the same on the NAV volume in v0.4.0. (I'm not saying that from memory. I've installed v0.4.0. to check.)
-
The majority of these issues are due to the MSFS electrical circuit system. There are individual circuits for controlling power to the two COM and NAV radios but it looks like the two are somehow linked together rather than being truly independent. We will speak to Asobo to see if there is a solution.
-
@sender46 I see what the difference is now. The sound was there before, but only when the radios were switched on. I usually turn the volume up first, then turn the radio on, so I didn't hear the sound before. Now you can hear the sound of the GNS knob turning in the background even when the KX170 radio is swiched off, and that's why I am hearing it now but didn't before.
-
Hi,
There is also a new bug in the radio stack :
If you dial 118.22 for example, the real frequency that you are going for is 118.225.
Since the last update (MSFS or Arrow ?), the frequency is interpreted as 118.220 by MSFS which makes impossible to set any xxx.xx5 frequency using the knobs.It can be easyly checked by comparing with the comms window. You have to use the comm window to automatically dial those frequencies correctly.
EDIT : I use the old radio stack (GPS100).
-
Hi,
I observed some weird things with the "old school" radio stack.The NAV radios are tied to COM+NAV power to be energized.
Another strange thing (was unable to replicate in flight, but on ground only, very strange) : COM radios are OFF when the NAV radios are OFF (ATC dialog is being "grayed").
There is definitely some strange things happening in the electrical wiring of this radio stack..... :p
-
@pepe_fr said in COM/NAV issues:
Another strange thing (was unable to replicate in flight, but on ground only, very strange) : COM radios are OFF when the NAV radios are OFF (ATC dialog is being "grayed").
That's unfortunately a limitation of the way MSFS simulates radios. We have separate power circuits and logic for the COM and NAV radios but, presumably because the default aircraft haven't required entirely separate COM and NAV radios, the two are somehow linked 'behind the scenes'. We've not yet been able to find a way around that.
