COM1 and COM2 volumes still not included in save state
-
@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.
