|
|
Post by clive6354 on Feb 24, 2020 16:42:35 GMT -5
The APU restart time of 60 seconds is another area that I failed to highlight. It would be interesting to know what test platform was used to test this program before release as so many errors makes the program unusable. I hope that observations raised will be resolved sooner than later as a program has been purchased that is unusable and in its present state a refund should be given automatically
As a matter of interest I have tried this program using the 737 NGX and NGXu, thinking that maybe there was a difference between the two, however trying the progam out with the NGX and NGXu gave the same results
|
|
|
|
Post by Matthew King on Feb 26, 2020 1:09:15 GMT -5
Hi Matthew, just bought it yesterday and i have the same observations than Clive6354 regarding the switches and selectors with the PMDG NGXu. I am also wondering why after the APU start (take too long for me), i have an APU restart for 60 seconds. Would like to bring a little more feedback but I didn't go too far exploring it as in it's state right now, it is totally useless until fixed. I also have the PMDG 777 and the QW787. I still have to see how it works with these two. I also forgot to mention the Display Source selector should remain on AUTO instead of ALL ON 2. Setup here i9-9900K (5.0) RTX 2070S OC 2X NVMe 250g WD SSD 1TB HDD TrackIR Win10 P3D v4.5 fully upgraded ORBX PFPX FSiPanel 2017 Active Sky FlyTampa and Tropicalsim sceneries Navigraph subscription Hey backyardflyer! Concerning the APU start, FSFO doesn't control how long it takes the APU to start...he simply flips the switches. The time it takes to start is based on PMDG's internal parameters. The restart occurs when FSFO has detected the APU did not start correctly. I'll check again though. You're absolutely correct concerning the Display Source Selectors; I'll check to ensure it's set correctly. Also, am I understanding your correctly...the program is useless because it takes the APU too long to start, or are you having other significant problems not listed here? Just want to insure I'm tracking before fixing this weekend... |
|
|
|
Post by Matthew King on Feb 26, 2020 1:32:02 GMT -5
The APU restart time of 60 seconds is another area that I failed to highlight. It would be interesting to know what test platform was used to test this program before release as so many errors makes the program unusable. I hope that observations raised will be resolved sooner than later as a program has been purchased that is unusable and in its present state a refund should be given automatically
As a matter of interest I have tried this program using the 737 NGX and NGXu, thinking that maybe there was a difference between the two, however trying the progam out with the NGX and NGXu gave the same results
Problems need to be duplicated and understood before they can be fixed, clive. To date, only 2 of 400+ people have reported issues. I'm sure you can understand my perspective; by fixing your problems, I may inadvertently break something for the other hundreds. This isn't suggesting the problems won't be dealt with, they will! However, I'm cautious about making whole sale changes when the program is working well for others. Is it perfect? Heck no, I have literally thousands of line of code to accommodate 4 developers, 3 platforms and 7 add-on aircraft...I'm sure they're are mistakes. The program is only been out for 2 weeks; however, I plan to make your issue a priority this week. Also, have you verified your FSUIPC? Again, FSFO uses this to read your PMDG internal settings and may be why you're having some issues. |
|
|
|
Post by Matthew King on Feb 26, 2020 2:02:59 GMT -5
SUCCESS..that has worked. The application panel is how it should be Please would you now go through the problems I am experiencing with the First Officer setting switches and knobs incorrectly? The problems I am experiencing are all performed from a COLD & Dark setup. Your video explains the procedures correctly but for some reason the program is not performing correctly. I will list the items that I wish you to investigate When the GPU starts a message flags up in a bar at the top of my monitor "Problem detected with GPU" When the IRS is being set up, why are the switches set to ATT mode and not Align? Why are the packs not set correctly (configured for engine start) before the engine start procedure is commenced? When theFirst Officer begins his PRE FLIGHT FLOW. Why does he set No 1 engine start selector switch to GRD and No 2 to CONT. When the First officer is starting engine 2 the engine selector switch goes from CONT to OFF. The first officer continues oblivious that there is something wrong. After No 1 engine is selected to GRD the procedure continues with a message that both engines are stabilised. BOTH ENGINES ARE OFF and the packs were not set correctly. Would it be possible to amend the program so that it would not be possible for the First Officer to go through the process of starting the engines without the packs being set correctly? At the moment with the packs on I can instruct the First Officer to start engines and he will go through the process oblivious that the packs are not set correctly Clive, I was actually able to duplicate your exact problems by removing the EnableDataBroadcast line from the 737NGXu_Option.ini file. Once I removed said line, I experienced the exact problems you detailed above, including the Eng start problem. Can you please refer to page 21 of the FSFO manual and ensure your applicable PMDG aircraft are configured to allow third party programs to interact with them? |
|
|
|
Post by clive6354 on Feb 26, 2020 6:57:03 GMT -5
Hello Matthew
Success I have edited the 737NGXu_Option.ini file and all appears resolved, thankyou
I now realise that the problem was my own fault (red face) not editing the PMDG file after a PMDG update, I apologise for the inconvenience caused.
May I clarify a procedure when editing the ini file. Although you describe in the manual how to edit the file is it important that the additional lines are inserted in the exact position as shown
|
|
|
|
Post by Matthew King on Feb 26, 2020 11:14:52 GMT -5
Hello Matthew Success I have edited the 737NGXu_Option.ini file and all appears resolved, thankyou I now realise that the problem was my own fault (red face) not editing the PMDG file after a PMDG update, I apologise for the inconvenience caused. May I clarify a procedure when editing the ini file. Although you describe in the manual how to edit the file is it important that the additional lines are inserted in the exact position as shown No worries, sir! PMDG recommends putting the line at the end of the file; however, it shouldn’t matter where it’s placed. |
|
|
|
Post by clive6354 on Feb 26, 2020 16:32:46 GMT -5
Hi Matthew
I am currently watching and enjoying your video tutorial. When the First Officer manages system checks, I have an idea of a task that he could perform, however, it may be very complicated to program, however, this is my idea
During monitoring and system checks the First Officer also makes a note on the flight plan of time reached and fuel burn at each or specific waypoints. Would it be possible for the Flightplan (possibly created using Simbrief) to be exported into FSFO and actual time and fuel plan readings be entered onto the flight plan and then at the end of the flight have an option to print out the flight plan with the actual time and fuel burn figures included in the flight plan?
When using the simulator I wonder how many times this data is actually recorded on the Flightplan.
Clive
|
|
|
|
Post by Matthew King on Feb 26, 2020 23:47:14 GMT -5
Hi Matthew, I found what was the problem. I was still on FSUIPC 5.151. I installed 5.153 and now everything is working the way it should. In fact, it's beyond my expectations. Sorry that I told you it's useless but I was really upset that nothing was working as expected. May I suggest that you add to the manual what FSUIPC version is needed for P3D v4 and up . May I also suggest to turn the AC Selector to APU GEN when the APU in online. Will fly the B737 with my FO for a while and will get back if I have some more suggestions. I will try the 777 and the 787 this weekend. First, I'm glad you got it working! Concerning your suggestion, it was in the original document but I just realized the person who created a more professional product for me removed it; I'll ensure it's added back. |
|
