Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hi, 
I am running the latest version of FSUIPC 7.3.16 but when i try to use the JF BAE 146 there is no throttle. If I go into FSUIPC it is detecting a throttle input ( on 1 0f 11 : Main Controls) and it is set to Direct input. Other inputs from my saitek work, such as rudder and flaps.

If I change my controls to MSFS assigned, then the throttles work.

I can use FSUIPC assignments with other aircraft, just not the BAE 146

 

thanks

FSUIPC7.ini

Posted

You need to assign to the THROTTLEn_AXIS_SET_EX1 controls for the JF BAE 146 - see 

 

You should create a specific profile for this aircraft, import your current axis assignments and then switch the throttle to assign with 'Send to FS as normal axis' and then select the appropriate throttle _EX1 control. If you also need to reverse, scale by -1 as shown in that post.

John

Posted

Hi John

I tried to follow the instructions to create the new profile, but I seem to have got myself into a bit of a tangled mess. I cannot see where I am supposed to add the second throttle line in the .ini file, as mine only has one (shown as line 3) - even though I added two throttle lines onto the Axis Assignment tab

Before Changes

0=AX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
1=AY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
2=AZ,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
3=AU,256,D,4,0,0,0    -{ DIRECT: Throttle }-
4=AV,256,D,23,0,0,0    -{ DIRECT: Flaps }-

 

After adding BAE-146 profile and adding two throttle assignments:

 

[Axes.FSUIPC]
RangeRepeatRate=10
0=AX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
1=AY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
2=AZ,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
3=AU,256,D,4,0,0,0    -{ DIRECT: Throttle }-
4=AV,256,D,23,0,0,0    -{ DIRECT: Flaps }-
5=CX,256,D,21,0,0,0    -{ DIRECT: ElevatorTrim }-
6=DX,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
7=DY,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
8=DR,256,D,3,0,0,0    -{ DIRECT: Rudder }-

[Buttons.FSUIPC]
0=PA,32,C65734,0     -{PAN_UP}-
1=PA,38,C65671,0     -{PAN_LEFT}-
[Profile.Bae-146 Professional]
1=Whopperators JF 146-100 Flybe Old
[Buttons.Bae-146 Professional]
0=PA,32,C65734,0     -{PAN_UP}-
1=PA,38,C65671,0     -{PAN_LEFT}-
[Axes.Bae-146 Professional]
RangeRepeatRate=10
0=AX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
1=AY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
2=AZ,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
3=AU,256,F,67096,67110,0,0    -{ TO SIM: THROTTLE_AXIS_SET_EX1, THROTTLE2_AXIS_SET_EX1 }-
4=CX,256,D,21,0,0,0    -{ DIRECT: ElevatorTrim }-
5=DX,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
6=DY,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
7=DR,256,D,3,0,0,0    -{ DIRECT: Rudder }-
 

 

 

Posted
On 2/5/2023 at 1:16 PM, chickster25 said:

I cannot see where I am supposed to add the second throttle line in the .ini file, as mine only has one (shown as line 3) - even though I added two throttle lines onto the Axis Assignment tab

You have assigned a single axis to  THROTTLE_AXIS_SET_EX1 and THROTTLE2_AXIS_SET_EX1. This is not correct - either assign to THROTTLE_AXIS_SET_EX1 only, or assign to both THROTTLE1_AXIS_SET_EX1 and THROTTLE2_AXIS_SET_EX1.

The assignments in the referenced post were for using two separate throttle axes, one for throttle1 and one for throttle2. If you are only using one axis, you will only have one assignment.

Not sure why you have an FSUIPC profile called FSUIPC - you should change this or remove it.

On 2/5/2023 at 1:16 PM, chickster25 said:

[Profile.Bae-146 Professional]
1=Whopperators JF 146-100 Flybe Old

Change this to

Quote

[Profile.Bae-146 Professional]
1=JF 146-100

This will catch more variants, i.e. when using other liveries.

Any further issues, please attach your full FSUIPC7.ini file rather than pasting extracts.

Thanks,

John

Posted

Hi John

Thank you for your help with this. I have made the amends as you recommended and it is working, although I did not change the profile name from FSUIPC as its taken me months to get it all set up and I dont want to lose what I have configured so far. I also have two questions if you have time

1. For the Bae-146, the rudder does not work first time, unless I jump out of MSFS and open FSUIPC to detect the rudder on the Axes Assignment, then I can go back into MSFS and its working

2. I have attempted to load the variants for the BAE -146, but I am not sure if I have added them correctly via the same profile?

[Profile.Bae-146 Professional]
1=JF 146-100
2=JF 146-200
3=JF 146-300

 

Thanks for your assistance

FSUIPC7.ini

Posted
12 hours ago, chickster25 said:

1. For the Bae-146, the rudder does not work first time, unless I jump out of MSFS and open FSUIPC to detect the rudder on the Axes Assignment, then I can go back into MSFS and its working

That is strange... Can you show me a log file please, with logging for Axes Controls activated. Start MSFS / FSUIPC7 and activate logging for Axes Controls and also open the logging console window, load your aircraft and then move the rudder through its full range. Do you see any rudder event logged in the console? Then go into the Axes Assignments panel and detect the rudder, close and move the rudder again. Do you then see the rudder events logged? Exit FSUIPC7 and attach your FSUIPC7.log file and I will take a look.

12 hours ago, chickster25 said:

2. I have attempted to load the variants for the BAE -146, but I am not sure if I have added them correctly via the same profile?

[Profile.Bae-146 Professional]
1=JF 146-100
2=JF 146-200
3=JF 146-300

Simpler to just use:

Quote

[Profile.Bae-146 Professional]
1=JF 146

John

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.