Aerosoft Scenery
Support for all the FSX / FS2004 products that do not have separate support forums
7408 topics in this forum
-
Pinned topics
-
- 289 replies
- 37716 views
-
- 12 replies
- 18283 views
-
- 0 replies
- 7246 views
-
- 342 replies
- 70445 views
-
- 0 replies
- 6328 views
-
Topics
-
- 3 replies
- 380 views
-
- 5 replies
- 159 views
-
- 8 replies
- 219 views
-
- 3 replies
- 178 views
-
- 0 replies
- 72 views
-
- 4 replies
- 249 views
-
- 12 replies
- 616 views
-
- 1 reply
- 104 views
-
- 22 replies
- 802 views
-
- 9 replies
- 235 views
-
- 2 replies
- 122 views
-
- 2 replies
- 140 views
-
- 3 replies
- 188 views
-
- 17 replies
- 511 views
-
- 5 replies
- 630 views
-
- 9 replies
- 340 views
-
- 36 replies
- 2279 views
-
- 2 replies
- 125 views
-
- 3 replies
- 178 views
-
- 3 replies
- 215 views
-
Posts
-
By Secondator · Posted
A318/319/320/321 version 1.3.0.3 is now available on the store. As previously mentioned this is a big update bringing many fixes on different issues and therefore we decided to make fully new builds. Please do note that it's advised to uninstall any previous versions before installing the new version. We apologise for the small delay before releasing this update and thank you for the patience. Changelog: New Feature: EFB with NDP and Navigraph support Improvements: Engine start logic Improvement Improvements: Pacs logic Improvement Improvements: Added SID and Arrival to CFD sync Improvements: Changes MCDU menu Improvements: Conditions to show rising runway Improvements: GSX2 implementation updated Improvements: Cabin Crew Announcements - Cabin lights call during climb - Now also considers position of OVH light switch Improvements: Minor changes to printout position Improvements: Avoiding issues with 3rd party replacement of default files (ohhh please, never do that....) Improvements: Changed default bag weight to 25 Kg Improvements: Changes to fuel planner so users can edit amount and CG Improvements: After GO-AROUND checklist now proceeds (CLIMB or NEW APPROACH) Bug fix: Fuel display now correctly colored Bug fix: Small issues in CORTE selection and WIND pages Bug fix: QNH decrepancy when inHg was selected solved Bug fix: MCDU freeze issue solved Bug fix: Resetting of APU state avoided Bug Fix: Landing call memo now triggered correctly Bug fix: Fixes in FPLN page on landing phase Bug fix: Further fixes in DES page predictions -
By Secondator · Posted
A330 version 1.0.0.8 is now available on the store. As previously mentioned this is a big update bringing many fixes on different issues and therefore we decided to make fully new builds. Please do note that it's advised to uninstall any previous versions before installing the new version. We apologise for the small delay before releasing this update and thank you for the patience. Changelog: Improvement: Pacs logic improvement Improvement: Engine start logic improvement Improvement: FF and Brake indications better Improvement: Added SID and Arrival to CFD sync Improvement: Changes MCDU menu Improvement: Fuel calculation Improvement: LOW FUEL message added to ECAM Improvement: Conditions to show rising runway Improvement: Copilot now also adjusts FO BARO settings Improvement: Timing start DESCENT PREP CL changed (starts 5 NM earlier) Improvement: GSX-Pushback – Good Engine Start PF call added and call modified (no GSX confirmation necessary anymore) Improvement: parking – Dome lights are automatically switched on, Cones are set and GPU-unit connected Improvement: Breaks between various checks / settings added when aircraft is moving – during those breaks the standard VC view is called (looking outside) Improvement: Timing Seatbelt Announcement CLIMB: Adapted to OVHD switch setting Improvement: Aircraft.cfg – Views added and adapted to CL/ViewFocus Improvement: ViewFocus now also works for ChasePlane users Improvement: Cabin Crew Announcements - Cabin lights call during climb - Now also considers position of OVH light switch Improvement: After GO-AROUND checklist now proceeds (CLIMB or NEW APPROACH) Improvement: GSX2 implementation updated Improvement: Mavigraph chart support added Improvement: Minor changes to printout position and texture Improvement: Changed default bag weight to 25 Kg Improvement: Avoiding issues with 3rd party replacement of default files (ohhh please, never do that....) Improvement: Changes to fuel planner so users can edit amount and CG Bug fix: Small issues in CORTE selection and WIND pages Bug fix: Spoiler imbalance issue solved Bug fix: QNH decrepancy when inHg was selected solved Bug fix: MCDU freeze issue solved Bug fix: Auto trim now suits animations Bug fix: Fixes in FPLN page on landing phase Bug fix: Further fixes in DES page predictions -
Hi MarcusB757: I am not in the computer right now, but I remember that both the B757 and the B767 do not program radio navigation, or ils with the fms. The radios are located on the central pedestal. In fact, the B767 has a special radio to tune the ils, located in the lower part of the central pedestal. Greetings. -
Alles aus und die Force Trim Kalibrierung brauchst du da nicht, der Heli hat doch eine eigene Force Trim Einrichtung, oder? Die Kalibrierungswerte sind egal, wenn du FTU Force Trim nicht verwendest sondern die Einrichtung des Helicopters. Nutzt du (zB bei anderen helis ohne eigenes Force Trim) die FTU Force Trim Einrichtung müssen die Kalibrierungswerte für Pitch, Roll und Yaw so angepasst werden, dass bei aktivieren des Force Trim der Heli die Fluglage beibehält (die Werte sind dann von heli zu Heli verschieden, weshalb es die Kalibrierung braucht, FTU ist ja nicht nur für einen Heli geschrieben sondern fumktioniert prinzipiell mit allen). Zum Nutzen des FTU Force Trim müssen Tasten mit folgenden Parametern belegt werden: FlyAgi > Tweak Utility > Force Trim FlyAgi > Tweak Utility > Force Trim Release Das sind die Knöpfe zum aktivieren und abschalten des Force Trim, wenn du die gar nicht belegt hast kannst du die Kalibrierungswerte im obigen Screenshot ignorieren, die wirken sich auf nichts anderes aus als Force Trim und das nur, wenn du diese beiden Tasten entsprechend belegt hast und verwendest. -
Dein Speicher ist auch 50% schneller getaktet als der vorherige (2133 --> 3200), da ist das ein normales Ergebnis. Die Speichermenge ist nicht von bedeutung solange für die Anwendung kein Mangelzustand herrscht. Bringt aber nichts (außer einem psychologischen Vorteil) solange er nicht genutzt wird.
-