Jump to content

Emanuel Hagen

admins
  • Content Count

    9633
  • Joined

  • Last visited

  • Days Won

    96

Everything posted by Emanuel Hagen

  1. Hi Emir, Turkish authorities have in the past prooven to be very restrictive with access to their airports for proper photoshootings. If we could get their full permissions to do all the necessary photoshootings the new Istanbul airport would for sure be a very interesting airport to do, without such access it is close to impossible to do though realistically though.
  2. As Juergen already correctly said, the issue with these multiple gates systems is that P3D can not make a difference between them so it sees all three as seperate gates. And therefore it will place three seperate airplanes on them if you include all three in the AFCAD. Therefore sometimes you have to leave some of the gates out in order to be able to put other in and to avoid AI traffic crashing into one another or even into the user if he's parked on one of the gates. This at the moment unfortunately is an issue with the P3D AI engine and nothing we can do anything about.
  3. How are you able to tell the AoA from looking at the aircraft? Have you measured the angle of incidence on the A321 wing and measured the flight path to compare the two? You might be confusing Pitch with Angle of Attack here which are two completly different and indipendant things.
  4. What you describe is normal behaviour. THR CLB is the most corresponding to CLB mode. The Airbus will pitch for speed in CLB and thus THR CLB is still the thrust mode since it will keep climbing with full thrust, regardless of what the speed is as long as you are in CLB or OP CLB. The pitch is then adjusted to keep the desired speed. That's how this mode is designed to work. Imagine it like LVL CHG in your favorite Boeing. Only in VS or FPA modes during climb the A/THR will engage in SPEED mode, adjusting thrust to maintain the speed. The big difference between real life and simulation is force feedback. The real A320 has a very high resistance on the side stick and even the smallest input will make quite a difference. In return this means that if you have a joystick with a low resistance then the Airbus will feel very easy to oversteer. This is nothing we can really change, you simply have to be careful with the controls. When connected to a stick with a realistic force the Airbus will be very easy and precise to fly. Just as the real one. While the picture seems to be missing (pic 1, 2 and 4 are identical and show your departure from Palermo) it seems like you might have a misunderstanding of what the WXR should indicate. Assuming you mean the same departure from your screenshots above, it does not look like anything should be shown on the WXR then. A WXR shows precipitation, not clouds. And it does not look like you had any precip there. Setting the tilt to -5 while in WX+T mode will not give you any good indication as the beam is just pointing down and there is not a lot to be shown there. In case you tried to see some terrain returns (which is the only reason I can imagine you to turn the tilt down during departure), this will only work if you made the according switching on the WXR panel. Which from your description you did not seem to do. And obviously you need to have the brightness of the overlay turned up, just like Tom described you for the terrain already.
  5. On top of what Stefan said already, keep in mind another little detail: The quality of the final visuals does not depend on texture size at all. It depends on how much area you cover with a certain texture file. If you cover a small area with a 1024 texture it can look a lot better than covering a large area with a 4096 texture. Did you know for example that PMDG uses mostly 1024 textures in their cockpits? Just take a look at their files in paint.net or phonoshop. Yet their aircraft look amazingly stunning! And on the other hands side I have seen other developers using 4096 textures whose aircraft look quite blurry if you go close up. It all comes down to what the texture artist does with the files, not to what resolution he uses.
  6. If you have AccuFeel by A2A please disable it with the Airbus.
  7. Hi Bernd, real wird in Airlinern alles nach dem Follow Up Prinzip gemacht. Das bedeutet, dass Du zuerst den Flow (also die Procedure) aus dem Gedächtnis machst und dann die wichtigsten Schritte mit der Checkliste überprüft werden. Für unseren Copiloten haben wir dieses System in ein Read and Do System modifiziert, damit der User die Möglichkeit hat zuzuschauen und zu lernen. Das ist nicht 100% realistisch, aber dafür ist unser Copilot auch nicht gedacht. Dafür gibt es dann FS2Crew, welches alles nach sehr realitätsnahen Procedures und den korrekten Prinzipien macht. Ps.: Ich hab mal auf Deutsch geantwortet und deinen Post in's deutsche Forum geschoben.
  8. Of course this depends on what kind of EFB you have, for the A320 and A330 where there are no class 3 EFB's available you are absolutely right, all entries have to be done manually. Even for aircraft where there are such EFB's available some companies still decide to not use the EFB available from the manuafacturer, for example Lufthansa does not use Boeings EFB in the 747-8, but they use their own one to keep commonality with their other types. My airline also uses an iPad which obviously means we have to enter everything ourselves. We do not plan to include such a feature. Reasons amongs others are: We feel such a feature should be provided by either the simulator itself or by a camera addon In real life you would simply not notice any such shaking. On cameras you do, but did you ever notice your "picture" of your eyes shake when driving a car? I at least never conciously did, not in my car and not in an airplane. If at all sometimes the panel (especially the FCU vibrates a bit, but that's a different thing than the head shaking. The human brain is very good in creating a stable picture in front of your eyes, even when there is a bit of vibration.
  9. Hi Remo, an dieser Stelle wird der Airbus das berechnete vertikale Profil wieder einfangen.
  10. We did a survey about an EFB not so long ago and people clearly voted against one.
  11. Hi, RNAV transitions are included in our dataset. They are located differently though. While Jepp/Navigraph locate those transitions among the STARs in the database LIDO inserts them as transitions (which they technically are). Therefore, in the Airbus, you will find them under APPR VIAS and not under the STARs.
  12. I also have Taxi2Gates Seattle, you can simply choose not to install KSEA with the pack from DD. Then you can use both. And for the price I think getting all the Boeing airfields is still a very good deal even without KSEA!
  13. Die von dir beschriebenen Beschleunigungen Kilopapa wurden in der Vergangenheit durch AccuFeelv2 von A2A ausgelöst. Das ist nicht mit dem Airbus kompatibel. Bitte deaktivier das einmal für den Airbus und dann probier es nochmal.
  14. Patrick, the fact that the ASK21 is not a 2018 release does not mean it is a bad product or not recommendable. In fact quite the opposite, as an ex real life ASK21 pilot I can tell you first hand that it is quite remarkable in terms of the flight dynamics and the feel. Chris, I'd recommend you to start with a "standard" joystick first, for the beginning that will be more than suitable. The Logitech Extreme 3D Pro is quite nice, so is their Attack 3. Both of them I used for quite some time, even though they are in the lower class price segment at about 30€. They are a good start into the hobby though! In the end which addons to go for fully depends on your ideas and needs Chris and of course also on which flight simulator you want to use. If you run FSX for example the ASK21 would be a good starter for sure! It is an easy to fly aircraft and used for training in real life in almost any club you can find.
  15. As you said, it's not v4 compatible, that's why I said we can't promise it yet
  16. Rumors are that Hans Hartmann is working on the 1000. Release 2035!
  17. Hi, Boeing Field is included in Seattle Airports X which you can find here (currently even at a reduced price!): https://www.aerosoft.com/de/flugsimulation/flight-simulator-x/szenerien/2397/seattle-airports-x?number=AS14380 Seoul would be very nice indeed, but it is very hard to get access to that airport. Toulouse we can't promise yet, sorry.
  18. No, this is not planned. Ps.: Please do not hijack other threads, just open your own one if you have a question which is not covered in another thread already.
  19. mmh, I'm also using hybrid and it work fine with that setting here. Anyway, we're glad your issue is solved!
  20. Ganz abgesehen davon, dass wir nicht zulassen dass ein Kunde als blöd bezeichnet wird, weil er eines unserer Produkte kauft. Ich habe die entsprechenden Kommentare gelöscht und wenn das nochmal vorkommt nehme ich mir jedes Recht heraus auch Accounts zu sperren. Solche Kommentare sind in unserem Forum, welches Teil unseres Marketings ist, nicht willkommen.
  21. Hi, did you maybe select the P3D internal altitude system to meters instead of feet? Try to set it to feet and see if that makes a difference please.
  22. Yes, that's why we specifically outline the requirement for P3Dv4.3 in the systemrequirements.
  23. On top of what Tom said already, I think another problem here might be that the forum can presently not search for usernames very well. We'll investigate if there is something we can do about that as the three character limit unfortunately can not be changed in the software we use for our forums. Thank you for your report!
  24. Hallo Ben, AirbusCG hat mit seiner Beobachtung recht, in deinen Screenshots ist die AKUDI STAR im FMGS ausgewählt - daher ist der Inboundwaypoint (den Du oben rechts am ND siehst) AKUDI. Und der ist etwa 60NM von deiner Position entfernt. In deinen Bildern mit dem FSL Airbus hast Du hingegen keine STAR ausgewählt, weshalb der Inboundwaypoint der FAP ist. Der Airbus wird das ILS zwischen 25 und 30NM entlang der Route zur Ziellandebahn einstellen. Hier mag es sich um Zufall handeln, aber da Du im FSL Airbus den FAP ausgewählt hast, welcher etwa 10NM von der Runway entfernt ist, und in unserem Airbus AKUDI, welches etwa 60NM entfernt ist, wird im FSL Airbus die ILS Frequenz eingestellt und in unserem nicht. Bei deinem Anflug auf Leipzig gestern war wahrscheinlich auch der Flugplan nicht richtig sequenziert. Ich sehe es sehr häufig bei Streams, dass Simmer vergessen den Flugplan nachzubearbeiten, wenn sie Vektoren von ATC bekommen. So auch oben in deinem Bild vom FSL Airbus zu sehen: Du bist auf dem ILS, der Inboundwaypoint ist aber weiterhin der FAP.. Wenn Du den gleichen Fehler gestern auch gemacht hast und einen falschen Inboundwaypoint hattest welcher mehr als 30NM entlang der Route vom Zielflughafen entfernt ist, wird sich das ILS nicht einstellen. Das ist normal und entspricht dem Verhalten des echten Airbusses. It's not a bug, it's a feature. Bekommst Du Vektoren für deinen Anflug solltest Du trotzdem den Flugplan "aufräumen" indem Du entweder einen Direct zum FAP eingibst oder die FROM Waypoints solange löschst, bis der FAP zum FROM Waypoint wird. Wenn Du das machst, wird der Airbus das ILS auch automatisch einstellen.
×
×
  • Create New...