J5flyer

Hello, Sorry to bring up a 3 month old topic, but I also noticed the PM no longer stops the elapsed time after shutdown and I cannot find a mouse macro for it to check in the FS2crew Mouse Macro Setup pages. Maybe I'm being blind, but I've checked several times.

Looking at the video it is probably because the FO has selected the PA on his side, hence it is still coming through the audio. I think the FO selects it on at some point during his pre-flight flows. Ensure it is switched off on both sides.

I have it and think it's great, having flown into there real world as a passenger last year, so I would recommend it. Support from the chap who made it is great too if you encounter any problems. This is the first up-to-date Slovakian airport I've seen produced in a long time.

Hello, Are you disarming the spoilers after vacating the runway? This is the trigger for the PM to start his after landing flow, which obviously includes retracting the flaps.

Not sure about the sounds but you can skip minutes in the preflight events by right clicking the down arrow on the main FS2crew panel (next to the HS button). Regards, James

Hello, Would it be possible to have an option for the PM to delay his taxi flow after the flight control check, maybe using the 'Taxi Procedure Please' voice command? This would help in situations where you would like to do the flight control check before the commencement of taxi, avoiding the issue of the weather radars being turned on too early and the TO config button being pressed before the temperatures have risen sufficiently and the resulting ECAM warning etc. The second user configurable option I would like to request is for the PM to turn Pack 2 on when clean configuration has been acheived on departure, shortly after selecting flap 0 (instead of the current minimum 10 seconds after pack 1 at Thrust Reduction altitude). Just throwing ideas out there 😉 All the best, James

Hi Stu, I can help with a few of those. EDIT: Byork beat me to it while I was typing it all out. Take his more knowledgeable answers of the software over mine! 1. The APU bleed (followed by APU shutdown in most cases) is part of the PF flow after engine start. For shutdown, the PM turns on the APU bleed just before you shutdown the engines. 2. The PM appears to start the timer from the start of taxi after engine start, and stops it after arriving on stand, this is to record the block time for that sector. Some airlines in reality start this from the commencement of pushback and/or engine start. For a bit of extra information it is worth mentioning that you are also expected to start the chrono at various stages to ensure sufficient engine warm-up/down time has elapsed before setting takeoff thrust or shutting down after landing, in addition to the start of the takeoff roll to monitor thrust time limits should anything abnormal happen that may take you close to exceeding those limits (such as an engine failure after V1 and the resulting sluggish climb that would produce, requiring TOGA thrust for a lot longer than normal). 3. I do not know of an option that would change this. Maybe someone else does. 4. Normally both pilots do a flight control check, although individual airlines can have their own Standard Operating Procedures which can modify this. 5. I'm sure I've read somewhere that the voice control method has more functionality, but off the top of my head I cannot tell you exactly what those are. Until someone else replies it would be worth checking the manual as I'm confident the information is in there somewhere. Regards,

Hi Bryan, I think this may be a bug, although I have not had the time to try it myself yet. Have a look at Blackbox's Twitch video linked below where he flew as PM earlier today: https://www.twitch.tv/videos/454079282 You can see at 23:30 into the Video what he enters into the FS2crew DEP page for Thrust Reduction / Acceleration and then the takeoff starts at 36:40. You'll see that the FO/PF sets climb thrust well after the altitude entered in the FMGS & FS2crew DEP page (around approx 2400 feet vice 1690 feet). The airport appears to have an elevation of around 700 feet, so it looks like the PF is incorrectly setting climb thrust at HEIGHT 1690 in this case, instead of ALTITUDE 1690 which is what is entered into the PERF page & FS2crew DEP brief. Hope that helps. Regards, James

Hello, Since installing FS2crew for the FS Labs I also get a CTD every time I try to exit P3Dv4.4. I never had CTDs upon exiting in the Airbus prior to this. My event viewer overview of the CTD contains this: Faulting application name: Prepar3D.exe, version: 4.4.16.27077, time stamp: 0x5bfdbb35 Faulting module name: FS2CrewAirbusLabs64.gau, version: 1.0.0.86, time stamp: 0x5d297907 Exception code: 0xc0000409 Fault offset: 0x00000000000968f4 Faulting process ID: 0x808 Faulting application start time: 0x01d53ce7e82e0cd0 Faulting application path: D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: D:\Lockheed Martin\Prepar3D v4\Gauges\FS2CrewAirbusLabs64.gau I've tried several things such as muting FS2crew before exiting, or switching it to button control, or even disabling it altogether, however it makes no difference. I've not had a CTD yet inflight which is good so its not a disaster to CTD on exit, but inconvenient all the same as any setting changes etc do not get saved. If a solution can be found it would be great to have P3D exit normally again. Regards, James