The A2A Simulations Community

LVar control listing
Here is the list of LVar controls for cockpit builders and advanced users to aid in the mapping of the custom controls;
http://www.a2asimulations.com/Cockpitbu ... 20list.pdf

thanks,
Lewis - A2A

Very Cool,

Thanks Lewis. This will come in handy. I had to do a lot of searching to set controls for the T6. Now I won't have to search anymore.

Roger

Thanks Lewis - this'll come in handy. I've already experimented a little bit with the T-6 L:Vars and thought I'd add another one which is handy but not listed on the linked PDF:

(L:handprop,bool) - can be used to turn the prop by hand without having to open the shift + 3 menu. I use it with a key press (SET to 1 on press and SET to 0 on release).

Cheers,
Nick

Thanks should go to Michal who put the pdf together for you guys

thanks,
Lewis

Hello
I don't really understand how to use theses datas . I use the normal interface of FSUIPC and the A2A input configurator ; I set ,for example , left and right fuel selector with FSUIPC but I can't set "Fuel selector off", it don't work . Idem for the manual fuel pump , only available by left clicking with the mouse . An A2A input configurator more complete will be appreciated This T-6 is really my favorite A2A aircraft !

AWKM80 wrote:Hello
I don't really understand how to use theses datas . I use the normal interface of FSUIPC and the A2A input configurator ; I set ,for example , left and right fuel selector with FSUIPC but I can't set "Fuel selector off", it don't work . Idem for the manual fuel pump , only available by left clicking with the mouse . An A2A input configurator more complete will be appreciated This T-6 is really my favorite A2A aircraft !

Here are the entries from my INI file for the functions you mention above.

I use 3 switches to select the desired Fuel Select State and one for the Fuel Pump.
Switches 14, 15, 16 and 18 on my Saitek Throttle Quad ID'd AS Controller 'D'


30=PD,14,CM23:50,2 ;// LEFT WING FUEL TANK SELECT -{Macro A2A_T6: L:FSelT6State set}-
31=PD,15,CM23:51,0 ;// MANUAL FUEL PUMP -{Macro A2A_T6: L:FuelPumpManualLever tgl}-
32=PD,16,CM23:50,1 ;// RIGHT WING FUEL TANK SELECT -{Macro A2A_T6: L:FSelT6State set}-
34=PD,18,CM23:50,0 ;// FUEL TANK SELECT OFF -{Macro A2A_T6: L:FSelT6State set}-

From my T-6 MCRO file

50=L:FSelT6State=SET
51=L:FuelPumpManualLever=TOGGLE

Paul

From my T-6 MCRO file

50=L:FSelT6State=SET
51=L:FuelPumpManualLever=TOGGLE

What are MCRO files ? FSUIPC files ? I understand that standard FSUIPC interface is not enough for some functions .

Here is my FSUIPC. INI For the T-6 :


[Profile.T6]
1=North American T-6 Texan N5199V
2=North American T-6 Texan N73RR
3=North American T-6 Texan N711SQ
4=North American T-6 Texan F-AZBQ
5=North American T-6 Texan ZS-WLP "Spook"
6=North American T-6 Texan F-HLEA
7=North American Harvard 4 20412
8=North American T-6 Texan F-AZBE
9=North American T-6 Texan Flotille 54.S 32360

[Axes.T6]
RangeRepeatRate=10
0=0Z,256,D,4,0,0,0 -{ DIRECT: Throttle }-
1=0U,256,D,6,0,0,0 -{ DIRECT: Mixture }-
2=0V,256,D,5,0,0,0 -{ DIRECT: PropPitch }-
3=1X,256,D,1,0,0,0 -{ DIRECT: Aileron }-
4=1Y,256,D,2,0,0,0 -{ DIRECT: Elevator }-
5=2X,256,D,7,0,0,0 -{ DIRECT: LeftBrake }-
6=2Y,256,D,8,0,0,0 -{ DIRECT: RightBrake }-
7=2R,256,D,3,0,0,0 -{ DIRECT: Rudder }-
8=3S,256,D,6,0,0,0 -{ DIRECT: Mixture }-
9=4S,256,D,4,0,0,0 -{ DIRECT: Throttle }-

[Buttons.T6]
0=P1,5,K50,9 -{Key press: shft+2}-
1=P1,6,K51,9 -{Key press: shft+3}-
2=P1,10,K52,9 -{Key press: shft+4}-
3=P1,9,K53,9 -{Key press: shft+5}-
4=P1,7,K54,9 -{Key press: shft+6}-
5=P1,8,K55,9 -{Key press: shft+7}-
6=R1,1,C65615,0 -{ELEV_TRIM_UP}-
7=R1,2,C65683,0 -{ELEVATOR_DOWN}-
8=R4,4,C66278,0 -{RUDDER_TRIM_LEFT}-
9=R4,5,C66279,0 -{RUDDER_TRIM_RIGHT}-
10=P0,18,C65957,0 -{FUEL_SELECTOR_LEFT}-
11=P0,19,C65958,0 -{FUEL_SELECTOR_RIGHT}-
12=P0,22,C65955,0 -{FUEL_SELECTOR_OFF}-

All works fine ,except {FUEL_SELECTOR_OFF}

An MCRO file defines the L:Vars for an aircraft so that FSUIPC 'knows' about them
and you can use the FSUIPC drop-down menus to assign them to buttons, keys, etc.

A simple, fast 'fix for the case of the 'OFF' and the Fuel Pump would be to crates
a test file in notepad with the entries below and then save it to your 'Modules' folder
with the name 'A2A_T-6.MCRO'. The extension must be 'MCRO' when saved.

[MACROS]
1=L:FSelT6State=SET

FSUIPC willl assign a number to that file to be used when editing the INI file entries
by hand....in my case it is '23' as seen in my list as 'CM23'.

For your single change you can use the Menu to change the assignment

12=P0,22,C65955,0 -{FUEL_SELECTOR_OFF}-

TO this. IF the MCRO file is number 1 under the INI heading [MacroFiles]

12=P0,22,CM1:1,0 -{FUEL_SELECTOR_OFF}-

To use the drop-down menu when in the T-6 free flight simply press the
desired button/switch (Profile Specific), set 'Select for FS control' and then look down the list of controls
until you find 'A2A T-6:L:FSelT6State' and select that entry with a Parameter of '0' the hit 'OK'.

That should result in the INI entry I showed here for Line 12.

Paul

AWKM80 wrote:

From my T-6 MCRO file

50=L:FSelT6State=SET
51=L:FuelPumpManualLever=TOGGLE

What are MCRO files ? FSUIPC files ? I understand that standard FSUIPC interface is not enough for some functions .

Just to show you what my MCRO file looks like as I assign a whole lot of the functions to
my throttle-quads switches using 'conditional assinments' to assign multiple functions to
each of my available buttons/switches. ( I don't use all of them but I could. They all show
up as assignable in the Drop-Down menu. )

[MACROS]
1=L:BreakerStarter=SET
2=L:BreakerGaugesEngine=SET
3=L:BreakerGaugesEngine2=SET
4=L:BreakerLightCockpit1=SET
5=L:BreakerLightCockpit2=SET
6=L:BreakerLightFuelGauge=SET
7=L:BreakerLightFuelLevel=SET


8=L:BreakerGaugesAirTemp1=SET
9=L:BreakerGaugesAirTemp2=SET
10=L:BreakerLandingGearIndicator=SET
11=L:BreakerGaugesMixtTemp1=SET
12=L:BreakerGaugesMixtTemp2=SET
13=L:BreakerGaugesTurnCoord=SET
14=L:BreakerGaugesTurnCoord2=SET


15=L:BreakerNavCom1=SET
16=L:BreakerXpndr=SET
17=L:BreakerGaugesHobbs=SET
18=L:BreakerAutopilot=SET
19=L:BreakerSmoke=SET
20=L:BreakerAvnFan=SET
21=L:BreakerRemoteCompass=SET

22=L:BreakerWarningStall=SET
23=L:Breaker1=SET
24=L:Breaker4=SET
25=L:Breaker5=SET
26=L:BreakerGeneratorField=SET
27=L:BreakerHsi=SET

28=L:CanopyOpen1=TOGGLE
29=L:Door1Open=TOGGLE
30=L:ExitOpen1=SET

34=L:LightBrightDim=TOGGLE
35=L:PassingLightSwitch=TOGGLE
36=L:LandingGearLightLF=TOGGLE
37=L:LandingGearLightRF=TOGGLE
38=L:LandingGearLightRR=TOGGLE
39=L:LandingGearLightLR=TOGGLE
40=L:PassingLightSwitch=TOGGLE
41=L:APUSwitch=SET
42=L:LandingLightLeftSwitch=TOGGLE
43=L:LandingLightRightSwitch=TOGGLE
44=L:FuelGageLight=TOGGLE
45=L:Eng1_GeneratorSwitch=SET
46=L:CabinFlood1LightSwitch=TOGGLE
47=L:CabinVent=CYCLIC
48=L:CabinTempControl=CYCLIC
49=L:ControlsLockLever=TOGGLE
50=L:FSelT6State=SET
51=L:FuelPumpManualLever=TOGGLE
52=L:Eng1_CarbHeatSwitch=CYCLIC
53=L:MarkerBeaconLampTest=SET
54=L:LandingGearLightRFTest=TOGGLE
55=L:LandingGearLightRRTest=TOGGLE
56=L:LandingGearLightLFTest=TOGGLE
57=L:LandingGearLightLRTest=TOGGLE
58=L:FuelLowLFLampTest=SET
59=L:FuelLowRFLampTest=SET
60=L:FuelLowLRLampTest=SET
61=L:FuelLowRRLampTest=SET
62=L:SmokeSwitch=TOGGLE
63=L:SmokeArm=TOGGLE
64=L:Nav1StbySwitch=SET
65=L:Com1StbySwitch=SET
66=L:Nav1PullIdent=TOGGLE
67=L:NavComStandbySwitches=TOGGLE
68=L:XpdrModeKnobPos=INC
69=L:XpdrModeKnobPos=DEC
70=L:GpsOnSwitch=TOGGLE
71=L:XpdrIdentSwitch=SET
72=L:ApMaster=TOGGLE
73=L:ApOnOffButton=TOGGLE
74=L:ApAltButton=SET
75=L:ApControlStickButton=SET
76=L:ApLeftArrowButton=SET
77=L:ApRightArrowButton=SET
78=L:PrimerState=SET
79=L:Eng1_StarterSwitch=TOGGLE
80=L:Headphones=TOGGLE

81=L:PitotTubeCover=SET
82=L:vis_WingLeft_TieDown=SET
83=L:vis_WingRight_TieDown=SET
84=L:vis_Tail_TieDown=SET
85=L:vis_WheelChockR=SET
86=L:vis_WheelChockL=SET
87=L:OilCleanKitOn=SET
88=L:handprop=SET

89=L:ExitOpen2=SET
90=L:DoorOpen=TOGGLE
91=L:Door2Open=TOGGLE

Paul

Thank you very much and sorry for my english

My new "buttons" section :
[Buttons.T6]
0=P1,5,K50,9 -{Key press: shft+2}-
1=P1,6,K51,9 -{Key press: shft+3}-
2=P1,10,K52,9 -{Key press: shft+4}-
3=P1,9,K53,9 -{Key press: shft+5}-
4=P1,7,K54,9 -{Key press: shft+6}-
5=P1,8,K55,9 -{Key press: shft+7}-
6=R1,1,C65615,0 -{ELEV_TRIM_UP}-
7=R1,2,C65683,0 -{ELEVATOR_DOWN}-
8=R4,4,C66278,0 -{RUDDER_TRIM_LEFT}-
9=R4,5,C66279,0 -{RUDDER_TRIM_RIGHT}-
10=P0,18,C65957,0 -{FUEL_SELECTOR_LEFT}-
11=P0,19,C65958,0 -{FUEL_SELECTOR_RIGHT}-
12=P0,22,CM1:1,0 -{Macro A2A_T-6: L:FSelT6State set}-
13=P0,21,CM1:2,0 -{Macro A2A_T-6: L:FuelPumpManualLever tgl}-
It works fine now , thank you again Gypsy Baron !

Glad you have it working! And their is no problem with your english.

Paul

Hello,

I have also tried to create macros for my home cockpit.
I created a macro file by using the example that parachutesj gave in this topic; http://a2asimulations.com/forum/viewtop ... 21&t=47440

[MACROS]
1=L:FSelC182State=SET
2=L:Eng1_CowlFlapsLever=SET
3=L:RadioLightKnob=SET
4=L:PanelLightKnob=SET
5=L:PedestalLightKnob=SET
6=L:GlareshieldLightKnob=SET
7=L:WindowDefrosterControlKnob=SET
8=L:AnnunciatorPanelTestSwitch=SET
9=L:FloodLight1Switch=TOG
10=L:FloodLight2Switch=TOG
11=L:StaticAir=SET
12=L:GpsNavSelector=SET

After inserting the macro file in the FSUIPC5 module folder, it was recognized and everything worked perfect.

However, I do also have the A2A C182, Comanche and Bonanza.

I have tried to make some macros from A2A's LVAR listings (http://www.a2asimulations.com/Cockpitbu ... 20list.pdf - example file), but came to the conclusion that there's more behind this than just copying the LVAR lines into a .mcro file.
I therefore had little succes so far.

My question: are there already pre-made macro files available that I can directly insert to my FSUIPC5 folder (like the listing parachutesj and other members made)?

Thank you for the help!

Paul

Hello Paul,

Paul94 wrote:I have tried to make some macros from A2A's LVAR listings (....) but came to the conclusion that there's more behind this than just copying the LVAR lines into a .mcro file.

Yes, the other thing you'll need to do is make sure each L:Var has an appropriate action assigned to it. For example, SET, INC, DEC, or TOG and then assign the L:Var and action via FSUIPC.

I can try to point you in the direction of some more advice, but before I do, have you heard of the free 'LINDA' interface for FSUIPC? If not, I'd recommend you check out their forum on Avsim. It may be just what you're looking for and includes some predefined A2A modules. Actually, one of the developers (Guenseli) is also an A2A community member and beta tester.

Thanks,
Nick