any chance of Rudder/SlewHdg on Offset 0366=1 only?

[mtjoeng]

any chance of axis Rudder/SlewHdg on Offset 0366=1 only?

cant find in search

I want to have a - second - joystick Z

- do Rudder/slewHDG (taxi) onGROUND

- inAir slewHDG only

this can be done thru macro?

there's an offset 0366 for ground/air condition

there's no Rudder/slewHDG FSX-control (or i cant find one)

i see all the slews,

but not the combi Rudder/SlewHDG as per the dropdown

thx, mt

[Pete Dowson]

any chance of axis Rudder/SlewHdg on Offset 0366=1 only?

cant find in search

You won't find it searching because it is such an obscure requirement.

I want to have a - second - joystick Z

- do Rudder/slewHDG (taxi) onGROUND

- inAir slewHDG only

this can be done thru macro?

You could do it pretty easily using a Lua plug-in.

there's no Rudder/slewHDG FSX-control (or i cant find one)

They are separate controls. FS uses the slew set in slew mode, the flight set in flight mode.

i see all the slews,

but not the combi Rudder/SlewHDG as per the dropdown

The FSUIPC combi axis controls are there so you can do all assignments in FSUIPC without losing the ability to slew with them that you have in FS.

Regards

Pete

[mtjoeng]

You could do it pretty easily using a Lua plug-in.

i need help with Lua

because

3=RudderSlew

3.1=W0366=1,C65764 ;65764 AXIS_RUDDER_SET

3.2=W0366=1,C65869 ;65869 AXIS_SLEW_HEADING_SET

3.3=W0366=0,C65869 ;65869 AXIS_SLEW_HEADING_SET

oops :rolleyes:

(or variations of above)

doesnt work (dont even show in the dropdown)

a pointer for howto lua would be appreciated (rusty here, long time ago)

[Pete Dowson]

i need help with Lua

because

3=RudderSlew

3.1=W0366=1,C65764 ;65764 AXIS_RUDDER_SET

3.2=W0366=1,C65869 ;65869 AXIS_SLEW_HEADING_SET

3.3=W0366=0,C65869 ;65869 AXIS_SLEW_HEADING_SET

oops :rolleyes:

(or variations of above)

doesnt work (dont even show in the dropdown)

What IS that? It's no syntax I've ever invented! <G>. The W part is an offset conditional, but there must be a space after that, then a normal button assignment type. What section is this in? A Macro file with a suitable [...] heading?

a pointer for howto lua would be appreciated (rusty here, long time ago)

I can answer specific questions but I cannot enter into a tutorial here. Please use the resources supplied already -- the Lua package with documentation of the FSUIPC Lua libraries and lots of examples (all installed with FSUIPC), the Lua website, and the ample examples in the User Contributions subforum.

Regards

Pete

[mtjoeng]

What IS that? It's no syntax I've ever invented! <G>. The W part is an offset conditional, but there must be a space after that, then a normal button assignment type. What section is this in? A Macro file with a suitable [...] heading?

tried with a "space after that"

i figured, perhaps this works in the [axis], but alas

I can answer specific questions but I cannot enter into a tutorial here. Please use the resources supplied already -- the Lua package with documentation of the FSUIPC Lua libraries and lots of examples (all installed with FSUIPC), the Lua website, and the ample examples in the User Contributions subforum.

Regards

Pete

tried

rudderslew.lua

"

if ipc.readUW(0366)= 1 -- //ground=1

ipc.control(65764) -- AXIS_RUDDER_SET 65764

ipc.control(65869) -- AXIS_SLEW_HEADING_SET 65869

else

ipc.control(65869) -- AXIS_SLEW_HEADING_SET 65869

end

"

and assigned to axis (lua rudderslew)

but nothing

not sure which ipc.readUW(or other) to use

N.B also, weird sideeffect, but perhaps superflues

this lua rudderslew.lua seems to trigger FSX at load to say

'detected a problem' 'third party software .. ' 'FSUIPC4.DLL v4.726' 'do you want to run this software' etc

when i xchg back to 'FSUIPC4.DLL v4.703', no such error

thx, mt

EDIT:

found a pointer in USER CONTRIB, ill be allright

(ground=ipc.readUW(0x366))

[Pete Dowson]

tried with a "space after that"

i figured, perhaps this works in the [axis], but alas

No, never. Macros go into Macro files. The conditionals you tried are for buttons only.

ipc.control(65764) -- AXIS_RUDDER_SET 65764

ipc.control(65869) -- AXIS_SLEW_HEADING_SET 65869

else

ipc.control(65869) -- AXIS_SLEW_HEADING_SET 65869

end

but nothing

Of course.! All "SET" controls require a value, the parameter to send for that action. How else will FS know what to do? Those controls mean nothing at all without a value to work with! It's called, in FSUIPC, the 'parameter'.

this lua rudderslew.lua seems to trigger FSX at load to say

'detected a problem' 'third party software .. ' 'FSUIPC4.DLL v4.726' 'do you want to run this software' etc

No, that's nothing whatsoever to do with Lua or anything else in FSUIPC. It is simply the Trust bug in Simconnect. When that occurs FSUIPC itself hasn't even started, it's being loaded by SimConnect and checked -- see the thread about this in the FAQ subforum.

Pete

[mtjoeng]

No, never. Macros go into Macro files. The conditionals you tried are for buttons only.

well, i tried

Of course.! All "SET" controls require a value, the parameter to send for that action. How else will FS know what to do? Those controls mean nothing at all without a value to work with! It's called, in FSUIPC, the 'parameter'.

so i'm not the brightest in programming

file rudderslew.lua

attached in dropdown to Z-axis

::loop::

ground=ipc.readUW(0x366)

if ground == 0

ipc.control(65869) -- AXIS_SLEW_HEADING_SET 65869

else

ipc.control(65764) -- AXIS_RUDDER_SET 65764

ipc.control(65869) -- AXIS_SLEW_HEADING_SET 65869

end

sleep( 2000 )

goto loop

rr, no rudder?

so how wrong am i here?

[Pete Dowson]

file rudderslew.lua

attached in dropdown to Z-axis

So, it will be loaded, compiled and executed on every change in the rudder axis. Okay.

But you've programmed it as a loop? Why? Every time the axis moves you want it to run a loop with 2 second delays? Makes no sense. If you want it executed on every axis input you want it as short as possible and exiting directly it has done what you want it to o.

so how wrong am i here?

You seem to have completely missed my last reply? All axis or "SET" controls need a parameter, the value they are supposed to set. How can FS do anything with the control with no parameter? What do you think it will set for the value? (FSUIPC will simply give it zero for lack of anything different!).

You've obviously looked up the "ipc.control" function. Please notice the second parameter it can take. Also check "ipcPARAM" which will provide your Axis value. Please do read more of what is provided, and maybe look at some of the examples.

Regards

Pete