NEW FSUIPC X MACRO

[ALBERTO22]

Pete ,

Thanks for the new FSUIPC , but I have noted a problem ,I do not know if is a misinterpetration from my side or a bug.

I am using the macros( with keys ) for the OverHead panel of the 737PMDG and noted that the 2nd instruction , "when key is released ", disappear when I return back after the FS be turn off ,this means that every time I turn off the FS in the next time I turn on the FS the 2nd instruction is blank.

Any idea why this ?

Thanks and regards

Alberto

[Pete Dowson]

Thanks for the new FSUIPC , but I have noted a problem ,I do not know if is a misinterpetration from my side or a bug.

I am using the macros( with keys ) for the OverHead panel of the 737PMDG and noted that the 2nd instruction , "when key is released ", disappear when I return back after the FS be turn off ,this means that every time I turn off the FS in the next time I turn on the FS the 2nd instruction is blank.

Any idea why this ?

By "new FSUIPC", which do you mean, please? Always state version numbers, they are easy enough to find.

Please show me the [Keys] section of your FSUIPC INI file and tell me exactly what additional action you are trying to assign to which key, and I will try it here. -- but if you are not using the very latest FSUIPC version (3.822 or 4.303 at present, see Downloads announcements above) please try that to make sure it is still a problem. I hate looking for problems I've already fixed!

Regards

Pete

[ALBERTO22]

Pete ,

I am using the lasted version of FSUIPC , I suppose.

In tab "About+ Register" I saw version 3.817 dated 16 July 2008 , the version I download is the lasted in your site , Version 3.20.

The problem occurs with any key.

The instruction in " Control sent when main key released " box is not there when I turn on the FS after it has been turn off.

When I assign the keys it works 100% , the instruction in "Control sent when main key released " box is there , it is wonderful , the problem is when I turn on the FS after it has been turn off the " Control sent when main key released " box is blank.

Hope to have been clear now.

Best regards

Alberto

[Pete Dowson]

I am using the lasted version of FSUIPC , I suppose.

In tab "About+ Register" I saw version 3.817 dated 16 July 2008 , the version I download is the lasted in your site , Version 3.20.

I hope you mean 3.82, not 3.20!

Please first try 3.822 which you can obtain from the Other Downloads announcement above.

The instruction in " Control sent when main key released " box is not there when I turn on the FS after it has been turn off.

When I assign the keys it works 100% , the instruction in "Control sent when main key released " box is there , it is wonderful , the problem is when I turn on the FS after it has been turn off the " Control sent when main key released " box is blank.

Hope to have been clear now.

Yes, but I understood what you were saying in your first message!!!

What i said last time, which you appear not to have read at all was this (I have highlighted the parts asking you to do something):

Please show me the [Keys] section of your FSUIPC INI file and tell me exactly what additional action you are trying to assign to which key, and I will try it here. -- but if you are not using the very latest FSUIPC version (3.822 or 4.303 at present, see Downloads announcements above) please try that to make sure it is still a problem. I hate looking for problems I've already fixed!

The point here is that I want to test it here and to make sure I do EXACTLY the same as you I need the EXACT information I asked for. I don't ask these things for nothing!

Regards

Pete

[ALBERTO22]

Pete ,

I just installed the version 3.822 , and problem remains.

Also ,here is the FSUIPC.ini

[General]

History=UB8DM7RRCMYSXEILWG9TY

TCASid=Flight

TCASrange=40

TrafficScanPerFrame=10

AxisCalibration=No

CentredDialogue=Yes

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

ClearWeatherDynamics=Yes

OwnWeatherChanges=Yes

WeatherReadInterval=4

MoveBGLvariables=Yes

TimeForSelect=4

WeatherReadsFast=No

MainMenu=&Modules

SubMenu=&FSUIPC ...

WindSmoothing=No

AutoTaxiWind=No

PropTaxiWind=No

TimeSetMode=Partial

WhiteMessages=No

ThrottleSyncAll=No

GraduatedVisibility=No

LowerVisAltitude=0

UpperVisAltitude=25000

UpperVisibility=6000

GenerateCirrus=Yes

WindShearSharp=No

UpperWindGusts=No

ExtendMetarMaxVis=Yes

CorrectVSsign=Yes

DisconnTrimForAP=No

ZeroElevForAPAlt=Yes

AutoClearWeather=Yes

ExtendTopWind=Yes

WindSmoothness=5

SmoothPressure=No

PressureSmoothness=5

SmoothVisibility=No

VisibilitySmoothness=2

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

MinimumVisibility=0

MaximumVisibilityFewClouds=0

MaximumVisibility=0

MaximumVisibilityOvercast=0

MaximumVisibilityRainy=0

OneCloudLayer=No

ThinClouds=No

ThinThunderClouds=No

CloudThinness=1000

ThunderCloudThinness=10000

CloudTurbulence=No

CloudIcing=No

WindTurbulence=No

SuppressAllGusts=No

ExternalOptionControl=Yes

AutoTuneADF=No

KeepFS98CloudCover=No

ShowPMcontrols=No

MagicBattery=No

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

StopAutoFuel=No

TrapUserInterrupt=Yes

NavFreq50KHz=Yes

ClockSync=Yes

SmoothIAS=Yes

SetVisUpperAlt=No

VisUpperAltLimit=6000

MaxIce=3

MinIce=-1

WindSmoothingDelay=0

WindSmoothAirborneOnly=No

LimitWindVariance=No

VisSmoothingDelay=0

VisSmoothAirborneOnly=No

TrafficControlDirect=Yes

SuppressCloudTurbulence=No

SuppressWindTurbulence=No

SpoilerIncrement=512

ShortAircraftNameOk=No

FixWindows=Yes

FixControlAccel=Yes

MouseWheelTrim=No

AxisInterceptIfDirect=No

ZapSound=firework

MouseWheelTrimSpeed=1

[JoystickCalibration]

SepRevsJetsOnly=No

ApplyHeloTrim=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=0

RudderTrimControl=0

CowlFlaps1Control=0

CowlFlaps2Control=0

CowlFlaps3Control=0

CowlFlaps4Control=0

MaxSteerSpeed=60

Aileron=-16383,0,512,16383

Elevator=-16383,0,512,16383

Rudder=-16383,0,512,16383

LeftBrake=-16380,16380

Throttle1=-16380,-512,512,16380

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

[JoystickCalibration.PMDG 737-900]

ExclThrottleSet=No

SepRevsJetsOnly=No

ApplyHeloTrim=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=0

RudderTrimControl=0

CowlFlaps1Control=0

CowlFlaps2Control=0

CowlFlaps3Control=0

CowlFlaps4Control=0

MaxSteerSpeed=60

Aileron=-16383,-512,0,16383

Elevator=-16383,-512,0,16383

Rudder=-16383,-512,0,16383

LeftBrake=0,6967

Throttle1=-3744,0,512,6916

Throttle2=-6631,0,512,6913

Flaps=-10991,16192

RightBrake=-5923,6334

[JoystickCalibration.PMDG 737-800]

SepRevsJetsOnly=No

ApplyHeloTrim=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=0

RudderTrimControl=0

CowlFlaps1Control=0

CowlFlaps2Control=0

CowlFlaps3Control=0

CowlFlaps4Control=0

MaxSteerSpeed=60

Aileron=-16383,0,0,16383

Elevator=-16383,0,0,16383

Rudder=-16383,0,0,16383

LeftBrake=0,6816

RightBrake=0,7040

Throttle1=-7040,0,0,7040

Throttle2=-7040,0,0,6928

Flaps=-14073,13483

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

[buttons.PMDG 737-800]

0=P0,0,C65752,0

1=P2,0,C66066,0

2=P2,1,C66068,0

3=P2,2,C65987,0

4=P2,3,C65992,0

5=U2,3,C65988,0

6=P0,1,K67,8

[MacroFiles]

1=737 OHD

[Keys]

1=N67,8,M1:1,0

[Keys.PMDG 737-800]

1=N65,8,M1:342,0

2=67,8,M1:4,0

3=N68,8,M1:193,0

5=N78,8,M1:163,0

6=N77,8,M1:165,0,M1:164,0

8=N188,8,M1:164,0

9=N72,8,M1:189,0

10=N74,8,M1:201,0

11=N75,8,M1:200,0

12=N76,8,M1:197,0

13=N186,8,M1:198,0

14=N88,8,M1:194,0

15=N222,8,M1:40,0

16=N73,8,M1:362,0

17=N79,8,M1:363,0

18=N90,8,M1:343,0

19=N70,8,M1:344,0

20=N84,8,M1:345,0

21=N80,8,M1:346,0

22=N219,8,M1:347,0

23=N86,8,M1:195,0

24=N66,8,M1:196,0

25=N192,8,M1:161,0

26=N49,8,M1:163,0

27=81,8,M1:162,0

29=N50,8,M1:166,0

31=N51,8,M1:167,0

32=N52,8,M1:168,0

34=N53,8,M1:340,0

35=N54,8,M1:341,0

36=N55,8,M1:241,0

37=N56,8,M1:242,0

38=N57,8,M1:240,0

[buttons]

1=P0,2,K68,8

Regards

Alberto

[Pete Dowson]

I just installed the version 3.822 , and problem remains.

Okay, so I should be able to reproduce it.

Also ,here is the FSUIPC.ini

Thanks, Actually all i needed was the Keys section -- i.e. this bit:

[Keys]

1=N67,8,M1:1,0

[Keys.PMDG 737-800]

1=N65,8,M1:342,0

2=67,8,M1:4,0

3=N68,8,M1:193,0

5=N78,8,M1:163,0

6=N77,8,M1:165,0,M1:164,0

8=N188,8,M1:164,0

9=N72,8,M1:189,0

10=N74,8,M1:201,0

11=N75,8,M1:200,0

12=N76,8,M1:197,0

13=N186,8,M1:198,0

14=N88,8,M1:194,0

15=N222,8,M1:40,0

16=N73,8,M1:362,0

17=N79,8,M1:363,0

18=N90,8,M1:343,0

19=N70,8,M1:344,0

20=N84,8,M1:345,0

21=N80,8,M1:346,0

22=N219,8,M1:347,0

23=N86,8,M1:195,0

24=N66,8,M1:196,0

25=N192,8,M1:161,0

26=N49,8,M1:163,0

27=81,8,M1:162,0

29=N50,8,M1:166,0

31=N51,8,M1:167,0

32=N52,8,M1:168,0

34=N53,8,M1:340,0

35=N54,8,M1:341,0

36=N55,8,M1:241,0

37=N56,8,M1:242,0

38=N57,8,M1:240,0

So, now I need to know which of these keys I should be testing to reproduce the result you get. Don't you remember, I did ask

tell me exactly what additional action you are trying to assign to which key

You seem to miss half of what i say and ask each time, so this is getting to be really hard work!

i am not going to embark on experiments to reproduce the problem until I can do exactly what you are doing, so I need for you to TELL me. See? I cannot see your PC from here, I cannot guess exactly what you do, this is why I ask the questions. I have to repeat the same questions over and over because you seem not to read them.

Incidentally, I note that you already have one key programmed for Macro actions on both press and release. This one:

6=N77,8,M1:165,0,M1:164,0

That appears to be for an ordinary "M" key press (i.e unadorned by Shift, Control etc).

Regards

Pete

[ALBERTO22]

Pete,

I will try to show you what I am doing.

Very simple , I am assigning " keys" to buttons and switches of the Overhead panel of 737 PMDG .

For instance , I will assign the letter "U" to turn on and off the SbyRdrA switch.

1) In the tab Keys of FSUIPC I assign the letter U.

2) In box " Control sent when keys pressed " I put 737OHD:SbyRdrA " ( from the listing )

3) In box " Control sent when keys released " I put 737OHD:SbyRdrA " ( from the listing )

3) I check the "No repeats " box

4) Click in "OK", and that it's.When keeping the key "U" pressed the switch( of OHD 737 PMDG panel ) goes to off position and when released the switch goes to on position . Up to here fine.

In FSUIPC.ini , I got one line more: N85,8,M1:161,0,M1:161,0.

After turn off the FS and turn on again ,when the key "U" is pressed the switch goes to off position and when key "U" is released nothing happen ,the switch remains in the off position.

Sorry to take your time.

Regards

Alberto

[Pete Dowson]

In FSUIPC.ini , I got one line more: N85,8,M1:161,0,M1:161,0.

After turn off the FS and turn on again ,when the key "U" is pressed the switch goes to off position and when key "U" is released nothing happen ,the switch remains in the off position.

Thanks for the example. I have reproduced that and found the bug. Sorry about that. I am building versions 3.823 and 4.304 now and will upload them later today. Please watch for updates in the Downloads announcements.

[LATER]

Okay, the updated versions are now available.

Regards

Pete

[ALBERTO22]

Pete ,

Thanks for Version 3.823 now the problem above was corrected.

I have two other problems :

1) The SbyRdrB is not working , there is no way to do it works, below is a copy of the 737OHD.macro I am using , think that in SbyRdrB there is a number in excess (1).

Module8="PMDG_737NG_OHD_Flight_Controls.GAU"

161=SbyRdrA=R8:1

162=SbyRdrB=R8:21

163=AltFlpArm=R8:3

164=AltFlpUp=R8:8

165=AltFlpDn=R8:7

166=SplrA=R8:4

167=SplrB=R8:5

168=YD=R8:6

2) The " No repeats " does not works at the first time that you check the box, only if you return to tab "Keys" and check that box again.

Hope these are not a big problem for you.

Thanks a lot.

Regards

Alberto

[Pete Dowson]

1) The SbyRdrB is not working , there is no way to do it works, below is a copy of the 737OHD.macro I am using , think that in SbyRdrB there is a number in excess (1).

No idea, sorry. Does it work without the extra 1? Have you tried making your own macro for it? I only supplied the Macro files as (I hoped) working examples. I'm pretty sure i checked each one but maybe I forgot to use that one. I don't have the PMDG 737 aircraft panels installed as a rule, and i am a bit tied up at present, unable to install and check immediately.

If it works without the '1' let me know please and I'll change the example.

2) The " No repeats " does not works at the first time that you check the box, only if you return to tab "Keys" and check that box again.

Really? That's odd. It seems to work here. Are you pressing "confirm"?

I'll do some experiments, but it will be later in the week.

[LATER]

Okay, I've reproduced the problem and fixed in in FSUIPC4, so it will be the same in FSUIPC3. I'll sort it out tomorrow, probably. Look out for an update.

If the Macro is in error all I can do at present is fix my copy (delete the '1'?) and include it when i upload the updated FSUIPC3.

Regards

Pete

[ALBERTO22]

Pete,

The SbyRdrB really have a number in excess , see below the macro I have produced and it works.

[Macros]

Module="PMDG_737NG_OHD_Flight_Controls.GAU"

1=SbyRdB=R2

Another problem I found now refers to sequence of keys press and keys release .

For instance , if I have two (2) keys pressed and did not release the keys in the same sequence I pressed them , only the first key released will work , the second one when released will not have any effect in the panel.

T & A ( keys pressed in this sequence ) if I release T & A ( same sequence ) no problem .

T & A ( keys pressed in this sequence ) if I release A & T ( sequence different from key pressed sequence ) only the A will work , no action when released T.

Sorry if I sometimes repeat the problem , as English is not my native language I try to be more clear than necessary .

Thanks and regards

Alberto

[Pete Dowson]

The SbyRdrB really have a number in excess , see below the macro I have produced and it works.

[Macros]

Module="PMDG_737NG_OHD_Flight_Controls.GAU"

1=SbyRdB=R2

Okay, then it was a typo in the original file. I'll fix it on next release.

Another problem I found now refers to sequence of keys press and keys release .

For instance , if I have two (2) keys pressed and did not release the keys in the same sequence I pressed them , only the first key released will work , the second one when released will not have any effect in the panel.

T & A ( keys pressed in this sequence ) if I release T & A ( same sequence ) no problem .

T & A ( keys pressed in this sequence ) if I release A & T ( sequence different from key pressed sequence ) only the A will work , no action when released T.

Er, what sorts of keys are these? FSUIPC doesn't combinational sequences of keys other than using shifts with keys, and then the shifts must be pressed first, naturally -- the graphic or action key must be pressed last whilst the shifts are held.

The shifts supported by FSUIPC are: Shift, Ctrl, Alt (the normal ones as in Windows), plus extra ones to give a greater variety: Tab, Windows and Menu.

If you mean you are trying to use "press" and "release" of keyboard keys for different things, and sometimes in combination, then FSUIPC is completely dependent upon Windows ability to decode those events. Normal keyboards are built using matrices and many combinations of key presses don't have the results you might expect. Maybe some specific examples of what you are trying to do will help me understand. What are these "A" and "T" doing, for instance?

Maybe you should tell me exactly what you are actually trying to do. You must be using some huge keyboard emulating circuit or something I assume? I've not been asked so many questions on Key programming in the 10 years they've been available. The recent "no repeats" option was the first change for many years.

Pete

[ALBERTO22]

Pete,

The keyboard "T" I am using for the switch of the Spoiler A and the keyboard "A" I am using it for the switch of the SbyRdrB , I am not doing any combination of keyboard keys .

regards

Alberto

[ALBERTO22]

Pete ,

On time , I am using a hacked keyboard , no other circuit .I have opencokpits key send circuit but I am not using it by now.

regards

Alberto

[Pete Dowson]

The keyboard "T" I am using for the switch of the Spoiler A and the keyboard "A" I am using it for the switch of the SbyRdrB , I am not doing any combination of keyboard keys .

But why are you holding down a key for Spoiler A whilst operating SbyRdr B ?

I would like to understand the need for multiple unrelated simultaneous keypresses. It doesn't seem logical to me.

Pete

[ALBERTO22]

Hi Pete ,

I am trying to do the OHD panel the most realistic possible , it's obvious that we will have some limitations .

As you know the majority of switches in the OHD panel are toggle switches and I was trying to use a toggle switch exactly like in the original OHD panel. A switch in "on" position in the OHD panel would be a toggle hardware switch in the "on" position , the toggle switch closed , key pressed . Maybe I have to use some sort of push button simulating a toggle switch , if I do not get to have the above limitation solved.Is this a Windows limitation ?

If you or any other reading this one have any idea ,please let me know.

In meantime I will continue trying to use this excellent software .

Thanks and regards

Alberto

[Pete Dowson]

As you know the majority of switches in the OHD panel are toggle switches and I was trying to use a toggle switch exactly like in the original OHD panel.

Ah, right. So you are connecting real buttons and switches to the PC as if they are keyboard items rather than the more usual USb/joystick switch adapters or Hagstrom key encoders?

A switch in "on" position in the OHD panel would be a toggle hardware switch in the "on" position , the toggle switch closed , key pressed . Maybe I have to use some sort of push button simulating a toggle switch , if I do not get to have the above limitation solved.Is this a Windows limitation ?

I'm not sure. I thought perhaps the keyboard matrix you were using was based on AZERTY so A and T would be in the same matrix row, but I checked using Microsoft Spyxx with my Q and T keys (the same positions as A and T on an Azerty) and all KEYDOWN and KEYUP messages were seen. Only one of the two pressed actually repeats -- the last one pressed. But both KEYUPs seem to occur in either order, at least here with this Keyboard and this version of Windows.

So, I will do some tests in FSUIPC and get back to you. Quite honestly I don't know how FSUIPC could operate KEYUPs in one order and not the other if they are both arriving. I keeps no lists of keys pressed or anything.

I'll get back to you. Meanwhile, please test your Keys (A T down, A T up) with the attached DIVIEW program. It will show the exact keyboard actions and you can see if you are getting the needed KEYUP messages. Let me know please.

Regards

Pete

DIView.zip

[ALBERTO22]

Hi Pete ,

Yes , I see both key down and keyup using Diview .

regards

Alberto.

[Pete Dowson]

Yes , I see both key down and keyup using Diview .

Okay. Meanwhile, I found and fixed the problem. The difference between the Windows action in the two orders is as follows:

A downA repeats till T downT repeats till A upT still repeats .... T up. This works.

A downA repeats till T downT repeats till T upNo repeats, so no more KEYDOWNs .... A up. Doesn't work.

I found code in FSUIPC which ignores any KEYUP without a preceding KEYDOWN. In the first case the Repeats stop that code operating. In fact if you release the keys in the working order fast enough not to incur repeats between them, it fails there too.

Version 3.825 fixes this, and the "no repeats" un-setting problem too. It is now available in the Other Downloads announcement. The same things affect FSUIPC4 too and will be fixed in 4.305, later today (I have other changes in that to be tested first).

Thanks & Regards

Pete

[ALBERTO22]

Hi Pete ,

Everything working very well .Perfect.

Do you know what this means ? We can use now a simple hacked keyboard ( US 5 )and have almost a hundred switches working , instead of an eletronic device which must be programmed ,etc .

Thank you .

Best regards

Alberto