Jump to content

JoshF

Moderator
  • Posts

    1330
  • Joined

  • Last visited

  • Days Won

    15

Everything posted by JoshF

  1. Thanks Haseen, I'll take a look as soon as possible
  2. Okay might be a navdata issue then, thanks we'll escalate it as required
  3. The Asobo one is nice, but I personally find ours to just have that bit extra detail. All approaches should be present
  4. Do other default aircraft have STARs for rwy 10?
  5. Hi Haseen, In order to to properly diagnose this, I need the following: A screenshot of your FMS (with constraints inserted) Your full route, including weights and cost index A screenshot of your FCU
  6. I can't say as I've been able to replicate this, this is on the PC version, however. All Xbox testing is done by Microsoft
  7. Hi, as Alexair says, the A310 can fly DME-ARCs as part of a navdata approach despite the ND showing a straight line (a real life quirk of the A310)
  8. Hi, thanks for getting in touch. Do you mind sharing a screenshot/image of the frequency and course you tune and a shot of the PFD?
  9. Yes it probably would in that case if you armed it at the same time as you did LAND there, as the intercept angle was too sharp. Please try again with a shallower approach angle
  10. Hi, if you're trying to do an APU assisted start, you need to use the IGN modes (A or B), not CONT RELIGHT
  11. Hi Tomás, you can edit your PROF speeds on either the MODE or TACT MODE page
  12. A few things to try Push LAND later. Use V/L first to establish fully on the localiser when the diamond is +/- 1 dot. You need to be LOC captured before it will descend on the G/S. It looks like in the video that the FDs don't command nose down until the G/S diamond is one below; but if you watch your FMAs at the same time, you can see that it actually descends when LOC* transitions to LOC.
  13. The A310 does not feature the Enhanced LOC* found on more modern Airbuses. It actually had a quite a restrictive intercept angle, and we have modelled this in the sim. If you feel that even factoring that in that work needs to be done, please post a video if possible of a LOC capture that doesn't work, but you think it should
  14. Hi there, Please try deleting the .dat files at one of these locations: `C:\Users\YourUsername\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes (MS Store)` or `C:\Users\YourUsername\AppData\Roaming\Microsoft Flight Simulator\SceneryIndexes (Steam)`, also try clearing the contents of the scenerycache location too
  15. Thanks! We've noted this for future improvements
  16. Welcome to Detroit! iniScene Detroit Metro Wayne County (KDTW) is now available for Microsoft Flight Simulator. Fly to this Delta super hub serving destinations across the United States and beyond.
  17. Thanks for the reports guys, rest assured we are looking into it
  18. Thanks, we've got this logged internally already 🙂
  19. Does this persist with a clean community folder?
  20. Performance is still something we are working to improve. The .dll files not being present, and a fast load time are expected. We initially thought it might've been an issue; but after further investigation with Asobo it turns out it wasn't. For reference; I get + 10/15 fps compared to the Fenix, and +/- 2 fps to the PMDG in the same scenario. A lot of others are also reporting higher frame rates so whatever is causing these issues for you guys is obviously something else. As I say, we're continually looking into it.
  21. Thanks, I've got this logged for us to take a look at 🙂
  22. Hi, we have this logged internally. For now, please continue to use the pushbutton on the glareshield
  23. Hi! Was this in flight or on the ground?
  24. Hi! Please see this video (timestamped)
×
×
  • Create New...