TszChun.Anson

Thanks for your reminder. I will soon have another test flight, hopefully the problem can reoccur then for our diagnosis. Anson

Dear Pete, Just completed another test flight with same route and configs as previous, but unfortunately the issue of uncommanded fuel cut-off could be replicated. This was the first successful flight which I don't know why...Anyway, I have attached the log here and would be very thankful if you could help check whether there are something suspicious. Anson FSUIPC5.ini FSUIPC5.JoyScan.csv FSUIPC5.log

Thanks for your correction. Indeed I use ASP4 not AS16. I will further investigate the loadings, but maybe after I solve the in-flight fuel cut-off issue since they seem not related. Anyway thanks for reminding me about that. What I am going to do, is to enable the loggings and clear the assignments of locking toggle switches which involve “when released...” command. As far as I notice, the landing gear lever and fuel cut-off switch which both moved at the exact moment of the issue (2:48:08 of my Youtube video recording) were assigned with such “when released...” command. Particularly, if the physical toggle I assigned for gear lever is flipped up, it is detected by PC as a button-holding and FSUIPC will send the command of gear up (but I set control not to be held so that it will not repeat the gear up command endlessly). Then, if the toogle is flipped down, it is detected by PC as a button-release and FSUIPC will send the command of GEAR DN. At 2:48:08, for some reason the landing gear lever was set down then up, I suspect that it related to such kind of control assignment. Maybe the toogle has been detected as released? Sorry that my explanation may be confusing. Anson

Thanks for your help. I have never paid attention to the loading of WX.pln. However, is it possible that the action was stuff relevant to the weather up-/downlink coordination between Active Sky 16 and PMDG 777? I did type this post with the problematic sim paused (if I remember it correctly). I will enable the loggings you suggested and report back. Thanks very much for your advice. Anson

For your easy reference, this MIGHT be the relevant lines as when issue occurred the fuel control switches and gear lever moved themselves without my input: 13=PT,24,C70153,0 -{Custom control: <70153>}- 14=UT,24,C70153,1 -{Custom control: <70153>}- 15=PT,23,C70152,0 -{Custom control: <70152>}- 16=UT,23,C70152,1 -{Custom control: <70152>}- 5=PT,19,C66079,0 -{GEAR_UP}- 6=UT,19,C66080,0 -{GEAR_DOWN}- P.S. 70152 and 70153 are the event IDs of left and right engine fuel control switches respectively; 0 and 1 are the parameters of start and shutdown respectively.

Dear Pete, I am glad that my issue of unexpected in-flight engine shut-down can now be replicated. I would be very thankful if you could diagnose with me. https://youtu.be/LX_BNFEjzME?t=4681 As you can see, when the plane was cruising, suddenly without my control the two fuel control switches switched themselves OFF. Also, I didn't know why the landing gear lever also attempted to switch itself to DN position but bounced back. Based upon this observation, I suspect that I did something wrong in my control assignment. Particularly, the two buttons on my Thrustmaster warthog throttle unit that I had assigned to fuel control switches are both "on-off button", which means that it was ON and HELD when it was flipped UP while OFF when flipped down. Therefore I assigned the buttons, when released, will send the command of switching the fuel control switches to OFF. I know it is very hard to understand, so I have attached my FSUIPC config file for your reference. Please take a look at the assignments of fuel control switches (event ID 70152 & 70153) and landing gear lever. Thanks very much. Anson FSUIPC5.ini FSUIPC5.JoyScan.csv FSUIPC5.log

Thanks for your clarification. One more thing I would like to know is that, should the selection between rawinput and directinput matters for FSUIPC? Anson

Dear Pete, Greetings! I am writing to consult about the letters for joystick devices. As far as I understand, with AutoAssignLetters=No, if I manually change the numbers to meaningful letters (e.g. from 0 to T for throttle) under [Joynames] section and start the sim again, FSUIPC will adjust itself and eventually the buttons and axes sections of different aircraft profiles will be using those letters set instead of numbers. However, I just realise that the profiles of some aircrafts are not using the letters that I set but the original numbers even though I have already restarted the sim for the sake of auto adjustment of FSUIPC, like while The reason I check the files and realise this is that, when I fly PMDG 777 today, the aircraft suddenly lose all power while no failures are armed or set previously. Having consulted PMDG, I was told that having mixture control set even for other aircrafts with separate profiles MAY need to the issue. In my case, controls are intentionally separated between individual aircrafts (i.e. checking the box "profile specific" in FSUIPC. I do have a physical slider assigned for both PMDG 777's spoiler and C172's mixture control but in separate profiles. May I know if PMDG's interpretation is reasonable from FSUIPC's point of view? Will assignments in separate control profiles occasionally affect each other? Regards, Anson FSUIPC5.ini

Dear NixDevelopment, Greetings! I am writing to consult about the update method of the TOPER 777 program. I downloaded and installed the .exe from SimMarket, the version was v3.0.4. As I know there is an update available from your support forum, I tried to install the update v3.3.13. An error popped out "Previous version of TOPER 777 already installed......Please run TOPER uninstaller to remove previous version...". However, actually I had tried to run the update file BEFORE I run the installer from SimMarket, but it stated "No TOPER installation found". May I know the correct way to update the program? Best Regards, Anson

Oh! I got it. Thanks very much Pete. Anson

Dear Pete, Recently my throttle unit does not work properly therefore I need to do a RMA and get another unit from the vendor. May I know if the GUID of the new unit will be different from my current one provided that they are both the same model? This is my concern because I am not sure whether I should delete all the corresponding assignments and the entry in [Joynames] section as a good practice (according to user guide, users are advised to manually delete unused entries in that section). If I have to delete the entries, should I just go to FSUIPC options in the sim and delete the assignment one-by-one? Or is there any faster way to do it? Thanks very much for support. Anson

https://youtu.be/Y5ITGr4NMRo This is a short video showing the issue. Hope this helps! Note that at the beginning of the video, actually I did physically moved the yoke but as you can see nothing happened. Anson

Dear Pete, I'm sorry that the issue still persists. This time the yoke did not respond although it seemed to be correctly detected according to the csv and ini files. They were extracted and uploaded to here immediately after I noticed the problem (P3D still running). Y, x1E, x06A3, x0763, Flight Rudder Pedals, 4, 4, 0, {AF48AE50-3E72-11E8-8006-444553540000}, {AF48AE50-3E72-11E8-8006-444553540000}, {AF48AE50-3E72-11E8-8006-444553540000}, Y, Y Y, x1E, x12DA, x0920, Plasma-MM2, 5, 5, 0, {AF48AE50-3E72-11E8-800A-444553540000}, {AF48AE50-3E72-11E8-800A-444553540000}, {AF48AE50-3E72-11E8-800A-444553540000}, Y, Y N, x11, x12DA, x0920, Plasma-MM2, -1, -1, 1, {NULL}, {AF4AF840-3E72-11E8-8011-444553540000}, {NULL}, N, N Y, x1E, x044F, x0404, Throttle - HOTAS Warthog, 2, 2, 0, {AF48AE50-3E72-11E8-800B-444553540000}, {AF48AE50-3E72-11E8-800B-444553540000}, {AF48AE50-3E72-11E8-800B-444553540000}, Y, Y Y, x1E, x0738, x2215, Saitek Pro Flight X-55 Rhino Stick, 3, 3, 1, {AF48AE50-3E72-11E8-800C-444553540000}, {AF48AE50-3E72-11E8-800C-444553540000}, {AF48AE50-3E72-11E8-800C-444553540000}, Y, Y N, x11, x0738, x2215, Saitek Pro Flight X-55 Rhino Stick, -1, -1, 0, {NULL}, {AF48AE50-3E72-11E8-8005-444553540000}, {NULL}, N, N FSUIPC5.ini FSUIPC5.JoyScan.csv FSUIPC5.log

Thanks very much Pete! I followed your advice to modify the ini file. The lines seems ok now and so far the yoke works perfectly. I will continue to see whether the issue exist. Anson FSUIPC5.ini FSUIPC5.JoyScan.csv FSUIPC5.log

Sorry for my misleading words. I mean, AFTER closing P3D in step 3, should I change (again) the letters of Plasma MM2 and Rudder Pedals to a different numbers (like 4 and 5). I thought that step 1 have already prevented the numerical IDs from overlapping. Thanks. Anson

Just to confirm I understand right... 1. Manually change the numbers to letters in ini file like your example 2. Start P3D to let FSUIPC automatically adjust itself 3. Close P3D. Then manually change the letters of Plasma MM2 and Rudder Pedals to a different numbers (like 4 and 5) May I confirm that in step 1 I don’t need to set AutoAssignLetters=Yes if I choose to manually change the numbers to meaningful letters? May I know why step 3 is needed? Step 1 that changed the IDs to letters should have already avoided overlapping 0 and 1? Thanks very much! Anson

FSUIPC5.ini

Yes, the CSV and log I uploaded EARLIER were extracted when my yoke was NOT USABLE. The files I uploaded LATER was when my yoke DIDN'T HAVE THE ISSUE (after I restarted P3D). The issue seems happening randomly. Most often the yoke will be normal and responding properly. But about 1/5 chance of starting P3D with an problematic yoke. Not yet but I will. They are famous for their responsive customer service... Anson

I just started P3D again and extracted the csv and log files out immediately after P3D main page was loaded. I noticed a few major difference, the ID did not overlap anymore. Y, x1E, x06A3, x0763, Flight Rudder Pedals, 0, 0, 0, {AF48AE50-3E72-11E8-8006-444553540000}, {AF48AE50-3E72-11E8-8006-444553540000}, {AF48AE50-3E72-11E8-8006-444553540000}, Y, Y Y, x1E, x12DA, x0920, Plasma-MM2, 1, 1, 0, {NULL}, {AF48AE50-3E72-11E8-800A-444553540000}, {AF48AE50-3E72-11E8-800A-444553540000}, Y, Y N, x11, x12DA, x0920, Plasma-MM2, -1, -1, 1, {NULL}, {AF4AF840-3E72-11E8-8011-444553540000}, {NULL}, N, N Y, x1E, x044F, x0404, Throttle - HOTAS Warthog, 2, 2, 0, {AF48AE50-3E72-11E8-800B-444553540000}, {AF48AE50-3E72-11E8-800B-444553540000}, {AF48AE50-3E72-11E8-800B-444553540000}, Y, Y Y, x1E, x0738, x2215, Saitek Pro Flight X-55 Rhino Stick, 3, 3, 1, {AF48AE50-3E72-11E8-800C-444553540000}, {AF48AE50-3E72-11E8-800C-444553540000}, {AF48AE50-3E72-11E8-800C-444553540000}, Y, Y N, x11, x0738, x2215, Saitek Pro Flight X-55 Rhino Stick, -1, -1, 0, {NULL}, {AF48AE50-3E72-11E8-8005-444553540000}, {NULL}, N, N Then I loaded into flight and found that the yoke was usable. What makes me puzzled is why the result differs everytime I started P3D... Anson FSUIPC5.log FSUIPC5.JoyScan.csv

There is no overlapping ID found in Joynames section. However it seems strange that none of the devices are assigned ID=1... [JoyNames] AutoAssignLetters=No 2=Throttle - HOTAS Warthog 2.GUID={AF48AE50-3E72-11E8-800B-444553540000} 3=Saitek Pro Flight X-55 Rhino Stick 3.GUID={AF48AE50-3E72-11E8-800C-444553540000} 0=Plasma-MM2 0.GUID={AF48AE50-3E72-11E8-8006-444553540000} Sorry I cannot fully understand what you mean by "Odd that one of the non-joystick accesses to the Plasma-MM2 has been assigned ID=1 in the Registry.". You mean the the rudder pedals are having the same ID with Plasma-MM2? Anson

This was because I tried to disconnect and reconnect the yoke to see whether the yoke could resume normal without restarting P3D. The device is plug-and-play. No software was provided by the vendor. Yes! I have already disabled USB power management in both Windows High Performance power plan (the one activated) and device manager (each device available). Under the section "Joystick Device Scan", there was "125 Product= <not readable at this time: maybe device disconnected?>" shown, which was indicating that my yoke was not readable. However my yoke was actually physically connected and detected by Windows (shown in Windows Device Manager and Game Controller Setting). Is this providing us some clue? Also, is the following log may suggesting an ID overlapping issue? 2455219 Device acquired for use: 2455219 Joystick ID = 0 (Registry okay) 2455219 0=Flight Rudder Pedals 2455219 0.GUID={AF48AE50-3E72-11E8-8006-444553540000} 2455219 Device acquired for use: 2455219 Joystick ID = 0 (Registry okay) 2455219 0=Plasma-MM2 2455219 0.GUID={AF48AE50-3E72-11E8-8006-444553540000} Anson

Dear Pete, I really hope that you could help! I have experienced this issue so many times. After I loaded into a flight in P3D, my ACE yoke was not usable. The strangest thing was that, the yoke resumed normal every time after I restarted P3D. Once I noticed the yoke was not usable, I immediately opened the FSUIPC log file to see whether my yoke was recognised, and the answer was yes - the yoke (Plasma MM2) was successfully detected by FSUIPC and listed under Device acquired for use section. After that I tried reconnect the yoke a few times but it was still not usable. Please help me! I was very tired and did not want to experience this anymore. Thank you very much. Best Regards, Anson FSUIPC5.log FSUIPC5.JoyScan.csv

Thank you very much! Yes you are right. Of course! They are attached to this comment. It was set to Raw Input. Should I check the other one instead? https://youtu.be/HelcGmMwwmw This is a short screen recording demonstrating the issue. 0:14 is the moment when I moved the yoke but not well-detected. 0:56 is when I moved the yoke but not detected by the axis assignment page. Interestingly, 1:00 is when I moved the yoke and the movements of axes were detected, but in a strange way. In particular, the changes in numbers shown were exceptionally gradual, slowed and delayed. I suspect that this is caused by the lack of driver tuned by the yoke manufacturer. Without calibration via either Windows or P3D setting, the range of axes' parameters are not well-defined which may lead to FSUIPC's failure to detect the yoke. Actually I thought I could directly do all calibration and axis assignment work via FSUIPC, could you please clarify if I misunderstand how it work? I hope this can help you understand more about the issue. Anson FSUIPC5.ini FSUIPC5.JoyScan.csv FSUIPC5.log

Hi, Still struggling to get the axes detected, appreciate if you could help :) Anson

Yes you are right. The other detected devices are showing values properly. The buttons on my new yoke are properly detected as well. Anson