|
|
Post by Gus Pacleb on May 14, 2021 11:10:30 GMT -5
Hi folks,
I hope everyone is doing well. I have been using first officer pro for a good few weeks now, and it is such an amazing product! Thanks for all of the work that has and is currently being done to maintain and release support for paywhere aircraft. As some of you may know, myself and a few others are blind simmers, and we are using Flight Simulator First Officer to aid us with the PMDG airplanes. Typically, I've been using liveries downloaded from the PMDG operations center and have been flying them without issue for the 737 NGXU and 747 QOTS II. I had loaded up as usual in an AirCanada 777-300ER, let FSFO configure the plane and did my part of programming the FMC. When I went to takeoff, I got a master caucion warning alarm, which silenced when I got up in the air, and began to blare again crossing 10000 feet. No messages on the FMC to indicate something was wrong. Reloaded the plane and reconfigured to make sure the cause of the master warning alarm wasn't due to human error, and again, I had the same sequence of events. I then decided to test the in-house 300-ER, configured everything with the same weights and flight plan, and we were able to take off and climb without any issue or alarm. Do we know if FSFO is only limited to flying these in-house liveries? If so, is it possible to add full support for the liveries that can be downloaded via the PMDG operations center, so that First Officer will detect these changes and configure the plane so that these alarms do not go off when using airline liveries downloaded from the center?
Thanks so much for any help, and I hope all is well.
Gus Pacleb
|
|
|
|
Post by timbersim on May 15, 2021 2:08:01 GMT -5
Hi,
Super late over here, thank you insomnia, so why not experiment.
I just took up a Boeing 777F (UPS variant from the PMDG operation's center) and did not have this problem. This is also known as the freighter variant of the 200lr.
I then attempted to download the one and only Air Canada 300er from the same place. Keep in mind I have the IRS setting to quick align (setting 1 in the ini file). I have the save state set to cold and dark.
I ran through the exact same procedure (Preflight flow, configuring the FMC as per the tutorial / previous experience with the 747), entering info into the briefing, setting MCP with FSFO, followed by preflight checklist, before start flow, before start checklist, engine start, after start flow (or rather letting flaps get set, among everything else). I then ran through taxi and before t/o checklist. I should mention here that my FSFO is still crashing upon the first attempt to run this last checklist, and in the case of the Boeing 747 and 777, the first officer only speaks the words 'before takeoff checklist' before it force closes. In the 737, he goes through the checklist and immediately crashes instead of telling flight attendants to take their seats. I'm still not sure where exactly to find the log file to send.
Restarting and reconnecting fixes this - I throw the briefing in once again and go through the checklist and everything went smoothly.
However, in the Air Canada 300er, here's where I had the exact same problem as the above poster. It appears to be the master warning alarm and I can't figure out why. It went off on takeoff, despite everything being set (according to FSFO, at any rate). We climbed out successfully, the alarm then silenced as soon as the wheels left the runway. Then, right after 10000, it went off once again, and remained on indefinitely-was still on during cruise, despite the aircraft following procedures - vnav and lnav were both enabled as was autopilot, nothing was out of place.
I should also mention here that I attempted this with version 2.02 and 2.03 of FSFO, both with the same result. This is, to put it mildly, quite mystifying. I'm not sure if this is a problem with that particular variant of the plane (I have yet to try another 300er livery from the operation center). I don't appear to be getting any CDU messages and everything appears normal from that side of the aircraft.
One final observation is that neither version powers on the GPU in the 777, neither the 200lr or 300er that I tried. However, the 737 is powering up beautifully with lovely ground power now, as is the 747.
And, finally, in the 747 and 777, despite setting flaps 25 in the briefing, FSFO, if set to handle flaps automatically during landing, will bring them to 30 (or 40 in the 737 instead of 30). Is this by design - can it autodetect if an autoland is in progress?
Thanks for everything. If someone could attempt to replicate this issue it would be greatly appreciated - especially curious if a warning is displayed anywhere in the cockpit either on takeoff or passing 10000 with the 300er from Air Canada. I truly do not understand what the issue could be.
|
|
|
|
Post by Matthew King on May 15, 2021 12:34:31 GMT -5
Hi folks, I hope everyone is doing well. I have been using first officer pro for a good few weeks now, and it is such an amazing product! Thanks for all of the work that has and is currently being done to maintain and release support for paywhere aircraft. As some of you may know, myself and a few others are blind simmers, and we are using Flight Simulator First Officer to aid us with the PMDG airplanes. Typically, I've been using liveries downloaded from the PMDG operations center and have been flying them without issue for the 737 NGXU and 747 QOTS II. I had loaded up as usual in an AirCanada 777-300ER, let FSFO configure the plane and did my part of programming the FMC. When I went to takeoff, I got a master caucion warning alarm, which silenced when I got up in the air, and began to blare again crossing 10000 feet. No messages on the FMC to indicate something was wrong. Reloaded the plane and reconfigured to make sure the cause of the master warning alarm wasn't due to human error, and again, I had the same sequence of events. I then decided to test the in-house 300-ER, configured everything with the same weights and flight plan, and we were able to take off and climb without any issue or alarm. Do we know if FSFO is only limited to flying these in-house liveries? If so, is it possible to add full support for the liveries that can be downloaded via the PMDG operations center, so that First Officer will detect these changes and configure the plane so that these alarms do not go off when using airline liveries downloaded from the center? Thanks so much for any help, and I hope all is well. Gus Pacleb Gus, Every livery comes with it's own unique configuration; so, it's probably a config that I'm not tracking. I will download the livery your mentioned and see if I can find the cause of the alarm; it's got to be a feature on the AirCanada livery that does not exist on most others. |
|
|
|
Post by Matthew King on May 15, 2021 12:36:19 GMT -5
Hi, Super late over here, thank you insomnia, so why not experiment. I just took up a Boeing 777F (UPS variant from the PMDG operation's center) and did not have this problem. This is also known as the freighter variant of the 200lr. I then attempted to download the one and only Air Canada 300er from the same place. Keep in mind I have the IRS setting to quick align (setting 1 in the ini file). I have the save state set to cold and dark. I ran through the exact same procedure (Preflight flow, configuring the FMC as per the tutorial / previous experience with the 747), entering info into the briefing, setting MCP with FSFO, followed by preflight checklist, before start flow, before start checklist, engine start, after start flow (or rather letting flaps get set, among everything else). I then ran through taxi and before t/o checklist. I should mention here that my FSFO is still crashing upon the first attempt to run this last checklist, and in the case of the Boeing 747 and 777, the first officer only speaks the words 'before takeoff checklist' before it force closes. In the 737, he goes through the checklist and immediately crashes instead of telling flight attendants to take their seats. I'm still not sure where exactly to find the log file to send. Restarting and reconnecting fixes this - I throw the briefing in once again and go through the checklist and everything went smoothly. However, in the Air Canada 300er, here's where I had the exact same problem as the above poster. It appears to be the master warning alarm and I can't figure out why. It went off on takeoff, despite everything being set (according to FSFO, at any rate). We climbed out successfully, the alarm then silenced as soon as the wheels left the runway. Then, right after 10000, it went off once again, and remained on indefinitely-was still on during cruise, despite the aircraft following procedures - vnav and lnav were both enabled as was autopilot, nothing was out of place. I should also mention here that I attempted this with version 2.02 and 2.03 of FSFO, both with the same result. This is, to put it mildly, quite mystifying. I'm not sure if this is a problem with that particular variant of the plane (I have yet to try another 300er livery from the operation center). I don't appear to be getting any CDU messages and everything appears normal from that side of the aircraft. One final observation is that neither version powers on the GPU in the 777, neither the 200lr or 300er that I tried. However, the 737 is powering up beautifully with lovely ground power now, as is the 747. And, finally, in the 747 and 777, despite setting flaps 25 in the briefing, FSFO, if set to handle flaps automatically during landing, will bring them to 30 (or 40 in the 737 instead of 30). Is this by design - can it autodetect if an autoland is in progress? Thanks for everything. If someone could attempt to replicate this issue it would be greatly appreciated - especially curious if a warning is displayed anywhere in the cockpit either on takeoff or passing 10000 with the 300er from Air Canada. I truly do not understand what the issue could be. Great feedback, sir!! There's got to be something with that particular livery; let me see if I can't sort it out. |
|
|
|
Post by timbersim on May 16, 2021 2:52:26 GMT -5
Hi, Super late over here, thank you insomnia, so why not experiment. I just took up a Boeing 777F (UPS variant from the PMDG operation's center) and did not have this problem. This is also known as the freighter variant of the 200lr. I then attempted to download the one and only Air Canada 300er from the same place. Keep in mind I have the IRS setting to quick align (setting 1 in the ini file). I have the save state set to cold and dark. I ran through the exact same procedure (Preflight flow, configuring the FMC as per the tutorial / previous experience with the 747), entering info into the briefing, setting MCP with FSFO, followed by preflight checklist, before start flow, before start checklist, engine start, after start flow (or rather letting flaps get set, among everything else). I then ran through taxi and before t/o checklist. I should mention here that my FSFO is still crashing upon the first attempt to run this last checklist, and in the case of the Boeing 747 and 777, the first officer only speaks the words 'before takeoff checklist' before it force closes. In the 737, he goes through the checklist and immediately crashes instead of telling flight attendants to take their seats. I'm still not sure where exactly to find the log file to send. Restarting and reconnecting fixes this - I throw the briefing in once again and go through the checklist and everything went smoothly. However, in the Air Canada 300er, here's where I had the exact same problem as the above poster. It appears to be the master warning alarm and I can't figure out why. It went off on takeoff, despite everything being set (according to FSFO, at any rate). We climbed out successfully, the alarm then silenced as soon as the wheels left the runway. Then, right after 10000, it went off once again, and remained on indefinitely-was still on during cruise, despite the aircraft following procedures - vnav and lnav were both enabled as was autopilot, nothing was out of place. I should also mention here that I attempted this with version 2.02 and 2.03 of FSFO, both with the same result. This is, to put it mildly, quite mystifying. I'm not sure if this is a problem with that particular variant of the plane (I have yet to try another 300er livery from the operation center). I don't appear to be getting any CDU messages and everything appears normal from that side of the aircraft. One final observation is that neither version powers on the GPU in the 777, neither the 200lr or 300er that I tried. However, the 737 is powering up beautifully with lovely ground power now, as is the 747. And, finally, in the 747 and 777, despite setting flaps 25 in the briefing, FSFO, if set to handle flaps automatically during landing, will bring them to 30 (or 40 in the 737 instead of 30). Is this by design - can it autodetect if an autoland is in progress? Thanks for everything. If someone could attempt to replicate this issue it would be greatly appreciated - especially curious if a warning is displayed anywhere in the cockpit either on takeoff or passing 10000 with the 300er from Air Canada. I truly do not understand what the issue could be. Great feedback, sir!! There's got to be something with that particular livery; let me see if I can't sort it out. Thanks a lot. One thing I should mention is it does like to use KG on the weights and things, but I think that is all in terms of difference from the in house. I of course could be very wrong - there must, as you say, be something quirky with it. Thank you for investigating. |
|
|
|
Post by Matthew King on May 27, 2021 8:25:50 GMT -5
Thanks to a fellow user, I think we got this nailed down; essentially, it deals with pressure system. I will try to get an update out over the weekend
|
|
|
|
Post by timbersim on May 29, 2021 13:05:13 GMT -5
Thanks to a fellow user, I think we got this nailed down; essentially, it deals with pressure system. I will try to get an update out over the weekend Awesome, thank you so much for all the great work you have and continue to put into this! |
|
|
|
Post by timbersim on Jun 12, 2021 15:08:23 GMT -5
Hello,
How is progress coming on the new version? A few more observations...
It appears FSFO does not support center runways - it simply labels them as runway 10, 22, etc. Without the c.
The GPU powerup does not appear to work with the 777 - similar to the 737, this could be due to a PMDG update?
How do flaps work with FSFO? Can it read the speed tape? I've had to disable them simply due to the fact that especially on landing, despite setting them to 30 in the 737, it will bring them to 40 on its own. It also appears there are times where it will not bring them up all the way despite a target speed that is well in excess of flaps up speed, in the 737 especially but the 747 as well. I believe this may have something to do with airspeed before accelleration altitude? I have them enabled for takeoff still, however end up setting them manually for landing.
That is all for now - I hope you are doing well and taking care!
thank you again
|
|
|
|
Post by Matthew King on Jun 19, 2021 12:44:12 GMT -5
Hello, How is progress coming on the new version? A few more observations... It appears FSFO does not support center runways - it simply labels them as runway 10, 22, etc. Without the c. The GPU powerup does not appear to work with the 777 - similar to the 737, this could be due to a PMDG update? How do flaps work with FSFO? Can it read the speed tape? I've had to disable them simply due to the fact that especially on landing, despite setting them to 30 in the 737, it will bring them to 40 on its own. It also appears there are times where it will not bring them up all the way despite a target speed that is well in excess of flaps up speed, in the 737 especially but the 747 as well. I believe this may have something to do with airspeed before accelleration altitude? I have them enabled for takeoff still, however end up setting them manually for landing. That is all for now - I hope you are doing well and taking care! thank you again It appears FSFO does not support center runways - it simply labels them as runway 10, 22, etc. Without the c. - Great catch; corrected in v2.04The GPU powerup does not appear to work with the 777 - similar to the 737, this could be due to a PMDG update? - Corrected in v2.04How do flaps work with FSFO? Can it read the speed tape? I've had to disable them simply due to the fact that especially on landing, despite setting them to 30 in the 737, it will bring them to 40 on its own. It also appears there are times where it will not bring them up all the way despite a target speed that is well in excess of flaps up speed, in the 737 especially but the 747 as well. I believe this may have something to do with airspeed before accelleration altitude? I have them enabled for takeoff still, however end up setting them manually for landing. Can you provide some more information? Are you referring to voice commanded flaps or automated flaps? The latter is based in v2 and vref speeds. |
|
|
|
Post by timbersim on Jun 19, 2021 13:09:37 GMT -5
Hello, How is progress coming on the new version? A few more observations... It appears FSFO does not support center runways - it simply labels them as runway 10, 22, etc. Without the c. The GPU powerup does not appear to work with the 777 - similar to the 737, this could be due to a PMDG update? How do flaps work with FSFO? Can it read the speed tape? I've had to disable them simply due to the fact that especially on landing, despite setting them to 30 in the 737, it will bring them to 40 on its own. It also appears there are times where it will not bring them up all the way despite a target speed that is well in excess of flaps up speed, in the 737 especially but the 747 as well. I believe this may have something to do with airspeed before accelleration altitude? I have them enabled for takeoff still, however end up setting them manually for landing. That is all for now - I hope you are doing well and taking care! thank you again It appears FSFO does not support center runways - it simply labels them as runway 10, 22, etc. Without the c. - Great catch; corrected in v2.04The GPU powerup does not appear to work with the 777 - similar to the 737, this could be due to a PMDG update? - Corrected in v2.04How do flaps work with FSFO? Can it read the speed tape? I've had to disable them simply due to the fact that especially on landing, despite setting them to 30 in the 737, it will bring them to 40 on its own. It also appears there are times where it will not bring them up all the way despite a target speed that is well in excess of flaps up speed, in the 737 especially but the 747 as well. I believe this may have something to do with airspeed before accelleration altitude? I have them enabled for takeoff still, however end up setting them manually for landing. Can you provide some more information? Are you referring to voice commanded flaps or automated flaps? The latter is based in v2 and vref speeds. Hello, I'm referring to automated flaps. Despite setting flaps to 30 in the briefing, for example, in the 737, when flaps are automated they automatically go to 40 despite the briefing saying otherwise. They also tend to come out very early - maybe this is by design and I'm bringing them out late. Using voice works flawlessly however. Thank you for the update - will give this a look and report back! |
|
|
|
Post by Matthew King on Jun 20, 2021 9:08:52 GMT -5
Another good catch, Timbersim....I just checked the code and you're correct. I'm fixing now...it will be fixed in 2.04 too
Keep the reports coming, sir!!!
|
|
|
|
Post by timbersim on Jun 22, 2021 13:03:42 GMT -5
Hi again,
I'm also noticing at times, even with 2.04, on takeoff, flaps not coming all the way up automatically. I'm not sure if it has something to do with pitch, but it seems like if flaps are not fully up when vnav comes on I have to manually intervene otherwise our speed will never come fully up to where it is supposed to. This happens more on the 747 and 777, but has in the 737 as well.
Also - out of curiosity - how does FSFO account for changes in weather? E.g. I notice if there is precipitation the windshield whipers will come on before takeoff - but not on descent or approach. Is this normal or a bug? I'm also aware this is pretty low on the list of issues but something I noticed last night while flying into BIKF and active sky was listing there to be moderate to heavy rain and thunderstorms in the vicinity on the approach. This was the first time I have had this happen so was just curious.
Does FSFO also account for needing antiice on descent? Still not sure how that works and am making sure I have all my ducks in a row for the winter flying.
Once again thank you for everything you have done so far and hope things are slowly improving your way, at least as much as they are able.
Timber
|
|
|
|
Post by Matthew King on Jun 23, 2021 8:16:24 GMT -5
Hey timbersim!
I'm also noticing at times, even with 2.04, on takeoff, flaps not coming all the way up automatically. I'm not sure if it has something to do with pitch, but it seems like if flaps are not fully up when vnav comes on I have to manually intervene otherwise our speed will never come fully up to where it is supposed to. This happens more on the 747 and 777, but has in the 737 as well.
- The flaps are retracted based on Boeing flap recommendation card, which is based on your v2 speed. So, if the aircraft doesn't exceed a certain speed (e.g. v2+ 40), the flaps won't be retracted. At acceleration height, are you pitching down to increase the aircraft speed?
Also - out of curiosity - how does FSFO account for changes in weather? E.g. I notice if there is precipitation the windshield whipers will come on before takeoff - but not on descent or approach. Is this normal or a bug? \
- FSFO can detect partipiation and intensity during both the after start and approach flows. I'll check to see why it's not happening in the latter. This feature will be discontinued for V3 though...
I'm also aware this is pretty low on the list of issues but something I noticed last night while flying into BIKF and active sky was listing there to be moderate to heavy rain and thunderstorms in the vicinity on the approach. This was the first time I have had this happen so was just curious.
Does FSFO also account for needing antiice on descent? Still not sure how that works and am making sure I have all my ducks in a row for the winter flying.
- Yes, FSFO can detect anti-ice conditions and turn on your ice systems; however, because 777 and 747 have auto system, he only does it for the 737.
|
|
|
|
Post by timbersim on Jun 23, 2021 12:07:51 GMT -5
Hey timbersim! I'm also noticing at times, even with 2.04, on takeoff, flaps not coming all the way up automatically. I'm not sure if it has something to do with pitch, but it seems like if flaps are not fully up when vnav comes on I have to manually intervene otherwise our speed will never come fully up to where it is supposed to. This happens more on the 747 and 777, but has in the 737 as well. - The flaps are retracted based on Boeing flap recommendation card, which is based on your v2 speed. So, if the aircraft doesn't exceed a certain speed (e.g. v2+ 40), the flaps won't be retracted. At acceleration height, are you pitching down to increase the aircraft speed? Also - out of curiosity - how does FSFO account for changes in weather? E.g. I notice if there is precipitation the windshield whipers will come on before takeoff - but not on descent or approach. Is this normal or a bug? \ - FSFO can detect partipiation and intensity during both the after start and approach flows. I'll check to see why it's not happening in the latter. This feature will be discontinued for V3 though... I'm also aware this is pretty low on the list of issues but something I noticed last night while flying into BIKF and active sky was listing there to be moderate to heavy rain and thunderstorms in the vicinity on the approach. This was the first time I have had this happen so was just curious. Does FSFO also account for needing antiice on descent? Still not sure how that works and am making sure I have all my ducks in a row for the winter flying. - Yes, FSFO can detect anti-ice conditions and turn on your ice systems; however, because 777 and 747 have auto system, he only does it for the 737. Hello! I am - though I do have vnav set to activate a bit earlier, and always thought that when autopilot was active, I could not use any manual flight control so as not to disengage it? So it is okay to pitch the nose down somewhat to increase speed despite autopilot being active? Why is this precipitation feature being discontinued in v3, out of curiosity? Too much work to keep up with it? Excellent to know re: 747 and 777. Will anti ice being engaged automatically make the engine idle on descent increase on these two planes as well? thanks! |
|
