Jump to content
The simFlight Network Forums

FSUIPC Upgrade from v5 to v6 oddity. Need Help Please


Recommended Posts

I just upgraded from FSUIC5 to FSUIPC6. I copied the FSUIPC5.ini to FSUIPC6.ini. Rebooted.

First flight, flying "Flight1 Beechcraft KingAir B200".

Parking Brake control IS programmed in a specific profile to this aircraft. I can see it in the FSUIPC config buttons window..  However, it no longer works. What's more is when I select that button to program it I can not select a replacement command; the dropdown does not work.  If I exit the FSUIPC interface and reenter I can select any other push button or switch on the same controller (TM HOTAS Warthog) and FSUIPC works fine.  For some reason this ONE BUTTON registers in FSUIPC which describes it as set for command "Parking Brake", but FSUIPC not only does NOT perform the "Parking Brake" function, but it will not display the dropdown to even let me select another command.

That you for the help.

 

ETA
I did reboot and restart everything a few times and always the same issue. I have flown this aircraft a lot the past week and it was working just fine under FSUIPC5.

P3D V4.5/ Windows 7 XP1 (soon upgrading to Win10/P3D v5)

Edited by ArJuna
Link to comment
Share on other sites

Here is the relevant (bold) portion of the Module file for that aircraft "KingAir B200.ini"

 

[Profile]
Created=07/04/2019 20:53:40

[Buttons]
PollInterval=25
ButtonRepeat=20,10
3=PB,32,C66056,0     -{PANEL_LIGHTS_ON}-
4=RB,36,C66057,0     -{PANEL_LIGHTS_OFF}-
5=RB,34,C65879,0     -{HEADING_BUG_INC}-
6=RB,38,C65880,0     -{HEADING_BUG_DEC}-
11=RA,30,K113,8     -{Key press: F2}-
12=UA,30,K114,8     -{Key press: F3}-
13=PD,25,C65580,0     -{AP_MASTER}-
15=PD,21,C65597,0     -{FLAPS_1}-
16=UD,21,C65599,0     -{FLAPS_2}-
17=PD,22,C65601,0     -{FLAPS_3}-
18=UD,22,C65599,0     -{FLAPS_2}-
19=PD,6,C65752,0     -{PARKING_BRAKES}-
20=UD,6,C65752,0     -{PARKING_BRAKES}-

Link to comment
Share on other sites

11 hours ago, ArJuna said:

For some reason this ONE BUTTON registers in FSUIPC which describes it as set for command "Parking Brake", but FSUIPC not only does NOT perform the "Parking Brake" function, but it will not display the dropdown to even let me select another command.

This indicates that the button is either overloaded, or there is a compound or offset condition in the button press. Activate logging for Buttons & Keys, open the logging console and see what is logged when the button is pressed - that should give you some idea.
Also, check that aircraft name is in your profile - use substring matching in profiles or when you use an aircraft with a different livery it may not match your profile.

But I am now on holiday until Monday 19th. If you are still having issues, post your FSUIPC6.ini as well as your FSUIPC6.log file with logging for Buttons & Keys added as well as Events and I'll take a look when I return.

There really should be no such issues switching from FSUIPC5 to FSUIPC6...

Link to comment
Share on other sites

The Parking Brake control is a "Toggle" control.   

19=PD,6,C65752,0     -{PARKING_BRAKES}-
20=UD,6,C65752,0     -{PARKING_BRAKES}-

You are essentially toggling the parking brake ON then immediately OFF as you release the key.  Remove the line 20=UD,6,C65752,0  and it will work as desired.

 

Link to comment
Share on other sites

On 9/11/2022 at 12:37 PM, Donovan said:

The Parking Brake control is a "Toggle" control.   

19=PD,6,C65752,0     -{PARKING_BRAKES}-
20=UD,6,C65752,0     -{PARKING_BRAKES}-

You are essentially toggling the parking brake ON then immediately OFF as you release the key.  Remove the line 20=UD,6,C65752,0  and it will work a desired.

 

Thank you, but that is intentional and correct. The switch is a three position with one side being momentary and the other locks. I use one to lock the parking brakes ON and the momentary one to reset the position if out of sync.  I keep intending to write a LUA script to get past the simple toggle "Parking brakes".  You are also not seeing but a small part of the file.

Here you can see the other side of the rocker:

19=PD,6,C65752,0     -{PARKING_BRAKES}-
20=UD,6,C65752,0     -{PARKING_BRAKES}-
21=RD,7,C65588,0     -{PARKING_BRAKES}-

It has worked great for me for years.  I only had trouble when I upgraded to ver 6 and ONLY with the one aircraft.  I have not yet had time to fully sort it out.

 

Cheers

KingAir B200.ini

Link to comment
Share on other sites

Your ini shows multiple assignments, which is why they are grayed-out in the assignments tab:

Quote

...
19=PD,6,C65752,0     -{PARKING_BRAKES}-
20=UD,6,C65752,0     -{PARKING_BRAKES}-
...
76=PD,6,C65752,0     -{PARKING_BRAKES}-
77=UD,6,C65752,0     -{PARKING_BRAKES}-
78=PD,7,C65752,0     -{PARKING_BRAKES}-
 

So when you press button 6, assignments 19 and 76 are triggered, so toggles twice resulting in the same state. and when you release, assignments 20 and 77 are triggered, again two toggles resulting in no change to the parking brake state.

On 9/14/2022 at 7:57 AM, ArJuna said:

Here you can see the other side of the rocker:

19=PD,6,C65752,0     -{PARKING_BRAKES}-
20=UD,6,C65752,0     -{PARKING_BRAKES}-
21=RD,7,C65588,0     -{PARKING_BRAKES}-

It has worked great for me for years. 

But I don't see how this could have worked with FSUIPC5, as the assignments are still the same.

You can always set logging for Buttons & Keys as well as Events, open the logging console and you can see what is being sent when you press or release the button in real-time. This should tell you what is going on.

Note that as you have overloaded/multiple assignments, you will have to adjust/remove these by editing the ini file directly rather than using the button assignments panel.

John

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.