Stuck with double assignment.

[flyingdog]

Hi folks.

This is a LONG story and I shall leave a lot of it out to not bore you to pieces.

However, a quick version:

XP, SP1 512 Meg ram. Bought FSUPIC.

FS9 with patch worked.

I could fly single/twin and 4 engine planes. No worries.

I have a lot of GoFlight gear and a MS Sidewider FFB stick.

Machine died.

Rebuilt. Still dead. Rebuilt again and again.....

Finally got it working.

Had to re-install the OS and everything else. Re-installed FSUPIC.

The only difference is it is now SP2.

Had a lot of trouble getting the FS working. Would not get good FPS.

Resolved that it was the Joystick.

Bought new Joystick and all works good.

Mostly flew Single engine planes and all is good.

One day flew twin engine prop plane and realised that the joystick's Pitch control adjusts engine 1 throttle, and roll control adjusts engine 2 throttle.

I have checked the assignments in FS9 and there is no conflict with control axis and what they do.

In FSUPIC's screen as I am setting assignments I discovered that as I move the joystick's stick it alters the engine throttle values. Which way I move it depends on which engine. The other (correct) device is the GoFlight TQ6 unit. I have to do it this way as the GoFlight software is now pathetic and doesn't support some of their modules.

Anyway, that aside, I don't know how to remove the assignment from the joystick axis to the engine throttle assignment.

Furthermore, the joystick's throttle lever was assigned to cowel flaps. But if I move it, it "defaults" to both engine throttle lever.

Trying to fly a twin plane how it is now, pitch controls engine 1 and roll controls engine 2. Climbing and turning can become quite difficult.

Can someone please help me?

[Pete Dowson]

One day flew twin engine prop plane and realised that the joystick's Pitch control adjusts engine 1 throttle, and roll control adjusts engine 2 throttle.

As well as, or instead of, the elevator and aileron?

I have checked the assignments in FS9 and there is no conflict with control axis and what they do.

Did you check all controllers in the drop down, or do you only have the one?

In FSUPIC's screen as I am setting assignments I discovered that as I move the joystick's stick it alters the engine throttle values.

There is no display of throttle values in any Assignments tabs in FSUIPC. There's an axis assignments tab which shows axes and allows assignments, and a separate Joystick Calibration tab which reads incoming FS controls from either FS or FSUIPC assignments ("IN") and shows the effect on the assigned controls ("OUT").

So please differentiate between ASSIGNING and CALIBRATING. Where are you seeing what?

And in any case, if you are assigning in FS what are you doing in FSUIPC assignments, if indeed that is where you are?

Anyway, that aside, I don't know how to remove the assignment from the joystick axis to the engine throttle assignment.

If it is assigned in FS you remove that assignment in FS. If it is in FSUIPC you remove it in FSUIPC. If you really cannot figure FSUIPC out just delete the [Axes] sections in the FSUIPC INI file. Then FSUIPC won't be assigning any axes.

Furthermore, the joystick's throttle lever was assigned to cowel flaps. But if I move it, it "defaults" to both engine throttle lever.

I can't help with FS assignments -- FS help should be okay there. For FSUIPC if you are in a total mess and don't understand what you've done, simply delete the INI file (or the [Axes sections only) and start again. It will probably be easier for you if you stick to FS assignments. FSUIPC's are probably over the top (too powerful) for your needs. You can still calibrate in FSUIPC, just don't use the Axes tab if it confuses you. It is really intended for more advanced uses such as assigning different controls to different aircraft.

Regards

Pete

[flyingdog]

SOrry for the badly formatted reply. I am not used to this system yet.

One day flew twin engine prop plane and realised that the joystick's Pitch control adjusts engine 1 throttle, and roll control adjusts engine 2 throttle.

As well as, or instead of, the elevator and aileron?

Both.

The external view shows aleron/elevators moving as I move the stick. But with the engine control view also open, I see the throttle levers moving too.

I have checked the assignments in FS9 and there is no conflict with control axis and what they do.

Did you check all controllers in the drop down, or do you only have the one?

In FSUPIC's screen as I am setting assignments I discovered that as I move the joystick's stick it alters the engine throttle values.

There is no display of throttle values in any Assignments tabs in FSUIPC. There's an axis assignments tab which shows axes and allows assignments, and a separate Joystick Calibration tab which reads incoming FS controls from either FS or FSUIPC assignments ("IN") and shows the effect on the assigned controls ("OUT").

So please differentiate between ASSIGNING and CALIBRATING. Where are you seeing what?

It has been years since I have "talked the talk" of FS9. Please forgive me not being able to use the correct terms every time.

In FSUIPC, I go to one of the tabs where the assignments and calibration are. There is a "sub section" of about 15 pages which cover things like breaks, engines, thorttles, pitch, mixture, etc etc etc.

To me, slightly confusing. But anyway....

So there is a screen where I have engine throttle values which change as I move the levers of the GoFlight unit.

I move the lever on the GoFlight TQ6 for engine 1 and I see the values for that engine change.

I move the second lever and see engine two's throttle value change. All good.

it was only by fluke that I bumped the joystick once while I was trying to work out what was going on, I noticed the value change as I moved the joystick.

Ofcourse this was way after I had been flying and discoverd the problem while flying and was trying to debug the probelm.

And in any case, if you are assigning in FS what are you doing in FSUIPC assignments, if indeed that is where you are?

No, in FS, I have checked the assignments in FS for engine control, axis etc etc, and all of them are un-ticked when I select the joystick. Alas FS9 is painful in how it works when I change the top tab of functions listed.

I have even tried un-ticking the "enable joystick" box, so FS doesn't use the Joystick - or so I hope.

Anyway, that aside, I don't know how to remove the assignment from the joystick axis to the engine throttle assignment.

If it is assigned in FS you remove that assignment in FS. If it is in FSUIPC you remove it in FSUIPC. If you really cannot figure FSUIPC out just delete the [Axes] sections in the FSUIPC INI file. Then FSUIPC won't be assigning any axes.

Where is this file of which you speak? Is it in FS's directory, the modules' directory, or......

Sorry, I am not a full time windoze person and as I said, it has been YEARS since I have use FS because of ongoing problems with a) the computer b) problems with SP2 and the original joystick I had. c) getting all the stuff working again.

Furthermore, the joystick's throttle lever was assigned to cowel flaps. But if I move it, it "defaults" to both engine throttle lever.

I can't help with FS assignments -- FS help should be okay there. For FSUIPC if you are in a total mess and don't understand what you've done, simply delete the INI file (or the [Axes sections only) and start again. It will probably be easier for you if you stick to FS assignments. FSUIPC's are probably over the top (too powerful) for your needs. You can still calibrate in FSUIPC, just don't use the Axes tab if it confuses you. It is really intended for more advanced uses such as assigning different controls to different aircraft.

Regards

Pete

I think starting again would be the quickest way.

I have tried the "delete assignments" (is it? - or reset... what ever) and started from scartch, but it doesn't seem to work.

Oh, I am using "aircraft specific" on the settings because it is probably the best way.

but on that...... There are some things I want to be UNIVERSAL - like breaks, rudder, cowel flaps. I can't understand how to make some plane specific and others UNIVERSAL which apply to ALL planes.

I may have to sit down infront of FSUIPC and take more notes.

[Pete Dowson]

Both.

Okay, then you most certainly have double assignments.

In FSUIPC, I go to one of the tabs where the assignments and calibration are. There is a "sub section" of about 15 pages which cover things like breaks, engines, thorttles, pitch, mixture, etc etc etc.

There are no assignments there -- that's the joystick calibration section. The values you see moving are only reflecting assignments made elsewhere, either in FS or in FSUIPC, or possible both.

To me, slightly confusing. But anyway....

Really? Why? Doesn't documentation help or don't you use that?

Assignments of Axes are in the Axes tab, assignments of buttons are in the Buttons tab. Assignment of Keys are in the Keys tab. Why isn't that clear?

No, in FS, I have checked the assignments in FS for engine control, axis etc etc, and all of them are un-ticked when I select the joystick.

So, then, you have dual assignments in FSUIPC.

Where is this file of which you speak? Is it in FS's directory, the modules' directory, or......

All FSUIPC files are in the FS Modules folder. That's where you find FSUIPC.DLL, FSUIPC.INI, FSUIPC.LOG and FSUIPC.KEY. You'll also find all of the FSUIPC documentation (which, if you are up to date with FSUIPC should be in their own folder inside Modules), which I suggest you peruse, or at least look up the sections you seem to want to use but don't know how.

If there's no good reason to assign things in FSUIPC I suggest you simply delete the FSUIPC.INI files and leave it all to FS.

I have tried the "delete assignments" (is it? - or reset... what ever) and started from scartch, but it doesn't seem to work.

What's this "delete assignments" you are talking about? Where do you see that? To start from scratch just delete the INI file before running FS. Then none of your settings in FSUIPC will be there any more.

Oh, I am using "aircraft specific" on the settings because it is probably the best way.

Why? You are making things much more complicated. Please only use facilities you understand, or at least have read about beforehand.

Regards

Pete

[flyingdog]

I am going to have to really try to make time to sit in front of the PC and "document" what I am meaning.

Why "aircraft specific"?

Well, first off here's my setup:

I have FS9 - obviously.

A Saitek USB FFB stick - as opposed to the initial M$ Sidewinder Pro FFB which killed the FS when SP2 was installed I think.

CH HOTAS - though seldom used nowadays.

CH Pedals.

GF gear - TQ6, a few PB8, a few PT8, a radio unit, an ATC unit, the original MCP, the original Landing gear/flap unit.

(That is about 9 units from GoFlight)

All but the TQ6 and one of the set of switches are all fixed in what they do. However, the TQ6 changes functions depending on the plane.

Yes, GF's software kind of supports that, but they shot them selves in the foot and now their software doesn't support some of their gear. I now have the "best" version of their software which supports are much as I can get.

Having FSUIPC and it sees the GF gear it seems better/easier to use it to define the functions rather than trying their software.

Also, if I change planes, I don't have to exit FS and re-load the config for GF then re-load FS, and start.

FSUIPC's ability to identify plane changes, it makes it way easier.

So I wasn't doing Pitch/Roll callibration with FSUIPC, I had not touched it. I fly single engine planes and was happy.

One day I was flying a twin prop plane and was flying. I noticed something weird happening while taxiing but didn't worry too much.

Takeoff was a bit strange too, but after takeoff, I used autopilot. Arriving at the destination I disengaged autopilot and started to do the circuit.

Suddenly the engines are going wild and doing weird things. Engine 2 was reving up or back as I turned. Then as I started to descent, engine 1 went carzy.

I aborted the flight and studdied the plane's responce to inputs.

I noticed that as I moved the stick, the engine levers were moving.

I checked in FS assignments and couldn't find anything. So I am guessing it is caused by FSUIPC. (No offence.)

It doesn't show me "who" is controlling what on the plane. I get device "names" in the calibration window but it doesn't really tell me who they are.

All the GF gear has unique names - as stated by GoFlight and I guess it needs to be to let it's software know "who is who" if I have two of the same thing plugged in.

I kept screen shots to help me when setting the breaks, rudder, etc so I have better control of them. But even reading the documents, what these numbers do/mean and how to set them is beyond me.

In some cases I have to press the SET button twice to get the value into the box, other times, once.

I don't remember the specifics and shall discuss this later on after we get this original problem resolved.

Back to the original problem:

People have told me to try disabling the joystick in FS and doing that makes no difference.

What did work for a while was plugging the joystick into a different USB port. But shortly after, the probelm returned.

To me that means it is seeing the name of the joystick and assigning the functions from that.

I'll stop talking now as I think I have said what I need to, and am babeling now.

[Andydigital]

When you unplug a device and plug it back in again into a different port FS automatically generates defaults settings for the device again, even if you don't want it to, so if I were you I would check that the assignments really have been removed in FS.

[Pete Dowson]

I noticed that as I moved the stick, the engine levers were moving.

Yes, as you've already described.

I checked in FS assignments and couldn't find anything. So I am guessing it is caused by FSUIPC. (No offence.)

It is caused by dual assignments, wherever they may be. FSUIPC does nothing you don't tell it to do!

It doesn't show me "who" is controlling what on the plane. I get device "names" in the calibration window but it doesn't really tell me who they are.

Sorry, I don't understand this part.

In some cases I have to press the SET button twice to get the value into the box, other times, once.

What SET button and what value? The centre SET has two values so needs two presses. None of the others do. The main SET/RESET button on the left controls whether the axis is calibrated or not. None of the buttons will allow impossible calibrations -- numbers have to increase left to right or they are not accepted.

What did work for a while was plugging the joystick into a different USB port. But shortly after, the probelm returned.

If you move things between USB ports, their joyistick ID numbers change. If you then make new assignments to the new IDs the old assignments still stand with the old IDs, so when something else is plugged in which gets those IDs you get dual assignments. Unplugging and moving things around is the biggest single cause of confusion and dual assignments.

If you've been moving stuff, or don't leave things plugged in all the time, then you really either need to DELETE your entire Axes and Buttons assignments sections every time you move or unplug anything, OR, much easier, use the joystick lettering system provided in FSUIPC in order to allow it to keep track of named joysticks and change the assignments for you automatically.

If you want me to analyse the reasons for the mess, please post the [Axes ...] sections from the FSUIPC INI file here and I'll point out where the problems are occurring. Please also include the [JoyNames] section (which is where you could assign devices letters).

However, really your best bet now is to delete everything and start again, but before loading FS again, first enable Profiles to cut down on the huge number of "aircraft specific" sections you might generate (adding to your confusion), and enable joystick lettering so that FSUIPC has a chance of doing reassignments when you move things.

Regards

Pete

[flyingdog]

I may be a bit quite for a while.

I haven't got upset, just extremely busy.

When I have news, I'll let you know.

[flyingdog]

Good news!

I renamed the existing .ini file and started again.

It all works. Not that I didn't believe it, but it just seems weird how it all happened.

If you (Peter) will indulge me now, I shall put my questions here.

I don't want to make too many posts. They are hard to track.

Yes, I am sure that it is explained in the manual, but I am confused and asking here may help clear the confusion.

Ok, AXIS ASSIGNMENT screen in FSUIPC.

Rescan - I guess this is pressed when you are doing multiple axis on multiple sticks?

Clear - nice word but not exactly specific. I had pressed it with the initial problem and it didn't change anything, so what does it clear?

Over in the middle of the window, there is a Joy#, and then an AXIS #.

Ok, the axis are difficult to "name" but I thought each USB device had a better name than a number.

Looking at it, how do I know which number is which device?

I am taking it that the four input fields at the bottom are for when an axis is "sectionalised" into parts?

CALIBRATION screen.

Min - Cent - Max.

Yeah, ok for rudder, aileron, and..... Elevator.

Back to that in a moment - I am typing in the notes I made on the paper in the order I wrote them. It is confusing enough for me. Sorry if this makes it confusing to read. But I hope we can work on that and resolve the confusion as we go.

Breaks: These are really confusing.

If I tell the assignment to give it to FSUPIC to calibrate in the previous window, something weird happens.

LEFT BREAK: Fully off I get 16383 in the window.

Fully on I get -16178 in the window.

So, I pusht the pedal down with my heal to get the 16383-ish value. Breaks fully off.

I press the SET button on the left, I get the number into the field below.

Then I press the pedal with my toes and get the -16xxx value. I press the button to set that and all I get is a beep.

The program/something won't accept it.

That aside for a second, the RIGHT BREAK now:

Fully off, I get -16xxx

Fully on, I get 16xxx

The numbers are REVERSED in their values with where the pedals are. WHY?

Anyway, to "resolve" this, I simply go back to the assignment window and tell it not pass the values DIRECTLY to the FS and then when I go the calibrate window and have the break part open and press the breaks I get the values moving as I press the pedals and they both have the same range. That is going from (say) -16xxx to 16xxx when the pedal is pressed with toes.

Now, I appreciate the rudder/break pedals I have can get "noise" in them and causes stutter in the rudder - well, that's what I am getting with the rudder.

How do I put in a "null zone"?

In one of the screens (Assign - I would think) when I am trying to name and pass the "joystick" axis to FSUPIC, I can't find BREAKS - left or right. Annoying. Though when I go to the CALIBRATE window/tab, the values change when I press the pedals.

Suggestion on this point:

Why is it that most other things are like: Engine 1 - blah. Engine 2 - blah, and so on.

Why isn't it Breaks - left

Breaks - right

and not left break and right break. It is confusing trying to find them sometimes.

The "View cycle" is also not listed in the FS commands. I have to "cheat" and if I want to cycle views by pressing a button on the Joystick I have to assign a "key press" to the button and make it "s" and to cycle back I have to assign keypress "S" to the buttons.

Why isn't there a "View cycle foreward" and "View cycle backward" functions listed in the list of FS commands?

[Pete Dowson]

Ok, AXIS ASSIGNMENT screen in FSUIPC.

Rescan - I guess this is pressed when you are doing multiple axis on multiple sticks?

Well that's one use, though a more important one is to find the axis you want to assign when there's another with "jitters" which keeps getting detected first. You can use the "ignore" button to tell it to (temporarily) ignore the axis which is getting in the way, and then rescan from the beginning ot find the right one.

Clear - nice word but not exactly specific. I had pressed it with the initial problem and it didn't change anything, so what does it clear?

It clears the assignment and parameters currently displayed, in the mode (aircraft specific or profile or global0 you are currently in (and shown as in), so that when you press "OK" that assignment is removed from your settings.

If you press ESCape at any time when in the FSUIPC options, all changes you make are reversed. It genuinely means "escape", i.e. "get out of whatever I've done". In order for changes to stick they have to be confirmed, or OKayed.

Over in the middle of the window, there is a Joy#, and then an AXIS #.

Ok, the axis are difficult to "name" but I thought each USB device had a better name than a number.

The Windows joystick API uses numerics, 0-15, for joysticks. Those have been used universally since Windows 3.1 days or before. FSUIPC operates with FS98, FS2000, CFS1, FS2002, CFS2, FS2004, FSX and ESP, and throughout al those it has been consistent, with ongoing compatibility. USB is a recent invention comparatively, and there were no readable names for game port devices.

Looking at it, how do I know which number is which device?

By moving an axis or pressing a button, depending which screen you are looking at. But you can also look in the FSUIPC NI file, in the [JoyNames] section, where you wil see the names assigned to the numeric IDs. There you can also assign letters instead of numbers, and doing this will enable FSUIPC to automatically track devices, using names and GUIDs, in order to allow for unplugging and re-plugging, which changes the numeric IDs. Please refer to the section on this useful facility in the documentation.

FS uses GUIDs to identify devices, as well as many other things.

I am taking it that the four input fields at the bottom are for when an axis is "sectionalised" into parts?

No. You can assign one axis to up to 4 different controls at the same time. It does have uses, believe me. To make different things happen along different places or regions along the axis travel you use the right-hand side of the page. There's an example in the documentation for using an axis for Gear operation.

Back to that in a moment - I am typing in the notes I made on the paper in the order I wrote them. It is confusing enough for me. Sorry if this makes it confusing to read. But I hope we can work on that and resolve the confusion as we go.

That's all very well, but I spent many many hours on the documentation in order to explain things. I don't intend to do it all again here. If the documentation is confusing to you, please, wouldn't it be more constructive for you to point out places there which you don't understand, and tell me exactly why?

Breaks: These are really confusing.

Breaks? What are they? Or do you mean "brakes"?

So, I pusht the pedal down with my heal to get the 16383-ish value. Breaks fully off.

I press the SET button on the left, I get the number into the field below.

Then I press the pedal with my toes and get the -16xxx value. I press the button to set that and all I get is a beep.

The program/something won't accept it.

As it clearly says, the numbers MUST increase left to right on screen. The "Minimum" number means the LOWEST, the Maximum number means the HIGHEST. +16384 is much higher than -16384. It is simply arithmetic to understand the concept of lower versus higher, surely?

The numbers are REVERSED in their values with where the pedals are. WHY?

Because that is the way many (but not all) manufacturers wire their pedals. This is why there's a "REV" button in the calibration screen. It does explain all this in the documentation. You will find exactly the same in FS assignments -- there's a REV button there too!

How do I put in a "null zone"?

A dead zone in the centre of rudder, aileron or elevator axes is produced by having two different values in the two centre boxes of the calibration. that is EXACTLY why there are two values for centre. If you'd ever read the documentation and followed the easy numbered steps to proper calibration you would have known this. Why don't you try something like that? You obviously haven't read it, or skipped too much!

In one of the screens (Assign - I would think) when I am trying to name and pass the "joystick" axis to FSUPIC, I can't find BREAKS - left or right. Annoying.

Perhaps if you looked for Brakes instead you'd find them. They are certainly there. There aren't any controls for any "breaks" as hopefully there are none in your aircraft.

Why is it that most other things are like: Engine 1 - blah. Engine 2 - blah, and so on.

Why isn't it Breaks - left

Breaks - right

and not left break and right break. It is confusing trying to find them sometimes.

The names are chosen by Microsoft. Go complain to them. FSUIPC is not inventing any names there, it gets them form FS.

The "View cycle" is also not listed in the FS commands. I have to "cheat" and if I want to cycle views by pressing a button on the Joystick I have to assign a "key press" to the button and make it "s" and to cycle back I have to assign keypress "S" to the buttons.

ALL of the FS controls are listed, but with the names FS assigns to them!

Why isn't there a "View cycle foreward" and "View cycle backward" functions listed in the list of FS commands?

Because Microsoft did not name them that way. They named them "View mode" and "View Mode Rev" respectively, at least in FSX. There's also "Next Sub view" and "Prev sub view" normally assigned to the A key.

There are two ways to identify exactly the correct names. One is to look at the default assignments XML file in the FSX installation, and the other, which works for all versions of FS since FS98, is to enable Event logging in FSUIPC, then press the key and see what the Log says it is called.

Pete

[flyingdog]

Hi again Peter.

I don't know why it is I can't spell brakes and put the extra 'e' in there. I think it is a "crossed wire between the brain and the hands when I type. There are many words like that and unless I REALLY REALLY concentrate, I spell it incorrectly.

Changing numbers to letters sounds perfect! I had a look at the old .ini file and shall now look at t he new one and find the place where the nubmers are assigned to the joysticks and change them to letters.

But I guess then I will have to go through and find subsequent references to the old numbers and replcae them with the new letters.

"Sectionalising an axis"

That's weird. Your explination is exactly what I thought. If the stick has 4 axis, I could do them all then and there.

The CH pedals was the perfect example. But I push one pedal and I get the input push the other one and don't see it.

Anyway, I'll work on it.

You mentioned GEAR operation for sectionalising the axis.... Errr why? Gear is usually UP or DOWN. Ok, there is the middle "OFF" section for jets. I was trying with the cowel flaps.

Ok, with the joystick button/s to cycle the view mode.

I clicked the button and went off looking through the huge list. No, I didn't know the name, so looked for what I thought was the name. Couldn't find what looked right.

Stopped and went into FS"s assignments. Went to views. Scrolled through the FS list and found the "s" key reference and noted the name. I am 99% sure that is the name I used in my earlier post and couldn't find it listed. So what I did was make that button equal to pressing the "s" key, and another one to the "shift + s" key - is FS depicts it.

Anyway, I'm back to being able to fly and am happy.

Oh brakes. (had to go back and take out that extra e again)

On the assignment screen I ticked the send straight to FS box.

Went to the calibration screen and went to the window with the brake value listed.

Pressing the LEFT pedal numbers go from small to big.

Pressing the RIGHT pedal numbers go from small to big.

However, if I go back to the assign screen/tab and tick "Send to FSUIPC to calibrate" THEN the numbers on one are reversed.

No worries, as you say: There is a reverse button to fix the problem.

I am only asking why are they reversed in the first place from when they are not "parsed"?

Thanks very much for the help though. It isn't that I like making a fool of myself and showing people I can't spell for the sake of learning. It is just that sometimes data just doesn't get in and I can read it until the cows come home it is confsing.

I don't know why, but reading what you say HERE (be it verbatum to what is in the instructions or not) it makes sence to me or is clearer. Don't ask me why, because I don't know.

I am also noticing that my typing skills are getting worse as I could usually nearly touch type - yeah, ok with a few mistakes - but could at least get the keys pressed in what I thought was the right order. Now the keys have a mind of their own and are getting in the wrong order. Scarey stuff from my perspective!

I have not had the machine working now for about 4 years! Before that I had invested hours installing and setting things up.

Now the machine is working, I am (maybe foolishly) wanting to fly again and am hoping that things are as easy to get working as they were the first time. Funny how it seemed so much easier then than now.

Anyway, it is early Sat morning and I have other jobs to do before I can indulge myself in flying.

Bye and thanks.

"I'll be back" though. Even if all is good. Just to stay across things.

[Pete Dowson]

But I guess then I will have to go through and find subsequent references to the old numbers and replcae them with the new letters.

No, FSUIPC will do that for you automatically! Just add the assignments in the [JoyNames] section -- don't remove any lines, just reproduce those there replacing the numbers on the left by your chosen letters. Or let FSUIPC do even that for you if you don't mind simply "A", "B", "C" etc for 0, 1, 2 ...

You mentioned GEAR operation for sectionalising the axis.... Errr why?

You misunderstand. Some folks use a lever rather than a switch for gear, i.e. a lever which looks like an axis to Windows. You can't program those in the Buttons & Switches tab -- you have to use the Axis tab. But you can assign a region at one end for GEAR UP and the other for GEAR DOWN. If FS supported the "Gear OFF" position which airliners have you'd have then in the centre, but that isn't the point.

I clicked the button and went off looking through the huge list. No, I didn't know the name, so looked for what I thought was the name. Couldn't find what looked right.

Oh dear. Please read what I write or I waste my time. I told you a way to find out using the tools in FSUIPC. But please yourself if you don't want such help. :-(

On the assignment screen I ticked the send straight to FS box.

Went to the calibration screen and went to the window with the brake value listed.

Pressing the LEFT pedal numbers go from small to big.

Pressing the RIGHT pedal numbers go from small to big.

However, if I go back to the assign screen/tab and tick "Send to FSUIPC to calibrate" THEN the numbers on one are reversed.

Again you persist in ignoring what I tell you. FS has a "REVERSE" checkbox too. Go look! If you assign to FS and it reverses you don't need to also reverse in FSUIPC.

I am only asking why are they reversed in the first place from when they are not "parsed"?

Because that's the way manufacturers often make them. Go ask them.

Pete

[flyingdog]

Hi!

Good news!

Most of the problems are now "resolved" WRT Double assignments.

There are still problems with me understanding how to do all the little things.

So as to not get lost with multiple threads, indluge me continuing my questions in this thread.

It is kind of along the original thread anyway.

I have a bit of GoFlight gear. I've posted on/in their forum too.

What I want to do is use FSUIPC to set the assignment/s which their software is "sadly lacking".

The problem is that when I press the button the LED doesn't come on. Is there a way I can make FSUIPC turn on the LED?

[Andydigital]

I'd start another thread if I was you this GoFlight question will get lost in here and wont be answered.

[Pete Dowson]

What I want to do is use FSUIPC to set the assignment/s which their software is "sadly lacking".

The problem is that when I press the button the LED doesn't come on. Is there a way I can make FSUIPC turn on the LED?

FSUIPC's inbuilt support for GoFlight equipment is only as a source for buttons and switches. It has never provided any display facilities. To do that it would need an intimate knowledge of each type of device which can display anything, and that's not not viable in a generic support-everything program.

However, late last year I did add full Goflight programming facilities to the plug-in Lua facilities. Using short Lua programs you can send values to GoFlight digital displays and light or extinguish GoFlight LEDs. There are examples provided in the Lua package.

There is one "gotcha". Whilst the Lua library facilities for Goflight are written cooperatively, in that a Lua statement written to light or extinguish a single LED will only affect that LED and no others on the same GF unit, the GoFlight software itself isn't so friendly and assumes it is the only one using the unit. Thus, if you take over one indicator on a GF unit you really have to take them all over. I have written to the author of the GoFlight software about this but I think he's rather busy on other matters these days.

Regards

Pete