If it is working for you, isn't it maybe some trigger in latest FlightGear itself preventing frequency to be 0? I use no additional addons, just vanilla FlightGear build from scratch. I'm starting to suspect that the MCDU is trying to set correct "data" frequency, but it is reset to the 118.000 mentioned earlier (as this exact frequency appears on RMP after MODE DATA pressed). Thinking about those steps, I'm wondering if there is any other folder with fgfs settings, where any corrupted config file might be? If there is any debug information I can provide, let me know what should I post. (unfortunately I am not able to recall which pull it was)ģ) I've done some search online about this, found some documents about frequency switching on RMP, but as stated above, I have no "DATA" frequency available.Ĥ) I've tried to change it through MCDU as mentioned above, no success either.ĥ) Tried to temper with the the property tree, going through the code looking for some hints, all unsuccessful.Ħ) Tried to remove all fgfs and a320 (including home folder) and clean reinstall, the same behavior as before.ħ) Registered here on forum to find out if there is known solution for this. So, maybe to sum up a little bit:ġ) I was using happily SimBrief integration for few days (I've returned to FG after some time)Ģ) After some update, message about VHF3 appeared on ECAMS and flight plan loading stopped working. I was looking for VHS3, ACARS and so on in scripts, found only some references to display message on ECAMS and MCDU, no setter of the value that I was able to track, however I am not too familiar with working of this plane scripting, so I did just some basic searches. I did not mention this earlier as I was unsure if this was the correct property. Well I was tempering with property tree and source scripts as well after I figured out no normal way, found out this properties, but they are immediately reset to 118 after the change. Thank you for you replies!ĮDIT: I'm using last build of fgfs and A320 from git. I can still input the flight plan manually, but it gets quite inconvenient after few flights. This plane is really great, it even inspired me to get Thrustmaster A320 set, but now I'm kind of grounded. I've tried to set Datalink through MCDU as well (MCDU MENU > ATSU > COMM MENU > VHF3 VOICE DIRECTORY > MODE DATA), but it was just going through "118.000 123.200", "123.200 118.000" (kind of expected) and finally on next push of "MODE DATA" "123.200 123.200" (not sure how it gets to this state). Ready to start eng, but others as well) with the same result. Is this a bug, or am I doing something wrong here? I've tried to load some predefined states (e.g. Ok, so I was on the right path from the beginning, however I'm afraid I have frequencies in both Active and Stand by displays, see attached screenshot:
0 kommentar(er)
