manfredc3
March 25th, 2014, 21:42
I can only agree with what GipsyBaron has stated.
I have been using a registered version of FSUIPC for many years now, and could not imagine running a FSX without it. If you have more than just a keyboard and mouse to control your aircraft (like a yoke, joystick, throttle quadrant, or pedals), then having a registered version of FSUIPC is a must!
I have all my buttons, switches and axis for every airplane I fly assigned through FSUIPC and LUA (LINDA), using switch commands as well as mouse macro's.
I even wrote tutorials on how to use FSUIPC, focused on even the least experiences flight simmer.
It takes time and effort to get your assignments set up, but once done, it is such great experience to just flip a switch on your controller without touching your keyboard, or moving your mouse across the screen. It makes it all worth while.
I even ended up building me a switch panel, using a printboard from DesktopAvaitor.com, and switches from Radioshack, that controlled my lights, battery, avionics and nav/gps switch. THat switchbox I used for a few year, and a tear ago I decided to take the plunge and built my own cockpit.
In short, FSUIPC is a "must have" for anyone using flight simming controls for their simulator.
Daveroo
March 26th, 2014, 08:08
i dont comprehend the written word as well as most people..im ADHD/ADD ,im fine in chatrooms,and these forums,ect..but once i see a guide or instruction set like what comes with FSUIPC ( and yes ive used the paid version since way back in FS9)im overwhelmed and cant take in what ive read,,i even begin to feel panic'd inside..im not trying to make excuses but it is why i ask so many questions on the forums..that other people tend to take for granted ,i often see.."read the manual"...thats all good,bit im 51 and have struggled all my life with this,and it doesnt seem it will ever change.
that said..i wish someone would explain how the "nodes" work as described above...i use CH Products,yoke,peddles,and two throttle quadrants,im thinking of adding the saitek cessna trim wheel,and one of there switch boxes,,but id like to make my own using the same method as described above .but back to the nodes,,,,say ive assigned all my switches on the throttles and the buttons/switches on the yoke,how do you switch nodes,to use them again in a different setup?...
GypsyBaron
March 26th, 2014, 11:49
Daveroo, What I was talking about was Modes as opposed to 'nodes' :)
At 72 going on 73 I have a bit of a problem with my typing and my old eyes aren't what they used to be so
I usually have to use the + zoom function on PDF docs and Control + Mousewheel for Firefox browser docs.
Let me do some explaining here. Perhaps it will clarify things a bit and help others as well. Some of this
may seem complicated, and at first it is a bit of a task but once one has the method mastered, it is rather
simple to implement for any aircraft and expand upon the 'basics'.
First, with FSUIPC, I always 'check' the "Aircraft specific" box when making control assignments. That way the
assignments are unique to each platform based upon the contents of the "title=" entry in the aircraft.cfg file.
One thing I do is have the FSUIPC4.ini entry in the "General" section set as below:
//ShortAircraftNameOk=No default setting
ShortAircraftNameOk=Yes
(See Appendix 2, Page 54 of the FSUIPC for Advanced Users.pdf)
So, if I have entries for "title=Airbus A321 Paint2" and "title=Airbus A321 Paint4" in the "Airbus_A321" aircraft.cfg,
when I assign controls to the first "Paint2" aircraft and then edit the FSUIPC4.ini file (it is just a text file..use notepad)
to change the title of the entries from:
[Buttons.Airbus A321 Paint2]
to:
[Buttons.Airbus A321]
Those button assignments will apply to ALL aircraft whose "title=" entries start with "Airbus A321".
There are other methods (profiles) to do similar things but I started using this method years ago so stick with it.
Another thing I do is in the [JoyNames] section, I have this statement:
AutoAssignLetters=Yes
What this does is replace all the numerical controller designations with letter assignments.
The numerical assignments made by Windows CAN change when you move a controller to another
USB port or add a controller or even disconnect and reconnect a joystick. If this happens, ALL
of your assignments may no longer be valid as "Joy0" may now be "Joy2", etc.
The letter assignments are made by FSUIPC and are locked to the GUID of the controller, which does
NOT change. I always recommend that this option be used.
Here is what my JoyNames block looks like with the Letter and the Number assignments:
[JoyNames]
AutoAssignLetters=Yes
A=Saitek Pro Flight Quadrant
A.GUID={C2624D30-8952-11DF-8008-444553540000}
B=USB ADAPTOR
B.GUID={C2624D30-8952-11DF-8009-444553540000}
C=Saitek X45
C.GUID={C2624D30-8952-11DF-8006-444553540000}
D=Saitek Pro Flight Yoke
D.GUID={C2624D30-8952-11DF-8007-444553540000}
E=Logitech Dual Action
E.GUID={90BAE6A0-6D1A-11E0-8001-444553540000}
0=Saitek Pro Flight Quadrant
0.GUID={C2624D30-8952-11DF-8008-444553540000}
1=Saitek Pro Flight Yoke
1.GUID={C2624D30-8952-11DF-8007-444553540000}
4=Logitech Dual Action
4.GUID={90BAE6A0-6D1A-11E0-8001-444553540000}
3=Saitek X45
3.GUID={C2624D30-8952-11DF-8006-444553540000}
2=USB ADAPTOR
2.GUID={C2624D30-8952-11DF-8009-444553540000}
Now, for the "Modes" approach, I use one of the FSUIPC4 "User defined offsets" (0x66C0 to 0x66FF") to hold the "Mode" number.
In my case, I use the first offset in that block in the assignments statements, 0x66C0.
To implement my 'Mode' scheme, one must be able to edit the FSUIPC4.ini file as the FSUIPC inflight menu accessed via
the "Tools" tab will only allow for a single control assignment for the "press" or "Down" operation of a button/switch
and one for the "Release" or "Up" operation.
To implement multiple assignments for a given button/switch for a particular aircraft, you must use the "conditional
assignment" feature (Page 24 of the FSUIPC for Advanced Users.pdf)
First an example from my ini file, my B-17G section, for the six switches on my
Saitek quadrant 1 (D14,15,16,17,18) and the the first two switches on quadrant 2 (A0, 1)
The part of the entry "B66C0=x " is the 'qualifier' or 'MODE' and "x" = the mode number.
Control statements will only be activated if the current number in offset 66C0 matches the number
in the control statement. So changing the value in offset 66C0 changes the mode.
Some explanations of the notation:
"PD,14," is a 'press' of switch 14 on joy D, my throttle quadrant 1..far left
"UA,0, "is a release of switch 0 on joy A, my throttle quadrant 2...closest to me on the left.
"RD,15," specifies a repeating control as long as switch 15 is held
"CM6,x" refers to the MCRO file #6, the file that defines the L:variables used in the B-17G
the "x" is the line number of the L:Var for that particular control statement. See the list
of my MCRO files near the end of this post, as numbered by FSUIPC and shown near the top of the ini file
"C66340,0" is a 'standard FSX control code" found in the "List of FSX and P3D controls.pdf" file
These begin with C65.... or C66.... and have a passed parameter following the control number.
In many cases I have multiple controls being activated for the same switch in a particular mode
so that a single "press" of a switch will operate multiple switches in the aircraft.
A case where I use this is when starting engines of the B-17G. See the full 10-switch assignments
in Mode 1 below where a "press" of switch PD,14, sets the B-17G Starter Sitch for Engine 1,
the Primer select to Engine 1 and sets the Fire Extinguisher to Engine 1. Similar multiple operations take place
for the other three engines.
Mode 4 below shows the use of the 'Control on Press' and a different 'Control on Release'. In this case
I am sending the standard cowl flap FSX controls to open the cowl flaps 1 incrementally to a maximum of "99"
when Switch RD,14 is held down and UD,14, returns the VC engine 1 cowl flap switch to the neutral position when released.
[Buttons.Boeing B-17G]
!1=//SET 1 GENERATORS, FUEL PUMPS, FUEL VALVES, CONTROLS LOCK "Mode 0"
0=B66C0=0 PD,14,CM6:39,0 ;//TOGGLE ENG1 FUEL VALVE
1=B66C0=0 PD,16,CM6:40,0 ;//TOGGLE ENG2 FUEL VALVE
2=B66C0=0 PD,18,CM6:41,0 ;//TOGGLE ENG3 FUEL VALVE
3=B66C0=0 PA,0,CM6:42,0 ;//TOGGLE ENG4 FUEL VALVE
4=B66C0=0 PD,15,C66340,0 ;//TOGGLE FUEL PUMP 1
5=B66C0=0 PD,17,C66341,0 ;//TOGGLE FUEL PUMP 2
6=B66C0=0 PD,19,C66342,0 ;//TOGGLE FUEL PUMP 3
7=B66C0=0 PA,1,C66343,0 ;//TOGGLE FUEL PUMP 4
!2=//SET 2 STARTERS ENG 1 - 4 CLEAR START & MESH SET 4 PRIMER & PUMP - ALL MACROS - Mode 1
20=B66C0=1 PD,14,CM6:5,0 ;//STARTER ENG 1 - SET PRIMER TO ENG 1 MACRO
21=B66C0=1 PD,16,CM6:5,2 ;//STARTER ENG 2 - SET PRIMER TO ENG 2 MACRO
22=B66C0=1 PD,18,CM6:6,2 ;//STARTER ENG 3 - SET PRIMER TO ENG 3 MACRO
23=B66C0=1 PA,0,CM6:6,0 ;//STARTER ENG 4 - SET PRIMER TO ENG 4 MACRO
24=B66C0=1 PD,15,CM6:7,0 ;//MESH ENG 1
25=B66C0=1 PD,17,CM6:7,2 ;//MESH ENG 2
26=B66C0=1 PD,19,CM6:8,2 ;//MESH ENG 3
27=B66C0=1 PA,1,CM6:8,0 ;//MESH ENG 4
28=B66C0=1 PA,2,CM6:5,1 ;//CLEAR STARTER 1/2
29=B66C0=1 PA,2,CM6:6,1 ;//CLEAR STARTER 3/4
30=B66C0=1 PA,2,CM6:7,1 ;//CLEAR MESH 1/2
31=B66C0=1 PA,2,CM6:8,1 ;//CLEAR MESH 3/4
32=B66C0=1 PA,2,CM6:30,0 ;//SET PRIMER SELCT TO OFF
33=B66C0=1 PA,3,CM6:31,1 ;//ACTIVATE PRIMER
34=B66C0=1 PD,14,CM6:30,1 ;//SET PRIMER SELCT TO ENG 1
35=B66C0=1 PD,16,CM6:30,2 ;//SET PRIMER SELCT TO ENG 2
36=B66C0=1 PD,18,CM6:30,3 ;//SET PRIMER SELCT TO ENG 3
37=B66C0=1 PA,0,CM6:30,4 ;//SET PRIMER SELCT TO ENG 4
38=B66C0=1 PD,14,CM6:37,1 ;//SET FIRE EXT. SWITCH TO ENG 1
39=B66C0=1 PD,16,CM6:37,2 ;//SET FIRE EXT. SWITCH TO ENG 2
40=B66C0=1 PD,18,CM6:37,3 ;//SET FIRE EXT. SWITCH TO ENG 3
41=B66C0=1 PA,0,CM6:37,4 ;//SET FIRE EXT. SWITCH TO ENG 4
42=B66C0=1 PA,2,CM6:37,0 ;//SET FIRE EXT. SWITCH TO OFF
.
.
.!5=//SET 5 COWL FLAP SETTINGS,HYDR PUMP MODE,CARB FILTER "Mode 4"
90=B66C0=4 RD,14,C66329,99 ;//OPEN COWL FLAPS 1
91=B66C0=4 RD,15,C66330,1 ;//CLOSE COWL FLAPS 1
92=B66C0=4 RD,16,C66331,99 ;//OPEN COWL FLAPS 2
93=B66C0=4 RD,17,C66332,1 ;//CLOSE COWL FLAPS 2
94=B66C0=4 RD,18,C66333,99 ;//OPEN COWL FLAPS 3
95=B66C0=4 RD,19,C66334,1 ;//CLOSE COWL FLAPS 3
96=B66C0=4 RA,0,C66335,99 ;//OPEN COWL FLAPS 4
97=B66C0=4 RA,1,C66336,1 ;//CLOSE COWL FLAPS 4
98=B66C0=4 UD,14,C66330,0 ;//SET COWL FLAP SWITCH TO NEUTRAL ON RELEASE
99=B66C0=4 UD,15,C66329,0 ;//SET COWL FLAP SWITCH TO NEUTRAL
100=B66C0=4 UD,16,C66332,0 ;//SET COWL FLAP SWITCH TO NEUTRAL
101=B66C0=4 UD,17,C66331,0 ;//SET COWL FLAP SWITCH TO NEUTRAL
102=B66C0=4 UD,18,C66334,0 ;//SET COWL FLAP SWITCH TO NEUTRAL
103=B66C0=4 UD,19,C66333,0 ;//SET COWL FLAP SWITCH TO NEUTRAL
104=B66C0=4 UA,0,C66336,0 ;//SET COWL FLAP SWITCH TO NEUTRAL
105=B66C0=4 UA,1,C66335,0 ;//SET COWL FLAP SWITCH TO NEUTRAL
.
.
.
.!10=//CONTROL SET INCREMENT/DECREMENT These controls change the Mode
161=PA,4,Cx510066C0,x00080001 ;//INCREMENT 0X66C0 VALUE BY 1, MAX 8 THEN 0, CYLCLIC
162=PA,5,Cx610066C0,x00080001 ;//DECREMENT 0X66C0 VALUE BY 1, MIN 0 THEN 8, CYLCLIC
.
Here are some non-mode-specific assignments for the B-17G:
212=PE,9,CM6:87,0 ;//PDI HOLD OFF
213=PE,8,CM6:87,2 ;//PDI HOLD ON
214=PE,6,CM6:81,99 ;//OPEN PILOTS COCKPIT WINDOW
215=PE,6,CM6:82,99 ;//OPEN COPILOTS COCKPIT WINDOW
216=PE,7,CM6:81,0 ;//CLOSE PILOTS COCKPIT WINDOW
217=PE,7,CM6:82,0 ;//CLOSE COPILOTS COCKPIT WINDOW
219=RE,4,CM6:86,0 ;//CABIN VENT CLOSE
220=RE,5,CM6:85,100 ;//CABIN VENT OPEN
Above , switches 4 and 5 on quadrant 2 change the mode UP or DOWN, cyclically so repeated
UP presses go from 0 to 8 than back to 0. Down presses would go from 8 to 0 and back to 8.
These just happen to be the switch pair closest to me on my left side, my throttle hand.
(See Page 35 of the FSUIPC for Advanced Users.pdf for the list of these special FSUIPC controls and their format)
Some related stuff...a portion of the "A2A_B17G.MCRO" file referenced by "CM6, x" above: This is a text file
with the unique extension of "MCRO" that resides in the Modules folder and is read by FSUIPC4. The L:Variables defined
in the file are added to the FSUIPC4 list of assinable controls and appear in the menu items alphabetically sorted
prefixed by the file title "A2A_B17G" so they are near the top of the list.
L:Variables are used internally to XML gauges to control special functions not using standard FSX controls.
(See Page 40 of the FSUIPC for Advanced Users.pdf)
[MACROS]
1=L:Eng1_IntercoolerLever=INC
2=L:Eng2_IntercoolerLever=INC
3=L:Eng3_IntercoolerLever=INC
4=L:Eng4_IntercoolerLever=INC
5=L:Starter12Start=SET
6=L:Starter34Start=SET
7=L:Starter12Mesh=SET
8=L:Starter34Mesh=SET
13=L:Eng1_GeneratorSwitch=TOGGLE
14=L:Eng2_GeneratorSwitch=TOGGLE
15=L:Eng3_GeneratorSwitch=TOGGLE
16=L:Eng4_GeneratorSwitch=TOGGLE
17=L:OxyMaskOn=TOGGLE
18=L:Battery1Switch=SET
19=L:Battery2Switch=SET
20=L:Battery3Switch=SET
21=L:Eng1_IntercoolerLever=DEC
22=L:Eng2_IntercoolerLever=DEC
23=L:Eng3_IntercoolerLever=DEC
24=L:Eng4_IntercoolerLever=DEC
30=L:PrimerSel=SET
31=L:PrimerOn=TOGGLE
32=L:APUSwitch=TOGGLE
33=L:CowlFlapsSpeedKnob=SET
34=L:DialTurbocharger=INC
35=L:DialTurbocharger=DEC
36=L:MasterIgnitionSwitch=TOGGLE
37=L:FireEngineSelected=SET
38=L:InverterSwitch=SET
39=L:Eng1FuelCutOffSwitch=TOGGLE
40=L:Eng2FuelCutOffSwitch=TOGGLE
41=L:Eng3FuelCutOffSwitch=TOGGLE
42=L:Eng4FuelCutOffSwitch=TOGGLE
43=L:HydrModeSwitch=SET
44=L:CarbFilterOnSwitch=TOGGLE
45=L:ControlLockRudElev=SET
46=L:ControlLockAilerons=SET
.
.
.
81=L:WindowSliding1Lever=SET
82=L:WindowSliding2Lever=SET
83=L:SuitHeater0=SET
84=L:SuitHeater1=SET
85=L:CabinVent=INC
86=L:CabinVent=DEC
87=L:c1PDIkeepPosition=SET
88=L:AutopilotType=SET
Here is the list of my MCRO files and their assigned numbers.
!3=//----------------- Macro Files ------------------------
[MacroFiles]
1=APchart
2=747 OHD
3=A2A_J3
4=A2A_B377
5=A2A_P47
6=A2A_B17G
7=L1049H
8=A2A_Spit
9=A2A_P40
10=A2A_P51D
11=AF_F4U
12=91stBG_Guns
13=A2A_P51D_Civ
14=B25J
15=Avro_Lanc
16=A2A_C172
17=Avro_Anson
That's about it for now. I suspect I may have created more questions than answers but that is the most
important part of the learning experience.
As much as I have 'learned' vis-a-vis FSUIPC and Lua functions, I still refer to the documentation on a
regular basis whensetting up the control sets...modes... for a new aircraft. And Pete's FSUIPC forum
is a good place to get answers that aren't in the exstensive documentation.
Paul
vBulletin® v4.2.1, Copyright ©2000-2024, Jelsoft Enterprises Ltd.