Axis to Offset feature request...

[dcutugno]

Hi Peter, i would like to ask if it is possible to include this option directly in FSUIPC main interface, what i need is to pass a joystick axis value to an offset to resolve this problem what i did is to use a lua script but i would feel more comfortable if you can do this natively you can follow the discussion regarding this in the ast forum http://www.airsimtech.com/forum/forum_pD=286&PN=1

Also another thing is that i saw that now you can limit the range instead of -16383, but use full travel of the axis what i need is from -4096 to +16383 needed for AST throttle how i can obtain this?

Thank you for your support.

[Pete Dowson]

Hi Peter, i would like to ask if it is possible to include this option directly in FSUIPC main interface, what i need is to pass a joystick axis value to an offset

You mean, to assign the axis, in the FSUIPC axis assignments, to the "Offset Word Set" control?

I would like to understand more, please. I read through the thread you referred to and I still don't understand why you are doing what you are doing, or what is that 0x4898 is doing. Who or what is reading that? According to my list it is assigned to a Mr. Herberg for some EPIC project.

I need to understand such things so that I can be sure the solution is correct, the right way to do things.

Also another thing is that i saw that now you can limit the range instead of -16383, but use full travel of the axis what i need is from -4096 to +16383 needed for AST throttle how i can obtain this?

That's the normal calibrated range of a throttle with reverse if the AIRCRAFT CFG specifies 25% max reverse thrust. Just calibrate it.

Pete

[dcutugno]

The 4898 is used for Flaps logic in AST, what the 4898 need is the a value passed by an axis it is basically a flap lever.

So the point is this we need a custom facility to Calibrate an axis, name it for example custom axis 1 then assign the constantly updated values to an offset in this case 4898.

What i did you can understand in the lua logic script, i assigned an axis from my joystick card i took Mixture4('cause it is unused in my setup) then pass the values to offset 4898.

Hope i explained myself.

[Pete Dowson]

The 4898 is used for Flaps logic in AST, what the 4898 need is the a value passed by an axis it is basically a flap lever.

And "AST" is, what, please? Is this related to the EPIC project I mentioned, because that is what is supposed to be using that offset area?

So the point is this we need a custom facility to Calibrate an axis, name it for example custom axis 1 then assign the constantly updated values to an offset in this case 4898.

Yes, but why? What is forcing you into this weird round-about way of doing things? This is what I don't understand. What application is deliberately using private offsets, designated for other things, and then somehow by magic expecting axis values to appear there?

Why isn't this AST, whatever it is, using the facilities available to it?

[LATER]

I found "airsimtech"'s website. They appear to be using FSUIPC commercially, for very expensive packages, without an agreement or license, and furthermore, they are using offsets without requesting any allocation. I don't really think you can expect me to support them in such circumstances? In any case, if they are forcing you into the roundabout methods you seem to be asking for, they are doing things wrong in the first place. I respectfully suggest you deal with them on this matter. :-(

Regards

Pete

[dcutugno]

And "AST" is, what, please? Is this related to the EPIC project I mentioned, because that is what is supposed to be using that offset area?

AST is a company like Projec Magenta but they do a more specific Airbus suite.

Yes, but why? What is forcing you into this weird round-about way of doing things? This is what I don't understand. What application is deliberately using private offsets, designated for other things, and then somehow by magic expecting axis values to appear there?

Why isn't this AST, whatever it is, using the facilities available to it?

Don't know why they use those specific offsets, the only thing i know is that they use the 4898 take the values then control the fs flaps by using their logic 'cause the airbus logic acts different on flaps.

As you can see we asked in their forum but nothing happens so i have had to invent some way to do this, maybe they used an epic card before but now it is useless.

If i used a pots in an opencockpits card we can use SIOC, but using a joystick card i was forced thanks to LUA to reprogram it...

[LATER]

I found "airsimtech"'s website. They appear to be using FSUIPC commercially, for very expensive packages, without an agreement or license, and furthermore, they are using offsets without requesting any allocation. I don't really think you can expect me to support them in such circumstances? In any case, if they are forcing you into the roundabout methods you seem to be asking for, they are doing things wrong in the first place. I respectfully suggest you deal with them on this matter. :-(

Regards

Pete

So can't you help us on that?

[Pete Dowson]

So can't you help us on that?

Well, I would like to know why they are making it so difficult for you. After all, it looks like you paid a lot of money for their software. And they should certainly write to me to arrange a proper license for their, till now, apparently free use of FSUIPC, saving them a lot of work. I'm not really terribly inclined to solve their problems in such a situation.

If there really was a good reason (which there is not), and truly no other way (which there is -- you found it, via Lua) then I might relent and do some work on it one day (it wouldn't be soon in any case, too much on). But I think this is wrong in any case, and you have a workaround you can use until you can get this AST company to sort things out and do it properly.

Regards

Pete

[Pete Dowson]

The 4898 is used for Flaps logic in AST, what the 4898 need is the a value passed by an axis it is basically a flap lever.

I've been doing some more work this week on FSUIPC, and I tried an experiment.

If you assigned your axis to any normal FS control, such as the flaps, whatever (it doesn't matter), THEN load up the FSUIPC INI file into a text editor, you can change the assignment to be one to an FSUIPC offset control.

To take an example. In my [Axes] section, of the INI file, I had this line:

2=BR,256,F,65696,0,0,0

This is basically assigning joystick B, axis R (*rudder) to the FS "Rudder Set" control (number 65696.

If I change the 65696 to x020066C0:

2=BR,256,F,x020066C0,0,0,0

and tell FSUIPC to reload the assignments (in the Axes tab), then the axis value is written to the 16-bit word at offset 66C0. The x0200xxxx format is from the list of additional FSUIPC controls given in the Advanced User's manual.

I could, if needed, actually have the value going to FS's rudder as well as offset 66C0:

2=BR,256,F,65696,x020066C0,0,0

In fact you can do up to 4 different actions, using the 4 places here.

Note that having done this you cannot edit or reassign that axis in the dialogue without losing this action. The dialogue does recognise the "Offset word set" control, and lists it so, but it will write it back with a zero offset because there's no way in the dialogue to specify offsets. You end up with x02000000 which you'd need to change again to include the offset.

I hope this helps you. Sorry about the delay.

Regards

Pete

[dcutugno]

Peter you're the man! Your support is great!

At the moment i can't try it in my sim to see the results, can you tell me if it is better using my lua script or assign it directly in fsuipc .ini? Ok now it will be great if you can add copy to offset xxxx in the interface tabs and we will be ok, i think it is one missing function in the FSUIPC not only for the AST, 'cause many Interface like FDS or opencockpit use Joystick emulation. So it will be great if we can program or re-route a joystick axis value to the specific offset.

Best regards,

[Pete Dowson]

At the moment i can't try it in my sim to see the results, can you tell me if it is better using my lua script or assign it directly in fsuipc .ini?

That's up to you. with the Lua method you have the opportunity to manipulate or calibrate the values, which you cannot do with the Offset control, which would simply write what it sees,

Ok now it will be great if you can add copy to offset xxxx in the interface tabs and we will be ok

No, i really don't want to do that. I'd have to remove two of the 4 possible assignments for an axis, and I cannot remove capabilities like that to make room for a minority requirement which is easy enough to do via INI file editing. After all, most button conditional programming or multi-action needs also have to be met by INI file editing.

If I was really good at user interface design I'd make everything doable that way, but I'm not, and even the simplest things in a UI take me longer than complex facilities internally.

Regards

Pete

[Pete Dowson]

Ok now it will be great if you can add copy to offset xxxx in the interface tabs and we will be ok

With reference to that request, and my reply:

No, i really don't want to do that. I'd have to remove two of the 4 possible assignments for an axis, and I cannot remove capabilities like that to make room for a minority requirement which is easy enough to do via INI file editing. After all, most button conditional programming or multi-action needs also have to be met by INI file editing.

If I was really good at user interface design I'd make everything doable that way, but I'm not, and even the simplest things in a UI take me longer than complex facilities internally.

I woke up Saturday morning with a bright idea -- of how to do it quite easily. So I have now done it and tested it. Please see the Updates Announcement above. With FSUIPC 3.918 or 4.525 you can assign axes to up to 2 offsets right there in the Axis Assignments tab.

Regards

Pete

[dcutugno]

Peter i was out on holiday, i will check the new version and see how it works, without you FS will not be the same! many thanks.