Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 11/07/2020 in all areas

  1. Just to close this out, FlyWithLua has a built in module called radio.lua which executes the following code, amongst other things for consistency within scripts: dataref("COM1_STDBY", "sim/cockpit2/radios/actuators/com1_standby_frequency_hz", "writable") dataref("COM2_STDBY", "sim/cockpit2/radios/actuators/com2_standby_frequency_hz", "writable") Setting those to "readable" will solve the issue, but doesn't help for those that intend to write to the datarefs from their Lua scripts. Using the 8.3 khz spacing datarefs will also fix the problem. dataref("COM1_STDBY", "sim/cockpit2/radios/actuators/com1_standby_frequency_hz_833", "writable") dataref("COM2_STDBY", "sim/cockpit2/radios/actuators/com2_standby_frequency_hz_833", "writable")
    2 points
  2. Jan, Many thanks. I'll do so experimenting. Regards, Ben
    1 point
  3. Happy to see you got it straightened out.
    1 point
  4. If it's the same problem happening again, and you're getting a message telling you to connect to the internet, then there is definitely something preventing you from connecting to the XA servers. Turn off all internet security and all firewalls and try again. Also, do you have more than 1 account at X-Aviation? Are you using symbols in your password?
    1 point
  5. Thanks for the help, I found the culprit to be a Lua script in FlyWithLua NG that had require("radio") at the top, removing the script, or even commenting out that single line made the problem go away.
    1 point
×
×
  • Create New...