Jump to content

こばと 笠森

Member
  • Posts

    23
  • Joined

  • Last visited

Posts posted by こばと 笠森

  1. First time to have WASM crash on my plane. All screens and buttons are freeze after takeoff.

    • Aircraft: A350-900 (v1.0.8)
    • Simulator: FS2020
    • Navdata Method: NAVIGRAPH
    • OFP: attached below.
    • WASM Error: WASM: Exception c0000005 in gauge Systems in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm
    • Specs: R5-3600X, 64GB DDR4, RTX3060 12GB
    • Autosave File:  attached below.


    MicrosoftFlightSimulator2025_4_2208_05_30.thumb.png.038873d20a2103b529f568cd3ff33196.png

    螢幕擷取畫面 2025-04-22 202643.jpg

    1745323111.bin RCKHRCTP_PDF_1745319674.pdf

  2. 13 hours ago, richboy2307 said:

    Hi,

    Sorry we're not seeing this issue on our end on any of our own liveries (default or from the iniManager). Try loading into a -1000 variant on the default iniBuilds livery or any livery installed via the iniManager to verify.

    This China Airlines livery appears to be a community made one so you should contact the maker of this livery if you continue to experience issues.

    FS20

    image.thumb.png.4d88673cfbf151f9cce011654e9a2578.png

    FS24

    image.thumb.png.66ae7818090fa7fa7c6b9c41f0b69ae1.png

     

    Hi

    Yes the livery is community made and this is one of my own project.
    Can you advice which part of livery files can modify aircraft model on FMS like this?

    I have never experienced such a situation with other airframe before.

    Thanks

  3. Like the title.

    I noticed this issue with the recent updates, maybe started from 1.0.5 and later.

    When the plane in approach phase and both LOC and G/S are captured, the plane starts going pitch up and down slightly, but the closer it got to the airport, the worse it got. As video I posted shows, It almost plummets to the ground itself.
     

  4. 2 hours ago, Eddie said:

    Hello,

    Can you advice whether or not you have enabled "AP Discon Protection" in the OIS? 
    I understand this is extremely frustrating and we have been working very hard on trying to consistently reproduce the issue but have not been successful on that front just yet. If you have an autosave from around when this happened, please attach it here. See below image on how to do that image.thumb.png.9f6263e322f59bc93a1165eaa7f30dd8.png

    Hi

    I do have AP Discon Protection turned on.
    But I don't have autosave file for that very moment, basically you'll notice your plane is deviating from the route after few hours of AFK.

  5. 1 hour ago, OxkyGThaib said:

    Guys, found this on Navigraph Forum, remember this works on MSFS2020, I apologize that I know nothing with MSFS2024.

    https://forum.navigraph.com/t/simbrief-dispatch-not-loading-3-10-2025/18973/11

    The same idea I tried to use but changed the folder type to:

    • Steam Version:
      %appdata%\Microsoft Flight Simulator\Packages\inibuilds-aircraft-a350
    • Store Version:
      %localappdata%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\inibuilds-aircraft-a350

    DELETE ALL THE inibuilds-aircraft-a350 FOLDER and restart the MSFS20, try to re-login to navigraph on OIS and it will be connected (at least for me).

    I am hoping you guys able to connect using the same method.

    Cheers 😁

    That's how you clean the WASM folder, but not the solution for this issue.

    You just need to restart the flight if this problem occurs before takeoff, but you can't do anything if you're already in-flight.

  6. I got FS2020 and latest update 1.0.4 with A350

    My flight from ONT to TPE on monday, didn't see anything wired before i'm going for work, then It went into spinning above Bering Sea, and it crashed after runinng out of fuel.

    I don't have much information about this flight because I'm not home that time, but Volanta flight data shows that no significan altitude change after it went into spinning and airspeed went up and down.

    image.png.4705dd7f758f360eacf75f67bff929af.png

    Then I took sencond attempt next day night, about 2 hours in flight, before I went to sleep I noticed that the autopilot went into HDG and ALT mode itself, AP went working normal again after I pushed both buttom back to NAV and ALT CRZ mode.

    Same issue happened about 7.5 hours in flight, AP went into HDG and ALT mode AGAIN near Kamchatka Peninsula and flew into Russian airspace. I pulled the airplane back on the route on second pic below.

    This is kind of frustrating that It seems she is not ready for long hual flight.

    2025-03-19071708.thumb.png.163bd40bb421e0c8c9dee1b825c8a006.png

    MicrosoftFlightSimulator2025_3_1907_02_11.thumb.png.1167328f8cdfbd081165c2068c6df340.png

     

    • Thanks 1
  7. 1 hour ago, giumanz said:

    Hi, a temporary solution is to replace two lines in the [models] entry inside the "model.cfg" file from:

    [models]
    normal=A35K_EXT.xml
    interior=..\..\inibuilds-aircraft-a350-900\model.900\A35K_INT.xml

    to:

    [models]
    normal=..\..\inibuilds-aircraft-a350-900\model.white\A35K_EXT.xml
    interior=..\..\inibuilds-aircraft-a350-900\model.interior\A35K_INT.xml

    This while waiting for other solutions.

    Greetings to all from Giuseppe

    model.CFG 309 B · 1 download

    This method only work if the livery painted by old tranditional way (DDS exported by Phtoshop... etc), but only wing regs doesn't work properly even you replaced model.cfg by this method.

    If you're painted by sub-model method with Blender, you all have to wait inibuilds update the paintkit.

    Microsoft Flight Simulator 2025_3_16 上午 11_58_39.png

    • Like 1
  8. 9 hours ago, dhiggs92 said:

    I've managed to make the plane visible again, you need to Nuke any a350 files off of your PC, a regular uninstall in the ini manager on it's own doesn't seem to fix it.

    The following worked for me:
     

    • Remove all liveries from the community folder
    • uninstall the plane through the ini Manager
    • delete the A350 folder under the following path:
      AppData\Roaming\Microsoft Flight Simulator\Packages (The easy way to get to AppData is to do 'win+R' and then type %appdata% in the text box)
    • Reinstall via the ini manager
    • Launch MSFS - at this point the plane should be visible.
    • Close MSFS reinstall liveries as you please
      Bare in mind I am using the Steam version of MSFS 2020 and your file location may be slightly different if you're using the windows store version for example.

    Hope this helps 🙂

     

    That's not gonna work for 3rd party liveries.

    They modified the model in this version, so you need to apply new model if you're painting by sub-model method with Blender, and small modify with model.cfg if you painting with old traditional way (Photoshop and DDS files).

     

    I don't think inibuilds has mentioned this at all.

  9. 14 minutes ago, LNOSS said:

    Remove all your 3rd party liveries!
    The repainters of 3rd party paint have to update their liveries and then we need to download it again.

    As easy as that!

    What file exactly should be update? They even not mention it in change log.

×
×
  • Create New...