wawona Posted August 15, 2022 Report Posted August 15, 2022 Hello, I have noticed a climb performance problem on PMDG 737-700 MSFS2020 with running FSUIPC7. The problem is vertical speed and climb performance is very low after FL200. And at FL280 the aircraft is no more able to climb and maintain required airspeed. I made several flight sessions with the next results: 1. FSUIPC7 was running whole the flight - issue was there. Was not able to climb above 28000. 2. FSUIPC7 was NOT running (exit application) whole the flight. No issues was there. Climb performance is good. Climb to 38000 fast. 3. FSUIPC7 was running from the start of flight. At FL200 where climb perfomance issue happened I exit FSUIPC7 application. Then after 3 seconds vertical speed began to rise sharply. Then I re-launched FSUIPC7 application. Vertiacal speed was OK for the rest of the flight. I have to re-launch FSUIPC7 every flight after takeoff at climb phase for normal gaming. Tried with versions 7.3.7 and 7.3.8b with similar results. PMDG 737-700 is the latest version 3.00.0031. I had opened a support ticket with PMDG team and they suggested to ask FSUIPC team for investigation. Also I enabled events logging in the FSUIPC. When there was the issue (below FL200 with climb problem) - it was too much ROTOR_BRAKE events in the log. Almost whole the log has these ROTOR_BRAKE events: 1345968 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 38303 (0x0000959f) ROTOR_BRAKE 1346000 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 38303 (0x0000959f) ROTOR_BRAKE 1346062 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46503 (0x0000b5a7) ROTOR_BRAKE 1346343 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346359 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346375 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346406 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346422 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346453 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346468 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346500 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346531 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346562 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346593 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346625 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346656 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346687 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346703 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346718 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1346750 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1346797 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1346812 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1346843 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1346859 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1346953 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46301 (0x0000b4dd) ROTOR_BRAKE 1347031 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46304 (0x0000b4e0) ROTOR_BRAKE 1347047 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1347078 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1347093 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1347125 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1347265 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 36603 (0x00008efb) ROTOR_BRAKE 1349156 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 34903 (0x00008857) ROTOR_BRAKE 1349312 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 33903 (0x0000846f) ROTOR_BRAKE 1349390 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37303 (0x000091b7) ROTOR_BRAKE 1349406 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37403 (0x0000921b) ROTOR_BRAKE 1349437 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37403 (0x0000921b) ROTOR_BRAKE 1349656 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE 1349672 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE 1349703 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE 1349718 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE 1349734 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE 1349765 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE 1349797 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37501 (0x0000927d) ROTOR_BRAKE 1349890 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37504 (0x00009280) ROTOR_BRAKE 1349906 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE 1349922 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE 1349953 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37403 (0x0000921b) ROTOR_BRAKE 1349984 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37203 (0x00009153) ROTOR_BRAKE 1350015 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 36003 (0x00008ca3) ROTOR_BRAKE 1350031 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 35703 (0x00008b77) ROTOR_BRAKE After exit and re-launch FSUIPC it was only two ROTOR_BRAKE events: 16141 4104 Starting WAPI... 16141 4104 [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 0.5.10 (WASM version 0.5.9) 16141 4104 [INFO]: Connected to MSFS 16172 4104 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 16219 29444 Lvars/Hvars received - checking aircraft autos.... 20766 4104 *** EVENT: Cntrl= 67226 (0x0001069a), Param= 0 (0x00000000) WINDSHIELD_DEICE_OFF 32172 4104 **** Thread 13604 created for PerfTimer 69391 4104 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 99003 (0x000182bb) ROTOR_BRAKE 69422 4104 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 99003 (0x000182bb) ROTOR_BRAKE 72938 4104 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE 72938 4104 EV_KEYDOWN received: 0x23 (#) 72938 4104 KEYDOWN: VK=35, Waiting=0, Repeat=N, lParam=0 (0x0), Shifts=0 72938 4104 .. KeyDown received from FS but not programmed 73031 4104 EV_KEYUP received: 0x23 (#) 73031 4104 KEYUP: VK=35, Waiting=0, Shifts=0, lparam=0 (0x0) 73031 4104 .. KeyUp received from FS but not programmed 97531 4104 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE 97531 4104 EV_KEYDOWN received: 0x23 (#) 97531 4104 KEYDOWN: VK=35, Waiting=0, Repeat=N, lParam=0 (0x0), Shifts=0 97531 4104 .. KeyDown received from FS but not programmed 97578 4104 EV_KEYUP received: 0x23 (#) 97578 4104 KEYUP: VK=35, Waiting=0, Shifts=0, lparam=0 (0x0) 97578 4104 .. KeyUp received from FS but not programmed 127094 4104 EV_KEYDOWN received: 0x1B () 127094 4104 KEYDOWN: VK=27, Waiting=0, Repeat=N, lParam=0 (0x0), Shifts=0 127094 4104 .. KeyDown received from FS but not programmed 127109 4104 *** EVENT: Cntrl= 66055 (0x00010207), Param= 1 (0x00000001) PAUSE_SET 129516 4104 Sim stopped: average frame rate for last 121 secs = 48.3 fps 129516 4104 Max AI traffic was 0 aircraft Thank you for support.
John Dowson Posted August 15, 2022 Report Posted August 15, 2022 What is sending those rotor brake commands? What else do you have running? Can you show me your FSUIPC7.ini file please, as well as attach your complete log (you can zip it if large). When you relaunch FSUIPC, the rotor brake control with parameter 99003 is just a mouse-move (3) for this control: #define EVT_ISFD_ATT_RST (THIRD_PARTY_EVENT_ID_MIN + 990) // When you have your issue, many different controls are being sent, most with a mouse move (3) command but also a click (1) and release (4): 15 minutes ago, wawona said: 1345968 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 38303 (0x0000959f) ROTOR_BRAKE - EVT_MCP_CO_SWITCH 1346000 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 38303 (0x0000959f) ROTOR_BRAKE - EVT_MCP_CO_SWITCH 1346062 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46503 (0x0000b5a7) ROTOR_BRAKE - EVT_MPM_SPEED_REFERENCE_CONTROL 1346343 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE - EVT_MPM_MFD_SYS_BUTTON 1346359 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE - 1346375 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346406 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346422 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346453 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346468 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346500 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346531 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346562 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346593 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346625 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346656 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346687 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346703 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE 1346718 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE - EVT_MPM_MFD_ENG_BUTTON 1346750 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1346797 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1346812 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1346843 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1346859 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1346953 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46301 (0x0000b4dd) ROTOR_BRAKE - EVT_MPM_MFD_ENG_BUTTON (left click) 1347031 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46304 (0x0000b4e0) ROTOR_BRAKE - EVT_MPM_MFD_ENG_BUTTON (left release) 1347047 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1347078 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1347093 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1347125 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE 1347265 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 36603 (0x00008efb) ROTOR_BRAKE - EVT_EFIS_CPT_BARO_IN_HPA 1349156 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 34903 (0x00008857) ROTOR_BRAKE - EVT_SYSTEM_ANNUNCIATOR_PANEL_LEFT 1349312 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 33903 (0x0000846f) ROTOR_BRAKE - EVT_DSP_CPT_AP_RESET_SWITCH 1349390 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37303 (0x000091b7) ROTOR_BRAKE - EVT_EFIS_CPT_DATA 1349406 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37403 (0x0000921b) ROTOR_BRAKE - EVT_EFIS_CPT_POS 1349437 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37403 (0x0000921b) ROTOR_BRAKE 1349656 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE - EVT_EFIS_CPT_TERR 1349672 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE 1349703 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE 1349718 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE 1349734 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE 1349765 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE 1349797 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37501 (0x0000927d) ROTOR_BRAKE 1349890 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37504 (0x00009280) ROTOR_BRAKE 1349906 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE 1349922 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE 1349953 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37403 (0x0000921b) ROTOR_BRAKE - EVT_EFIS_CPT_POS 1349984 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37203 (0x00009153) ROTOR_BRAKE - EVT_EFIS_CPT_ARPT 1350015 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 36003 (0x00008ca3) ROTOR_BRAKE - EVT_EFIS_CPT_MODE_CTR 1350031 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 35703 (0x00008b77) ROTOR_BRAKE - EVT_EFIS_CPT_MINIMUMS_RST You need to determine what is sending those commands. FSUIPC does not send anything unless asked, so I am not sure where those are coming from at the moment. John
wawona Posted August 15, 2022 Author Report Posted August 15, 2022 Hello John, I have a joystick, rudder pedals and a throttle quadrant with throttle, flaps, spoiler axises and a few buttons. No any 3rd party software installed. MSFS2020 steam version and PMDG 737-700 bought a week ago. Please take a look at ini attached. Compressed log file has 80kb size (1.3Mb befor compression). There is a limit 20kb total of attachment here. How is better to deliver log file? Thank you. FSUIPC7.ini
John Dowson Posted August 15, 2022 Report Posted August 15, 2022 You could try activating logging for Buttons & Keys as well, which would tell you if any of those control are being sent from a button press/release. Other than that, there are two things that stand-out in your ini file: 1. One of your controllers was not connected: Quote A=TCA Q-Eng 1&2 << MISSING JOYSTICK >> A.GUID={A371ECA0-79FA-11EC-8002-444553540000} ? 2. You have some controls being sent when your spoiler axes enters/leaves two distinct ranges: Quote 1=AR,1,D,22,0,0,0 -{ DIRECT: Spoilers }- 2=AR,B,6237,11736,4199503,0 -{ DIRECT: SpoilersEntering=Preset Control }- 3=AR,B,11884,16383,4199504,0 -{ Entering=Preset Control }- Can you check (using the UI axes assignment window) what these presets are that you have assigned to please and let me know? This actually shows an issue - the control numbers are being used here, where the preset name should really be used (as in your button assignments) as the actual control numbers for presets can change when the events.txt file is updated. Therefore please check that they are still assigned to the correct controls/presets. I will look into this. As for the log file, you could try emailing me the zipped log to jldowson@gmail.com Can you also check if you have any assignments in MSFS, or are you using an empty profile in MSFS for your controllers? John
John Dowson Posted August 15, 2022 Report Posted August 15, 2022 I see you also have lots of other logging activated....just log events and buttons & keys - turn the other logging options off. That should reduce the log file size. You can also provide a second log with Axes controls logged as well as Buttons & Keys (nothing else). John
wawona Posted August 16, 2022 Author Report Posted August 16, 2022 Hello John, Missing Joystick was because I'm not always connect throttle quadrant for test flight. Problem exists with as well as without joystick. I removed these two for test: 2=AR,B,6237,11736,4199503,0 -{ DIRECT: SpoilersEntering=Preset Control }- 3=AR,B,11884,16383,4199504,0 -{ Entering=Preset Control }- It was ARM Spoilers and Disarm Spoilers at specific position of spoiler axis. Doesn't help with climb problem. I set logging parameters as requested and sent log files to email. Joystick and throttle quadrant have custom profile in MSFS with non-assigned controls in MSFS that used by FSUIPC. No conficts there. Thank you.
John Dowson Posted August 16, 2022 Report Posted August 16, 2022 (edited) 9 hours ago, wawona said: It was ARM Spoilers and Disarm Spoilers at specific position of spoiler axis. Doesn't help with climb problem. Well, arming does no harm but climbing will certainly be affected of the spoilers are actually deployed... 9 hours ago, wawona said: I set logging parameters as requested and sent log files to email. It is difficult to determine what is happening when there are so many Rotor Brake/custom controls being sent... If VS is the issue, maybe the spoilers or flaps could be an issue. Could you remove all current logging, and do another test where you just log the spoiler and flap positions, and see if those change when you restart FSUIPC7 (they shouldn't!). Try logging the following four offsets, all as U32: 0BE0, 0BE4, 0BD4, 0BD8. Later: I'll see if I can reproduce this issue tomorrow... Edited August 16, 2022 by John Dowson Later added
John Dowson Posted August 17, 2022 Report Posted August 17, 2022 22 hours ago, John Dowson said: Try logging the following four offsets, all as U32: 0BE0, 0BE4, 0BD4, 0BD8. Also show me your FSUIPC7.ini when you show me this log... Note it is also not possible to send presets on entering/leaving axis ranges at the moment, so do not use that. I will correct this in the next beta release. If you still get issues, maybe worth temporarily removing the spoiler and flap assignments and calibration, to see if that makes any difference... John
wawona Posted August 17, 2022 Author Report Posted August 17, 2022 (edited) Hello John, I removed Spoiler and Flaps axises assignment and calibration. Also added offset logging only. Problem has been gone with these settings. ini and log is attached. Next I'm going to add Spoiler and Flaps settings back one by one and will check what exact axis do this problem. Thank you! Update1: Added spoilers axis. Everything works good. Going to return back Flaps settings. FSUIPC7_log_without_spoiler_and_flaps.zip FSUIPC7_log_with_spoilers_without_flaps.zip Edited August 17, 2022 by wawona Added test with Spoilers axis settings
wawona Posted August 17, 2022 Author Report Posted August 17, 2022 John, I returned back Flaps config and the problem is back. I checked that Flaps, Slots, Spoilers were retracted at that time. Then I exit FSUIPC and the problem was gone. I'll send you email with screenshots how problem looks like. Thank you. FSUIPC7_log_with_flaps_and_spoilers.zip
John Dowson Posted August 18, 2022 Report Posted August 18, 2022 17 hours ago, wawona said: I returned back Flaps config and the problem is back. Ok, then it is the flaps config that must be causing this issue,,, 17 hours ago, wawona said: I checked that Flaps, Slots, Spoilers were retracted at that time. How did you check this? You cannot rely on just the visuals to check this....it is quite possible that the visuals don't confirm to the actual flight model, which is why we need logging. The log file you attached doesn't contain any offset monitoring lines, even though the ini file shows you have added the offset monitoring that I suggested. I would expect each offset value to be logged at least once, with an initial value of 0. I see you have also assigned flaps to 'Send to FS as Normal axis' but have also calibrated. This has been known to cause issues with PMDG aircraft. Can you try two things: 1. Change your Flaps assignment to 'Direct to FSUIPC calibration' and see if that helps. 2. Use the flaps assignment as-is (i.e. 'Send to FS as normal axis'), but remove the calibration, i.e. remove the following lines from your FSUIPC7.ini: Quote FlapStarts=-16384,-14641,-12439,-7720,-4520,-1000,2533,5109,16000 Flaps=-16383,16384/16 FlapEnds=-16000,-14400,-12000,-5737,-4000,1000,3120,9521,16384 The next time this issue occurs, could you also perform and Add-ons->WASM->List Lvars before you exit FSUIPC7, and then again after you restart. I can then check the values of the *flaps* lvars. John
wawona Posted August 18, 2022 Author Report Posted August 18, 2022 Hello John, Quote 1. Change your Flaps assignment to 'Direct to FSUIPC calibration' and see if that helps. This helps me. And now it works like a charm. I've just bought a full license of FSUIPC. Thank you very much for helping to solve my problem.
John Dowson Posted August 19, 2022 Report Posted August 19, 2022 11 hours ago, wawona said: Quote 1. Change your Flaps assignment to 'Direct to FSUIPC calibration' and see if that helps. This helps me. And now it works like a charm. 👍 11 hours ago, wawona said: I've just bought a full license of FSUIPC. Thank you! And thanks for reporting back - happy flying! John
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now