Version 3.6 Axis Assignment

[Roland]

Hi Pete,

we talked about in threat "CH Flightstick ...

I made some test today and have problems to assign axis aircraft-specific.

My Setup as FSUIPC recognice them:

Controller 0 = CH Flightsim Yoke USB

Controller 1 = MS Sidewinder FF Gameport (FF disabled)

Controller 2 = CH Simpedals USB

All Controllers are deleted in FS9 Axis assignment

They where send direct to FSUIPC Calibration.

This is the a part of my FSUIPC.ini before I made axis assignments to my Bell Jetranger.

[Axes]

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

4=1Y,256

5=1Y,U,1760,13312,66079,0

6=1Y,D,-12593,-6586,66080,0

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

8=2X,256,D,7,0,0,0

9=2Y,256,D,8,0,0,0

10=2Z,256,D,3,40,0,0

11=2Z,256,D,3,40,0,0

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

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

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

As you can see, the Yoke (0) is assigned to Elevator, Aileron and Throttle,

Pedals (2) Rudder and Brakes

The Joystick X-Axes is assigned to Prop Pitch

and the Y-Axes is assigned to Gear (works fine, great feature!!)

Z-Axes works as Mixture.

OK now I load my Bell Jetranger and like to assigne the joystick axes X and Y to Aileron and Elevator, Z to Prop-Pitch (Rotor RPM)

The Yoke X should pan the View in 3D-Cockpit, Yoke Throttle works normal (as Pitch) and Yoke Y is not assigned.

Here are some Screens of my assignments:

And now the new FSUIPC.ini ( I cuted some entrys between the axes Section and the Aircraft-specific Section)

[Axes]

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

4=1Y,256

5=1Y,U,1760,13312,66079,0

6=1Y,D,-12593,-6586,66080,0

7=2X,256,D,7,0,0,0

8=2Y,256,D,8,0,0,0

9=2Z,256,D,3,40,0,0

10=2Z,256,D,3,40,0,0

11=2Z,256,D,3,40,0,0

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

...

[Axes.Bell 206B JetRanger]

0=0X,256,D,33,38,0,0

2=2X,256,D,7,0,0,0

The problem now is, FSUIPC shows the Axis 1X and 1Y with aircraft-specific-box checked but it changed the normal section.

In every test there are only 2 Axes saved aircraft specific and I never assigned any axes from the Ruderpedals (2) aircraft-specicfic)

Then I deleted the FSUIPC.ini and made some new assignments.

This time some strange things haben with the aircraft-entry

[Axes]

1=0Y,256,F,2,0,0,0

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

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

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

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

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

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

[Axes.Bell 206B JetRanger]

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

2=2X,256,D,7,0,0,0

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

1Y works as aileron, but isn't shown in FSUIPC.ini.

And it is not assigned in FS9!

This works until I restart the FS9.

Every other Axes is written to FSUIPC.ini when I assign it to a funktion.

Ehm... can you follow, its a bit confusing and difficult to explain :-)

[Pete Dowson]

This is the a part of my FSUIPC.ini before I made axis assignments to my Bell Jetranger.

Okay.

OK now I load my Bell Jetranger and like to assigne the joystick axes X and Y to Aileron and Elevator, Z to Prop-Pitch (Rotor RPM)

The Yoke X should pan the View in 3D-Cockpit, Yoke Throttle works normal (as Pitch) and Yoke Y is not assigned.

You realise, unlike buttons and keys, the axis assignments change completely (or should do) if you change to an aircraft specific set? In other words, unassigned ones do not default to the 'global' assignements.

Hmmm. You example does, indeed, seem very strange. Let me see: you made how many assignments to "aircraft specific"? Let me list them from what you said.

1X aileron Direct 1 (and slew side, 38?)

1Y elevator Direct 2 (and slew ahead, 39?)

1Z prop pitch, Direct 5

0X pan heading, Direct 33

0Z throttle, Direct 4

I assume all these and only these were programmed before what appears in the second listing from the INI?

Ignoring the numbers left of the "=" (which aren't relevant), we have, in axis order for the first set before changes:

0X,256,D,1,38,0,0

0Y,256,D,2,39,0,0

0Z,256,D,4,0,0,0

1X,256,D,5,0,0,0

1Y,256

1Y,U,1760,13312,66079,0

1Y,D,-12593,-6586,66080,0

1Z,256,D,6,0,0,0

2X,256,D,7,0,0,0

2Y,256,D,8,0,0,0

2Z,256,D,3,40,0,0

2Z,256,D,3,40,0,0

Just stopping there first, it is odd that there are TWO identical entries for 2Z. That shouldn't happen. I'd like to know how that came about.

Now listing the second (default) set in the same way:

1X,256,D,5,0,0,0

1X,256,D,5,0,0,0

1Y,256

1Y,U,1760,13312,66079,0

1Y,D,-12593,-6586,66080,0

2X,256,D,7,0,0,0

2Y,256,D,8,0,0,0

2Z,256,D,3,40,0,0

2Z,256,D,3,40,0,0

2Z,256,D,3,40,0,0

Comparing these, we appear to have completely lost the three entries for Joystick 0, and the 1Z mixture, and gained more duplicates -- 1X and yet another 2Z. A net loss of two entries -- which appears to be the number placed in the Aircraft Specific list.

Looking at that:

0X,256,D,33,38,0,0

2X,256,D,7,0,0,0

the 2X entry appears to be a duplicate of the default 2X entry, whilst the new 0X entry here is actually one which, as I listed earlier, is one you assigned and appears to be the only correct change.

The other 4 assignments you mention appear nowhere, not in either section.

This is indeed a puzzle. I seem to be able to edit these things here without problems -- something in the sequences you go through must be different. I'm not saying they are wrong, but in order for me to reproduce these problems and so fix them I think we'll need to help each other in more detail, step by step.

Best to start with no assignments, so either delete those sections or move them out someplace.

Then, sorry this is going to be long-winded, I need you to go through what you do, keypress and mouseclick one by one, writing down each step and what you see. Sorry, I know it's going to be a pain.

It would be good to see/check the result of each assignment as you do it, but that would mean "okaying" out of the dialogue and saving the sections each time -- and this alone may "fix" it. So it might as well be done in the two parts as you just described. I'll try to do the same here then.

I really do want to fix this, so sorry if this takes time. It is very puzzling. Something is evidently getting messed up in the internal tables as the editing process proceeds -- and judging by the duplicate entry you had BEFORE even going to "aircraft specific", it should be reproducing somehow.

Thanks

Pete

[Roland]

Hi Pete,

its a pleasure to go thru this pain :-)

Ok here we go.

First I deleted the whole Axis Section, open FSUIPC go to Axis Assignments and klick Reload all assignments.

After this, no assignments are shown.

Now I klick Rescan

Move the Yoke X-Axis

Picture1 after this step

Now I klick "Send direct to FSUIPC Calibration

and chose "Aileron" in the dropdown menue

Picture 2

To see this assigment in FSUIPC.ini I close with OK

The correkt entry in FSUIPC.ini

[Axes]

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

To make it short :-) I do so for the other Axis

All axis not specified for an aircraft at this moment.

Yoke Y = Elevator

Yoke Z = Throttle

Pedal X = Left Brake

Pedal Y = Right Brake

Pedal Z = Rudder

Joystick X = Prop pitch

Joystick Y = Gear Up Gear down

Joystick Z = Mixture

FSUIPC.ini after this

[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,5,0,0,0

4=1Y,256

5=1Y,U,6464,16383,66079,0

6=1Y,D,-16384,-4787,66080,0

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

8=2X,256,D,7,0,0,0

9=2Y,256,D,8,0,0,0

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

looks fine, I think.

Bevor I continue I wait for your "Go" :-)

[Pete Dowson]

Bevor I continue I wait for your "Go" :-)

Okay. My wife and I were out this evening, just got back. I will print each instalment out and analyse it before we move on. I'll attach three devices to my test system and try to do exactly the same as well. I have two handy, and I think I have one tucked away in a cupboard somewhere ;-)

I'll start on this in the morning and be back to you then.

Thanks,

Pete

[Pete Dowson]

I am not as tired as I thought so I checked the first steps this evening.

[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,5,0,0,0

4=1Y,256

5=1Y,U,6464,16383,66079,0

6=1Y,D,-16384,-4787,66080,0

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

8=2X,256,D,7,0,0,0

9=2Y,256,D,8,0,0,0

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

looks fine, I think.

Yes. that's all good. Not even that duplicate line we had before. I'm ready to press on when you are. It probably all starts going awry either when doing aircraft specific stuff, or maybe re-eding previously entered stuff. Lets do the straight-forward things first and if it is still okay (as is my experience here) we'll try editing in whatever fashion you normally do it.

It is obvious that there's something wrong, and all I need to do is be able to reproduce it to nail it! ;-)

Thanks. See you tomoorow.

Pete

[Roland]

Hi Pete,

OK lets go on with it.

First try, reassigned Controller 0 X-Axis (CH Yoke USB) to Pan Heading

Result:

[Axes]

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

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

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

4=1Y,256

5=1Y,U,6464,16383,66079,0

6=1Y,D,-16384,-4787,66080,0

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

8=2X,256,D,7,0,0,0

9=2Y,256,D,8,0,0,0

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

0=0X,256,D,33,0,0,0

Thats OK I think

Next try, Joystick Z-Axis (MS SW FF Gameport) from Mixture to Spoiler

Result:

[Axes]

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

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

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

4=1Y,256

5=1Y,U,6464,16383,66079,0

6=1Y,D,-16384,-4787,66080,0

7=1Z,256,D,22,0,0,0

8=2X,256,D,7,0,0,0

9=2Y,256,D,8,0,0,0

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

0=0X,256,D,33,0,0,0

Seems that normal assignments work well

Now setting back Yoke X to Aileron and second funktion to SlewSide and MSJoystick Z back to Mixture

Result:

[Axes]

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

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

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

4=1Y,256

5=1Y,U,6464,16383,66079,0

6=1Y,D,-16384,-4787,66080,0

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

8=2X,256,D,7,0,0,0

9=2Y,256,D,8,0,0,0

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

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

Perfect :-)

And now the first Aircraft-Specific Assigment.

Aircraft Standard-Boeing 737

Same as above, Yoke X to PanHeading (with makes no sense I know :-)

To do so, I klick on Rescan, move Yoke X, klick checkbox "aircraft specific" and change the entry in the first tab from Aileron to PanHeading.

The second entry "SlewSide" was left unchanged.

Result:

[Axes]

1=1Y,256

2=1Y,U,6464,16383,66079,0

3=1Y,D,-16384,-4787,66080,0

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

5=2X,256,D,7,0,0,0

6=2Y,256,F,8,0,0,0

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

8=2X,256,D,7,0,0,0

9=2Y,256,D,8,0,0,0

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

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

[Axes.Boeing 737-400]

0=0X,256,D,33,38,0,0

No more 0-Controller in the global axis section, all entrys from controller2 twice.

I just checkt the FS9-axis-assignments and found that FS9 reassigned the USB-Pedal (Controller2) when I start FS9. So I disable them again and

repeat the assignments of the last step. Befor this, I reset the FSUIPC.ini to the last working version.

But...

Same Result:

[axes]

1=1Y,256

2=1Y,U,6464,16383,66079,0

3=1Y,D,-16384,-4787,66080,0

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

5=2X,256,D,7,0,0,0

6=2Y,256,F,8,0,0,0

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

8=2X,256,D,7,0,0,0

9=2Y,256,D,8,0,0,0

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

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

[Axes.Boeing 737-400]

0=0X,256,D,33,38,0,0

Reset to working status and trying another axis. Now I try MSjoystick on gameport (Controller1) Z-Axis to Spoiler

Result:

[axes]

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

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

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

4=1Y,256

5=1Y,U,6464,16383,66079,0

6=1Y,D,-16384,-4787,66080,0

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

8=2X,256,D,7,0,0,0

9=2Y,256,D,8,0,0,0

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

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

[Axes.Boeing 737-400]

1=1Z,256,D,22,0,0,0

We lost 1Z in the normal section and dubbled 2Z

Again Reset and now assigning Controller2 (Pedals USB) Z to Pan Heading

Result:

[axes]

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

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

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

4=1Y,256

5=1Y,U,6464,16383,66079,0

6=1Y,D,-16384,-4787,66080,0

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

8=2X,256,D,7,0,0,0

9=2Y,256,D,8,0,0,0

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

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

[Axes.Boeing 737-400]

2=2Z,256,D,33,0,0,0

Looks OK I think. Very strange.

OK, stop trying at this point.

[Pete Dowson]

OK lets go on with it.

Okay. I think there's enough here. I think I see how the logic is twisted in my original design.

No more 0-Controller in the global axis section

I think, here, that the program is assuming you want to Edit the existing default assignment and make it aircraft-specific only. This is why you get the correct entry, but only in the specific section.

Although what you expected to happen does also seem logical, to be honest I never edited them this way. I always started programming aircraft-specific with a clear (no programmed axis) screen.

I suspect it is this changeover step which is causing all the problems. Let me explain:

Unlike buttons or keys, FSUIPC only uses one set of assignments at a time -- the "default" ones in [Axes] if the current aircraft has no aircraft-specific assignments, or the assignments actually made for this aircraft and no others.

Hence, once you have an aircraft loaded which has such a set, you should only be able to edit those assignments. The default ones should never be visible nor editable. I should auto-set the checkbox and disable it.

The other way round is not the same of course. If you have loaded an aircraft with no specific assignments, so I load the [Axes] ones, what should I do when you change to aircraft-specific? Start with a blank sheet, or copy all the default settings to the specific section, ready for editing?

Thinking back I think I tried to do something not quite either of these two, retaining the default settings in the table, but simply not using them until you've selected them into aircraft-specificness (so to speak ;-)).

I am going to have to think about this before changing anything. Easiest would be for me to only ever hold one set in memory -- either the defaults from [Axes] or the specific ones for this aircraft. This would mean that as soon as you started to make an aircraft-specific assignment for an aircraft not already so, you have no previous assignments to work with -- you make them all.

The alternative is to copy ALL the defaults into the specific section, so that you then have to edit them to change whatever you need. This would not be difficult either.

I think, rather than try to debug my existing code, I will do one of these two. Maybe, when you first click "aircraft specific" I should simply come up with a message box asking whether you want to start afresh or edit the existing assignments? This would give you both methods to choose from.

What do you think?

Thanks for all the help.

Regards,

Pete

[Roland]

Hi Pete,

first of all, we have to thank you for this great tool!

For me, it would be the best to make a copy of all defaults, cause this is the base of all alterations. I think most aircraft do need the same assignments and for example in a jet I would like the mixture set as spoiler.

And it would be great if we could edit the FSUIPC entries in that way, that special assignments work on a group of aircraft, i.e. all boeing or all bell.

AFAIK we could do this in the calibration section in this way.

[Pete Dowson]

For me, it would be the best to make a copy of all defaults, cause this is the base of all alterations. I think most aircraft do need the same assignments and for example in a jet I would like the mixture set as spoiler.

Yes, but there are big exceptions, like a helicopter with its own separate controls altogether. I think a Message Box "Yes, No, Cancel" would be okay.

And it would be great if we could edit the FSUIPC entries in that way, that special assignments work on a group of aircraft, i.e. all boeing or all bell. AFAIK we could do this in the calibration section in this way.

Yes, this already works for Axes too -- same method. You have to edit the [Axes.aircraft name] in the INI -- it works on the aircraft name in all cases, Keys, Buttons, JoystickCalibrations and Axes.

Regards,

Pete

[Roland]

Great Pete,

so I'm standing by for further updates :-)

[Pete Dowson]

so I'm standing by for further updates :-)

Okay. Please give the attached version 3.608 a good going over. I've been testing here and it seems okay so far. I'll continue over the weekend too.

Basically this is now what happens:

1. FSUIPC only loads the default Axes or the ones specific to the current aircraft (allowing for the shortened name option if that is set and used). The decision is based not on the presence of an [Axes ...] header, but on there actually being valid assignments in that section. In other words, you can't have an aircraft-specific section with no assignments -- it will be ignored.

2. Everything in the on-line editing works identically for the general and aircraft specific assignments.

3. When running with the general assignments (i.e. for an aircraft not provided with a valid section), selecting "aircraft specific" will bring up a message box asking if you want to use all the general assignments for this aircraft. Here you can cancel (go back to general) , or select Yes to work with the general ones, changing them as needed, or select No to start with a blank sheet.

In either Yes or No case you may be asked if you want to save any changes in the general axis assignments you may have made so far (else they will be lost).

If you select "No", to start from scratch, but then don't assign anything, FSUIPC will revert to the general assignments for this aircraft (it will reload them automatically when you Ok).

4. The converse is a little different. If you enter the dialogue whilst running an aircraft with existing specific assignments, then try to de-select "aircraft specific", you will be asked if you want to delete all the specific assignments. No or Cancel will retain the status quo, otherwise the general assignments will again prevail for this aircraft.

This actually represents a new facility -- before this it was only possible to lose aircraft-specificness by deleting every such assignment via the dialogue, or by deleting the section in the INI file.

Note that FSUIPC does not (cannot) delete the [Axes....] heading in the INI file, but it will be emptied, making it ineffective.

I hope this is all clear! Have fun, and let me know how you get on.

Best regards,

Pete

FSUIPC3608.zip

[Roland]

Hi Pete,

this version works great, except editing the aircraft name in FSUIPC.ini to make it work for i.e. all Bell does not work.

This works perfekt:

[axes]

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

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

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

4=1Y,256

5=1Y,U,6464,16383,66079,0

6=1Y,D,-16384,-4787,66080,0

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

8=2X,256,D,7,0,0,0

9=2Y,256,D,8,0,0,0

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

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

[Axes.Boeing 737-400]

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

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

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

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

4=1Y,256

5=1Y,U,6464,16383,66079,0

6=1Y,D,-16384,-4787,66080,0

7=1Z,256,D,22,0,0,0

8=2X,256,D,7,0,0,0

9=2Y,256,D,8,0,0,0

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

[Axes.Bell 206B JetRanger]

0=0X,256,D,33,38,0,0

1=0Z,256,D,4,0,0,0

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

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

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

5=2X,256,D,7,0,0,0

6=2Y,256,D,8,0,0,0

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

This do not:

[axes]

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

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

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

4=1Y,256

5=1Y,U,6464,16383,66079,0

6=1Y,D,-16384,-4787,66080,0

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

8=2X,256,D,7,0,0,0

9=2Y,256,D,8,0,0,0

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

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

[Axes.Boeing]

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

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

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

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

4=1Y,256

5=1Y,U,6464,16383,66079,0

6=1Y,D,-16384,-4787,66080,0

7=1Z,256,D,22,0,0,0

8=2X,256,D,7,0,0,0

9=2Y,256,D,8,0,0,0

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

[Axes.Bell]

0=0X,256,D,33,38,0,0

1=0Z,256,D,4,0,0,0

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

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

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

5=2X,256,D,7,0,0,0

6=2Y,256,D,8,0,0,0

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

[Pete Dowson]

this version works great, except editing the aircraft name in FSUIPC.ini to make it work for i.e. all Bell does not work.

You didn't show me the main INI file parameters -- did you set "ShortAircraftNameOk=Yes"? This is needed to make that work on all parts -- Keys, Buttons, Calibrations and Axes.

Regards,

Pete

[Roland]

Arrrgh, I'd better read the manual twice :-)

Your right, now it works perfekt. This is really great!!

On my wishlist :-)

As a future update it could be possible to choose if we want to save settings for a exact Model or group of Models. That would prevent editing the ini-file.

Thx Pete

[Pete Dowson]

As a future update it could be possible to choose if we want to save settings for a exact Model or group of Models. That would prevent editing the ini-file.

Well, it isn't that easy. The problem is that the "short name" option was a later add-on, so I couldn't default it in case it messed existing users up -- there are lots of cases where the short name would match others. I did think of using "*" for "anything else after this", but there's actualy nothing stopping that, or any other character, being used in the aircraft title.

Regards,

Pete

[Roland]

Hi Pete,

yes that seems to be difficult.

Anyway, this FSUIPC works perfect and now there is a real big potential in it.