Multiple Joystick Assignments

[BrassEm 0]

Hello Crum, Guenseli, My understanding is that FSUIPC is required to handle the joystick axes inputs, and I have a question about multiple joystick axes input configurations and how LINDA would handle them. My hardware consists of; A. VRInsight MCP COMBO PanelB. VRInsight YokeC. Microsoft Force Feedback 2 joystickD. GoFlight GF-TQ6 ThrottleE. CH PRO Throttle I am enjoying the challenge of programming up the Captain Sim B727 in LINDA with the configuration of A-B-D, but am thinking of maximising the potential of my hardware that I have with other payware aircraft and programming up the configurations to suit. I am thinking; Fighters: A-C-E (No pun intended.) Boeing: A-B-D Airbus:A-C-D Reading through the FSUIPC documentation there are two options. Multiple FSUIPC4 .ini’s or profiles. Multiple ini’s seems the most logical way to go as it would be aircraft independent. However I would need to make up the files for each configuration; Fighters:- FSUIPC4_Fighters.ini, .log, .key & FSX_Fighters.exe,.cfg Boeing:- FSUIPC4_Boeing. ini, .log, .key & FSX_Boeing.exe,.cfg Airbus:- FSUIPC4_Airbus. ini, .log, .key & FSX_Airbus.exe,.cfg Will LINDA be able to parse between these different file references or is LINDA looking exclusively for FSUIPC4.ini? Cheers, BrassEm.(No problem if exclusive, just means I need to write a program to rename the needed files into the default filename format.)

[Artem Crum 5]

BrassEm,In fact it just doesn't matter for LINDA. It will show you an error about something is wrong with FSUIPC config, but this doesn't mean it will not work. It will. Just remember to put [VRinsight] section with corresponding COM-port assignment into each of your custom ini files.But if you want to get rid of error message, you should rename custom ini to the standard name of 'fsuipc4.ini'.

[Andydigital 93]

Deleted Artem beat me to it.Although I still think it is better to use profiles in FSUIPC then you do not need to swap out ini files, you can assign multiple aircraft types to a profile.

[BrassEm 0]

That was super quick reply crum! Renaming to default seems logical. I didn't want to start diving in too deep. I can't find enough time to get the 727 going as it is.Thanks!(And thanks Andy too!)

[Andydigital 93]

Here is an example of a profile section from the FSUIPC.ini

[Profile.GA]1=C Skylane 182Q62=C Skylane II RG R182 13=American Champion Scout FSX Red with Black4=American Champion Citabria FSX Red and White5=Beech Baron 58 Paint26=Cessna Skyhawk 172SP Paint17=jfarcher_FR3[buttons.GA]0=PX,25,CM2:2,01=PX,23,CM2:1,04=PI,3,C66240,06=UI,3,C66240,08=PI,4,C66059,09=UI,4,C66060,021=P258,8,C66127,022=U258,8,C66127,023=P258,2,C66126,024=U258,2,C66126,025=P258,10,C66129,026=U258,10,C66129,027=P258,3,C66128,028=U258,3,C66128,033=PI,0,C66052,034=UI,0,C66053,035=PX,3,C66506,1537238=PP,4,CM2:1,040=PQ,0,K49,1143=PQ,3,K52,1144=PQ,4,K53,1145=PQ,5,K54,1146=PQ,1,K50,1162=P256,26,K56,1163=U256,26,K56,1164=P256,25,K68,1165=U256,25,K68,1172=PQ,2,K51,1175=P256,30,C65956,076=U256,30,C65956,077=PP,5,CM2:2,078=P258,18,C65908,079=U258,18,C65908,0[JoystickCalibration.GA]AllowSuppressForPFCquad=YesExcludeThrottleSet=YesExcludeMixtureSet=YesExcludePropPitchSet=YesSepRevsJetsOnly=NoApplyHeloTrim=NoFlapsSetControl=0FlapDetents=NoReverserControl=66292Reverser1Control=66422Reverser2Control=66425Reverser3Control=66428Reverser4Control=66431MaxThrottleForReverser=256AileronTrimControl=66731RudderTrimControl=66732CowlFlaps1Control=66162CowlFlaps2Control=66163CowlFlaps3Control=66164CowlFlaps4Control=66165SteeringTillerControl=0MaxSteerSpeed=60Aileron=-16383,0,512,16383Elevator=-16383,0,512,16383Rudder=-16383,-512,512,16383SlopeRudder=7Throttle=-15935,16192PropPitch=-9882,9472Mixture=-16384,16128ElevatorTrim=-16384,-512,512,16254Spoilers=-16165,16383Flaps=-16384,16383/16Reverser=-16384,16168/16CowlFlaps1=-16384,16383SlopePanHeading=13SlopePanPitch=15SlopeElevator=5LeftBrake=-12954,13970RightBrake=-13462,13970UseAxisControlsForNRZ=NoThrottle1=-16253,-9882,-8712,16128Throttle2=-15993,-9882,-9362,16128Aileron Trim=-16253,-1300,-780,16383SlopeAileron Trim=7Rudder Trim=-16384,-1430,-1300,16383SlopeRudder Trim=6CowlFlaps2=-16253,16383[Axes.GA]0=MX,256,D,27,0,0,01=MY,256,D,28,0,0,02=MR,256,D,29,0,0,03=MS,256,D,30,0,0,04=QX,256,F,66424,0,0,05=QY,256,F,66422,0,0,06=QZ,256,F,66425,0,0,07=PX,256,F,66420,0,0,08=PY,256,F,66423,0,0,09=PZ,256,F,66421,0,0,0

[BrassEm 0]

Hello Andy,Thanks for the example.

[Profile.GA]1=C Skylane 182Q62=C Skylane II RG R182 13=American Champion Scout FSX Red with Black4=American Champion Citabria FSX Red and White5=Beech Baron 58 Paint26=Cessna Skyhawk 172SP Paint17=jfarcher_FR3Would a profile entry need to be made for each paint model? i.e. 6=Cessna Skyhawk 172SP Paint1if there were more Paints would the profile list be i.e. 7=Cessna Skyhawk 172SP Paint28=Cessna Skyhawk 172SP Paint3etc,?The reason I ask is that each IRIS aircraft have something like 30 different paint and model configurations.Cheers,BrassEm.

[Andydigital 93]

I can't remember if adding "ShortAircraftName=substring" to the general section of the FSUIPC.ini works or not with profiles the same way as it does with aircraft specific profiles, have a look in the FSUIPC manual to confirm. If it does work then shortening it to Cessna Skyhawk would be enough to make it work with every repaint. It's really quick to add a new aircraft to an existing profile from within the FSUIPC GUI though so it not an issue for me.

[BrassEm 0]

Hello Andy,I can confirm that using just the profile feature, (Which you have to enable in FSUIPC), does exactly what I needed easily. I will just have to enter each aircraft as required. That way I can see what I actually use and unclutter my FSX aircraft selection GUI of redundant paints. (I know for a fact that MSCFS3 had a 256 aircraft limit. Highly probably that this is carried over in FSX too.)Thanks for the help!

[FSC190 30]

Hi to all,I'm just wondering that profiles in FSUIPC4.ini are not working anymore.Befor working with LINDA I had a couple of profiles for my diffrent axis-assingments.Now with Linda no profile works, all aircraft use the last assigned axis.I hope there will be a solution. Meanwhile I try out to disable profiles and use the normal aircraft-spezific assignments.Regards,Roland

[BrassEm 0]

Hello Roland,Is sounds like there are axis entries that preceed the profiles section of your FSUIPC4.ini. This is quite easy to do if the profiles control is not checked when assigning new axis controls. If you are not familiar with the .ini's, perhaps you could pm me or post your .ini file to confirm that this is what has happened. (Your profiles should still be there.)Cheers,BrassEm.

[FSC190 30]

Hi BrassEm,thanks for ypour reply.I swichted back to normal aircraftspecific Assignments with shortaircraftname=subtitle.This works as usual.With profiles enabled strange things happen :-)I.E. I saved a new Profil, but the saved name was not set in FSUIPC4.ini.Profilename was "Jet with Yoke" and the [Axis]-Entry should reas [axis.Jet with Yoke]But there was only a new section [axis.]The Profile-Entry was korrekt i.E. [Profile.Jet with Yoke]1=IFly 737 (Wide)I'm just wondering if nobody else has this problem.Anyway, aircraftspec-assignements are working and this OK for me.Cheers,Roland

[BrassEm 0]

Hello Roland,I did a quick test and created a profile for Jet with Yoke and Jet_with_Yoke for the Captain Sim B707.I can confirm that .Jet with Yoke or .Jet_with_Yoke is not appended to the [Joystickcalibration] with either profile name so I would imagine it would be the same for [Axis] and [buttons] as well.It looks like a FSUIPC issueCheers,BrassEm.

[Andydigital 93]

Try not using spaces in the names and only use alpha numeric symbols, i.e. no mathematical symbols just letters and numbers.

[FSC190 30]

Hi Andy

Try not using spaces in the names and only use alpha numeric symbols, i.e. no mathematical symbols just letters and number

but this was never a factor befor using LINDA.Do you have working profiles with LINDA?with kind regardsRoland

[Andydigital 93]

but this was never a factor befor using LINDA.

I wasn't sure if it was or not it was just a suggestion, I've never used spaces in Profile names I have created myself.Yes I've been using profiles rather than aircraft specific for over 18 months now and it works fine with LINDA, I just have to watch for duplication of commands. You might want to start off with a fresh FSUIPC.ini with the profiles taken out and them add them back in one by one as you test the various aircraft with LINDA just to make sure you aren't duplicating anything.