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 - 1.31.18.0 BETA (SU12) - GIT errors

FYI

I just tried out the current beta (v1.31,18.0) for SU12 and GIT seems to be stuck after loading (yellow) with the following message repeated forever in the GIT logs:

SimConnect: Exception Received: OUT_OF_BOUNDS

I've backed out of this beta due to the GIT issue.
Hopefully this can be investigated and a new version released soon so I can do more testing with this beta.

Regards
David
Regards
David

Comments

  • Are you sure the GIT WASM module is in the community folder?

    Best wishes
    Steve
  • Hi,

    I use Addon Linker for everything that goes into the Community folder.

    For any new MSFS update or beta, I use AddOn Linker to 'remove' everything from the Community folder, and start up MSFS to ensure the new/beta starts with a clean slate. (I have a preset called -NONE which turns off every addon in Community).

    After which I start by relinking (in Addon Linker) key components, and restarting MSFS to check it still loads/functions.

    So via Addon Linker, I was using the same GIT WASM module before and after the Beta install.
    Ive opted in again for the beta, only to find GIT is still giving me the errors.

    I double checked to make sure the WASM module was loaded and checked that it was the ONLY addon I had linked into Community to ensure it wasnt anything else causing it.
    I checked the WASM version (as per manifest.json) to ensure it was v1.0.1

    It still caused GIT issues.

    Out of desperation (was not looking forward to another 24 hrs of effort to roll back MSFS), I redownloaded WASM module, and deleted and copied over WASM module.
    I restarted the beta, and this time there are no errors listed.

    I am at a total loss as to why, because prior to beta, GIT was working fine with v1.0.1 that was installed in Community folder.

    Anyway, a delete and reinstall/copy of the WASM module seems to have fixed it.

    Regards
    Regards
    David
  • The WASM module had a major update in the latest version of GIT. If the old version was running you would have got loads of errors.

    Best wishes
    Steve
Sign In or Register to comment.