COM1 and COM2 volumes still not included in save state
-
Hmmm, disappointed again. The changelog for v0.10.0 says "COM/NAV volume now included in state save" but it's no different than it was before for me.
If I leave COM1 and COM2 volumes at max. when I shut down and exit a flight, they are again back at zero volume when I start a new flight. NAV1 and NAV2 volumes save as zero or max. volume, wherever they are set on shutdown and exit, but not COM1 and COM2.
-
@sender46 I was about to agree with you till....I found that the radio needs to be on. If its off, the volumes go to 0. This is on the KX170s. The garmins seems ok as they only turn off at zero volume. Probably just part of the complication of supporting multiple radios.
-
@weptburrito said in COM1 and COM2 volumes still not included in save state:
....I found that the radio needs to be on. If its off, the volumes go to 0.But that's not realistic. On the real COM1 and COM2 radios the volume knobs would not turn themselves to zero when the radios are switched off. The NAV1 and NAV2 volumes behave realistically and remain where they are set when the NAV1 and NAV2 radios are switched off, so it seems reasonable to think that the COM1 and COM2 volumes could be programmed to state save in the same way.
-
@sender46 It's slightly different because it's the COM volume that controls whether the GPS is on or off, and I think the GNS is active in the background even when it's not selected. So even if the arrow saves the volume, the GNS will override it next time you load the plane if the radio was turned off last time.
-
@sender46 said in COM1 and COM2 volumes still not included in save state:
But that's not realistic.
I do agree. Monitoring the variables to see what happens when you turn the radio off I see why its doing what it does. When you turn the radio to off, the variable for the volume is being set to 0 even though the vol knob stays put. So the problem isn't the state saving, its that the volume is being set to 0, instead of turning the circuit off.
Maybe that's something they can change unless that was done to help the multiple radios play nice with each other.
-
@weptburrito OK, I see your reasoning. But why would they say in the changelog that this has been fixed?
-
@sender46 I dunno. Technically it is, IMO the problem is the on/off switch isn't turning off the power, its pretending to by setting the volume to 0.
Taking a closer look, NONE of the radios except the 530/430 have any effect on the power draw when on vs off. Even pulling the breaker for com1 is actually just setting the volume to 0...looks like a bit cheating going on in there JF ;)
-
@weptburrito Hmmmm :thinking_face: , technically cheating or whatever, if it ain't realistic it ain't fixed.
-
Please see - https://community.justflight.com/topic/1806/update-change-logs-v0-10-0-released-edited-18-11-21/1
Unfortunately there are various quirks and limitations to the MSFS radio system, especially when using custom-coded radios with multiple configurations (GTN, GNS etc).
-
@Martyn Yeah, that's understandable. You all seem to be doing the best with what MSFS provides so I can live with minor stuff like that.
@sender46 When I'm flying on pilotedge I of course have the radios on, but offline there's nobody to talk to so I basically pretend I'm flying nordo (which is perfectly legal as long as you stay out of airspace which requires comms). But turning the radio on is super easy, barely an inconvenience, so I suppose it doesn't really matter.
