[TrackIR request - feature, move eyepoint?]

the changelog of the latest DLL shows 'move' eyepoint

this is for non trackir

somewhat farfetched perhaps

but any chance you could look into 'moving' eyepoint of TrachIR

- this would involve a dynamic eyepoint

specifically up/down - for landing

also left/right - for looking at instruments

or perhaps a EZDok version

where different eyepoints (views) could be defined & switched to

(EZDok gave me a lot of problems, perhaps you can do better)

thx

[mouselook with no Controller(s) enabled?]

sorry, mixed up, mouseview and 'mouse as yoke'

got the mousewheel working on my Logitech wireless (after plugging in a logitech wired concurrently, that took a while!)

so that's half the battle, but not Toglle

because I use TrackIR, would want to use mouseview Toggle

when my TrackIR is put in 'Pause' (so I can fixate the VC view to certain instruments, f.i.)

.. & with the mouseWheel, the nearest 'button' .. I thought, well never mind :cool:

anyway,

I just realized, I can use the new mouseview toggle control added to the button code,

on my MCP Combo, where I freeze my TrackIR

i'll test that tonight, thx

[mouselook with no Controller(s) enabled?]

mouselook with no Controller(s) enabled?

using v4.803 / saw the 'mouseview' options

mouseview works in principle, with the regular FSX keys & controllers Enabled

but I have Unchecked my "Enable Controller(s)"

assigns Shift-O key to 'mouse look toggle' or 'mouselook toggle', or same to a button

and

the cross appears / the rightbutton menu is checked

but no MouseView

what am I missing?

[PMDG Flaps FSUIPC Detents - anomaly 2&5 ??]

FSX SP2

win64

pmdg NGX

fsuipc 4.743

anyone cares to duplicate?

assigned FSuipc flaps, pmdg NGX 737-800 profile, to a Saitek Throttle Quadrant lever

then, first time ever, figured I wanted to try FSuipc "Dt" detents

tested on Default B738, 9 flap positions, 8 detents & works,

copy these to a new profile "NGX"

detents work for:

UP.1.(not2/5).10.15.25.30.Dwn(40)

goes crazy at flaps position 2 & 5 ..

(I monitor the VC Flap Lever)

(perhaps have something to do with pmdg NGX slats programming (those move at 2&5?)

anyway

anyone cares to confirm there's a problem here, perhaps its my setup

my flap detents:

..

[JoystickCalibration.NGX]

..

FlapsSetControl=0

FlapDetents=Yes

FlapStarts=-16384,-12800,-8192,-4608,520,5461,9232,13263,15212

FlapEnds=-14592,-10112,-5632,-1280,3511,7672,10662,15211,16384

here's the full

[JoystickCalibration.NGX]:

[JoystickCalibration.NGX]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=No
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
MapThr12to34=Yes
FlapsSetControl=0
FlapDetents=Yes
FlapStarts=-16384,-12800,-8192,-4608,520,5461,9232,13263,15212
FlapEnds=-14592,-10112,-5632,-1280,3511,7672,10662,15211,16384
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=-16380,-512,512,16380/8
SlopeAileron=7
Elevator=-16380,-512,512,16380/8
SlopeElevator=10
Rudder=-16380,-512,512,16380/8
SlopeRudder=10
PropPitch=-16380,16380/8
Mixture=-16380,16380/8
LeftBrake=-16380,16380/24
SlopeLeftBrake=15
RightBrake=-16380,16380/24
SlopeRightBrake=15
Throttle1=-16380,-512,512,16380/40
Throttle2=-16380,-512,512,16380/40
SyncSlopeThrottle2=26/26,127/128
Spoilers=-16380,16380/8
Flaps=0,16380/16
SlewAlt=-16380,-512,512,16380/24
SlewSide=-16380,-512,512,16380/8
SlopeSlewSide=5
SlewAhead=-16380,-512,512,16380/8
SlopeSlewAhead=5
SlewHeading=-16380,-512,512,16380/8
SlopeSlewHeading=4

[Throttle Manager to Allow Axis Forward/Reverse Toggle]

really clever idea, Im gonna try

EDIT:

tested: this is a Great Mod

(some problems with hanging REV (I suspect dirty switches perhaps?), but sort of 'cleaning themselves' now that I use these buttons more)

the 'automatic toggle back to forward throttle' is quite an experience

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

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?

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

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))

[Destination winds]

PFE Pro Emulator, as I can remember

when in cruise, has an option

to 'request' ATIS of the destination airport

and sends this to the kneeboard (with a 'ding')

so there's a way from inside FSX (dont ask me, no idea)

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

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)

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

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

[Win7 64 WideFS com3 only on client & badly behaving]

Win7 64 WideFS com3 only on client & badly behaving

have a moving map on a client running

this worked with Vista 64 on FSX box & Vista 86 on notebook

upgraded FSX box with new Win7 64 & Win7 86 on notebook

(switched to DX10 Preview now, really nice looking)

and moving map (ancient Jeppesen Flitedeck) doesnt work any more

needs to connect to a COM port (preferably COM1 or COM3, but setup would chk any COM)

or 'cannot open port'

or 'no data coming from port'

1 of the porblems might be that WideFS "WideClient 6.899"

in Win7 can only open COM3 (on my client)

"842 Opening GPSout port COM3, speed=9600 -- OK!"

any other port:

"686 Opening GPSout port COM4, speed=9600 -- FAILED!"

and tried COM1 (connecting OK, but no data = a hardware port, oops)

COM2/4/5/7/9/11/13

did a VSPE Pair with 3/4 3/2 3/5, no data

did a MixW_ComEmul, ditto, no data

i suspect it's Win7 'new&improved' security settings, but ..

- i'm giving up (back to Flightsim Commander, oh dear)

anyone has the same problem?

(P.S.

I have a line in my widefs log:

"889 LUA: "F:\WinUPD\FSX\FSUIPC & Widefs\WideClientLATEST\Initial.LUA": not found"

what is this about?)

[Toggles in WideFS]

15=Tlbt"Beacon\rLights"

you're 'doubling' a Toggle = you're toggling a toggle

beacon is defined 'Toggle Beacon' fsx control

so its a 'button'

= B

you're confusing FSX

oh dear

change T to B

[Saitek Joystick Modes]

Mtjoeng,

Thanks for your reply; unfortunately it is a bit too cryptic for me to understand.

Do you mean that you can make all 3 modes on a Saitek X52 Pro run in FSUIPC by using the file C:\.....<= ?

I have looked in my System 32 folder but cannot find the file you mention (SaiD0BAC.pr0), I recognise this as a Saitek file from the .pr0 extension. The nearest I can find to yours in my folder is SaiD0762.pr0

Can you please explain bit a bit more about what you have done to make the 3 modes work?

I appreciate your comments, it seems that others have found the same problems that I have, so we can all benfit from your knowledge.

Thanks,

Tregarth

sorry i have misread the post

read Flight YOKE, iso Flight Joystick

anyway, should be the same Saitek method though

saitek let windows "hide" the 3mode button for their software

so the Saitek software has unique access to use for their '3modes' software

if - like me - you think their software isnt clever enough for FSX

.. you seem to be stuck with 3 hidden buttons @ driver level, so FSUIPC cannot see the 3mode switch

so with the YOKE its the SaiD0BAC.pr0 file that does that trick

found with google:

"Go into C/windows/System32 and look for a file called SaiD0762.pro

(it's with the rest of the saitek driver files) and remove it.

You can then programme buttons 16,19,32 and 39.

I've done this from my first X52 and my X52pro without any ill effect."

and it seems you can get 4 xtra buttons back for fsuipc

[Saitek Joystick Modes]

.. For my needs I find that I can get by with only the Saitek profiles. I would like to use the FSU profiles but it seems senseless to have a multimode stick which needs to have work arounds to make it function "as advertised". ..

Use either the Saitek 'Mode' with software, or redefine everythiong in FSUIPC ('disable' joystick control)

for FSUIPC, to get the 3 'mode' positions back (they're reserved/hidden for Saitek software only):

Windows Saitek YOKE driver MODE 123

C:\Windows\System32\SaiD0BAC.pr0 <= mode123 <= (rename)/delete/(restart windows)

[VRInsight MCP Lua crash (no biggie) DISENGAGE switch?]

Beech King has hardly any mouse macro's to define, amazingly, tried that, and writing 2 lua lines seemed the obvious

"Mouse" macros are merely ordinary macros which contain lines generated by mouse traps.

found the 'regular' macro in the doc, I'll do that, editing a MCRO file might actually be easier then editing the ini, got to remember that

Also consider assigning to both press and release.

did that, as in your document

And also consider using, for the VRInsight MCP, fast and slow assignments -- many of the knobs gives 4 button numbers, two each way.

found fast modes in MINS BARO CRS and V/S rotary, unfortunately not is HDG SPD ALT

got my HDG in Beechking now up te speed by doubling the ini control lines, thx, mt

[VRInsight MCP Pro Support]

no i didnt miss any part

[VRInsight MCP Pro Support]

I hope you didn't think I was calling you insane, what I meant was that it would drive me insane having to set my hat switch up like that when there was no need to :)

this is rather getting insane

when you attach saitek ware, what happens is this

the HAT's configure correctly by MSFS controls 'plug and play', automatically, hands off, like an intervention of Michael

and then .. you have to delete a dozen or so Axis and Buttons, that make your aircraft run itself into the ground, instantly

can remember Saitek rudder defined with Ailerons and Elevator Axis and the like, not to mention Trim Up or Down on unwanted places etc etc etc on the Yoke, its a long list

that takes half an hour+ easy, Quadrant, Yoke, Rudder, another Quadrant, another Quadrant, another Joystick, all to clear bizarre buttons, crazy Axis

so the thing to do is delete all definition But the HAT's

if someone asks to define a HAT in a Fsuipc forum

then where does such person would mean the defining would be desired?

[VRInsight MCP Lua crash (no biggie) DISENGAGE switch?]

Yes. you seem to be forgetting that any button can operate any number of controls, simply by INI file editing. Or you could use an ordinary macro for your list of controls. You are misusing Lua, using it for things which are far beneath its capabilities unnecessarily.

indeed, multiple 'Heading Bug Inc' lines, i'll do that

Beech King has hardly any mouse macro's to define, amazingly, tried that, and writing 2 lua lines seemed the obvious

2. DISENGAGE switch on MCP Up is "on", down is "off". On is "pressed", off is "Released".

You are missing the obvious again, looking for the complex instead! On the Buttons page there are TWO places to assign things -- press and release. You are forgetting the release!

actually I was so much focussed on not editing the ini and doing it through the drop downs, I forgot about the 'easy' way, mt :D

[VRInsight MCP Pro Support]

lets leave it to her then

maybe she's sane

[VRInsight MCP Pro Support]

I was only talking about assigning the Hat Switch on the Saitek yoke from within FS, if it really appears as a hat switch in windows then it is a simple matter of assigning it in the FS controls interface which takes about 10 seconds to achieve if you have hands and eyes. If the hat switch appears as just 4 buttons then its not so simple as you have pointed out.

Ms. CathyH seems obviously a newbe

I can remember to get the serial numbers of Fsuipc working took me hours as a newbe (and is still the case when you watch this forum)

Ms. CathyH also did not inquire about FS controls, for these are defined by default by MSFS so that would be redundant advice, like me, she appears to want to diable all FS Controls. Ever tried to clean out your FS Controls? that takes many many 10 seconds, and a HAT never appears anywhere as 4 buttons, btw.

Assigning the Saitek throttle quadrant to send F2 when the levers are pulled to the reverse detent (which is a switch not an axis) is also very easy to assign in FS or FSUIPC, and also only takes a very short time to achieve.

Mr. VRInsight moderator (yes we know), many people (like me when a newbe with my 1st CH Yoke) will have no clue if its a slider or a switch

so lets disregard supposed professional near sightedness

no, flight simulator hardware add-ons are Not easy to connect

unless you fly Cessna 172 only

so let Ms. CathyH do her reading (she only has to notice the ******* in between *******)

and no, I do not think marketing speak is the holy grail towards prosperity

on the contrary

can I myself define a HAT in 10 minutes, sure, now I can, after owning fsuipc for 6 years

(its late Andy)

[VRInsight MCP Lua crash (no biggie) DISENGAGE switch?]

got a brandnew MCP combo (after a month+ waiting) in exchange for my faulty returned one

(~6.5 months, LCD's garbage output, - huge - Schiphol airport shop 10 minutes to drive, me lucky, now)

hip hurray

anyway

VSPE pair COM7<>COM8

[Programs]

Run1=READY,CLOSE,g:\Program Files (x86)\SerialFP2\SerialFP2.exe

[VRInsight]

1=COM5, COM8

1. Lua crash

programming default Beech King, many dials work without programming

([Aircraft7] Module = SFP2_MCP_DEFAULT_FSUIPC.dll KeyMap1 = .dat)

lights, prop sync, via mouse macro's etc, no problem, all is well, but

HDG bug dreadfully slow, so create

kingHDGinc.LUA:

-- 65879 HEADING_BUG_INC

ipc.control(65879)

ipc.control(65879)

to double the speed, but after 10+ turns, crashes FSX

when inserting sleep

kingHDGinc.LUA:

ipc.sleep(50)

ipc.control(65879)

ipc.sleep(50)

ipc.control(65879)

sleep(50) makes unusefull anyway, for it is as slow as without, but also crashes fsx

fsuipc log ends with

..

721005 [buttons.Beech King Air 350 Paint1] 608=P257,17,CL12:R,0

721052 Button changed: bRef=0, Joy=257, Btn=17, Released

721052 [buttons.Beech King Air 350 Paint1] 649=U257,17,CL12:R,0

721083 Button changed: bRef=0, Joy=257, Btn=17, Pressed

721083 [buttons.Beech King Air 350 Paint1] 608=P257,17,CL12:R,0

721115 Button changed: bRef=0, Joy=257, Btn=17, Released

721115 [buttons.Beech King Air 350 Paint1] 649=U257,17,CL12:R,0

****crash****

regular right and left Heading Bug Inc or Dec work without a hitch

what could i do? am i missing something?

also:

of course I first named Lua:

kingairHDGincrease.LUA

and forgotten my first encouter with 'Lua file name too long' (silly me, year(s) ago)

and (of course?) nothing happens, and eats time and effort

and would like to request an error flag for this (perhaps not showing in dropdown?) ? (for next time silly, Im getting old)

or LUA working with long file names?

2. DISENGAGE switch on MCP

when toggled Up or Down triggers Rx light on MCP

but only Up seems to be noticed by Fsuipc

(at least nothing shows in the log, when down)

so I cannot program down

or am I (or MCP) missing something?

thx, great job, mt

[VRInsight MCP Pro Support]

Or just assigned it in FS like any normal sane person does, which will take all of about 10 seconds :D

that's how you did it?

your first HAT definition in 10 second?

your first reverse throttle in a seperate 3 engine MD11 aircraft model in 10 seconds?

that's also how your nose grew a couple of inches in the last 10 seconds :twisted:

[VRInsight MCP Pro Support]

Thanks for all the help, Pete, much appreciated. Quick question, how can I program my Saitek Yoke hat switch via FSUIPC so it pans smoothly,

dear fellow Saitek user,

you (unfortunately) need to learn how to read/edit your fsuipc.ini

and/or know exactly how it is defined in your fsuipc interface showing;

'Buttons + Switches' menu in the Interface with the

'Select for FS control' checkbox (up right)

dropdown menu 'Control send when button pressed', to be used for Panning, involving

a 'parameter' box that defaults to 0 or Empty

a checkbox 'Control to repeat while held' will write "R" to the fsuipc.ini, to be used for Panning

dropdown menu 'Control send when button RELEASED' not to be used for Panning

(middle checkbox "Aircraft specific" you will want to use when defining Reverse Throttle with different engine aircraft, get to that later)

I have my Saitek configered/checked, referenced to

the "List of FSX controls.pdf" doc's (learn to search it quickly)

'' values, the numbers

the controls named f.i.:

'PAN_DOWN, xx_LEFT, xx_RIGHT' etc. and to be repeated when held 'R'

and

in the fsuipc.in will show up in the [buttons] section as:

210=RJ,32,C65734,0

and means;

210(starting any high number for Line Numbering)=R(for 'repeat')J(your 'Joystick Letter' in Fsuipc menu when you press),32(button number when you press),C(precedes a Control)65734(=control PAN_RIGHT_UP),0(defaults parameter 0)

and the full 8 directions being;

"List of FSX controls.pdf" your pan has 8 'buttons' up, upleft, left, leftdown, etc:

PAN_DOWN 65735

PAN_LEFT 65671

PAN_LEFT_DOWN 65855

PAN_LEFT_UP 65854

PAN_RIGHT 65672

PAN_RIGHT_DOWN 65857

PAN_RIGHT_UP 65856

PAN_UP 65734

so my

[buttons]

(will add line numbering in sequence what is found there before,

but I edit to 'HighUp' sequence, 'out of the way',

so I do not even repeat this block of line in specific other aircraft,

f.i. [buttons.FeelThere Boeing] or [buttons.Piper PA31T], and

this will be remembered for these other planes

(not sure if it's supposed to be like this, but laziness was involved))

has added:

210=RJ,32,C65734,0

211=RJ,33,C65856,0

212=RJ,34,C65672,0

213=RJ,35,C65857,0

214=RJ,36,C65735,0

215=RJ,37,C65855,0

216=RJ,38,C65671,0

217=RJ,39,C65854,0

for my Saitek at "J", and hat buttons 32-39

*******************

and is done through the Fsuipc interface (bar errors, if I mix up the sequence):

*******************

1. go to 'Buttons + Switches' menu in the Interface

2. press Hat (Up) button, shows Joy# and Btn# in upper middle

3. 'Select for FS control' checkbox (to define by dropdown)

4. scroll and select down to 'Pan Up'

5. keep parameter '0' or Empty

6. check box 'Control to repeat while held', this will write "R" to the fsuipc.ini, to be used for Panning (continued)

7. 'Control send when button RELEASED' not to be used for Panning (used for Cut Reverse Throttle)

8. again keep parameter '0' or Empty

and repeat for all 8 directions (middle directions Hard to toggle, good luck :)

******************

done

******************

for education and checking (and cleaning redundant) your fsuipc.ini:

I have also a MS Sidewinder FF joystick attached, same thing for that HAT:

590=RY,32,C65734,0

591=RY,33,C65856,0

592=RY,34,C65672,0

593=RY,35,C65857,0

594=RY,36,C65735,0

595=RY,37,C65855,0

596=RY,38,C65671,0

597=RY,39,C65854,0

makes sense (does it?)

also, how can I assign the F2 thrust revers to a Throttle qaudrant lever so that it works?

Saitek does not really support throttle "Cut" & Reverse <> like in the 'classic' CH Yokes

when you 'click' down to below 'horizontal'

that's really a Button, so no gradual reverse,

BUT that's exactly what you ask for, a 'F2-epeat' to Reverse after touchdown

and the control '#'s I use are

THROTTLE_DECR 65602 (checkbox 'Control to repeat while held' will write "R" to the fsuipc.ini)

THROTTLE_CUT 65604 (define this in the 'Control send when button RELEASED' so

your Throttle gets Unstuck for sure, back up to Cut)

or (multiple engines)

THROTTLE1_CUT 65967

THROTTLE1_DECR 65966

THROTTLE2_CUT 65972

THROTTLE2_DECR 65971 etc 3/4 for multiple engine sliders

for 1/2/3/4 engine planes, that I use

besides 1 original, I have 2 xtra Saitek Quadrants, so 9 sliders,

but with 6 sliders, you can of course do 4 engine jets also,

with 1 qudrant, you have to define 1 slider for left 2 engines,

1 slider for right 2 engines, and there are difinitions for that in the fsuipc interface,

Joystick calibration "3 of 11" "Seperate throttles per engine" "Map" 1->12, 2->34

and this will show up in your [buttons] like this:

50=RT,6,C65966,0 ;THROTTLE1_DECR 65966

51=UT,6,C65967,0 ;THROTTLE1_CUT 65967

52=RT,7,C65971,0 ;THROTTLE2_DECR 65971

53=UT,7,C65972,0 ;THROTTLE2_CUT 65972

R < repeat

65966 ("List of FSX controls.pdf")

T < the Letter show up in the fsuipc interface when click down

'6' < the number show up in the fsuipc interface when click down

*******************

and is done through the Fsuipc interface (bar errors, if I mix up the sequence):

*******************

1. go to 'Buttons + Switches' menu in the Interface

2. slide Throttle1 Down = slider button, shows Joy# and Btn# in upper middle (aircraft specific maybe?)

3. 'Select for FS control' checkbox (to define by dropdown)

4. scroll and select down to 'Throttel 1 Decr'

5. keep parameter '0' or Empty

6. check box 'Control to repeat while held', this will write "R" to the fsuipc.ini, to be used for continued pressing of F2

7. dropdown 'Control send when button RELEASED' to 'Throttel 1 Cut' and writes a 'U' in the fsuipc line

8. again keep parameter '0' or Empty

and repeat for all throttle sliders (or mixture cut or prop pitch feather)

******************

done

******************

for my (default flight) default 2 engine Beech King

I also have 2 slides defined for PropPitch, (could do mixture also, but lazy)

and 'reverse-down-bitton' defined as "Prop Pitch xx Decr" (repeated)

and cuts back to "Prop Pitch xx Hi' to Prop Feather (comes in handy when runaway taxiing)

of course, by now,

u have to figure out which planes will use 1 throttle, or 2 or 3 or 4

or 1 or 2 mixture, or Prop Pitch etc etc

and that's when you wnat to know how to edit your fsuipc.ini straight with

a (programmers!) text editor

(do Not use Wordpad, it leaves - invisible - formatting codes, that will ruin your effort)

not only for checkin errors, but to see what can be done with all those precious buttons and sliders

and then

you will have officialy joined the Fsuipc club :mrgreen: , mt, good night and good luck

[VRInsight MCP Combo HID?]

Sorry, all that is way over my head, or someplace. I don't know anything about "key commands" with VRI. I'm reading and writing to the devices directly.

MCPCombo could be used for the Lomac/Black Shark etc. software .. (and that I do with some trouble) .. and FSUIPC(?)

and unlike MS FS software, this software distinguishes beteen

and

shift keys (they call them 'modifiers')

I just read this probably means they're reading hardware input, other that (~virtual) 'keyboard' input

and it apears russian/korean/western hardware does weird things through an erroneously translated 'Regional' setting

other than that ..

my MCP combo just broke down and is in repair .. oh dear .. will be a week or so

thx, mt

[VRInsight MCP Combo HID?]

Ah, never mind. I can send you the stuff in anycase. You can have some fun with it. Won't be till next week -- maybe over the weekend if I get time. Send me an email as per the stickie.

will do, thx