Possible FSUIPC6 Issue

[beechcaptain]

I have an ongoing problem in P3Dv5.3.17.28160 with all of my addon jetliner aircraft.  After engine startup and commencing taxi to departure runway, the aircraft's engine generators get tripped (go offline) and the systems all shut down.  Note:  I do not have any failures turned on in PMDG a/c or P3D Vehicles sub menu sections.  Fortunately, with the PMDG 737NGXu a/c, probably because the 737 systems don't draw as much juice, if I immediately reset the engine generators, power & systems are restored.  I only have to reset yaw damper, autobrake and efb and then can continue taxi and complete my flight.  I can't reset the engine gens to restore everything in the Quality Wings 787 and Captain Sim 757/767 aircraft.  With those, it's flight over.

Someone on the Avsim P3D forums suggested deleting my FSUIPC.ini and letting it regenerate after starting P3D.  I did so and it seems to have worked, but only able to test once thus far.  Can do another test flight tomorrow morning.

Here is the before deletion FSUIPC.log from the previous flight in the PMDG 738NGXu that had the issue:  https://www.mediafire.com/file/732t9bpnd8lnnvw/FSUIPC6.log/file

Here is the rebuilt FSUIPC's log from my latest, successful test flight in the PMDG 738NGXu: https://www.mediafire.com/file/v6r34189y57iw34/FSUIPC_20231103.log/file

Can someone with in-depth knowledge of FSUIPC log data translate what was happening in the older log?  It definitely shows some issues, imho and perhaps one or more of those events caused the loss of power/generators to trip.  The latest rebuilt FSUIPC.ini's log file from the latest test was very clean, so I'm assuming whatever hiccup that was encountered by FSUIPC in the past is now gone.

Kindest regards,

Glenn W. / beechcaptain

Edited November 3, 2023 by beechcaptain
corrected file name error

[John Dowson]

31 minutes ago, beechcaptain said:

Someone on the Avsim P3D forums suggested deleting my FSUIPC.log and letting it regenerate after starting P3D.  I did so and it seems to have worked, but only able to test once thus far.  Can do another test flight tomorrow morning.

This cannot possibly have any effect whatsoever. It is just a log file, and is cleared/newly generated each time FSUIPC/P3D is ran.

34 minutes ago, beechcaptain said:

Can someone with in-depth knowledge of FSUIPC log data translate what was happening in the older log?  It definitely shows some issues, imho and perhaps one or more of those events caused the loss of power/generators to trip. 

That is a huge log file and I am certainly not going to go through that in detail, especially as you are using many Rotor Brake/Custom controls. What issues does it "definitely show"? Looks ok to me, on a quick scan.

36 minutes ago, beechcaptain said:

The latest rebuilt FSUIPC.ini's log file from the latest test was very clean

The difference between the two log files is that in the first one you had logging for Events (non-axes controls) activated, and in the second one not:

Quote

      156 LogOptions=20000000 00000001
vs
      156 LogOptions=00000000 00000001

I don't think this is an issue with FSUIPC, but you could possibly be accidentally triggering an assignment that is doing this. To narrow this down, you can use Event logging, with the logging console window open, and see what events are logged at the time, and just before, your issue occurs. Then track down where that event is originating,

John

[beechcaptain]

I meant to say deleting my FSUIPC.ini instead of .log.

I'll try that with the logging console window open and see what happens.

Thanks.

 

 

[beechcaptain]

I ran a short test with logging console window open and kept getting 2 events frequently:

EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE

EVENT: Cntrl= 66734 (0x000104ae), Param= 1 (0x00000001) MOUSE_LOOK_TOGGLE

I have the mouse look active so I understand that event will occur every time I use the mouse to look around within the sim.  However, I'm puzzled about the Rotor Brake event.  I wasn't doing much in the aircraft (PMDG 737-800 NGXu), sitting on the runway, engines running, parking brake set.  I was going through the FMC looking for any item that might have shft+B (Rotor Brake) assigned but found none.  I also verified that Rotor Brake shft+B was not checked in the P3D Controls, Key assignment section.  I also looked in my FSUIPC aircraft profile that I previously created for jet aircraft and did not find anything for shft+B or 66587.  I also did not find it in the FSUIPC.ini either.  Are there any other files I should check for this?

I did not touch my flight controls - joystick and throttle, so there were no hardware buttons pressed during this test.

After searching for ROTOR_BRAKE in the forum I believe "Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE" could be associated with the mouse & possible mouse look.  Would this be correct, and not a rogue assignment somewhere?

Thanks, 

Glenn

 

[John Dowson]

13 hours ago, beechcaptain said:

I meant to say deleting my FSUIPC.ini instead of .log.

Ah, ok. That would make a difference (such as de-activating the logging you had set), but I would be very surprised if anything in the ini could cause this issue. And if anything in the file had changed, then you must have done this via changing the settings in the UI (or editing directly). Doing this would also delete all your assignments, if you are using a registered version of FSUIPC6.

12 hours ago, beechcaptain said:

After searching for ROTOR_BRAKE in the forum I believe "Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE" could be associated with the mouse & possible mouse look.  Would this be correct, and not a rogue assignment somewhere?

The Rotor Brake control/event is one way to use the custom controls provided by the PMDG SDK. To understand how these work, see the following page: 

The parameter 97903 indicates a mouse-move event (03) on the following control:

Quote

#define EVT_HUD_STOW                                    (THIRD_PARTY_EVENT_ID_MIN + 979)    // 

So that event just looks like the mouse moving across the HUD, which is nothing to worry about, and is emitted by the aircraft.

[beechcaptain]

[quote]And if anything in the file had changed, then you must have done this via changing the settings in the UI (or editing directly). Doing this would also delete all your assignments, if you are using a registered version of FSUIPC6.[/quote]

Ah, yes I have directly edited the ini file.  I am a registered version user. 🙂

Thanks for your help.

Kindest regards,

Glenn

[beechcaptain]

Good news.  2 most recent flights, since deleting fsuipc.ini and letting it rebuild, I have not experienced any issues!  Nothing unusual showed up in the Events logging window.

Fingers crossed, hoping all is good from now on.  

Kindest regards,

Glenn

[John Dowson]

Ok, thanks for the update.

If you deleted the FSUIPC6.ini file, did you redo your settings/profiles/etc?
This seems such a drastic action to take, and I would never recommend this to fix in an issue (if this did indeed fix the issue, of which I am doubtful). Temporarily rename or moving it out of the installation folder for a test is ok though.

[beechcaptain]

Yes, I did redo my settings, et al.  Yes, I agree, it is drastic action taken on my part, but I did make a backup copy.  However, after two successful flights without incident, I just encountered the issue again on taxi after pushback.  Unfortunately, I forgot to turn the event logging window back on so I don't know what events took place.  I will fly another flight tomorrow and will keep events logging turned on.  I rechecked the current FSUIPC.ini and nothing had changed since it rebuilt two flights prior.

I'll report back after the next flight.

 

[beechcaptain]

John, would you mind reviewing my attached FSUIPC.ini file and see if there is anything unusual or potential problem causer?

Kindest regards,

Glenn

FSUIPC6.ini

[John Dowson]

Your ini is pretty empty and doesn't contain much - your settings will be in your Jet.ini file in your Profiles folder. All it tells me is that you are using an old and unsupported version of FSUIPC6 (6.1.9) and should update to the latest and only supported version (6.2.0).

You can clean your profile section, to catch more variants, by changing this:

Quote

[Profile.Jet]
1=PMDG 737-700NGX WestWind Winglets
2=PMDG 737-800NGXu BW Delta Air Lines (N399DA | 2016)
3=CS 757-26D Delta Air Lines 2018

to this:

Quote

[Profile.Jet]
1=PMDG 737-
2=CS 757

You should keep the event logging enabled for the time being (no need to keep the console window open), and when you experience this issue you can start a new log (from FSUIPC's logging tab) and then save the log containing the events that lead up to your issue. Once this has happened 2 or 3 rimes, you can then compare the logs to see if any of the logged events could cause this issue. This may be easier in the QW or Captain Sim, as with the PMDG you would also have to decode any custom and Rotor Brake controls to understand what is happening. 

 

[beechcaptain]

Oh, darn, I meant to check for latest version and forgot.  Let me update and then I'll keep the logging window active for all of my future flights and closely monitor so when the gremlin strikes again, hopefully the culprit will be detectable.

Thanks & kindest regards,

Glenn

[beechcaptain]

I almost forgot to ask, since my memory fails me sometimes (a lot according to my wife, ha, ha) can I install v6.2.0 over existing 6.1.9?  I assume so but want to be sure it's safe.  <--- I should have read the provided guide first, it answered my question.  Thanks.

& thanks for the tip on the profile listing format!

 

Glenn

[John Dowson]

14 hours ago, beechcaptain said:

I'll keep the logging window active for all of my future flights and closely monitor so when the gremlin strikes again, hopefully the culprit will be detectable.

As I said, you don't need to keep the logging window open, just keep the event logging active, and maybe also activate logging for Buttons & Keys. Then when you get your issue, immediately (i.e. before trying to recover from it or doing anything else) go into FSUIPC's logging tab and click the New Log button to start a new log file. Then find your FSUIPC6.1.log file and rename and save that somewhere. Once you have 3 or 4 of these log files, you  can examine them to see if you can see any similar events occurring just before you get the issue. You can also post/attach the log files here and I can take a look.

 

[beechcaptain]

I am happy to report the issue has been resolved.  I updated my P3Dv5.3 client to v5.4 and all is back to normal now.

 

[John Dowson]

14 hours ago, beechcaptain said:

I updated my P3Dv5.3 client to v5.4 and all is back to normal now.

Ok, very strange....I don't understand how that can solve your issue, unless your 5.3 client got corrupted somehow, but your symptoms were very strange if that was the case.

Thanks for the update.

John