How do I start one or more new profiles when adding a controller?

[Brian L]

Hi, hope someone can help me with this problem.

I'm adding a new controller, so need one or more new profiles, then to reallocate some aircraft on an

existing profile to a new one .

In my case I've started with a Saitek Evo Wireless Joystick with an appropriately named profile (Evo

Joystick) and allocated a few aircraft to it. Next I've added CH Pro pedals, by renaming the original

profile (to Evo Joystick + CH Pedals) in the FSUIPC.ini file, clearing the joystick rotation for rudder

axis, and adding the CH Pedals axes.

Next I've got a CH Yoke so I need a new profile, maybe changing some of the aircraft on the old

profile to the new. Then I might want to add multi-throttles, helicopter controllers, Spitfire joystick,

instruments, etc, in each case requiring new profiles and the switching of existing aircraft between

profiles.

In the axis assignments chapter of the User Guide top of second page (43) it says ‘Load FS and go to

the FSUIPC4's options. Select the Axis Assignment tab, and you will see this', and the screen shot

shows ‘Aircraft specific?' box (not greyed out). When I do this and move the yoke forward and back

the display shows Joy#Y Axis#Y with appropriate numbers, and my profile for Evo Joystick + CH

Pedals is shown at the top, which all seems correct, but the Aircraft Specific box, or in my case the

Profile Specific box (as I've enabled profiles in the FSUIPC4.INI file), and its tick, is greyed out.

Now I've just found the ‘Profile Assignment' post started by bradrcfii on Jan 14 2012 04:05pm. At last

the answer! So I've just deleted the default Cessna Skyhawk from the FSUIPC4.INI file, started a new

flight with it, and repeated the previous paragraph, but with the same result (profile specific box and

tick greyed out).

As a newbie to FSX and FSUIPC I've spent many hours reading the manuals and other guides but I can't

find a solution to this, though it worked for bradrcfii, so I'm hoping you can please tell me what am I

doing wrong?

Thanks

Brian L

[Pete Dowson]

I'm adding a new controller, so need one or more new profiles, then to reallocate some aircraft on an

existing profile to a new one .

Okay, easy enough, but it means editing the FSUIPC configuration settings file, FSUIPC4.INI.

For every Profile you created there will be a section entitled [Profile.<name>] where the <name> part is the name of the protifle you see in FS options. Withing that section are the names of all the aircraft which are using that profile, in lines numbered 1=... 2=... and so on. the aircraft names are usually the whole Title of the aircraft from its CFG file, but you can abbreviate them, for instance, to "PMDG 7372 or whatever -- some part which matches part of many names -- if you have "ShortAircraftNameOk=substring" set in the [General] section.

To move an aircraft from one profile to another just delete it in the one [Profile ...] section and add it to the other.

Select the Axis Assignment tab, and you will see this', and the screen shot

shows ‘Aircraft specific?' box (not greyed out).

Yes, that's the example for aircraft-specific options instead of Profiles, and "not greyed out" is only true when the aircraft isn't already assigned.

As a newbie to FSX and FSUIPC I've spent many hours reading the manuals and other guides but I can't

find a solution to this, though it worked for bradrcfii, so I'm hoping you can please tell me what am I

doing wrong?

Hopefully you can follow what I told you in the first paragraph? If not come back.

Regards

Pete

[Brian L]

Thanks for your quick answer.

Yes, I understand how I can transfer an aircraft from one profile to another and I could do that, but my problem is creating another profile.

Do I have to do that by editing the INI file? If so, I would need more information as the existing profile name appears four times.

Regards

Brian L

[Pete Dowson]

Yes, I understand how I can transfer an aircraft from one profile to another and I could do that, but my problem is creating another profile.

As I explained in my last reply, the aircraft is only assigned to the profile by being listed in the section headed [Profile.<name>] where <name> is the name of the profile. If you want to use an aircraft listed there to create another profile, just delete the line with the aircraft name in the [Profile.<name>] section. That makes the aircraft unattached to any existing profile.

Regards

Pete

[Brian L]

Sorry, but I've already done that as I said in my original post, see the para beginning 'Now I've just found ---'.

I've just repeated again what I said I did before with the same result as follows:

Checked that default Cessna 172 Skyhawk is NOT listed in my FSUIPC4.INI file.

Started FSX with the default Cessna 172 Skyhawk.

Gone into FSUIPC4, and selected the Axis Assignment tab.

Moved the CH Yoke forward and back.

The axis is correctly detected (Joy#Y, Axis#Y) with numbers OK.

The Profile Specific box and tick is greyed out.

Apologies if this post turns out to be repeated, there seemed to be a problem with the original send.

Brian L

[Pete Dowson]

Sorry, but I've already done that as I said in my original post, see the para beginning 'Now I've just found ---'.

Okay. Evidently I'm answering your first questions, in that post, and the subsequently arising question in your second post, which I had not noticed properly that you had in fact answered for yourself. Sorry. Maybe next time it would be quicker to just ask the actual question you really wanted answering? I do try my best, I assure you.

Please show me the INI file. There's evidently something wrong with it, because if the aircraft concerned is not listed at all it cannot possibly be assigned to any Profile. Tell me also the exact name of the aircraft (the title) and the profile displayed in the title bar of the assignments tab when you get the Profile Specific checkbox greyed out.

Regards

Pete

[Brian L]

Simflight FSUIPC Forum query 26-02-2012 1210.rtf

I'm hoping this post is published as I've had trouble posting (keeps sticking on 'saving post or server error', maybe because I'm trying to import it from a pre-written Wordpad document and I'm not sure what filetype and font to use, or it's too long).

Peter, I'm really very sorry - I do seem to have confused you, which means that your last reply is probably not relevant, so I've not replied to that as you requested.

Anyhow I have just returned to the problem 'How do I start a new profile when adding a new controller?', and I have just found a way of doing it, but not as given in manuals and tutorials. For the benefit of myself and others it would be helpful to find out why the documented method does not work, so please read on. I think it best if all previous posts are ignored and I now start again, and try to be clearer. I do stick to my original question though 'How do I start one or more new profiles when adding a controller'.

This was the situation at the start of my first post:

I had one profile for single engined aircraft using joystick + pedals. I had two aircraft in it, the default Piper Cub and the default Cessna C172SP Skyhawk. I wanted to start a new profile using the new yoke and existing pedals, which I could not do. When I found the Bradrdfii post I thought that might be the answer, ie using an unassigned aircraft (or deleting an assigned one and reusing it), and loading it, but as I said that did not work.

This is what I then did:-

Deleted the default Cessna C172SP Sykhawk from my FSUIPC4.INI file. Note that there is then only one profile (Joystick + Pedals) and only one aircraft in it (default Piper Cub).

Started FSX with the default Cessna C172SP Skyhawk, ie an unassigned aircraft, loaded it (and sometimes actually flown it in case that makes a difference).

Gone into FSUIPC4, and selected the Axis Assignment tab.

The Profile Specific box and tick is greyed out.

The title bar just says 'FSUIPC Options and Settings'.

Moved the CH Yoke forward and back.

The axis is correctly detected (Joy#Y, Axis#Y) with numbers OK.

The Profile Specific box and tick is greyed out.

The title bar says 'FSUIPC Options and Settings'.

I can now start a new profile by repeating as in the above 'This is what I then did' section, but ONLY by using the 'Buttons and Switches' tab or the 'Key Presses' tab, and NOT by using the 'Axes Assignment' tab. The FSUIPC manual at the top of page 43, and the Samurai tutorial both say specifically that I should be able to use the Axes Assignment tab, other tutorials do not cover profiles very well if at all, but it is assumed that profiles should work similarly to aircraft.

It seems that either:

(a) Various manuals and tutorials are incorrect, OR

(b) Using the Axes Assignment tab works, or did work, for aircraft specific and authors have assumed that it works similarly for profile specific when it actually doesn't, OR

© A program change has been made which inadvertently changes the way in which the program operates (resulting in manuals and tutorials becoming incorrect), OR

(d) There is something wrong with my particular installation or setup, OR

(e) Something else?

Peter, may I respectfully suggest that if you could quickly try starting a new profile using the Axes Assignment tab yourself, to check that it does actually work as you think it should, it would help to find out what is happening.

If you still wish me to send the FSUIPC4.INI file, please let me know how, eg copy/insert/attach it into this topic, or email to some address?

Thanks

Brian L

PS I'm using v4.80.

[Pete Dowson]

This is what I then did:-

Deleted the default Cessna C172SP Sykhawk from my FSUIPC4.INI file. Note that there is then only one profile (Joystick + Pedals) and only one aircraft in it (default Piper Cub).

Started FSX with the default Cessna C172SP Skyhawk, ie an unassigned aircraft, loaded it (and sometimes actually flown it in case that makes a difference).

Gone into FSUIPC4, and selected the Axis Assignment tab.

The Profile Specific box and tick is greyed out.

The title bar just says 'FSUIPC Options and Settings'.

This is the part I don't understand, and I cannot reproduce it here. If it did indeed behave like that then it is a bug, and i certainly need to fix it.

Please paste in your FSUIPC INI file, from the Modules folder.

It seems that either:

(a ) Various manuals and tutorials are incorrect, OR

(b ) Using the Axes Assignment tab works, or did work, for aircraft specific and authors have assumed that it works similarly for profile specific when it actually doesn't, OR

(c ) A program change has been made which inadvertently changes the way in which the program operates (resulting in manuals and tutorials becoming incorrect), OR

(d ) There is something wrong with my particular installation or setup, OR

(e ) Something else?

It is evidently (e) because none of the others apply.

Regards

Pete

[Brian L]

Below is INI file. I should now have a Joystick+Pedal profile with only the default Piper Cub in it, and a Yoke+Pedal profile with only the default Cessna C172SP Skyhawk in it. If I try to add a third profile by using another unassigned aircraft and the Axes Assignment tab the Profile Specific box is still greyed out.

[General]

UpdatedByVersion=4800

History=QNFQT9LLETI1HFAO960LP

MouseWheelTrim=Yes

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=Yes

MaxIce=0

MinIce=-1

UpperWindGusts=No

SuppressWindTurbulence=Yes

SuppressWindVariance=Yes

WindTurbulence=No

TurbulenceRate=1.0,5.0

TurbulenceDivisor=20,20,40,40

SuppressAllGusts=Yes

MaxSurfaceWind=20

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=Yes

WindSmoothness=1

WindSmoothAirborneOnly=Yes

PressureSmoothness=0

TemperatureSmoothness=0

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=No

WhiteMessages=Yes

ShowPMcontrols=No

SpoilerIncrement=512

MagicBattery=Yes

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=5

ClearWeatherDynamics=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=No

BrakeReleaseThreshold=75

SaveDataWithFlights=No

ZapSound=firework

ShortAircraftNameOk=No

UseProfiles=Yes

EnableMouseLook=No

AxesWrongRange=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

LogAxes=Yes

Console=No

DeleteVehiclesForAES=Yes

FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0

SimConnectUsed=10.0.61259.0

[JoyNames]

AutoAssignLetters=No

J=Cyborg evo Wireless

J.GUID={58CA1C70-19AE-11E1-8007-444553540000}

P=CH PRO PEDALS USB

P.GUID={AE2A34C0-1DA0-11E1-8001-444553540000}

Y=CH FLIGHT SIM YOKE USB

Y.GUID={FC1F2F10-407C-11E1-8001-444553540000}

0=Cyborg evo Wireless

0.GUID={D380EBC0-147B-11E1-8001-444553540000}

1=CH PRO PEDALS USB

1.GUID={D6EE2650-1DA0-11E1-8001-444553540000}

2=CH FLIGHT SIM YOKE USB

2.GUID={FC1F2F10-407C-11E1-8001-444553540000}

[buttons]

ButtonRepeat=20,10

1=P0,0,K80,8

2=PY,0,C65561,0

3=PY,1,C65561,0

[AutoSave]

Next=3

Interval=60

Files=10

SaveOnGround=No

AutoSaveEnabled=Yes

1=Mon 225722

2=Mon 225821

3=Mon 224531

4=Mon 224631

5=Mon 225029

6=Mon 225129

7=Mon 225228

8=Mon 225328

9=Mon 225523

10=Mon 225622

[GPSout]

GPSoutEnabled=No

Port=COM1

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[GPSout2]

GPSoutEnabled=No

Port=<none set>

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[WideServer]

WideFSenabled=Yes

[sounds]

Path=D:\Flight Simulator X\Sound\

Device1=Primary Sound Driver

Device2=Speakers (Realtek High Definition Audio)

Device3=Realtek Digital Output(Optical) (Realtek High Definition Audio)

Device4=Speakers (2- ASUS Xonar DX Audio Device)

Device5=Realtek Digital Output (Realtek High Definition Audio)

Device6=S/PDIF Pass-through Device (2- ASUS Xonar DX Audio Device)

[JoystickCalibration]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

Throttle1=-16380,-512,512,16380

Aileron=-15083,-1690,2688,15232

Elevator=-13523,-4161,4096,13952

Rudder=-15603,-512,512,15744

Throttle=-15773,15744

LeftBrake=-15733,13440/16

RightBrake=-15733,13568/16

[Profile.Piston 1 (J/S EVO W + Pedals CH Pro)]

1=Piper Cub

[JoystickCalibration.Piston 1 (J/S EVO W + Pedals CH Pro)]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

Rudder=-15733,-520,512,15744

LeftBrake=-14823,14976

RightBrake=-14563,14720

Throttle1=-16380,-512,512,16380

Aileron=-15741,-512,512,15744

Elevator=-15837,-512,512,15904

Throttle=-15773,15744

[Axes.Piston 1 (J/S EVO W + Pedals CH Pro)]

0=0X,256,D,1,0,0,0

1=0Y,256,D,2,0,0,0

2=0Z,256,D,4,0,0,0

3=0R,256,D,26,0,0,0

4=1X,256,D,7,0,0,0

5=1Y,256,D,8,0,0,0

6=1Z,256,D,3,0,0,0

7=YX,256,D,1,0,0,0

8=YY,256,D,2,0,0,0

9=YZ,256,D,4,0,0,0

10=YU,256,D,6,0,0,0

11=YV,256,D,5,0,0,0

[buttons.Piston 1 (J/S EVO W + Pedals CH Pro)]

0=P0,0,K80,8

1=P0,1,C65588,45

2=P0,32,C65875,0

3=R0,33,C66416,45

4=U0,33,C65875,0

5=R0,34,C66416,90

6=U0,34,C65875,0

7=R0,35,C66416,135

8=U0,35,C65875,0

9=R0,36,C66416,180

10=U0,36,C65875,0

11=R0,37,C66416,235

12=U0,37,C0,0

13=R0,38,C66416,270

14=U0,38,C65875,0

15=R0,39,C66416,315

16=U0,39,C65875,0

17=P0,0,K80,8

[Axes.]

0=0X,256,D,1,0,0,0

1=0Y,256,D,2,0,0,0

2=0Z,256,D,4,0,0,0

3=1X,256,D,7,0,0,0

4=1Y,256,D,8,0,0,0

5=1Z,256,D,3,0,0,0

[Profile.]

1=

[Profile.Piston 1 (Yoke CH + Pedals CH Pro)]

1=Cessna Skyhawk 172SP Paint2

[Axes.Piston 1 (Yoke CH + Pedals CH Pro)]

0=1X,256,D,7,0,0,0

1=1Y,256,D,8,0,0,0

2=1Z,256,D,3,0,0,0

3=YX,256,D,1,0,0,0

4=YY,256,D,2,0,0,0

5=YZ,256,D,4,0,0,0

[JoystickCalibration.Piston 1 (Yoke CH + Pedals CH Pro)]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

Aileron=-15083,-1690,2688,15232

Elevator=-13523,-4161,4096,13952

Rudder=-15603,-512,512,15744

Throttle=-15773,15744

LeftBrake=-15733,13440/16

RightBrake=-15733,13568/16

Throttle1=-16380,-512,512,16380

[buttons.Piston 1 (Yoke CH + Pedals CH Pro)]

0=PY,7,C65758,0

1=PY,6,C65759,0

2=PY,10,C65683,0

3=PY,11,C65616,0

4=PY,4,C66079,0

5=PY,5,C66080,0

[Pete Dowson]

Below is INI file. I should now have a Joystick+Pedal profile with only the default Piper Cub in it, and a Yoke+Pedal profile with only the default Cessna C172SP Skyhawk in it. If I try to add a third profile by using another unassigned aircraft and the Axes Assignment tab the Profile Specific box is still greyed out.

I shall try your INI here later. Thank you!

[LATER]

Initially I couldn't reproduce the problem, but then I added my defalut-loaded aircraft to one of your profiles, then i could reproduce it.

The problem is a corruption in your INI file. I don't know how it happened (it might have resulted from a bug in any older version of FSUIPC). Please delete these lines:

[Axes.]

0=0X,256,D,1,0,0,0

1=0Y,256,D,2,0,0,0

2=0Z,256,D,4,0,0,0

3=1X,256,D,7,0,0,0

4=1Y,256,D,8,0,0,0

5=1Z,256,D,3,0,0,0

[Profile.]

1=

What's happening is that the aircraft name is matching this blank one. Silly. I shall fix FSUIPC so it cannot do that, and will also see if I can detect bad sections like those above and automatically delete them. However, meanwhile, deleting them manually will fix it for you.

[LATER]

Fixed in 3.999c and 4.802, both now available in the Download Links subforum.

Regards

Pete

[Brian L]

Delayed thanks Pete, problem is solved now. (Delayed because I was looking for another post after the first part of your last reply and didn't realise that you'd added the 'Laters', as the topic date and time stayed as the original in the topic list).

I thought I'd do a summary of the answer to my original question in case anyone has the same problem as I had and is looking for a simple answer.

Firstly: Update to FSUIPC4 v4.804, which solves a possible relevant bug in earlier versions.

Secondly: Load a previously unassigned aircraft. If necessary delete an assigned aircraft in the INI file and reload it (particularly if there is one that you want to use with the new controller). This allows the profile options menu to appear from the Axes Assignment tab, or the Buttons and Switches tab. Not specifically stated anywhere or particularly logical or obvious - it seems to me that you are more likely to want to start a new profile when adding a new controller, than when adding a new aircraft. But easily done when you know how!

Brian L