Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content

Felix.k

members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Felix.k

  • Rank
    Flight Student - Groundwork
  1. Hi, first of all sorry for coming up with this problem. I've just experienced a similar issue. I was flying from EDDS to EDDP and after landing, during taxi, suddenly the aircraft slowed down immediately and turned to the left. I was wondering, what happend now. When I activated the brake-information-settings, the red line in the corner shows, that the differential brakes are activ. But I have not pressed any button and I don't find any solution to release the brakes. I don't use rudder-pedals, only a Thrustmaster T-Flight Hotas X. I use it for all axises. Normally I use the integrated Checklist- and Copilot-Feature of the Airbus for the full flight. In this case, I remember, that I had deactivated the autobrake twice (setting: Medium), because it was reactivated shortly before landing by the Copilot. I did it, because I wanted the aircraft to take one of the last exits of the runway. This was the only thing, I changed, compared to my regular flight-operations. For braking I use the default key ".". Could it be a problem with the Airbus or more with P3D V4? It was the first time ever, I had such an issue. Is there any solution to release the brakes? I tried to set and release parking brakes, reactivating the differential brakes by preselected keys, deleting the functions of these keys, but without success. Thanks for your help. Beste regards Felix
  2. I've just had the issue again, after a few flights without any problems. While I leave the room, the airbus was flying on autopilot. Smartcars was running in background. When I came back, after 20 minutes, the airbus was in Alpha-Floor-Mode. Crusing level was 260. I leaved the room with autopilot on in Managed-Mode during climb at about 23.000 feet. When I came back, alpha floor was activated and the aircraft flew at 16.000 feet. The Managed-Speed was reduced to 119 suddenly. A look into smartcars shows, that the aircrafts reached its cruising level a few minutes, after I left the room. After further 10 minutes, a stall was recorded. So the issue must have occured at that period of time. Of course I did not do any input, because I was not in the room. The flightplan seems to be complete, no gaps. I used the Checklist and CoPilot-feature, so there were no abnormalities, compared to my other flight with the airbus. I used the A319 IAE, Active Sky. Tailwind was about 40 knots at that time. Best regards Felix
  3. Regarding to the Autopilot NAV-issue, maybe this could be the solution: Best regards Felix
  4. Great news. I am a bit surprised that nobody else claimed this issue before, so I thought, this could be a local problem. Looking forward to next update. Thanks for your help. Best regards Felix
  5. Hello everyone, first of all, thanks for your responses. At the moment I am not at home, but I am always progressing the same way: Fuel is about 5-6 tons, because I always do short flights. PAX-number is different, because I have this issue with the A320 and the A319. I haven't tested the other two aircrafts yet. PAX number was 140, 116, when I remember correctly, but never full-loaded. I use the instant load option and than starting the Boarding via GSX. Aircraft state is set to cold and dark, my preselected default-state. I start external power, align the IRS and then I select the fuel and loads via the second MCDU (Instant load). As described above, in the next step I start the boarding progress via GSX V2. While this is progressing I enter my flight-plan into the Main-MCDU, fill in the performance page. When boarding is completed or almost finished, I start the "Checklist- and Co-Pilot-Feature" of the airbus to let him do the rest of the startup. As far as I have figured out, it makes no difference, at which time I start the checklist. This "door-issue" happend also, when I started the checklist after the boarding is completed. When the first passenger-bus leaves, I think there are no abnormalities regarding to the messages of GSX, compared to the procedures of other planes/older versions of the Airbus-Series. But if necessary, I will have a closer look to this the next days, when I am nearby my flightsimulator-PC. Setting up a flight without GSX Boarding leads to a successfull start-up, without any issues. Best regards Felix
  6. I have a strange behavior of my Airbus Pro-Series (all aircrafts). When I want GSX V2 to board my passengers, it always ends up in an endless door-opening and door-closing, when I use airside-busses. The first 90 passengers are boarding well, but when the first passenger-bus has finished its operations, the doors of the Aerosoft airbus were closing automatically by GSX. If I do not reopen them fast enough manually via MCDU, the passengers of the second bus are not able to board the plane. The doors begin to open and closing permanently and I am unable to regain control of the doors manually. Even reseting the aircraft-states via MCDU doesn't help. I use P3D V4.4, latest version. The issue occurs since the last official release ( new full-installer) 1.2.3.0. I also tried the recent experimental version 1.2.3.2 (changelog includes some changes regarding to GSX-support) without any differences and I've also activated GSX support inside the MCDU-settings (official and recent experimental version). It doesn't help. Maybe someone can help me to fix this issue respictively could it be a bug? Thanks for your help. Best regards Felix
  7. @fedenav I am following this topic for a couple of days. I've experienced the same bug with my A319, flying from Hamburg to Stockholm. I remember that I've also changed my arriving runway. This was the only flight with this issue and also the only flight, I was changing the runway during cruise/descent. All my other flights (could be about 10-15 flights) since the update were normal, but I didn't changed the runway there. I use Active Sky for P3D V4 and usually the wind-prediction seems to be correct. So changing the runway during flight was not necessary for the other flights, because I set the correct arrival-runway before departure. This could be indeed a hot tip. Best regards Felix
  8. Hallo, gleiches Problem habe ich vorhin ebenfalls festgestellt. Während des Reisefluges etwas "herumgespielt", auf AIDS Print geklickt, Kein Papier. Also nochmal auf AIDS Print geklickt, und ebenfalls "Klick" auf die Stelle wo das Papier hätte erscheinen sollen und der P3D stürzte ab. Exakt das selbe Vorgehen, war seit ca. 40 Flügen insgesamt der erste CTD mit dem AS-Bus. Ich verwende die aktuelle "Experimental-Version", welche diese Woche herausgekommen ist, Prepar3D in der Version 4.4 und AktiveSky P3D V4 mit dem aktuellen Beta-Update für 4.4. In der Windows-Ereigisanzeige konnte ich folgendes Problem feststellen, vielleicht hilft es ja weiter, kenne mich damit nicht wirklich aus 😄 Beste Grüße Felix Fehler - Quelle: Application Hang Programm Prepar3D.exe, Version 4.4.16.27077 kann nicht mehr unter Windows ausgeführt werden und wurde beendet. Überprüfen Sie den Problemverlauf in der Wartungscenter-Systemsteuerung, um nach weiteren Informationen zum Problem zu suchen. Prozess-ID: 2aec Startzeit: 01d493c349ef0ab9 Endzeit: 182 Anwendungspfad: E:\Prepar3D_Version4\Prepar3D.exe Berichts-ID: 98823faf-ffe0-11e8-86aa-f0795972902a Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: Information (Ereignisprotokoll, 1 Sekunde vor Fehlermeldung oben) Fehlerbucket , Typ 0 Ereignisname: AppHangB1 Antwort: Nicht verfügbar CAB-Datei-ID: 0 Problemsignatur: P1: Prepar3D.exe P2: 4.4.16.27077 P3: 5bfdbb35 P4: 4e4f P5: 134217985 P6: P7: P8: P9: P10: Angefügte Dateien: C:\Users\locadm\AppData\Local\Temp\WERCC55.tmp.appcompat.txt C:\Users\locadm\AppData\Local\Temp\WERDA6F.tmp.WERInternalMetadata.xml Diese Dateien befinden sich möglicherweise hier: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_Prepar3D.exe_83b480912e74a0679461434fc8633c889e931ed6_5e4d7e2c_0249da7e Analysesymbol: Es wird erneut nach einer Lösung gesucht: 0 Berichts-ID: 98823faf-ffe0-11e8-86aa-f0795972902a Berichtstatus: 97 Bucket mit Hash:
  9. Eigentlich sind alle Scenerien sehr schön, jedoch finde ich Diese hier am besten Alpha Echo Foxtrot
×
×
  • Create New...