Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.

MSFS 2020 Lua Connection Failures

Ncrh01Ncrh01
in GoFlight Interface Tool - Technical Support
Hi There,

Since the SU5 update whenever I load the GIT I am getting Winsock Lua errors and cannot test/run Lua events etc. The error I am getting as soon as GIT loads is:

LUA Processor: Connect Exception - Unable To Connect!
WinSock: Connection Failed: No connection could be made because the target machine actively refused it 127.0.0.1:27016

Any idea how I can resolve this?

Regards,
Neil
Tagged:

Comments

  • admin_ppsadmin_pps
    Is FlightSimIOLua running in the notification area on he Windows toolbar? Is your firewall blocking the connection?

    Best wishes
    Steve
  • Ncrh01Ncrh01
    Yes it is running. I've also opened the port and turned off the firewall but to no avail.

    When starting up LUA does connect via the port as I get the message

    WinSock: Connected To 127.0.0.1 On Port 27016!
    LUA Processor: Started!

    It then detects loads of LVARs for the FBW A320 and then soon after I start to get the Connect errors previously listed.

    Regards,
    Neil
  • admin_ppsadmin_pps
    Can you copy and paste the whole GIT log from start to when seeing the error so I can check for other errors that may be causing the problem.

    Thx
  • Ncrh01Ncrh01
    From Debug.txt

    Debugging Started
    Joystick Data:
    Joystick Device Found: T.A320 Pilot
    Joystick Device Found: Saitek Pro Flight Yoke (USB)
    Joystick Device Found: Saitek Pro Flight Rudder Pedals
    Joystick Device Found: Generic USB Joystick
    Joystick Device Found: Generic USB Joystick
    FP Device Found: TCA Q-Eng 1&2
    Device Found: GoFlight GF-T8 control module
    Device Found: WCP
    Device Found: MFR
    Device Found: GoFlight GF-T8 control module
    Device Found: GF-46
    Device Found: MESM
    Device Found: ITE Device(8595)
    Device Found: ITE Device(8595)
    Device Found: Saitek Pro Flight Switch Panel
    Device Found: MFR
    Device Found: WCP
    Device Found: GF EFIS
    Device Found: GoFlight GF-T8 control module
    Device Found: USB Receiver
    Device Found: MCP Pro
    Device Found: USB Receiver
    Device Found: USB Receiver
    Device Found: USB Receiver
    Device Found: MFR
    Device Found: RP-48
    Device Found: GoFlight GF-T8 control module
    Supp Device Found: Button Box Interface
    Supp Device Found: BU0836X Interface
    Mouse Device Found: Mouse
    Keyboard Device Found: Keyboard
    Qty: 7
    Joystick Found Device 0: T.A320 Pilot
    Device 0 Button Count: 17
    Device 0 POV Count:1
    T.A320 Pilot
    Y
    X
    Sliders0
    RotationZ
    Joystick Found Device 1: Saitek Pro Flight Yoke (USB)
    Device 1 Button Count: 23
    Device 1 POV Count:1
    Saitek Pro Flight Yoke (USB)
    Y
    X
    RotationY
    RotationX
    Z
    Joystick Found Device 2: Saitek Pro Flight Rudder Pedals
    Device 2 Button Count: 0
    Device 2 POV Count:0
    Saitek Pro Flight Rudder Pedals
    Y
    X
    Z
    Joystick Found Device 3: Generic USB Joystick
    Device 3 Button Count: 12
    Device 3 POV Count:1
    Generic USB Joystick
    RotationZ
    Z
    Z
    Y
    X
    Joystick Found Device 4: Generic USB Joystick
    Device 4 Button Count: 12
    Device 4 POV Count:1
    Generic USB Joystick
    RotationZ
    Z
    Z
    Y
    X
    Joystick Found Device 5: TCA Q-Eng 1&2
    Device 5 Button Count: 31
    Device 5 POV Count:0
    TCA Q-Eng 1&2
    Z
    Y
    X
    RotationZ
    Sliders0
    RotationX
    RotationY
    Joystick Found Device 6: Button Box Interface
    Device 6 Button Count: 128
    Device 6 POV Count:1
    Button Box Interface
    SimConnect Message Processing Started
    SimConnect Receive Message Exception: startIndex cannot be larger than length of string.
    Parameter name: startIndex
    WinSock: Connected To 127.0.0.1 On Port 27016!
    LUA Processor: Started!
    LvarName Request: A32NX_RMP_L_TOGGLE_SWITCH
    LvarName Request: A32NX_RMP_R_TOGGLE_SWITCH
    LvarName Request: A32NX_RMP_L_SELECTED_MODE
    LvarName Request: A32NX_RMP_R_SELECTED_MODE
    LvarName Request: A32NX_RMP_L_VHF2_STANDBY_FREQUENCY
    LvarName Request: A32NX_RMP_L_VHF3_STANDBY_FREQUENCY
    LvarName Request: A32NX_RMP_R_VHF1_STANDBY_FREQUENCY
    LvarName Request: A32NX_RMP_R_VHF3_STANDBY_FREQUENCY
    LvarName Request: XMLVAR_ENG_MODE_SEL
    LvarName Request: LANDING_1_Retracted
    LvarName Request: LANDING_2_Retracted
    LvarName Request: XMLVAR_Baro1_Mode
    LvarName Request: XMLVAR_SWITCH_OVHD_INTLT_SEATBELT_Position
    LvarName Request: XMLVAR_A320_WeatherRadar_Sys
    LvarName Request: A32NX_AVIONICS_STARTUP_SOUNDS_INHIBIT
    LvarName Request: A32NX_OVHD_ADIRS_IR_1_MODE_SELECTOR_KNOB
    LvarName Request: A32NX_OVHD_ADIRS_IR_2_MODE_SELECTOR_KNOB
    LvarName Request: A32NX_OVHD_ADIRS_IR_3_MODE_SELECTOR_KNOB
    LvarName Request: A32NX_OVHD_ADIRS_IR_1_PB_IS_ON
    LvarName Request: A32NX_OVHD_ADIRS_IR_2_PB_IS_ON
    LvarName Request: A32NX_OVHD_ADIRS_IR_3_PB_IS_ON
    LvarName Request: A32NX_OVHD_ADIRS_ADR_1_PB_IS_ON
    LvarName Request: A32NX_OVHD_ADIRS_ADR_2_PB_IS_ON
    LvarName Request: A32NX_OVHD_ADIRS_ADR_3_PB_IS_ON
    LvarName Request: XMLVAR_SWITCH_OVHD_INTLT_NOSMOKING_Position
    LvarName Request: XMLVAR_SWITCH_OVHD_INTLT_EMEREXIT_Position
    LvarName Request: A32NX_OVHD_INTLT_ANN
    LvarName Request: XMLVAR_Auto
    LvarName Request: XMLVAR_ALT_MODE_REQUESTED
    LvarName Request: XMLVAR_A320_WEATHERRADAR_MODE
    LvarName Request: A320_Neo_AIRCOND_LVL_1
    LvarName Request: A320_Neo_AIRCOND_LVL_2
    LvarName Request: A320_Neo_AIRCOND_LVL_3
    LvarName Request: PUSH_OVHD_OXYGEN_CREW
    LvarName Request: STROBE_1_Auto
    LvarName Request: A32NX_BARO_BRIGHTNESS
    LvarName Request: A32NX_SWITCH_RADAR_PWS_Position
    LvarName Request: A32NX_COLD_AND_DARK_SPAWN
    LvarName Request: A32NX_ELEC_COMMERCIAL_FAULT
    LvarName Request: A32NX_ELEC_COMMERCIAL_TOGGLE
    LvarName Request: A32NX_ELEC_GALYCAB_FAULT
    LvarName Request: A32NX_ELEC_IDG1_FAULT

    Hereafter loads of similar A32NX LVAR request / detected messages followed by:

    LvarName Update: A32NX_AUTOBRAKES_BRAKING
    Late Lvar Detected: A32NX_AUTOBRAKES_BRAKING
    LvarName Update: A32NX_AUTOPILOT_TRACK_SELECTED:1
    Late Lvar Detected: A32NX_AUTOPILOT_TRACK_SELECTED:1
    LvarName Update: GPS_Current_Phase
    Late Lvar Detected: GPS_Current_Phase
    LvarName Update: PFD_BRG1_Source
    Late Lvar Detected: PFD_BRG1_Source
    LvarName Update: PFD_BRG2_Source
    Late Lvar Detected: PFD_BRG2_Source
    LvarName Update: Glasscockpit_DmeSource
    Late Lvar Detected: Glasscockpit_DmeSource
    LvarName Update: DOOR_MAIN_DOOR_POS
    Late Lvar Detected: DOOR_MAIN_DOOR_POS
    LvarName Update: Main_Door
    Late Lvar Detected: Main_Door
    LvarName Update: A32NX_GOAROUND_PASSED
    Late Lvar Detected: A32NX_GOAROUND_PASSED
    LvarName Update: AIRLINER_APPR_TRANS_ALT
    Late Lvar Detected: AIRLINER_APPR_TRANS_ALT
    LvarName Update: XMLVAR_STBYBattery_Test
    Late Lvar Detected: XMLVAR_STBYBattery_Test
    LvarName Update: XMLVAR_BatterySTBY_SwitchState
    Late Lvar Detected: XMLVAR_BatterySTBY_SwitchState
    LvarName Update: XMLVAR_STBYBattery_IsHeld
    Late Lvar Detected: XMLVAR_STBYBattery_IsHeld
    LvarName Update: XMLVAR_ELECTRICAL_Switch_Power12V_ON
    Late Lvar Detected: XMLVAR_ELECTRICAL_Switch_Power12V_ON
    LvarName Update: XMLVAR_LeverMixtureHidden1
    Late Lvar Detected: XMLVAR_LeverMixtureHidden1
    LvarName Update: PFD_CDI_Source
    Late Lvar Detected: PFD_CDI_Source
    Creating Bespoke Vars
    Bespoke Vars Created
    Importing Bespoke Variables
    Bespoke Vars Assigned, Importing Bespoke Events
    Bespoke Events Temp Imported
    Bespoke Events Imported
    Loading Aircraft Settings
    GetXMLConfigData
    GotXMLConfigData
    Loading Power
    Loading MCPPRO
    Loading MCP
    Loading EFIS
    Loading P8
    Loading T8
    Loading RP48
    Loading MESM
    Loading WP6
    Loading LGT
    Loading LGT II
    Loading GF46
    Loading GF45
    Loading TQ6
    Loading DIO
    Loading GF166
    Loading SECM
    Loading Joysticks
    Clearing Displays
    Reset Data
    Aircraft Settings Loaded
    Calling Aircraft Changed
    Aircraft Changed
    WinSock: Connection Failed: No connection could be made because the target machine actively refused it 127.0.0.1:27016
    LUA Processor: Connect Exception - Unable To Connect!
    WinSock: Connection Failed: No connection could be made because the target machine actively refused it 127.0.0.1:27016
    LUA Processor: Connect Exception - Unable To Connect!
    WinSock: Connection Failed: No connection could be made because the target machine actively refused it 127.0.0.1:27016
    LUA Processor: Connect Exception - Unable To Connect!
    WinSock: Connection Failed: No connection could be made because the target machine actively refused it 127.0.0.1:27016
    LUA Processor: Connect Exception - Unable To Connect!
    WinSock: Connection Failed: No connection could be made because the target machine actively refused it 127.0.0.1:27016

    These errors continue ad infinitum until I closed down.
  • admin_ppsadmin_pps
    Strange. Can you terminate GIT via the task manager when the error occurs so that FlightSimIOLua remaining running and then start GIT and see if it can successfully connect to Winsock/Lua.

    Thx
    Steve
  • Ncrh01Ncrh01
    Terminating GIT via task manager also drops the FlightSimIOLua so I can't test that. I tried manually loading the IOLua first and that initially seemed to work in that I didn't get the connect errors but as soon as I tried one of my own Bespoke Events the IOLua crashed and the connect errors reappeared.
    Unfortunately nothing of interest in the IOLua log, all there is is this:

    10-35-23: FlightSimIOLua Starting ...
    10-35-23: LuaProcessor Starting ...
    10-35-23: LuaProcessor Started.
    10-35-23: TCPServer Starting ...
    10-35-23: TCPServer Connecting To 127.0.0.1 On Port 27016 ...
    10-35-23: TCPServer Started.
    10-35-23: FlightSimIOLua Started: 1
    10-35-23: TCPServer Listener Starting ...
    10-35-23: TCPServer Listener Started!
    10-35-27: TCPServer Client Listener Starting.
    10-35-27: TCPServer Client Listener Started.

    Regards,
    Neil
  • admin_ppsadmin_pps
    Is it happening with all aircraft or just this one?

    Best wishes
    Steve
  • Ncrh01Ncrh01
    Same problem with the 747. For both planes the MCPPRO work fine using the default option but the moment I assign and execute a bespoke event (in my case for the EFIS) the IOLua task crashes and I get the error messages. Once an event has been assigned then on any subsequent reload of the GIT the IOLua will crash and the errors will start. In both cases the MCPPRO continues to work ok despite the missing IOLua.
    Hope this helps.

    Regards,
    Neil
  • admin_ppsadmin_pps
    Ok, let me see if I can re-create the problem and fix it.

    Best wishes
    Steve
  • Ncrh01Ncrh01
    Hi Steve,

    Any progress or suggestions on this please. I am now running the latest GIT with the stable 0.7.0 FBW 320 and I still get exactly the same easily recreateable problem.

    Regards,
    Neil
  • Ncrh01Ncrh01
    If it is any help it is the FlightSimIOLua.exe program that is crashing with a 0xc000005 exception:

    Log Name: Application
    Source: Application Error
    Date: 05/10/2021 14:55:54
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: DESKTOP-3ISDGK3
    Description:
    Faulting application name: FlightSimIOLua.exe, version: 1.0.0.1, time stamp: 0x6130dcab
    Faulting module name: FlightSimIOLua.exe, version: 1.0.0.1, time stamp: 0x6130dcab
    Exception code: 0xc0000005
    Fault offset: 0x0000000000041d53
    Faulting process ID: 0x437c
    Faulting application start time: 0x01d7b9f025802145
    Faulting application path: C:\Program Files\GoFlight\FlightSimIOLua.exe
    Faulting module path: C:\Program Files\GoFlight\FlightSimIOLua.exe
    Report ID: c5302e1e-e8a4-40f0-8efe-a704cdac7191
    Faulting package full name:
    Faulting package-relative application ID:
    Event Xml:



    1000
    0
    2
    100
    0
    0x80000000000000

    27247


    Application
    DESKTOP-3ISDGK3



    FlightSimIOLua.exe
    1.0.0.1
    6130dcab
    FlightSimIOLua.exe
    1.0.0.1
    6130dcab
    c0000005
    0000000000041d53
    437c
    01d7b9f025802145
    C:\Program Files\GoFlight\FlightSimIOLua.exe
    C:\Program Files\GoFlight\FlightSimIOLua.exe
    c5302e1e-e8a4-40f0-8efe-a704cdac7191







    I've tried reinstalling GIT but to no avail.

    Regards,
    Neil

    PS: Unistalling GIT for MSFS2020 also uninstalls GIT for P3D
  • Ncrh01Ncrh01
    If it helps it appears to be the SETLVAR function that is causing this, the other functions seem to be working ok.

    Regards,
    Neil
  • admin_ppsadmin_pps
    Sorry for the late reply, I haven't been very well. I'll take a look over the weekend and see what is going on.

    Best wishes
    Steve
  • admin_ppsadmin_pps
    I have just run a simple Lua script on the TBM90:

    setlvar("AS1000_Warnings_Master_Set", 1)

    and it worked fine. Can you try the above and see if it errors for you. I tried from the Lua console and assigning to a switch and there was no crash.

    Best wishes
    Steve
  • Ncrh01Ncrh01
    Hi Steve,

    That does seem to work on most planes without crashing so I have done a bit more investigating and I think I have narrowed it down to using Bespoke Vars.

    If I use setlvar("A320_Neo_MFD_NAV_MODE_1",1) then it seems to work OK on the FBW A320..

    However if I use setlvar("A320_Neo_MFD_NAV_MODE_1",BespokeVar3) then it crashes.

    Hope this helps.

    Regards,
    Neil
  • admin_ppsadmin_pps
    Thx, I'll check again.
  • admin_ppsadmin_pps
    edited October 2021
    It's just dawned on me why that wont work. you need to use setlvar("A320_Neo_MFD_NAV_MODE_1", getbvar("BespokeVar3"))

    Lua will see BespokeVar3 as an internal local variable when used in the way you are using it. However, it shouldn't be crashing Lua, so I will still investigate.

    Thx
    Steve
  • admin_ppsadmin_pps
    I have tracked down the cause of the crash and will release a fix tomorrow.

    Best wishes
    Steve
Sign In or Register to comment.

© Vanilla Keystone Theme 2025