Jump to content

Speedbird643

Member
  • Posts

    7
  • Joined

  • Last visited

Everything posted by Speedbird643

  1. Same, I've previously reported it but haven't really got anywhere. Sometimes it works, sometimes not. I installed the latest version earlier today, deleted WASM as instructed and then tried to do a flight. At 90 minutes loading time I gave up, but as I'd quit from the loading screen I re-deleted WASM as per advice and tried to load again, but this time onto a runway as this should help. Currently at 45 minutes and not feeling optimistic.
  2. Same. Takes almost as long to load as to do the flight!
  3. After finally managing to load the A350 after a 35 minute wait, and completing flights in both the -900 and -1000 models, I'm now stuck on this screen again despite it being a model and livery I've used before without touching anything WASM related so shouldn't in theory be affected by the WASM load times for a new aircraft. However I'm now approaching an hour for this load and I'm not convinced its going to happen at all.
  4. I purchased on day one, and managed two short flights in the -900. So far, so good. On day 2, I return to flight sim for a third. At which point the sim won't go beyond the birds eye view load screen despite using a livery I've previously flown, so it isn't WASM generation. After over 20 minutes, I go back to the load screen and start a new flight. This one crashes the sim with no warning or error message. I do a reload, and eventually do get in to the flight deck except one of the screens is greyed out with some floating numbers from the 'wheels' page and uncontrollable Day 3 and I try again. Initially the same indefinite wait, but during the wait I discover the WASM issue from going back to the menu previously. So I shut flight sim down, delete WASM and start again. Only to once again spend over half an hour on the loading screen. I quit again, and delete the WASM folder contents for a second time, this time starting up in a new livery at a different airport and on a runway (which I didn't need to do on day 1, but I'll try anything) - success! So I head back to the menu and try to start my original flight again only for FS to crash, with no warning or error again. OK, perhaps because I just reloaded the aircraft and not the sim. So another reload of FS which this time results in another indefinite load screen. So now I delete the WASM folder contents for the third time because the crash may have messed things up, and reload on a runway again only to get stuck on the birds-eye loading screen yet again. So I quit, again, delete WASM, again, reload on a runway, again and finally get back in the flight deck. Quit FS, start fresh and reload the A359 and FS once again crashes with no warning or error. This is ridiculous. I've gone into the console and its showing 499 errors, mostly in the range of 1-2 minutes which presumably relate to the latest start of flight sim following the crash, although there 72 relating to the A350, mostly related to tooltip IDs. I'm using the SU1 beta version of FS2024 and am currently getting sick to death of the loading music
  5. First time I flew the GSX menu gave me the option to fuel to the Simbrief level; second time I just had the regular percentages. I've also had the discrepancy in passenger loading; and unless I use the EFB to load the aircraft get no value for the ZFWCG
  6. Thanks - the location was correct so I was able to delete the file, but unfortunately it hasn't fixed the issue
  7. Having the same issue, latest version installed along with the VDGS addon, however I can't find the folder mentioned above within the Packages folder to try deleting the .xml file (I use the Steam version)
×
×
  • Create New...