June 3, 20206 yr Hello Bryan. I‘m having troubles with my F/O whilst performing touch&gos ( P3D v4.5 ): All is fine after departure, but when configuring for approach with Flaps 1 and Flaps 5, the F/O does not reply to „Bug 1“ or „Bug 5“. All he says is „are you sure?“. During the first approach, all is fine, but during the succeeding approaches, the F/O demonstrates the above behaviour. Any help is appreciated. Best regards, Toto
June 3, 20206 yr Author One more thing: after touch down, the „rotate“ call comes about 10knots too late.
June 3, 20206 yr This would be a great time to have the traffic pattern checklist. Rick D http://g5flyer.tumblr.com/
June 4, 20206 yr Commercial Member 9 hours ago, Sonne said: Hello Bryan. I‘m having troubles with my F/O whilst performing touch&gos ( P3D v4.5 ): All is fine after departure, but when configuring for approach with Flaps 1 and Flaps 5, the F/O does not reply to „Bug 1“ or „Bug 5“. All he says is „are you sure?“. During the first approach, all is fine, but during the succeeding approaches, the F/O demonstrates the above behaviour. Any help is appreciated. Best regards, Toto For your 2nd approach, ensure VREF is entered in the FMC so FS2Crew can calculate the target speed. I suspect on the 2nd approach, your VREF in the FMC is resetting to 0 when the wheels hit the ground, so FS2Crew thinks the Bug target speed is a very low number (due to VREF being 0) , and that's why you're getting 'are you sure'. Cheers, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
June 4, 20206 yr Author Hello Bryan. No, vref is set and displayed correctly for all approaches, including the whole approach procedure ( ILS ). The correct Vref is also stated by F/O during the Descent Checklist.
June 4, 20206 yr Commercial Member Codewise, that's all I can think of? Is your autopilot on or off? B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
June 4, 20206 yr Commercial Member Oh, I think I may see the problem. FS2Crew uses "V2" speeds as read out of the FMC as part of the calculation. But it only reads it while the airplane is on the ground, not the air. That's why it worked on your first approach, but not your second, because when he touched down the speed would have been wiped. I'll see what I can do about this in the next update. Cheers, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
June 4, 20206 yr Author Thank you, Bryan. Would it be possible to release a fix for version 1.5? Due to the multiple problems that seem to be inherent to the recent PMDG 747 update for P3D v5, I‘m still running the pre v5 747, which seems to be the better choice at the time being. Thus I‘m not on FS2CREW v1.6 Best regards, Toto
June 4, 20206 yr Commercial Member What problems are those? I've heard of no issues with the FS2Crew PMDG 747 P3D V5 version. Unless you're referring to the PMDG aircraft itself. The FS2Crew PMDG 747 P3D v5 update was basically just an installer update. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
June 4, 20206 yr Author Hello Bryan. Yes, I‘m referring to the PMDG v5 Version which is having a hard time with blatant deficiencies and shortcomings, not to FS2Crew. So: can the FS2Crew version 1.6 also be installed into P3D v4.5 with the PMDG pre v5 release? Best regards, Toto Edited June 4, 20206 yr by Sonne
June 4, 20206 yr Commercial Member Yes, you can install the future V1.6 into P3D V4 with the P3D V4 version of the PMDG 747. No problem. All you would do is select P3D V4 on the installer screen. Cheers, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
Archived
This topic is now archived and is closed to further replies.