Jump to content

Eddie

Moderator
  • Posts

    1017
  • Joined

  • Last visited

  • Days Won

    37

Posts posted by Eddie

  1. 4 minutes ago, silentghostx said:

    Hi Eddie and team,

    Thanks for all the hard work. I wish that there could be consideration given to having a pinned topic with “known and logged issues” that’s worked on by the team. We understand not everything will make into the next update, but at least we know it’s being worked on.

    This would reduce a lot of cross and double posting. Might also be useful to use it to create the next change log when there is an update, can just take the issues from the post into fixed.

     

    Cheers,

    Chen

    Hi Chen,

    I'll look into what can be done regarding this. Would perhaps renaming the threads to include "LOGGED" in the title suffice? 

  2. Hi again,

    I recommend just not worrying about it and just living life until we are happy of the state it's in for release. I must reiterate, this is done to ensure you have as seamless of a start as possible. I admit it is taking its time but it is all for good reason. We are working very hard on delivering this as soon as possible and we are very sorry for the previous timeline we had given. Welcome to the unpredictable world of development! 🙂 

    Again, your patience and understanding is very much appreciated. 

    • Like 1
  3. 15 minutes ago, Der Michel said:

    The problem is, I don't know what reports are intended to be fixed and are not fixed in my testing. Especially the complexer ones.
    For example, GA in blue, was mentioned in changelog, but not fixed. Also FUEL calcaualtion was changed in update but still with errors.

    I hope you alos noticed the new reports from yesterday.

    Fair enough. I'll take a thorough look throughout today and tomorrow. 

  4. Hello,

    Note for all your reports: No need to confirm. Your reports have been logged and I can not promise that everything will make it into the next update. They're logged and will make it in as soon as possible. 

    Thank you 

    • Thanks 1
  5. Hello,

    This is not forgotten about. It is on our list. I cannot confirm/promise which update this will go into as it is unfortunately not a priority item at the moment. Thank you for your patience and understanding! 🙂

    • Thanks 1
  6. 13 hours ago, dreamlinear said:

    I have been facing the same issue for several days on the A35K. I've reinstalled iniBuilds A350 as well as MSFS2020 from scratch, cleared the WASM folder multiple times and tried multiple liveries - The outcome is always the same. 

    I tried to create a thread for support on discord, which I haven't received any help on: https://discord.com/channels/535246634448191499/1366483922292052070. This is leading me to not use this aircraft anymore since I cannot even load anything into FMS on the ground. I have noticed that if I do not click on the FMS dropdown in the MCDU initially, it seems to work fine but later on have noticed it still crashes.

    This is now causing me to lose any confidence flying this aircraft as the FMS is completely unstable and can just stop working mid-flight leading to cancelled trip. Please can you provide some sort of an update, since I would expect better support for a paid product. 

    Thanks.

    Hello,

    I am very sorry to hear that you've been experiencing this issue. As you can see by the original thread creator here, we need a few more details to be able to action these WASM reports. They're rare and differ greatly from person to person. Sometimes they're common and its an easy fix, other times we need said person to give us their specific report so we can squash that specific WASM crash. 

    Regardless, we are finalizing testing on version 1.0.9 and that version also comes with a slew of WASM-crash fixes. Please take a look if all is well in that version. Thank you for your patience and understanding! 

  7. Hello,

    I understand the wait is frustrating but we are working our hardest to get it out for you all. I can't give you an exact date or timeframe but sooner rather than later is all I can say. Your patience and understanding is very much appreciated 🙂

    • Thanks 1
  8. Hello,

    Please ensure the DEFAULT Asobo EGLL is disabled in the content manager in-sim. If yes, try clearing your scenery indexes. 
    To do that locate your folder by following the path below:
    MSFS 2020

    Quote

    MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes
    Steam: %APPDATA%\Microsoft Flight Simulator\SceneryIndexes

    MSFS 2024

    Quote

    MS Store: %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\SceneryIndexes
    Steam: %APPDATA%\Microsoft Flight Simulator 2024\SceneryIndexes


    Then delete the contents inside but leave the folder intact. The indexes will rebuild on next load of FS.
    Let me know either solves your issue. 

  9. Hello,

    Very sorry to hear that you've experienced a WASM crash. While this is not a guaranteed, please clear your WASM folders just incase: 

     

    I'll forward this to the team. Thank you 🙂 

  10. Nothing to be worried for! It is progressing nicely. We want to ensure it is as perfect as can be for launch. I understand the wait is frustrating but I assure you we are working as hard as we can to get this beauty out to you all. Please, just a little more patience and we should be good to go! 🙂

    • Thanks 1
  11. 1 hour ago, C. Schaffhausen said:

    Hello @Eddie, any news regarding this AP behaviour? I've had this issue twice on my flight from KSAN to EGLL, we really need a workaround to make sure our long-haul AP to be functioning reliably.

    • Prevent AP disconnection - ON
    • Navdata - Sim default
    • WASM folder - cleared before flight

    We're working hard on the 1.0.9 update doing our best to ensure this no longer happens! Your patience is very much appreciated. Thank you

  12. Oh my.. so.. I may or may not have misread the category. So used to replying to A350 threads. Terribly sorry!! 

    Unfortunately, the A400M does not support physical input, no. I believe it has been requested to MS/Asobo in the past. We'll see if we'll be asked to implement this or not. 

    Again, apologies and thank you 🙂

×
×
  • Create New...