Skip to content

edhl

Members
  • Joined

  • Last visited

  1. I'm not sure what a magenta EFOB number indicates versus a white number, but magenta certainly doesn't indicate insufficient fuel -- that is indicated by amber (source). The EFOB figure is the expected fuel on board at destination. If you load more fuel, you'll end up with more fuel left at your destination, so it's expected that the EFOB figure will increase.
  2. In the EFB I see some predefined situations for various failure scenarios. In Aerosoft One, under Manuals, I see a document "A340-600Pro_Situations_Tasksheets.pdf", which presumably contains descriptions of these situations. However, clicking on the document button does nothing, and I also don't see the document in my A340 installation folder. Is it possible that this document was inadvertently omitted from the release? Could it be included in a future update?
  3. From memory, the aircraft also pauses on step climbs and master cautions. Did you get one of those? I believe the exact conditions on which it pauses can be configured in the EFB. As for how to unpause, see the other posts in this thread.
  4. It looks as if the yaw damper is putting in rudder to counteract adverse yaw. I'm not sure how much rudder input you'd expect to see on a real A340-600, but I do note that you're at a relatively slow airspeed in both cases, so it seems plausible to me that you'd need a fairly large rudder input. Given that Toliss have created a custom coded flight model for this aircraft, I'd assume that they've checked this and that it's accurate. For more on the yaw damper's role in countering adverse yaw, see here.
  5. I have the same problem with the "PushbackHelper" addon.
  6. The aircraft already has a builtin feature for this -- on the EFB, see the "JOYSTICK / ACTIONS" page on the bottom right ("TARGET FMS POINT").
  7. I'm having issues activating the aircraft in the EFB. I copy my serial number from Aerosoft One (or the "Downloads" page on aerosoft.com, I've tried both), then click "Paste & Activate Key". The correct key is displayed below the button, but I get an error: "AUTHZ_007: Access denied" Is this a known issue? Does this mean there's an issue with my license key or is this a server issue?
  8. Did you activate with your license key in the EFB?
  9. Make sure your yaw dampers are turned on. They need to be turned on to engage the autopilot, and they are not turned on in Turnaround mode.
  10. Late to the game here, but have you made sure the yaw dampers are turned on? The autopilot won't engage unless at least one yaw damper is on.
  11. Wer es noch nicht mitbekommen hat: Kürzlich hat Aerosoft ein Update auf die Version 1.5.0.0 veröffentlicht, das die Mesh-Probleme behebt.
  12. Ich habe wieder eine neue Version auf flightsim.to hochgeladen mit folgenden Änderungen: Windsack entfernt, der in der Realität nicht existiert und die RVR-Messstrecke blockierte. (Danke an @Altair1986für den Hinweis!) Gras gekürzt, das an manchen Stellen die Beschilderung verdeckte. Menschen an verschiedenen Stellen auf dem Flugplatz hinzugefügt. https://flightsim.to/file/81234/aerosoft-edma-augsburg-enhancement
  13. Ich habe jetzt eine neue Version auf flightsim.to hochgeladen, die den Hügel entfernt: https://flightsim.to/file/81234/aerosoft-edma-augsburg-enhancement
  14. Das ist mir inzwischen auch aufgefallen. Braucht ein bisschen viel Leistung, um da hoch zu kommen... Bin schon seit einigen Tagen auf der Suche nach einer Lösung -- habe schon einiges probiert, was dann nicht funktioniert hat, aber ich glaube, ich habe jetzt vielleicht eine Möglichkeit gefunden. Ich möchte aber noch mal ein bisschen testen, ob nicht doch irgendwo noch der Hund begraben liegt, bevor ich sie auf flightsim.to veröffentliche. (Beim der ersten Version hätte ich ja offensichtlich ein bisschen genauer testen sollen.) Bitte also noch um ein bisschen Geduld.
  15. Freut mich, danke für die Rückmeldung!

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.