guenseli

October 22, 2009

Thanks again, Pete!

Maybe it looks very simple to you, but the following code took me 2 hours to create.

But now I can TOGGLE the two battery switches of the J41

Great :lol:


-- LEFT Battery switch TOGGLE
if ipcPARAM == 1 then   


	lbat = ipc.readLvar("L:LeftBatSwitch")

	if lbat == 1 then
   	ipc.writeLvar("L:LeftBatSwitch", 0)
	ipc.control(66587, 8028)

	elseif lbat == 0 then
   	ipc.writeLvar("L:LeftBatSwitch", 1)
	end


-- RIGHT Battery switch TOGGLE
elseif ipcPARAM == 2 then
	rbat = ipc.readLvar("L:RightBatSwitch")

	if rbat == 1 then
   	ipc.writeLvar("L:RightBatSwitch", 0)
	ipc.control(66587, 8028)

	elseif rbat == 0 then
   	ipc.writeLvar("L:RightBatSwitch", 1)
	end
end

October 22, 2009

UUUhhh heavy stuff in english language ;-)

i've understood the first part, ok.

For the second there're stil questions

As described in the FSUIPC Lua documentation, Lua programs are started with the value of "ipcPARAM" pre-set to the parameter value you enter into the Parameter field for the calling Key or Button press assignment, and you can use that parameter for whatever you like -- maybe an FS control number, or maybe just an index to switch to different parts in your Lua program.

I need an example for this, please.

Now I have understood that a LUA file with different commands could look like this:

Inside a file which is called example.lua

ipcPARAM=1

ipc.writeLvar("L:pmdg_hide_yoke", 0)

ipcPARAM=2

ipc.writeLvar("L:pmdg_hide_yoke", 1)

ipc.writeLvar("L:pmdg_hide_yoke", 2)

ipc.writeLvar("L:pmdg_hide_yoke", 3)

(its just examples, don't look at the commands as they all they same...)

As I understand it I can now choose via the FSUIPC menu for button 1 "lua example" with parameter 1

and for button 2 "lua example" with parameter 2.

Is that correct?

Is the code correct or how do I have to handle the ipcPARAM???

heavy stuff, heavy stuff :wink:

I'm very interested in this programming stuff, so forgive me my daily questions...

October 22, 2009

Hello, its me again... ;-)

I bring up this old thread because I'm still stuck on this "problem"

(I mean the initial post theme with combining LuaVars in Macros, not the last question here)

As above I'd like to get two commands together:

C66587, 8028 ; this plays a sound file in the PMDG J41 (don't ask why Rotor-Brake plays a sound file; PMDG does everything with the rotorbrake parameters)

L:LeftBatSwitch=TOG ; this toggles the Battery switch ON and OFF

As you stated above I can't combine these two commands into a Macro, e.g.

1=Batt

1.1=C66587, 8028

1.2=L:LeftBatSwitch=TOG

I'l see myself that it wouldn't work

But if I create a LUA file for the Battery switch and for all the switches coming after this, I get tons of separate LUA files for each switch in this plane.

Do you see my problem? A macro is much more handy as you write several commands in one file, named with numbers.

Do you think something like that would be possible also with LUA commands in the future?

Or do you have a solution that I just have one LUA file for different switch-commands?

Next question is, that I already now how to handle the LuaVrs in a Lua file, but I have no clue if it is possible and how to handle the comand for the rotor_brake (e.g. C66587, 8028) in a Lua File?

What ould you do to combine the Lua Var and the C66587 command for one button?

Except the possibility to assign it direct in the FSUIPC4.ini...

Hope you understood me...

And yes, I was flying yesterday without programming :wink: :lol:

October 21, 2009

I'm happy that I can get myself connected to the internet... no need till now to get something named LUA to this, too.... :lol:

But give me one or two month...

October 21, 2009

Hello Pete,

even that I haven't understood the most of your last thread, I'm sure thats really great work :wink:

thanks for your effort!!!!

guenter

(don't forget to sleep!)

October 21, 2009

But if you close DIView and start it again, does it repeat the 50%? I suspect so.

You suspect right, yes!

As all my controllers from Saitek, and Saitek isn't known for good Software, I'm not surprised...

But the X52 has also just the default windows drivers...but anyway

using your simulator for its real purpose! ;-)

honestly, playing around with FSUIPC and its possibilities is one of the main purposes for me :wink:

But sometimes flying could be also fun, you're right :lol:

October 21, 2009

Have you disabled power management on your USB sockets, in Windows?

No, just checked it again....

Actually, when you first enter the Axis assignment tab, it should show nothing

Here in my case it shows the two zeros from above...

I have tested it now with DIView-Tool:

If I start DIView it shows also 50% for each lever.

I have then moved one lever a bit and the values where correct

I have let DVIEW run for ten minutes without touching my levers and the values haven't changed or flipped back to 50%

Then I started FSX to compare between FSUIPC and DVIEW and I got the picture below

You see all three levers at 100% but FSUIPC shows zero...

Maybe this is driver related, could be. I'm out of ideas now...

I don't want to steal your time any longer with this, so we can end this story if you don't have any simple solution, too

Now I know how I can handle this issue: I just have to move one lever slightly when I'm inside FSUIPC menu...

I think thats easier than any further error searching...

But if you like to test something or would like to have more informations from me, then say it.

I'm glad if I could help you in any way!

October 21, 2009

Maybe we are one step further....

I have now made some tests and disconnected all my Joysticks and throttles, but that doesn't change anything...

But than I have sighted something:

With the last test I have just connected one of my two Saitek throttles - and not the X52, too.

And of course a virgin FSUIPC.ini

My Proplever was at 100%

The Throttlelever at 0%

The mixture lever at 100%

As I opened FSUIPC menu I saw at the Axis Assigmet tab, that the raw in and out is at 0

When I now just klick at "ok" nothing else, then all the levers move to 50% (throttle, mixture, prop)

I can read this by hovering with the mouse over the throttles - all three show exact 50%

When I enter FSUIPC menu again and move one throttle slightly, the RAW jumps to 16384 or -16384 and when I leave then the menu theres no movement...

i think that could be a very usefull information...hopefully.

btw: I have of course calibrated the levers with FSUIPC; tested also with and without calibrating

heres the picture from the Axis Assignment Tab; one picture after entering the menu without moving any lever.

The second when just moving the throttle a little bit

October 21, 2009

ok, have disabled FSUIPC.ini.

Have FSUIPC let built a new one and assigned my controls

AND: it happens again :roll:

Here's the code with the absolut virgin FSUIPC.ini:

********* FSUIPC4, Version 4.544 by Pete Dowson *********
User Name="Günter Steiner"
User Addr="guenseli@web.de"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
[Continuation log requested by user]
Running inside FSX on Windows Vista (using SimConnect Acc/SP2 Oct07)
Module base=61000000
Wind smoothing fix is fully installed
   101182 System time = 21/10/2009 12:04:18, Simulator time = 12:03:13 (11:03Z)
   101479 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
   101479 Axis 0Z=0: Action=48 (direct to calib)
   101479 Direct Axis 4, Ctrl 65765=0 : in calibration ...
   101479 ###JOY### Event seen, ID=65765 (0x000100E5), Joy=3, value=0 (Direct)
   101479 Direct Axis Control 65765=0 (cal=0): sent as Event
   101526 ***  AXIS: Cntrl= 65765 (0x000100e5), Param= 0 (0x00000000) AXIS_THROTTLE_SET
   101526 Axis 0V=0: Action=33 (direct to calib)
   101526 Direct Axis 33, Ctrl 66504=0 : in calibration ...
   101526 ###JOY### Event seen, ID=66504 (0x000103C8), Joy=32, value=0 (Direct)
   101526 Direct Axis Control 66504=0 (cal=0): sent as Event
   101526 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 0 (0x00000000) AXIS_PAN_HEADING
   101526 Axis 3X=0: Action=5 (direct to calib)
   101526 Direct Axis 5, Ctrl 66291=0 : in calibration ...
   101526 ###JOY### Event seen, ID=66291 (0x000102F3), Joy=4, value=0 (Direct)
   101526 Direct Axis Control 66291=0 (cal=0): sent as Event
   101526 ***  AXIS: Cntrl= 66291 (0x000102f3), Param= 0 (0x00000000) AXIS_PROPELLER_SET
   101526 Axis 3Y=0: Action=9 (direct to calib)
   101526 Direct Axis 9, Ctrl 66420=0 : in calibration ...
   101526 ###JOY### Event seen, ID=66420 (0x00010374), Joy=8, value=0 (Direct)
   101526 Direct Axis Control 66420=0 (cal=0): sent as Event
   101541 ***  AXIS: Cntrl= 66420 (0x00010374), Param= 0 (0x00000000) AXIS_THROTTLE1_SET
   101541 Axis 3Z=0: Action=10 (direct to calib)
   101541 Direct Axis 10, Ctrl 66423=0 : in calibration ...
   101541 ###JOY### Event seen, ID=66423 (0x00010377), Joy=9, value=0 (Direct)
   101541 Direct Axis Control 66423=0 (cal=0): sent as Event
   101541 ***  AXIS: Cntrl= 66423 (0x00010377), Param= 0 (0x00000000) AXIS_THROTTLE2_SET
   101588 Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION", Ref 2407, Index param -1 on Weather request type 5
   106065 Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION", Ref 2412, Index param -1 on Weather request type 5
   110558 Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION", Ref 2416, Index param -1 on Weather request type 5
   114021 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
[Log closed by user request, and continued in new file]
   118811 System time = 21/10/2009 12:04:36, Simulator time = 12:03:26 (11:03Z)
   118811 *** FSUIPC log file being closed
Average frame rate for running time of 43 secs = 21.8 fps
Memory managed: 74 Allocs, 52 Freed
********* FSUIPC Log file closed ***********

Could there be any "ghost" signal from one of the controllers?

But if so, why are all three controllers are affected?

And why is this just when leaving FSUIPC menu and not with other menues, e.g. FSX map or sth else?

stumped...

btw.: I have this issue a very long time, not just the last days.

I never said a word about it, because it haven't affected me too much. (And I freightened about this discussion here in english :wink: )

But the last weeks I experiment a lot with LUA and Macros and so on and must enter the menu a lot and now I'm affected a lot with it.

Unfortunately the new PMDG J41 got a complete engine damage when the PropFeather is pulled down to fast during flight... :wink:

October 21, 2009

ok, I have added and logged:

FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
[Continuation log requested by user]
Running inside FSX on Windows Vista (using SimConnect Acc/SP2 Oct07)
Module base=61000000
Wind smoothing fix is fully installed
   451483 System time = 21/10/2009 11:51:49, Simulator time = 11:46:53 (10:46Z)
   451748 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
   451748 Axis AZ=0: Action=48 (direct to calib)
   451748 Direct Axis 4, Ctrl 65765=0 : in calibration ...
   451748 ###JOY### Event seen, ID=65765 (0x000100E5), Joy=3(D), value=0 (Direct)
   451748 Direct Axis Control 65765=0 (cal=0): sent as Event
   451779 ***  AXIS: Cntrl= 65765 (0x000100e5), Param= 0 (0x00000000) AXIS_THROTTLE_SET
   451779 Axis AV=0: Action=33 (direct to calib)
   451779 Direct Axis 33, Ctrl 66504=0 : in calibration ...
   451779 ###JOY### Event seen, ID=66504 (0x000103C8), Joy=32, value=0 (Direct)
   451779Gone for filtering as axis 32, ctrl 66504=0
   451779 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 3778 (0x00000ec2) AXIS_PAN_HEADING
   451779 Axis DX=0: Action=5 (direct to calib)
   451779 Direct Axis 5, Ctrl 66291=0 : in calibration ...
   451779 ###JOY### Event seen, ID=66291 (0x000102F3), Joy=4, value=0 (Direct)
   451779 Direct Axis Control 66291=0 (cal=0): sent as Event
   451810 ***  AXIS: Cntrl= 66291 (0x000102f3), Param= 0 (0x00000000) AXIS_PROPELLER_SET
   451810 Axis DY=0: Action=9 (direct to calib)
   451810 Direct Axis 9, Ctrl 66420=0 : in calibration ...
   451810 ###JOY### Event seen, ID=65820 (0x0001011C), Joy=8, value=0 (Direct)
   451810 Direct Axis Control 65820=0 (cal=8223): sent as Event
   451810 ***  AXIS: Cntrl= 65820 (0x0001011c), Param= 8223 (0x0000201f) THROTTLE1_SET
   451810 Axis DZ=0: Action=10 (direct to calib)
   451810 Direct Axis 10, Ctrl 66423=0 : in calibration ...
   451810 ###JOY### Event seen, ID=65821 (0x0001011D), Joy=9, value=0 (Direct)
   451810 Direct Axis Control 65821=0 (cal=8224): sent as Event
   451857 ***  AXIS: Cntrl= 65821 (0x0001011d), Param= 8224 (0x00002020) THROTTLE2_SET
   451857 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 2007 (0x000007d7) AXIS_PAN_HEADING
   451904 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 1192 (0x000004a8) AXIS_PAN_HEADING
   451997 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 818 (0x00000332) AXIS_PAN_HEADING
   452060 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 645 (0x00000285) AXIS_PAN_HEADING
   452107 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 567 (0x00000237) AXIS_PAN_HEADING
   452169 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 530 (0x00000212) AXIS_PAN_HEADING
   452216 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 513 (0x00000201) AXIS_PAN_HEADING
   452325 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 506 (0x000001fa) AXIS_PAN_HEADING
   452372 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 502 (0x000001f6) AXIS_PAN_HEADING
   452419 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 500 (0x000001f4) AXIS_PAN_HEADING
   452528 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 499 (0x000001f3) AXIS_PAN_HEADING
   455258 Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION", Ref 2605, Index param -1 on Weather request type 5
   456381 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
[Log closed by user request, and continued in new file]
   463151 System time = 21/10/2009 11:52:01, Simulator time = 11:46:58 (10:46Z)
   463151 *** FSUIPC log file being closed
Average frame rate for running time of 153 secs = 21.0 fps
Memory managed: 98 Allocs, 76 Freed
********* FSUIPC Log file closed ***********

now i disable my current FSUIPC.ini and assign all axis new and see what happen...

will report soon

October 21, 2009

Let me get this straight, please -- you have it happening with axes which are assigned normally, with no ranges defined on the right-hand side with specific controls?

Yes, thats it.

I thought yesterday this happens ust with addons but on the other hand I thought about that I fly for 100% only with addons.

After trying around with the FSX default planes I have seen thats there, too.

And the normal planes are just normal assigned - no throttle ranges etc.

I've made a quick test now if I can reproduce the pan heading and it worked.

As I said yesterday, sometimes the pan heading is also affected. And pan heading is assigned to my Saitek X52 Joystick: This stick has an axis for this; its no coolie hat.

I've thought about a heardware fault, too, but I have now two saitek throttles and one x52 who are affected, so I don't think this could be.

Below is the logging from now.

As always its just the sequence when I leave FSUIPV menu by pressing "ok" (have nothing made inside the menu), do nothing and enter FSUIPC menu again.

Its with the default Beech58

Later this day I will delete my FSUIPC.ini and start all from scratch to see if theres some coding gone wrong or if this issue will happen again or not...

For now I have absolutely no other idea...

Running inside FSX on Windows Vista (using SimConnect Acc/SP2 Oct07)
Module base=61000000
Wind smoothing fix is fully installed
   192084 System time = 21/10/2009 08:54:46, Simulator time = 08:52:47 (07:52Z)
   192396 ***  AXIS: Cntrl= 65765 (0x000100e5), Param= 0 (0x00000000) AXIS_THROTTLE_SET
   192396 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 270 (0x0000010e) AXIS_PAN_HEADING
   192443 ***  AXIS: Cntrl= 66291 (0x000102f3), Param= 0 (0x00000000) AXIS_PROPELLER_SET
   192443 ***  AXIS: Cntrl= 65820 (0x0001011c), Param= 8223 (0x0000201f) THROTTLE1_SET
   192443 ***  AXIS: Cntrl= 65821 (0x0001011d), Param= 8224 (0x00002020) THROTTLE2_SET
   192443 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 394 (0x0000018a) AXIS_PAN_HEADING
   192552 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 451 (0x000001c3) AXIS_PAN_HEADING
   192583 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 478 (0x000001de) AXIS_PAN_HEADING
   192630 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 489 (0x000001e9) AXIS_PAN_HEADING
   192724 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 495 (0x000001ef) AXIS_PAN_HEADING
   192771 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 498 (0x000001f2) AXIS_PAN_HEADING
   192817 ***  AXIS: Cntrl= 66504 (0x000103c8), Param= 499 (0x000001f3) AXIS_PAN_HEADING
[Log closed by user request, and continued in new file]
   207263 System time = 21/10/2009 08:55:01, Simulator time = 08:52:56 (07:52Z)
   207263 *** FSUIPC log file being closed
Average frame rate for running time of 125 secs = 27.3 fps
Memory managed: 82 Allocs, 60 Freed
********* FSUIPC Log file closed ***********

October 20, 2009

No, it is not resolved...

same thing with other aircrafts, too. And also with the MD11 of course

Now even with a default FSX plane, the BeechBaron and the Cessna 172

So my conclusion is that it is not depending to any macros or special addons.

Its really strange, because every aircraft seems to be affected an an other way or better said, my joysticks seem to be affected.

I have had the issue also with pan view which is an axis assigned to my other joystick (X52)

Unfortunately I couldn't reproduce this.

It seems that with every new load some other axis are affected???

Here are the log from the BecchBaron

  
5440784 ***  AXIS: Cntrl= 65822 (0x0001011e), Param= 8224 (0x00002020) THROTTLE3_SET
  5440784 ***  AXIS: Cntrl= 65823 (0x0001011f), Param= 8544 (0x00002160) THROTTLE4_SET
  5440784 ***  AXIS: Cntrl= 66292 (0x000102f4), Param= 0 (0x00000000) AXIS_MIXTURE_SET
  5440800 ***  AXIS: Cntrl= 66291 (0x000102f3), Param= 0 (0x00000000) AXIS_PROPELLER_SET
  5440800 ***  AXIS: Cntrl= 65820 (0x0001011c), Param= 8223 (0x0000201f) THROTTLE1_SET
  5440800 ***  AXIS: Cntrl= 65821 (0x0001011d), Param= 8224 (0x00002020) THROTTLE2_SET
[Log closed by user request, and continued in new file]
  5500564 System time = 21/10/2009 00:23:34, Simulator time = 16:21:04 (07:21Z)
  5500564 *** FSUIPC log file being closed
Average frame rate for running time of 4101 secs = 28.3 fps
Memory managed: 5759 Allocs, 5737 Freed
********* FSUIPC Log file closed ***********

And heres the log from the default Cessna

   196779 Aircraft="Cessna Skyhawk 172SP Paint1"
   198745 ***  AXIS: Cntrl= 66292 (0x000102f4), Param= 15874 (0x00003e02) AXIS_MIXTURE_SET
   198776 ***  AXIS: Cntrl= 66292 (0x000102f4), Param= 15618 (0x00003d02) AXIS_MIXTURE_SET
   198823 ***  AXIS: Cntrl= 66292 (0x000102f4), Param= 16002 (0x00003e82) AXIS_MIXTURE_SET
   198854 ***  AXIS: Cntrl= 66292 (0x000102f4), Param= 16384 (0x00004000) AXIS_MIXTURE_SET
   199369 ***  AXIS: Cntrl= 66291 (0x000102f3), Param= 15490 (0x00003c82) AXIS_PROPELLER_SET
   199462 ***  AXIS: Cntrl= 66291 (0x000102f3), Param= 15746 (0x00003d82) AXIS_PROPELLER_SET
   199494 ***  AXIS: Cntrl= 66291 (0x000102f3), Param= 16384 (0x00004000) AXIS_PROPELLER_SET
   200383 ***  AXIS: Cntrl= 65765 (0x000100e5), Param= -16126 (0xffffc102) AXIS_THROTTLE_SET
   200430 ***  AXIS: Cntrl= 65765 (0x000100e5), Param= -15610 (0xffffc306) AXIS_THROTTLE_SET
   200617 ***  AXIS: Cntrl= 65765 (0x000100e5), Param= -15996 (0xffffc184) AXIS_THROTTLE_SET
   200648 ***  AXIS: Cntrl= 65765 (0x000100e5), Param= -16384 (0xffffc000) AXIS_THROTTLE_SET
[Log closed by user request, and continued in new file]

note that in both cases I have just left FSUIPC menu, have done nothing and then entered FSUIPC menu again.

Now I have to go to bed....

Maybe tomorrow we find a good solution for this...

thank you!

October 20, 2009

ok, I have deleted my whole axisentry for the MD-11 in the FSUIPC.ini.

For now it seems to be resolved. Since then I haven't had one single ghost movement.

Too bad, that I haven't had this idea earlier...

I hope this problem is really solved now.

Maybe you have an idea what the problem could have been, nut anyway many many thanks for your thoughts and time and support!

have a good night!

guenter

October 20, 2009

ok ok, I it is diffcult as I said... ;-)

First how the flap works (btw MD11 is McDonnell Douglas not Airbus. And today its already Boeing :wink: )

It seems more complicated as it is..

There are 6 flap positions

1) up

2) slats extended (call it flaps 5)

3) Dial a flap (where you choose a flap stage; but doesn't matter in our case - call it flap 15)

4) flap 28

5) flap 35

6) flap 50

I have assigned these 6 poitions to one of my levers, I name it "lever 6"

I have assigned it via FSUIPC by using 6 ranges and every range executes one flap position via the macro (entries number 31 to 36)

here's a log again.

I was in FSUIPC Menu and pressed "ok", then the movement of the flaps to position 15 begins, afterwards I pulled the lever 6 a little so that the flaps go up. After this I entered FSUIPC menu again.

Wind smoothing fix is fully installed

2986124 System time = 20/10/2009 21:13:06, Simulator time = 06:41:51 (20:41Z)

2986452 Macro: mouse action="PMDG_MD11.DLL":Xd4c0*Xa1cc

2986623 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70768 (0x00011470) NAV2_RADIO_SET

2989681 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70768 (0x00011470) NAV2_RADIO_SET

2992723 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70768 (0x00011470) NAV2_RADIO_SET

2994486 Macro: mouse action="PMDG_MD11.DLL":Xd480*X8bcc

2994626 Macro: mouse action="PMDG_MD11.DLL":Xd4a0*X8bcc

2995047 Macro: mouse action="PMDG_MD11.DLL":Xd480*X8bcc

2995780 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70768 (0x00011470) NAV2_RADIO_SET

2998869 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70768 (0x00011470) NAV2_RADIO_SET

[Log closed by user request, and continued in new file]

the red one is when the ghost move happens

the green one is my action to get the flaps up again

the blue one is some kind of PMDG stuff which occurs very often

After that I entered FSUIPC menu again and when I leave FSUIPC menu I can see instantly the red code - its always the same

Inside FSUIPC menu I do nothing - just klicking ok or abort

I really don't know how to explain it better - I hope you can understand me?

I do nothing, hands off of all controls but the flaps move when leaving FSUIPC menu....

October 20, 2009

Heres a complete log from starting FS to end.

Note, that first had to activate logging.

********* FSUIPC4, Version 4.544 by Pete Dowson *********
Reading options from "F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"
User Name="Günter Steiner"
User Addr="guenseli@web.de"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
Running inside FSX on Windows Vista (using SimConnect Acc/SP2 Oct07)
Module base=61000000
Wind smoothing fix is fully installed
DebugStatus=15
      124 System time = 20/10/2009 19:30:09
      124 FLT UNC path = "C:\Users\Cannelloni\Documents\Flight Simulator X-Dateien\"
      124 FS UNC path = "F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"
     1232 LogOptions=00000000 00000001
     1232 SimConnect_Open succeeded: waiting to check version okay
     3182 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
     3182 Initialising SimConnect data requests now
     3182 FSUIPC Menu entry added
     3260 C:\Users\Cannelloni\Documents\Flight Simulator X-Dateien\EDDT Standard.FLT
     3260 F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\beech_baron_58\Beech_Baron_58.AIR
    19391 F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\PMDG_MD11\MD-11.AIR
   124956 System time = 20/10/2009 19:32:14, Simulator time = 19:30:13 (18:30Z)
   125596 Aircraft="PMDG MD-11 Lufthansa"
   128030 Advanced Weather Interface Enabled
   171944 Sim stopped: average frame rate for last 48 secs = 13.0 fps
   183285 LogOptions changed, now 70000000 00000001
   183316 [Buttons] now profile-specific:
   183316    0=PB,11,CM1:63,0
   183316    0=PB,11,CM1:63,0
   183316    2=PB,10,CM1:65,0
   183316    2=PB,10,CM1:65,0
   183316    4=PB,9,CM1:64,0
   183316    4=PB,9,CM1:64,0
   183316    6=PB,8,CM1:66,0
   183316    6=PB,8,CM1:66,0
   183316    8=PB,6,CM1:59,0
   183316    8=PB,6,CM1:59,0
   183316    10=PB,7,CM1:61,0
   183316    10=PB,7,CM1:61,0
   183316    14=PA,2,C65580,0
   183316    16=PA,3,C66506,2007
   183316    17=RC,4,CM1:29,0
   183316    18=RC,5,CM1:30,0
   183316    19=RD,8,C65968,0
   183316    21=PB,4,CL17:R,0
   185142 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   186390 Macro: mouse action="PMDG_MD11.DLL":Xd480*X8bcc
   186468 Macro: mouse action="PMDG_MD11.DLL":Xd4a0*X8bcc
   186546 Macro: mouse action="PMDG_MD11.DLL":Xd4c0*Xa1cc
   186608 Macro: mouse action="PMDG_MD11.DLL":Xd500*X8bcc
   186686 Macro: mouse action="PMDG_MD11.DLL":Xd520*X8bcc
   186686 Macro: mouse action="PMDG_MD11.DLL":Xd540*X8bcc
   188246 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   191272 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   191974 Macro: mouse action="PMDG_MD11.DLL":Xd520*X8bcc
   191974 Macro: mouse action="PMDG_MD11.DLL":Xd500*X8bcc
   192052 Macro: mouse action="PMDG_MD11.DLL":Xd4c0*Xa1cc
   192193 Macro: mouse action="PMDG_MD11.DLL":Xd4a0*X8bcc
   192255 Macro: mouse action="PMDG_MD11.DLL":Xd480*X8bcc
   194377 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   197403 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   200835 [Buttons] now profile-specific:
   200835    0=PB,11,CM1:63,0
   200835    0=PB,11,CM1:63,0
   200835    2=PB,10,CM1:65,0
   200835    2=PB,10,CM1:65,0
   200835    4=PB,9,CM1:64,0
   200835    4=PB,9,CM1:64,0
   200835    6=PB,8,CM1:66,0
   200835    6=PB,8,CM1:66,0
   200835    8=PB,6,CM1:59,0
   200835    8=PB,6,CM1:59,0
   200835    10=PB,7,CM1:61,0
   200835    10=PB,7,CM1:61,0
   200835    14=PA,2,C65580,0
   200835    16=PA,3,C66506,2007
   200835    17=RC,4,CM1:29,0
   200835    18=RC,5,CM1:30,0
   200835    19=RD,8,C65968,0
   200835    21=PB,4,CL17:R,0
   201132 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   205203 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   207497 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   213456 Macro: mouse action="PMDG_MD11.DLL":Xd480*X8bcc
   215172 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   215406 Macro: mouse action="PMDG_MD11.DLL":Xd4a0*X8bcc
   215562 Macro: mouse action="PMDG_MD11.DLL":Xd4c0*Xa1cc
   215874 Macro: mouse action="PMDG_MD11.DLL":Xd4a0*X8bcc
   216092 Macro: mouse action="PMDG_MD11.DLL":Xd480*X8bcc
   218214 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   218510 Macro: mouse action="PMDG_MD11.DLL":Xd4a0*X8bcc
   220055 Macro: mouse action="PMDG_MD11.DLL":Xd480*X8bcc
   221287 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   224906 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   225296 Macro: mouse action="PMDG_MD11.DLL":Xd4c0*Xa1cc
   227964 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   230959 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   231115 Macro: mouse action="PMDG_MD11.DLL":Xd4a0*X8bcc
   231365 Macro: mouse action="PMDG_MD11.DLL":Xd480*X8bcc
   234032 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   237480 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   237558 Macro: mouse action="PMDG_MD11.DLL":Xd4c0*Xa1cc
   240538 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   242207 KEYDOWN: VK=27, Waiting=0, Repeat=N, Shifts=0
   242207 .. Key not programmed -- passed on to FS
   249929 Weather Mode now = Global
   249929 C:\Users\Cannelloni\AppData\Roaming\Microsoft\FSX\Vorheriger Flug.FLT
   254141 *** EVENT: Cntrl= 66268 (0x000102dc), Param= 0 (0x00000000) USER_INTERRUPT
   254141 *** EVENT: Cntrl= 65732 (0x000100c4), Param= 1 (0x00000001) EXIT
   257869 System time = 20/10/2009 19:34:27, Simulator time = 19:30:12 (18:30Z)
   257869 *** FSUIPC log file being closed
Average frame rate for running time of 94 secs = 13.2 fps
Memory managed: 85 Allocs, 85 Freed
********* FSUIPC Log file closed ***********

Do you always start a new log before each exit from the FSUIPC options menu?

not always, it was just in this case to show you the log.

Normally I have unchecked all log options.

the logfile above is now a new one; I've deleted the old log file before starting FSX.

Then I have activated the log options in the FSUIPC menu

The first two ro three times nothing happens, when FSUIPC menu is closed.

Then the flap starts to move as if by an invisible hand...

is what is moving your flaps? i do not know the term 2flaps dial" except as a gauge, not a control?

The MD11 has several Flap states

31=PED Flap up=RXd480*X8bcc -- means flaps up of course

32=PED Flaps Stats=RXd4a0*X8bcc -- means slats extended (Flaps one)

33=PED Flaps Dial=RXd4c0*Xa1cc -- means flaps to position "Dial a Flap"; you can choose the flaps range between 10 and 25

34=PED Flaps 28=RXd500*X8bcc -- flaps 28 and so on

35=PED Flaps 35=RXd520*X8bcc

36=PED Flaps 50=RXd540*X8bcc

And "Dial a Flap" is the position where my flaps move everytime i close FSUIPC menu

Assuming your MD11 macro is number 1 in the Macro files list, then the operating statement is presumably this one, in the Axes stuff: 9=CZ,B,-780,2816,M1:33,0

Yes, the MD11 macro is the first Macro.

And yes, M1:33 is the "Dial A Flap" entry which is executed by accident

Macro entry 31 to 36 is assigned to my right throttle.

I have made 6 ranges where the macro-commands were executed

I think thats this stuff in the FSUIPC.ini?

7=CZ,B,-16384,-15083,M1:31,0
8=CZ,B,-10012,-5331,M1:32,0
9=CZ,B,-780,2816,M1:33,0
10=CZ,B,6656,8960,M1:34,0
11=CZ,B,11264,12544,M1:35,0
12=CZ,B,12800,16383,M1:36,0

Its a little bit difficult for me to understand and answer this conversation in english, but I hope I have given you the information you wanted to know?

October 20, 2009

Now, I can just repeat this with the PMDG MD11...

But I had this even with other planes, but can only reproduce it with this bird actually.

Every time, really everytime when I leave FSUIPC menu, the flaps got to position "dial flap".

I don't press any button in FSUIPC menu, just open the menu and press cancel or ok...

This does not happen with any other kind of menu - not PMDG, nt FSX and so on.

I have two Saitek throttle quadrants, every quadrant has 3 levers.

The right quadrant has two unused levers (1,2) and the 3rd is for the flaps in the case of the MD-11

I have disabled of course tha other both levers vie FSUIPC axis assignment

I have found out that when I move one of the other two levers out of the lower position the flaps won't move from alone.

But when BOTH levers are down, the flaps move.

I've copied you all sorts of code below... hopefully we find sth

(the comments are not in the original FSUIPC4.ini of course)

My complete MD11 entry
------------------------------
[Buttons.PMDG MD-11]
0=PB,11,CM1:63,0
1=UB,11,CM1:63,0
2=PB,10,CM1:65,0
3=UB,10,CM1:65,0
4=PB,9,CM1:64,0
5=UB,9,CM1:64,0
6=PB,8,CM1:66,0
7=UB,8,CM1:66,0
8=PB,6,CM1:59,0
9=UB,6,CM1:60,0
10=PB,7,CM1:61,0
11=UB,7,CM1:62,0
12=PD,6,C66066,0
13=UD,6,C66067,0
14=PA,2,C65580,0
15=PA,6,K87,12
16=PA,3,C66506,2007
17=RC,4,CM1:29,0
18=RC,5,CM1:30,0
19=RD,8,C65968,0
21=PB,4,CL17:R,0

[Keys.PMDG MD-11]
2=96,8,66506,2020
3=97,8,66506,2001,66506,1010
4=98,8,66506,2002,66506,2004
5=99,8,66506,2007
6=100,8,66506,3002
7=101,8,66506,8003
8=102,8,66506,3001
9=103,8,66506,1005
10=104,8,66506,1000
11=105,8,66506,1009
12=115,26,M1:6,0
13=117,26,M1:7,0
15=112,26,M1:21,0
17=120,26,M1:11,0
19=118,26,M1:12,0
21=123,26,M1:19,0
23=121,26,M1:18,0
25=122,26,M1:22,0
28=51,26,M1:3,0
30=52,26,M1:5,0
32=53,26,M1:2,0
35=119,26,M1:1,0
37=87,26,M1:14,0
39=83,26,M1:16,0
42=81,26,M1:13,0
44=65,26,M1:15,0
46=57,26,M1:17,0
48=97,24,M1:23,0
51=98,24,M1:24,0
53=99,24,M1:68,0
55=100,24,M1:67,0
57=117,24,M1:53,0
59=115,24,M1:54,0
61=116,24,M1:46,0
62=120,24,M1:55,0
64=118,24,M1:56,0
66=70,24,M1:44,0
68=71,24,M1:43,0
70=119,24,M1:44,0
72=83,24,M1:71,0
74=123,24,M1:57,0
76=121,24,M1:58,0
78=122,24,M1:42,0
80=72,24,M1:41,0
82=51,24,M1:49,0
84=49,24,M1:50,0
87=74,24,M1:52,0
89=69,24,M1:40,0
92=82,24,M1:39,0
94=75,24,M1:38,0
97=84,24,M1:37,0
99=50,26,M1:4,0
101=68,24,M1:42,0
104=90,24,M1:37,0
106=85,24,M1:37,0
107=114,26,M1:20,0
109=73,26,M1:9,0



[Axes.PMDG MD-11]
0=AX,256,D,45,0,0,0
1=AY,256,D,46,0,0,0
2=AZ,256,D,48,0,0,0
3=AR,256,D,47,0,0,0
4=AU,256,D,21,0,0,0
5=AV,256,D,33,0,0,0
6=CZ,256
7=CZ,B,-16384,-15083,M1:31,0
8=CZ,B,-10012,-5331,M1:32,0
9=CZ,B,-780,2816,M1:33,0
10=CZ,B,6656,8960,M1:34,0
11=CZ,B,11264,12544,M1:35,0
12=CZ,B,12800,16383,M1:36,0
13=DX,256
14=DX,B,-16384,-15863,M1:25,0
15=DX,B,-9232,-2861,M1:26,0
16=DX,B,3968,11008,M1:27,0
17=DX,B,13824,16383,M1:28,0

---------------------------------------------

[JoyNames]
AutoAssignLetters=Yes
0=Saitek X52 Pro Flight Control System
1=Logitech Extreme 3D
2=Saitek Pro Flight Quadrant
3=Saitek Pro Flight Quadrant
A=Saitek X52 Pro Flight Control System
B=Logitech Extreme 3D
C=Saitek Pro Flight Quadrant
D=Saitek Pro Flight Quadrant

[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
FlapsSetControl=0
FlapDetents=No
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
PanHeading=-16383,-902,-515,16383/8
ElevatorTrim=-16380,-129,258,16380/16
Aileron Trim=-16384,0,0,16383/4
Throttle1=-16253,-15603,-15603,16128/32
Throttle2=-16253,-14953,-14953,16128/32
Throttle3=-16253,-15863,-15863,16128/32
Throttle4=-16253,-16123,-16123,16128/32
Aileron=-16380,-512,512,10000
Elevator=-16384,0,0,16383
Rudder=-16384,-512,512,16383
Throttle=-16384,16383
SlewAlt=-16380,-512,512,16380/16
SlopeElevatorTrim=9
PropPitch=-16380,16380
Mixture=-16380,16380
SyncSlopeThrottle2=53/51,60/58,70/70,81/81,94/95,108/109
SyncSlopeThrottle3=51/51,59/58,69/70,82/81,96/95,110/109
SyncSlopeThrottle4=45/51,54/58,66/70,79/81,94/95,108/109
Flaps=-15083,16380

[Axes]
0=AX,256,D,45,0,0,0
1=AY,256,D,46,0,0,0
2=AZ,256,D,48,0,0,0
3=AR,256,D,47,0,0,0
4=AU,256,D,21,0,0,0
5=AV,256,D,33,0,0,0
6=CX,256,D,11,0,0,0
7=CY,256,D,12,0,0,0
8=CZ,256,D,6,0,0,0
9=DX,256,D,5,0,0,0
10=DY,256,D,9,0,0,0
11=DZ,256,D,10,0,0,0

My MD11 macro
----------------------------------------------
[Macros]
Module="PMDG_MD11.DLL"
1=EFIS TRFC=RX5860*X8b00
2=EFIS DATA=RX5870*X8b00
3=EFIS WPT=RX5880*X8b00
4=EFIS VOR NDB=RX5890*X8b00
5=EFIS ARPT=RX58a0*X8b00
6=EFIS MAP=RX5820*X8b00
7=EFIS PLAN=RX5830*X8b00
8=EFIS VOR=RX5840*X8b00
9=EFIS APPR=RX5850*X8b00
10=EFIS TCAS=RX58b0*X8b00
11=EFIS Range INCR=RX5900*X8b00
12=EFIS Range DECR=RX5910*X8b00
13=EFIS VOR1=RX58c0*X8b00
14=EFIS VOR2=RX58e0*X8b00
15=EFIS ADF1=RX58d0*X8b00
16=EFIS ADF2=RX58f0*X8b00
17=EFIS IN HP=RX5740*X8bcc
18=EFIS BARO DECR=RX57a0*X8bcc,13
19=EFIS BARO INCR=RX57a0*X8bcc,14
20=EFIS MIN incr=RX57f0*X8b00,14
21=EFIS MIN dec=RX57f0*X8b00,13
22=EFIS BARO pull=RX5760*Xf7cc,31
23=PED AutoBrake de=RXf8d0*X8b00
24=PED AutoBrake in=RXf8d0*X8b00,31
25=PED Retr Spoiler=RXd990*X8bcc
26=PED 1/3 Spoiler=RXd9b0*X8bcc
27=PED 2/3 Spoiler=RXd9d0*X8bcc
28=PED Full Spoiler=RXd9f0*X8bcc
29=PED DialAFlap in=RXd560*X8bcc
30=PED DialAFlap de=RXd560*X8bcc,31
31=PED Flap up=RXd480*X8bcc
32=PED Flaps Stats=RXd4a0*X8bcc
33=PED Flaps Dial=RXd4c0*Xa1cc
34=PED Flaps 28=RXd500*X8bcc
35=PED Flaps 35=RXd520*X8bcc
36=PED Flaps 50=RXd540*X8bcc
37=MCP Autoflight=RX63b0*X8b00
38=MCP Appr=RX6440*X8b00
39=MCP NAV=RX6430*X8bcc
40=MCP PROF=RX6400*X8bcc
41=MCP ALT Push=RX6490*X8bcc
42=MCP Alt Pull=RX6490*X8bcc,31
43=MCP HDG Push=RX6410*X8b00
44=MCP HDG Pull=RX6410*X8b00,31
45=MCP SPD Push=RX6450*X8b00
46=MCP SPD Pull=RX6450*X8b00,31
47=MCP IAS MACH=RX6380*X8b00
48=MCP HDG Track=RX6370*X8bcc
49=MCP VS decr=RX6330*X8bcc
50=MCP VS incr=RX6330*X8bcc,14
51=MCP FT MTR=RX6390*X8b00
52=MCP VS FPA=RX63a0*X8b00
53=MCP SPD incr=RX6470*X8bcc,14
54=MCP SPD decr=RX6470*X8bcc,13
55=MCP HDG incr=RX6310*X8b00,14
56=MCP HDG decr=RX6310*X8b00,13
57=MCP ALT incr=RX64b0*X8bcc,14
58=MCP ALT decr=RX64b0*X8bcc,13
59=Lights LDG_ON
59.1=RX3270*X8bcc
59.2=RX3290*X8bcc
59.3=RX3270*X8bcc
59.4=RX3290*X8bcc
60=Lights LDG_OFF
60.1=RX3270*X8bcc,31
60.2=RX3290*X8bcc,31
60.3=RX3270*X8bcc,31
60.4=RX3290*X8bcc,31
61=LightsTaxi_ON
61.1=RX32b0*X8bcc
61.2=RX32b0*X8bcc
62=Lights Taxi_OFF
62.1=RX32b0*X8bcc,31
62.2=RX32b0*X8bcc,31
63=Lights Nav+
63.1=RX3350*X8bcc
63.2=RX3370*X8bcc
63.3=RX33b0*X8bcc
63.4=RX3390*X8bcc
64=Lights STROBE=RX33f0*X8bcc
65=Lights BCNt=RX33d0*X8bcc
66=Lights Panel=RX3450*X8bcc
67=Traffic inc=RX7220*X8b00,31
68=Traffic dec=RX7220*X8b00
69=MCP FMS SPD=RX6300*X8b77
70=FMS SPD=RX6300*X8b21
71=FMS SPD press=RX6300*X8b77
72=L:pmdg_hide_yoke=tog
73=Ignition ON/OFF=RXcbf0*X8bcc

and here's my logging file

********* FSUIPC4, Version 4.544 by Pete Dowson *********
User Name="Günter Steiner"
User Addr="XXX"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
[Continuation log requested by user]
Running inside FSX on Windows Vista (using SimConnect Acc/SP2 Oct07)
Module base=61000000
Wind smoothing fix is fully installed
   863700 System time = 20/10/2009 17:31:21, Simulator time = 17:24:37 (16:24Z)
   864214 Macro: mouse action="PMDG_MD11.DLL":Xd4c0*Xa1cc
   865291 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   868270 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   871312 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   874370 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   877474 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   880548 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70672 (0x00011410) NAV2_RADIO_SET
   885399 *** Entered Keys option page ***
   887724 *** Exiting Keys option page ***
[Log closed by user request, and continued in new file]
   896569 System time = 20/10/2009 17:31:54, Simulator time = 17:24:54 (16:24Z)
   896569 *** FSUIPC log file being closed
Average frame rate for running time of 459 secs = 13.3 fps
Memory managed: 169 Allocs, 147 Freed
********* FSUIPC Log file closed ***********

you can see " 864214 Macro: mouse action="PMDG_MD11.DLL":Xd4c0*Xa1cc"

Thats the dial flap...

But why and from what is it started???

thanks

October 20, 2009

If you like I can check through the dialogues and make sure every button and field hand dropdown has a TAB property. But i cannot guarantee that they'll operate in any logical order.

No you don't need to.

I just wondered if theres an error or what I do wrong.

It needs just half a second to klick at "reload" now that I have my FSUIPC_menu.Lua ;-)

If it is possible to add a own command into FSUIPC would be good, but it is really not important!

For the library:

would be great if we could build up sth like that.

I will collect them and send it to you the next days...

I note it first

October 20, 2009

Hello (part 2),

yes I have many questions these days ;-)

But I think its ok to open different threads for different themes?

My new best friend LUA programming let me made a little file that allowes me to acces the FSUIPC menu with one button klick of my joy.

ipc.keypressplus(18,1,4)	-- ALT and focus to FS



ipc.keypressplus(65)			-- A for Addons
ipc.sleep(50)
ipc.keypressplus(70)			-- F for FSUIPC

ipc.keypressplus(9, 2)
ipc.keypressplus(9, 2)
ipc.keypressplus(9, 2)
ipc.keypressplus(9, 2)
ipc.keypressplus(9, 2)
ipc.keypressplus(9, 2) 	-- Buttons and switches tab
ipc.keypressplus(9, 2)	-- Key presses tab

I have then directly the "key presses" tab opened.

Now I'd like to make an other file that let me open the FSUIPC menu, klick the "reload buttons" and "reload keys" and close the menu.

Because I often use this when editing macros and so on...

Problem is now, that I can't get to the "reload" buttons in the menu...

Do you have a solution?

Or is there an other ppossibility to "reload"?

thanks as always!!!

guenter

p.s. I have now some very useful files... macros, LUAs, etc...

What do you think about some kind of macro and LUA collection? separated fo the different addons or functions?

Would be very cool, if everybody knows that he could find here some FSUIPC tricks at one point for some addons...

All the files where a lot of work and I really like to share them for as much people as possible...

I don't know if you'd like to make a separate thread or you add them by yourself in a sticky or whatever.... if you want to...

October 20, 2009

Hello,

nearly every time I leave the FSUIPC menu, the levers of my throttlequadrants "move" virtually.

Doesn't matter wich function (throttle, feather, mixture, flaps) is assigned.

E.g. I have flaps down during a flight and enter FSUIPC menu and go back to FS, the flaps in FSX will move to nearly the middle.

Same with throttles or feather...

I think that just happens with special assigned throttle controls for Addon aircraft.

I have no throttles assigend in FSX controls...completely removed any entry manually in the controls.xml

Any idea about this?

guenter

October 20, 2009

Hello,

maybe you talk about the B377???

I have the same procedure for the B377, Take it as example for your problem.

in my Macro I have the code:

10=L:CarbHeat1Switch=TOG

11=L:CarbHeat2Switch=TOG

12=L:CarbHeat3Switch=TOG

13=L:CarbHeat4Switch=TOG

Now, go to the FSUIPC.ini and edit under the [buttons.B377] (or however your aircraft name is):

16=PD,1,CM8:10,0

17=PD,1,CM8:11,0

18=PD,1,CM8:12,0

19=PD,1,CM8:13,0

You can see, that Joystick D, button 1 is assigned 4 times to Macro 8 (the B377 macro), and there the function 10 to 13...

An other trick is that you have to change the SET in the LUA Var to TOG (toggle), so you can the carbHeat use with one switch.

October 19, 2009

http://forums1.avsim.net/index.php?s=&showtopic=263966&view=findpost&p=1653563

I hope you are proud of me :lol: :lol: :lol:

October 19, 2009

Ahhh, misunderstood.

I've thought the example file is called "ipc.keypressplus"...

Now, I've found it, thanks

October 19, 2009

8. Added another new Lua facility, "ipc.keypressplus" which is able to switch focus to and from FS and deliver keystrokes to FSX's menu dialogues. Documentation and two example plug-ins are provided in the latest Lua download zip.

I'm interested in this keystrokeplus, but I can't find any documentation or examples in the Lua_download.zip?

I'm blind (what could be) or are they somewhere else?

Little advice, please!

thanks, guenter

October 17, 2009

oh, sometimes there have to be just a little dinner between question and answer:

I made it!!!! I'm so proud (don't lough!)

[Auto.PMDG MD-11]

1=Lua MD11init

and the file contains

ipc.writeLvar("L:pmdg_hide_yoke", 1)

coooooool ;-)

Thanks for the new function!!!!

October 17, 2009

Hello,

I need a little help for the new [AUTO] function and generally with the LUA thingie...

I'm sure you have documented this somewhere, but I need some direct advice with an example to get this in my mind.

situation:

I have two Lua Variables for the PMDG MD-11

L:pmdg_hide_yoke=0

(hides the pilots yoke when set to "1")

L:HIDE_OVERHEAD_SWITCHES_var=0

(hides the overhead switches to gain some frames when set to "1")

Now, I want to get this two variables into the [AUTO] function to have the yokes hidden and the overhead switches, too.

I have made a LUA file named MD11init.lua

Inside this file theres the entry:

ipc.writeLvar(pmdg_hide_yoke,1)

(thats the part where the first big error is, I think)

and in the FSUIPV4.ini theres the entry

[Auto.PMDG MD-11]

1=MD11init

(and there's the second error, I think)

It's obvisiuous that I have no clue what to do and how to handle the LVars with the [AUTO] function or how to get them into a LUA file....

:?: :?: :?: :?:

So, please be so kind and help me...!

thank you very much as ever!

guenter

Profiles

Forums

Events

Gallery

Downloads

Posts posted by guenseli

Important Information