Jump to content

coceoca

Inactive Members
  • Content Count

    14
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No
  1. @mSparks Thanks a lot for your contribution! I am interested in this addon. May I ask you some questions? Will you continue with the development? If so, do you have a rough roadmap (approx. when will be implemented which feature)? What is the current status of your fork? Are there any issue with the latest release? Does this plugin eliminate the annoying cloud redraw of X-Plane? Thanks a lot in advance for providing your information. Kind regards
  2. Hello together, I have the same issue: If I go to the ACT RTE 1 page and click on the DELETE button in the FMC and then click on the 1st left LSK ("HOLD at"), my sim also freezes. I then have to terminate the sim. The event viewer provides the following information about the application hang (no trigger module mentioned): "Protokollname: Application Quelle: Application Hang Datum: 29.07.2016 21:17:28 Ereignis-ID: 1002 Aufgabenkategorie:(101) Ebene: Fehler Schlüsselwörter:Klassisch Benutzer: Nicht zutreffend Computer: MeinPC Beschreibung: Programm Prepar3D.exe, Version 3.2.3.16769 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: c74 Startzeit: 01d1e9cd88eefe53 Endzeit: 117 Anwendungspfad: D:\Prepar3D v3\Prepar3D.exe Berichts-ID: 13848c7e-55c1-11e6-9fe7-d43d7eea6ded Ereignis-XML: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Hang" /> <EventID Qualifiers="0">1002</EventID> <Level>2</Level> <Task>101</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-07-29T19:17:28.000000000Z" /> <EventRecordID>123080</EventRecordID> <Channel>Application</Channel> <Computer>MeinPC</Computer> <Security /> </System> <EventData> <Data>Prepar3D.exe</Data> <Data>3.2.3.16769</Data> <Data>c74</Data> <Data>01d1e9cd88eefe53</Data> <Data>117</Data> <Data>D:\Prepar3D v3\Prepar3D.exe</Data> <Data>13848c7e-55c1-11e6-9fe7-d43d7eea6ded</Data> <Binary>55006E006B006E006F0077006E0000000000</Binary> </EventData> </Event>" The hold was based on a fix which has been created by using the PPOS function. I can easily reproduce this issue with a certain saved flight. I use P3D 3.2 and the current version of the PMDG 777. Do you know if it is possible in the real 777 to delete the hold by clicking on the DELETE button and then on the 1st left LSK ("HOLD at") at the ACT RTE 1 page? Or is this a misuse? I had a second issue where I could not exit this hold by clicking on the 6th right LSK ("EXIT HOLD") at the ACT RTE 1 HOLD page. Unfortnately I could not yet reproduce the second issue. Do you know the probable root causes of the two issues? Thanks a lot for your comments. Regards Jens Müller-Junker
  3. Hello Romain, thank you for your answer. I've read 4.20.9 before posting: - A/T manual override option was set to IN HOLD MODE ONLY -> thrust levers were not manually overwritten - reverse thrust levers were in the idle position - A/T arm switches were in the ARM posision - failures were disabled Unfortunately I do not know anymore, what has been displayed in the FMA before and after the alert. My hardware button for disconnecting the autothrottle is 100% reliable (or was 100% reliable up to now...). The thing that could indicate that there might be an issue with the software is that the autothrottle disconnection occured in exactly that moment when I pressed the LOC switch. Kind regards Jens Müller-Junker
  4. Hello together, in my today's flight, the following happened during the descent phase: After I've pressed the LOC switch to arm the LOC lateral mode, the autothrottle was disconnected (immediately upon the switch actuation). I had the AUTOTHROTTLE DISC message and the acoustic warning. Has anybody an idea why the autothrottle was disconnected upon the arming of the LOC mode? I use a Saitek throttle quadrant button for disconnecting the autothrottle. However, this button seems to be ok. Thanks for your thoughts. Jens ... I just want to inform you, that I've clicked on the LOC button with my mouse.
  5. Hello Kyle, it was the ticket 08B-1E1EC17D-043F. Regards Jens
  6. Hello together, I have the same issue! I have created a ticket a long time ago. The PMDG support does not respond anymore to me. See the two linked images (they were from the same STAR): http://s1200.photobucket.com/user/qfhgghkhg/media/BASGO1_zpsl852bhhp.png.html http://s1200.photobucket.com/user/qfhgghkhg/media/BASGO2_zpslrixhxkm.png.html Kind regards Jens
  7. Hello everyone! After my last flight I noticed the following strange behaviour of the sim: After having completed the electrical power down procedure, there was a very small dynamic head movement in the VC (although the wheel chocks have been set by me). I use the DHM feature of EZCA, but I've correctly parked my aircraft. So how can this happen? I flew with the latest versions of P3D V3.2, PMDG 777, EZCA and ASN. I have never seen that weird behaviour after my previous flights. What could be the root cause? Thanks for helping me. Kind regards Jens
  8. Thank you so much, Bryan. Thank you so much, Bryan. Thank you so much, Bryan. sorry, my smartphone sent my last reply three times...
  9. Great. Just to make sure, your option should enable this: FO does the FCOM flow "Preflight Procedure - First Officer" and captain does (i.e. I do) the FCOM flow "Preflight Procedure - Captain". Thank you so much.
  10. According to the FCOM flow, the FO normally does the power up. Then, the captain normally does his flow. Unfortunately, this is not possible with Fs2crew, am I right? Can you add an option in the next version? This option should prevent the FO from doing flow steps which the captain normally does. Bryan, what do you think? Does my proposal make sense? Thanks for answering.
  11. According to the FCOM flow, the FO normally does the power up. Then, the captain normally does his flow. Unfortunately, this is not possible with Fs2crew, am I right? Can you add an option in the next version? This option should prevent the FO from doing flow steps which the captain normally does. What do you think? Does my proposal make sense?
  12. Can I configure FS2Crew so that the captain's preflight procedure is NOT performed by the FO? I want to go through the captain's flow manually. Can anyone please help me? Thanks a lot.
  13. Can I configure FS2Crew so that the captain's preflight procedure is NOT performed by the FO? I want to go through the captain's flow manually.
×
×
  • Create New...