Jump to content

Xenon341

Member
  • Posts

    125
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Xenon341's Achievements

19

Reputation

  1. Hello, Please follow this guide to provide the team the necessary information in order to investigate the problem.
  2. Hello, Please report your crashes by following this guide and giving all necessary informations :
  3. Hello, As WASM crashes are not occuring for everyone, without any report giving the parameters, the team cannot start looking at it. There is a guide available to report those crashes :
  4. Please follow this guide to give the team informations in order to try to investigate. Thanks
  5. 1+F on approach is correct
  6. No worries 🙂 Must depend on the software installed in the plane. Some auto enable after entering like altitude on the MCP, some other don't it seems. Happy flying !
  7. Did you enable Flight Directors ?
  8. IniBuilds Discord server. https://discord.com/channels/535246634448191499/1292807978986111046/1424997127007895617
  9. Hello, VNAV has been updated in 1.1.6, specially the TOD calculation. You should see some enhancement. From the dev team : Works still continue for other cases like sequencing closely spaced waypoints with restrictions.
  10. I can answer you on some points : When I come to an Airport and ask for Jetways, it connects to the first Door. Also wrong. --> It connects to the nearest door on the jetway, always has benn like that and not a 350 issue but a flight simulator limitation, just get the second door closer and you will see it will use it. It flies ok, but on the other side an old wisdom says "it´s not goeing, when its not a Boeing". There is that other developer who still develops those Boeing´s. We have to wait Centurys until they came out for MSFS 2024, but then they worked. Until now only ONE Update so far, not 10+. And guess what, Co-Pilot is sitting on the rigt side grinning and Jetways move to second Door as espected. Performance ++ and overall very satble flights. --> I had time to spare for this one but honestly this just show your bias. The 777F/200 fleet was released on May 19th and -300 on June 13th, I know it because I bought it that day. First update for 777F/200 on june 13th Update 116 on July 17th Update 121 on Aug 1st Sept 3rd, update for SU3 and the LOD problem Sept 12th, another update for SU3 changes Another subject, the 777 fleet is also subject to WASM crashes, I invite you to read their forums and Discord channels.
  11. That's a reasonable expectation, the problem in this case is that it's a platform bug, that mean that code must be added to do "wrong" things in order to make the thing work again. Code that will need to be reverted again when SU4 will release (as the platform bug has been fixed in SU4 it seems). I guess the problem is that if Asobo release a SU3 hotfix for that it can break what a dev could attempt to counter the bug.
  12. That's a platform bug, see https://devsupport.flightsimulator.com/t/rain-is-distorting-hud-textures-when-viewed-from-inside-aircraft/13563/2 Ini responded while ago on their discord.
  13. Yes SU4b bug related to WASM, below a message from the team.
  14. FYI, SU4b bring some bug related to WASM so expect some problems with the plane. Below a message from the dev team.
  15. Know issues from SU4 beta. Some platform bug on the WASM side have been raised. See the developers response here. You can use Sim default nav data as a workaround.
×
×
  • Create New...