Mark Hargrove Posted June 22, 2016 Report Posted June 22, 2016 I've been using FSUIPC for years but just recently have tried to map a button press to a keypress event for the first time. The process seems simple -- but when the button is pressed (on one of my Saitek throttle quadrants), it doesn't actually do anything. I'm running P3D v3.3.5 Professional Plus and FSUIPC v4.955c. To make troubleshooting easier, I mapped 'Q' (toggle sound) to a button. The fsuipc.ini file definition is: 14=PQ,2,K81,8 -{Key press: Q}- When I run the sim with logging for buttons and keys turned on, I see the following in the console log when I press the mapped button: 503891 Button changed: bRef=0, Joy=1 (Q), Btn=2, Pressed 503891 [Buttons] 14=PQ,2,K81,8 503891 SendKeyToFS(00000051=[Q], KEYDOWN) ctr=0 503906 Sending WM_KEYDOWN, Key=81 (Scan code 16), Ctr=1 504000 SendKeyToFS(00000051=[Q], KEYUP) ctr=0 504000 Sending WM_KEYUP, Key=81 (Scan code 16), Ctr=1 504031 Button changed: bRef=0, Joy=1 (Q), Btn=2, Released 504031 [Buttons] 14=PQ,2,K81,8 ...which sure seems to indicate that 'Q' was sent to the sim -- but the sound does not toggle off. Simply typing 'Q' from the keyboard produces: 752375 KEYDOWN: VK=81, Waiting=0, Repeat=N, Shifts=0 752375 .. Key not programmed -- passed on to FS 752547 KEYUP: VK=81, Waiting=0 ...and the sound does toggle. I'm at a bit of a loss here -- does anybody have any suggestions for further troubleshooting? -M.
Pete Dowson Posted June 22, 2016 Report Posted June 22, 2016 3 hours ago, Mark Hargrove said: When I run the sim with logging for buttons and keys turned on, I see the following in the console log when I press the mapped button: 503891 Button changed: bRef=0, Joy=1 (Q), Btn=2, Pressed 503891 [Buttons] 14=PQ,2,K81,8 503891 SendKeyToFS(00000051=[Q], KEYDOWN) ctr=0 503906 Sending WM_KEYDOWN, Key=81 (Scan code 16), Ctr=1 504000 SendKeyToFS(00000051=[Q], KEYUP) ctr=0 504000 Sending WM_KEYUP, Key=81 (Scan code 16), Ctr=1 504031 Button changed: bRef=0, Joy=1 (Q), Btn=2, Released 504031 [Buttons] 14=PQ,2,K81,8 ...which sure seems to indicate that 'Q' was sent to the sim -- but the sound does not toggle off. There's been no change in how key presses are sent for many years, and as far as I can tell it works no differently in P3D 3.3.5 than in any previous version or FSX. If you enable Event logging too you'd see that the Sound toggle event will be sent by FS as a result of the keypress. 3 hours ago, Mark Hargrove said: Simply typing 'Q' from the keyboard produces: 752375 KEYDOWN: VK=81, Waiting=0, Repeat=N, Shifts=0 752375 .. Key not programmed -- passed on to FS 752547 KEYUP: VK=81, Waiting=0 ...and the sound does toggle. Well, there's no difference. Both logging is correct. The "Key not programmed" bit is not present with the button assignment simply because FSUIPC is not intercepting Key Presses that it sends. If it did, and you'd programmed that keypress in FSUIPC, it could easily end in infinite loops being created. I have the Q keypress assigned in P3D 3.3.5 to its default, the sound toggle. I assign a button to send a Q keypress. Here is what it looks like pressing Q on the keyboard: 582320 KEYDOWN: VK=81, Waiting=0, Repeat=N, Shifts=0 582320 .. Key not programmed -- passed on to FS 582320 *** EVENT: Cntrl= 65552 (0x00010010), Param= 0 (0x00000000) SOUND_TOGGLE 582476 KEYUP: VK=81, Waiting=0 And here is me using the button I assigned to press Q: 195360 Button changed: bRef=0, Joy=101, Btn=0, Pressed 195360 [Buttons] 126=P101,0,K81,8 195360 SendKeyToFS(00000051=[Q], KEYDOWN) ctr=0 195360 JoystickValues PCnum=0, dwCount=1, data[2]={00000065 00000001} 195360 Sending WM_KEYDOWN, Key=81 (Scan code 16), Ctr=1 195469 SendKeyToFS(00000051=[Q], KEYUP) ctr=0 195469 KEYDOWN: VK=81, Waiting=0, Repeat=N, Shifts=0 195469 .. Key not programmed -- passed on to FS 195469 Sending WM_KEYUP, Key=81 (Scan code 16), Ctr=1 195469 *** EVENT: Cntrl= 65552 (0x00010010), Param= 0 (0x00000000) SOUND_TOGGLE 195469 KEYUP: VK=81, Waiting=0 195563 Button changed: bRef=0, Joy=101, Btn=0, Released 195563 [Buttons] 126=P101,0,K81,8 195563 JoystickValues PCnum=0, dwCount=1, data[2]={00000065 00000000} Now if you compare this to your log extract you'll see that the ".. Key not programmed -- passed on to FS" bit is missing in yours. I don't know why that might be, except for the possibility of something else having the Focus at the time maybe, or intercepting the keypress before FSUIPC sees it. I don't *think* there are any FSUIPC options which alter this behaviour, but if you show me your FSUIPC4.INI file I will check it out. BTW, just as a matter of interest, if I program keypress Q to "sound toggle" in FSUIPC instead of relying onthe P3D assignment, I get the same end result but it is FSUIPC sending the event instead. Here: 1290612 Button changed: bRef=0, Joy=101, Btn=0, Pressed 1290612 [Buttons] 126=P101,0,K81,8 1290627 SendKeyToFS(00000051=[Q], KEYDOWN) ctr=0 1290627 JoystickValues PCnum=0, dwCount=1, data[2]={00000065 00000001} 1290627 Sending WM_KEYDOWN, Key=81 (Scan code 16), Ctr=1 1290627 KEYDOWN: VK=81, Waiting=0, Repeat=N, Shifts=0 1290627 FS Control Sent: Ctrl=65552, Param=0 1290627 .. This key is programmed in FSUIPC4 'Keys' options 1290627 *** EVENT: Cntrl= 65552 (0x00010010), Param= 0 (0x00000000) SOUND_TOGGLE 1290768 Button changed: bRef=0, Joy=101, Btn=0, Released 1290768 [Buttons] 126=P101,0,K81,8 1290783 SendKeyToFS(00000051=[Q], KEYUP) ctr=0 1290783 JoystickValues PCnum=0, dwCount=1, data[2]={00000065 00000000} 1290783 Sending WM_KEYUP, Key=81 (Scan code 16), Ctr=1 1290846 KEYUP: VK=81, Waiting=0 The order of the logging ("Control Sent" before "This key is programmed") is only odd here because there are several things happening all at once and all competing for the log addition. Naturally the key programming in FSUIPC is detected before the control is sent, but the logging is just after. Pete
Mark Hargrove Posted June 23, 2016 Author Report Posted June 23, 2016 With event logging turned on as well as buttons/switches logging I get: 405875 Button changed: bRef=0, Joy=1 (Q), Btn=2, Pressed 405875 [Buttons] 14=PQ,2,K81,8 405875 SendKeyToFS(00000051=[Q], KEYDOWN) ctr=0 405875 Sending WM_KEYDOWN, Key=81 (Scan code 16), Ctr=1 405984 SendKeyToFS(00000051=[Q], KEYUP) ctr=0 405984 Sending WM_KEYUP, Key=81 (Scan code 16), Ctr=1 406047 Button changed: bRef=0, Joy=1 (Q), Btn=2, Released 406062 [Buttons] 14=PQ,2,K81,8 ...but sound doesn't toggle. If I switch the button action over to a FS 'control' event like you did it toggles correctly (which didn't surprise me at all; all of the other buttons I have mapped are using 'FS control' actions and work perfectly). This particular button (which is eventually going to be just one of four button actions) is to control the PMDG 737NGX "Fuel Idle/Cutoff" levers. I'll be happy to be wrong, but from the reading I've done I think the only way to control those is to use the PMDG-defined keyboard shortcuts (in this case, ctl-shift-F1, F2, F3, F4 for all four of the necessary actions). That's what started me down this path -- in the past I've only "flown" simpler aircraft that had direct control actions for any buttons I wanted to setup. I've got a multi-PC setup and I plugged a plain-old joystick into one of the "slave" PCs, configured FSUIPC exactly the same way using a button on that joystick to toggle the parking brakes (no sound on that PC) with CTL-. (period) -- and it worked perfectly. Same version of FSUIPC and of P3D. I'm kind of stumped. My FSUPIC.ini file is: [General] UpdatedByVersion=4955c History=GZWLG5SDA0MTUH1JZ4XIN InitDelayDevicesToo=No Annotate=Yes NewInterceptTextMenu=No UseSystemTime=No UseMidMouseBtn=Yes MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=No NewDeleteVehiclesForAES=No AutoScanDevices=Yes AssignJoystickIDs=Yes VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=Substring UseProfiles=Yes EnableMouseLook=No DelayedMouseLookZoom=No AxesWrongRange=No TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No InitDelay=0 GetNearestAirports=No LogOptionProtect=Yes OOMcheck=Yes OOMcheckInterval=10 WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 InitialStallTime=10 NormalStallTime=1 LuaRerunDelay=66 Console=Yes ConsoleWindow=-1123,95,-126,683 LogEvents=Yes LogButtonsKeys=Yes FSVersionUsed="Lockheed Martin® Prepar3D® v3",3.3.3.3 SimConnectUsed=3.3.0.0 [JoyNames] AutoAssignLetters=No Y=Saitek Pro Flight Yoke Y.GUID={92343EF0-3542-11E6-8006-444553540000} Q=Saitek Pro Flight Throttle Quadrant Q.GUID={92348D10-3542-11E6-8009-444553540000} R=Saitek Pro Flight Cessna Rudder Pedals R.GUID={92350240-3542-11E6-800A-444553540000} T=Saitek Pro Flight Throttle Quadrant T.GUID={92357770-3542-11E6-800D-444553540000} 0=Saitek Pro Flight Yoke 0.GUID={92343EF0-3542-11E6-8006-444553540000} 1=Saitek Pro Flight Throttle Quadrant 1.GUID={92348D10-3542-11E6-8009-444553540000} 2=Saitek Pro Flight Cessna Rudder Pedals 2.GUID={92350240-3542-11E6-800A-444553540000} 3=Saitek Pro Flight Throttle Quadrant 3.GUID={92357770-3542-11E6-800D-444553540000} [Axes] PollInterval=10 RangeRepeatRate=10 0=YX,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=YY,256,D,2,0,0,0 -{ DIRECT: Elevator }- 2=QX,256,D,9,0,0,0 -{ DIRECT: Throttle1 }- 3=QY,256,D,10,0,0,0 -{ DIRECT: Throttle2 }- 4=QZ,256,D,17,0,0,0 -{ DIRECT: PropPitch1 }- 5=RX,256,D,7,0,0,0 -{ DIRECT: LeftBrake }- 6=RY,256,D,8,0,0,0 -{ DIRECT: RightBrake }- 7=RR,256,D,3,0,0,0 -{ DIRECT: Rudder }- 8=TX,256,D,18,0,0,0 -{ DIRECT: PropPitch2 }- 9=TY,256,D,13,0,0,0 -{ DIRECT: Mixture1 }- 10=TZ,256,D,14,0,0,0 -{ DIRECT: Mixture2 }- [Buttons] PollInterval=25 ButtonRepeat=20,10 1=RY,38,C65671,0 -{PAN_LEFT}- 2=RY,32,C65734,0 -{PAN_UP}- 3=RY,34,C65672,0 -{PAN_RIGHT}- 4=RY,36,C65735,0 -{PAN_DOWN}- 5=PY,0,C1001,0 -{PTT Transmit On (SB3,RW,AVC)}- 6=UY,0,C1002,0 -{PTT Transmit Off (SB3,RW,AVC)}- 7=RY,2,C65607,0 -{ELEV_TRIM_DN}- 8=RY,3,C65615,0 -{ELEV_TRIM_UP}- 9=RY,7,C66279,0 -{RUDDER_TRIM_RIGHT}- 10=RY,6,C66278,0 -{RUDDER_TRIM_LEFT}- 11=PY,1,C65791,0 -{AUTOPILOT_OFF}- 12=PQ,0,C65752,0 -{PARKING_BRAKES}- 13=PQ,1,K190,10 -{Key press: ctl+.>key}- 14=PQ,2,K81,8 -{Key press: Q}- 15=PQ,2,K81,8 -{Key press: Q}- [AutoSave] Next=1 Interval=60 Files=10 SaveOnGround=No AutoSaveEnabled=No [GPSout] GPSoutEnabled=No [GPSout2] GPSoutEnabled=No [WideServer] WideFSenabled=Yes [Sounds] Path=C:\Prepar3D v3.3\Sound\ Device1=Primary Sound Driver Device2=Speakers (High Definition Audio Device) Device3=Digital Audio (S/PDIF) (High Definition Audio Device) Device4=SAMSUNG (2- High Definition Audio Device) Device5=Digital Audio (S/PDIF) (High Definition Audio Device) [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=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 Aileron=-16384,-512,512,16383 Elevator=-16319,-512,512,16160 Rudder=-16384,-512,512,16383 LeftBrake=-16384,16383/16 RightBrake=-16384,16383/16 [Profile.PMDG737NGX] 1=PMDG 737-800NGX PMDG House Winglets [Axes.PMDG737NGX] RangeRepeatRate=10 0=YX,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=YY,256,D,2,0,0,0 -{ DIRECT: Elevator }- 2=QX,256,D,22,0,0,0 -{ DIRECT: Spoilers }- 3=QZ,256,D,9,0,0,0 -{ DIRECT: Throttle1 }- 4=RX,256,D,7,0,0,0 -{ DIRECT: LeftBrake }- 5=RY,256,D,8,0,0,0 -{ DIRECT: RightBrake }- 6=RR,256,D,3,0,0,0 -{ DIRECT: Rudder }- 7=TX,256,D,10,0,0,0 -{ DIRECT: Throttle2 }- 8=TY,256,D,13,0,0,0 -{ DIRECT: Mixture1 }- 9=TZ,256,D,23,0,0,0 -{ DIRECT: Flaps }- [JoystickCalibration.PMDG737NGX] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=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 Aileron=-16384,-512,512,16383 Elevator=-16319,-512,512,16160 Rudder=-16384,-512,512,16383 LeftBrake=-16384,16383/16 RightBrake=-16384,16383/16 Throttle1=-16253,-512,512,16383 Throttle2=-16384,-512,512,16256 SyncSlopeThrottle2=31/29,90/89,127/128 Spoilers=-16384,16256/16 Flaps=-16384,16383/16 [Buttons.PMDG737NGX] 0=RQ,8,C65966,0 -{THROTTLE1_DECR}- 1=UQ,8,C65967,0 -{THROTTLE1_CUT}- 2=RT,6,C65971,0 -{THROTTLE2_DECR}- 3=UT,6,C65972,0 -{THROTTLE2_CUT}- 4=PQ,4,K113,11 -{Key press: ctl+shft+F2}- 5=PQ,5,K112,11 -{Key press: ctl+shft+F1}- 6=PT,0,K115,11 -{Key press: ctl+shft+F4}- 7=PT,1,K114,11 -{Key press: ctl+shft+F3}-
filippoporcari Posted June 23, 2016 Report Posted June 23, 2016 hi all. i'm also having troubles sending keystrokes non only thru FSUIPC but also using other programs. i was going to get crazy about this when i discovered this: http://stackoverflow.com/questions/31846863/sending-key-strokes-with-c-sharp-in-win10-outside-of-app and this http://visualbasic.ittoolbox.com/groups/technical-functional/visualbasic-l/win10-sendkeys-error-in-ide-5837488 i never got this problem in some 10 years...and now that i moved to win 10 for p3d 3.3.5 i got it! could win10 be responsible? all the best fil
Pete Dowson Posted June 23, 2016 Report Posted June 23, 2016 4 hours ago, Mark Hargrove said: This particular button (which is eventually going to be just one of four button actions) is to control the PMDG 737NGX "Fuel Idle/Cutoff" levers. I'll be happy to be wrong, but from the reading I've done I think the only way to control those is to use the PMDG-defined keyboard shortcuts (in this case, ctl-shift-F1, F2, F3, F4 for all four of the necessary actions). Actually, the PMDG 737NGX and 777X implementations support their own full range of additional FS controls. The start levers are defined in the list ("PMDG_NGX_SDK.h! in the NGX SDK folder) as #define EVT_CONTROL_STAND_ENG1_START_LEVER (THIRD_PARTY_EVENT_ID_MIN + 688) #define EVT_CONTROL_STAND_ENG2_START_LEVER (THIRD_PARTY_EVENT_ID_MIN + 689) In other words, add 688 or 689 to the value defined as the ID_MIN earlier in the list. You assign custom controls like this in FSUIPC as <custom control> and enter the number in the space then available. I don't know if those controls toggle, or whether you have to have a parameter (1 or 0 maybe) to set them one way or the other. (I don't use PMDG aircraft). 3 hours ago, filippoporcari said: ...and now that i moved to win 10 for p3d 3.3.5 i got it! could win10 be responsible? I don't know. Those two errors refer to C sharp and Visual Basic, and FSUIPC uses neither, but I suppose there might be something incompatible about programming keystroke inputs to programs. I've recently purchased a Surface Pro 4, and that comes with Win10 installed, so I try that -- need to install FSX on it first. I'll get back to you with results when I can, maybe next week. BTW, you have the same button sending Q twice (or rather, attempting to), so even if it did result in a "sound toggle" you'd not accomplish that: 14=PQ,2,K81,8 -{Key press: Q}-15=PQ,2,K81,8 -{Key press: Q}- Pete
Pete Dowson Posted June 23, 2016 Report Posted June 23, 2016 Wow! I got FSX-SE installed on the Surface Pro really quickly! Good fast SSD in it! I've tested button assignments to keypresses, and it works fine. So either it is NOT a Win10 problem, or your Win10 is out of date or corrupt. I think you must have something else going on there. Check what processes you have running at the time apart from FS. Here's the relevant part of the Log from the Win10 machine: 887766 Button changed: bRef=0, Joy=0 (A), Btn=0, Pressed 887766 [Buttons] 35=PA,0,K81,8 887766 SendKeyToFS(00000051=[Q], KEYDOWN) ctr=0 887781 Sending WM_KEYDOWN, Key=81 (Scan code 16), Ctr=1 887797 KEYDOWN: VK=81, Waiting=0, Repeat=N, Shifts=0 887797 .. Key not programmed -- passed on to FS 887797 *** EVENT: Cntrl= 65552 (0x00010010), Param= 0 (0x00000000) SOUND_TOGGLE 887891 SendKeyToFS(00000051=[Q], KEYUP) ctr=0 887906 Sending WM_KEYUP, Key=81 (Scan code 16), Ctr=1 887906 KEYUP: VK=81, Waiting=0 887984 Button changed: bRef=0, Joy=0 (A), Btn=0, Released 888000 [Buttons] 35=PA,0,K81,8 So, I'm sorry, but I don't know what is interfering with this on your PC, but I'd try stopping all other processes and possible some non-Microsoft services too, till you find the culprit. Pete
filippoporcari Posted June 23, 2016 Report Posted June 23, 2016 hi peter, thx SO MUCH for your fast reply ans your fast testing! (yed ssd speed is amazing :) ) i own a 320 homecockpit and on the server computer there's not so much running...btw i'll cross check it again and report to u asap. i'm running p3d 3.3.5....may be differences between fsx steam and p3d? what looks pretty strange here is that for the first week afterr the format and clean reinstall of everything keysends worked...then they started working some flights yes and some flights no...from 3 days they never work. i hate when things follow the random rule. i stress the point that NOTHING was changed in the system...no hardware and not a single line of new soft installed. an example: i have the PTT button of my sidesticks mapped to F12 thru fsuipc...F12 is assigned in Teamspeak...used this mapping for years starting from fs9 times....when button-to-key is not working the strange thing is that pressing F12 on the keyboard doesn't trigger the teamspeak ptt! only way to have it working is opening teamspeak window and pushing F12 on the keyboard with teamspeak in focus! this really looks odd and that's why i thought win10 or p3d was responsible because only differences in my setup are win10 and p3d 3.3.5. for your info this is a second win10 clean install because first time saw this i also thought win 10 could have been corrupted and so made a clean reinstall formatting. now i strongly doubt a second win10 corruption can occour :) thx really a lot for your time ans work fil
Pete Dowson Posted June 23, 2016 Report Posted June 23, 2016 37 minutes ago, filippoporcari said: i'm running p3d 3.3.5....may be differences between fsx steam and p3d? No, no difference for sending it keystrokes. That's all Windows stuff. I have tested with P3D 3.3.5 on my main PC (win7). 37 minutes ago, filippoporcari said: i stress the point that NOTHING was changed in the system...no hardware and not a single line of new soft installed. Well, something obviously changed somewhere. 37 minutes ago, filippoporcari said: this really looks odd and that's why i thought win10 or p3d was responsible because only differences in my setup are win10 and p3d 3.3.5. But you just said nothing was changed!? I'm confused. 37 minutes ago, filippoporcari said: now i strongly doubt a second win10 corruption can occour :) But have you checked that all the updates have installed? I notice there was yest another batch only 3 days ago. Anyway, for something to come between the definitely-accepted Windows API calls FSUIPC is making to get the KEYDOWN and KEYUP actions simulated (see below *) and the receipt of those messages in FSX or P3D, something is intercepting them first -- not not the real keyboard messages, which would be identical. So it must be something at a pretty low level which is interferng with the actual API calls somehow. This is why I'd suspect some service, running in the background. Pete * It uses a sort of recorded-keypress playback option which has been in Windows over many versions. The idea of using this is that the end results seen in the receiving program look identical to those it would receive from the real keyboard. The only ways it can be defeated is if the target program used a hardware-access polling method insted, which neither FSX nor P3D do. Hardly anything does, in fact.
filippoporcari Posted June 23, 2016 Report Posted June 23, 2016 hi peter, maybe i've not been clear: after they two win10 reinstalls ans after starting testings, flights and keysend working/not working nothing was changed in the system. the main change was switching to win 10 and p3d 3.3.5....that's all. yes all the windows updates are in... all the best fil
Pete Dowson Posted June 23, 2016 Report Posted June 23, 2016 30 minutes ago, filippoporcari said: the main change was switching to win 10 and p3d 3.3.5....that's all. Pretty major changes, and maybe something else you had installed is now behaving differently on Win10. Have you checked the Processes and Services running, yet? BTW in the last two messages you've been talking about "KeySend", which is the term used in FSUIPC/WideFS for special messages sent from FSUIPC to a WideClient on a network and programmed, often to a keypress, in the WideClient.INI file.. Did you really mean keypress assignments in FSUIPC, as when we started all this? Pete
filippoporcari Posted June 23, 2016 Report Posted June 23, 2016 hi peter, i'll check windows services and report but this looks strange to me. yes win10 was a huge change...but as reported during first days it worked flawlessly now not. believe me NO CHANGES at all when all this started...that's why i'm puzzled. sorry for KEYSEND....my mistake of course i meant button(joy) to key. regards fil
Pete Dowson Posted June 23, 2016 Report Posted June 23, 2016 Just now, filippoporcari said: but as reported during first days it worked flawlessly now not. believe me NO CHANGES at all when all this started...that's why i'm puzzled. Are, so P3D3.3.5 and Win10 were not a change before this happened? Sorry, it got very confusing in the messages above. So not even the Win10 updates of 3 days ago were a "change"? You see why I'm a bit dubious over this "nothing changed" claim? (If nothing changes then neither will behaviour). Pete
filippoporcari Posted June 23, 2016 Report Posted June 23, 2016 of course win10 and p3d were a change...they were THE change :) after that nothing was changed in the system apart windows updates...which never gave me this kind of issues. i'm in the cockpit buildings for some 12 years now...built a 737 dstd...then a 320 dstd which i currently own and fly...sorry if i was confusing, not my intention indeed. so if the windows updated could have caused this...this should be windows related. regards fil
Pete Dowson Posted June 23, 2016 Report Posted June 23, 2016 I'm still confused, but never mind. I can't help anyway. 12 minutes ago, filippoporcari said: of course win10 and p3d were a change...they were THE change :) But you also said, just before: 24 minutes ago, filippoporcari said: yes win10 was a huge change...but as reported during first days it worked flawlessly now not. believe me NO CHANGES at all when all this started So you already knew it couldn't be Win10 itself!? No need to reply. The repeated contradictions confused me, but it doesn't change my conclusions. Pete
filippoporcari Posted June 23, 2016 Report Posted June 23, 2016 i feel necessary a reply from my side... sorry if i generated confusion of course it was not in my mind. i don't see the contraddictions u encountered but nevermind. i just tried to make a report of what i changed in my system and which results i had...of course i thought win10 was responsible and that's why i attached the two links in my first post. sorry to have confused u peter and thx for your time fil
Mark Hargrove Posted June 24, 2016 Author Report Posted June 24, 2016 19 hours ago, Pete Dowson said: Actually, the PMDG 737NGX and 777X implementations support their own full range of additional FS controls. The start levers are defined in the list ("PMDG_NGX_SDK.h! in the NGX SDK folder) as #define EVT_CONTROL_STAND_ENG1_START_LEVER (THIRD_PARTY_EVENT_ID_MIN + 688) #define EVT_CONTROL_STAND_ENG2_START_LEVER (THIRD_PARTY_EVENT_ID_MIN + 689) In other words, add 688 or 689 to the value defined as the ID_MIN earlier in the list. You assign custom controls like this in FSUIPC as <custom control> and enter the number in the space then available. I don't know if those controls toggle, or whether you have to have a parameter (1 or 0 maybe) to set them one way or the other. (I don't use PMDG aircraft). I don't know. Those two errors refer to C sharp and Visual Basic, and FSUIPC uses neither, but I suppose there might be something incompatible about programming keystroke inputs to programs. I've recently purchased a Surface Pro 4, and that comes with Win10 installed, so I try that -- need to install FSX on it first. I'll get back to you with results when I can, maybe next week. BTW, you have the same button sending Q twice (or rather, attempting to), so even if it did result in a "sound toggle" you'd not accomplish that: 14=PQ,2,K81,8 -{Key press: Q}-15=PQ,2,K81,8 -{Key press: Q}- Pete I *thought* I'd read that such codes existed but got all twisted up by looking at the 737NGX offsets document in the FSUIPC documents folder, realizing immediately this wasn't what I was looking for, and decided I'd just imagined reading about the codes. Thanks hugely for pointing me in the right direction! Just for posterity (or if anybody else is searching, the necessary codes and parameters are 70320 Control STAND Engine 1 Start lever --- Idle: 0 Cutoff: 1 70321 Control STAND Engine 2 Start lever --- Idle: 0 Cutoff: 1 ...and these work perfectly. Separately: Yeah, I noticed that duplication of the key press shortly after I made my post -- deleting the duplicate didn't help. There's something funky going on with this particular system -- as I mentioned earlier I tested on another virtually identical instance of my simulator cluster and button-to-keypresses worked just fine. Thanks again! -M.
filippoporcari Posted June 27, 2016 Report Posted June 27, 2016 hi peter, sorry to disturb again but i tried again enabling fsuipc buttons logging... i tried pushing many times a joy button whom has been assigned sending the key CTRL+F9 after that i quit the sim pushing the ESC key. this is the log i got: 135281 LogOptions changed, now 40000000 00000001 155969 Button changed: bRef=0, Joy=0, Btn=2, Pressed 155969 [Buttons] 7=P0,2,K120,10 155969 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 155969 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 155984 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 156109 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 156109 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 156125 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 156203 Button changed: bRef=0, Joy=0, Btn=2, Released 156203 [Buttons] 7=P0,2,K120,10 156609 Button changed: bRef=0, Joy=0, Btn=2, Pressed 156609 [Buttons] 7=P0,2,K120,10 156609 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 156625 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 156641 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 156719 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 156719 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 156734 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 156781 Button changed: bRef=0, Joy=0, Btn=2, Released 156781 [Buttons] 7=P0,2,K120,10 157734 Button changed: bRef=0, Joy=0, Btn=2, Pressed 157734 [Buttons] 7=P0,2,K120,10 157734 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 157750 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 157766 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 157844 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 157844 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 157859 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 157984 Button changed: bRef=0, Joy=0, Btn=2, Released 157984 [Buttons] 7=P0,2,K120,10 168625 Button changed: bRef=0, Joy=0, Btn=2, Pressed 168625 [Buttons] 7=P0,2,K120,10 168625 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 168625 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 168641 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 168750 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 168766 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 168781 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 168891 Button changed: bRef=0, Joy=0, Btn=2, Released 168891 [Buttons] 7=P0,2,K120,10 169266 Button changed: bRef=0, Joy=0, Btn=2, Pressed 169266 [Buttons] 7=P0,2,K120,10 169266 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 169266 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 169281 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 169375 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 169375 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 169391 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 169531 Button changed: bRef=0, Joy=0, Btn=2, Released 169531 [Buttons] 7=P0,2,K120,10 170281 Button changed: bRef=0, Joy=0, Btn=2, Pressed 170281 [Buttons] 7=P0,2,K120,10 170281 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 170297 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 170313 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 170391 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 170391 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 170406 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 170453 Button changed: bRef=0, Joy=0, Btn=2, Released 170453 [Buttons] 7=P0,2,K120,10 171281 Button changed: bRef=0, Joy=0, Btn=2, Pressed 171281 [Buttons] 7=P0,2,K120,10 171281 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 171281 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 171297 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 171406 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 171422 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 171438 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 171484 Button changed: bRef=0, Joy=0, Btn=2, Released 171484 [Buttons] 7=P0,2,K120,10 171891 Button changed: bRef=0, Joy=0, Btn=2, Pressed 171891 [Buttons] 7=P0,2,K120,10 171891 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 171891 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 171906 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 172031 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 172031 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 172047 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 172125 Button changed: bRef=0, Joy=0, Btn=2, Released 172125 [Buttons] 7=P0,2,K120,10 172938 Button changed: bRef=0, Joy=0, Btn=2, Pressed 172938 [Buttons] 7=P0,2,K120,10 172938 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 172953 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 172969 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 173047 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 173047 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 173063 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 173156 Button changed: bRef=0, Joy=0, Btn=2, Released 173156 [Buttons] 7=P0,2,K120,10 173359 Button changed: bRef=0, Joy=0, Btn=2, Pressed 173359 [Buttons] 7=P0,2,K120,10 173359 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 173359 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 173375 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 173484 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 173500 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 173516 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 173531 Button changed: bRef=0, Joy=0, Btn=2, Released 173531 [Buttons] 7=P0,2,K120,10 174688 Button changed: bRef=0, Joy=0, Btn=2, Pressed 174688 [Buttons] 7=P0,2,K120,10 174688 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 174688 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 174703 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 174813 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 174828 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 174844 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 174922 Button changed: bRef=0, Joy=0, Btn=2, Released 174922 [Buttons] 7=P0,2,K120,10 175297 Button changed: bRef=0, Joy=0, Btn=2, Pressed 175297 [Buttons] 7=P0,2,K120,10 175297 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 175297 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 175313 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 175438 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 175438 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 175453 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 175531 Button changed: bRef=0, Joy=0, Btn=2, Released 175531 [Buttons] 7=P0,2,K120,10 179953 Button changed: bRef=0, Joy=0, Btn=2, Pressed 179953 [Buttons] 7=P0,2,K120,10 179953 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 179953 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 179969 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 180094 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 180094 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 180109 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 180156 Button changed: bRef=0, Joy=0, Btn=2, Released 180156 [Buttons] 7=P0,2,K120,10 180391 Button changed: bRef=0, Joy=0, Btn=2, Pressed 180391 [Buttons] 7=P0,2,K120,10 180391 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 180391 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 180406 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 180500 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 180500 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 180516 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 180594 Button changed: bRef=0, Joy=0, Btn=2, Released 180594 [Buttons] 7=P0,2,K120,10 180906 Button changed: bRef=0, Joy=0, Btn=2, Pressed 180906 [Buttons] 7=P0,2,K120,10 180906 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 180906 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 180922 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 181031 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 181047 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 181063 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 181078 Button changed: bRef=0, Joy=0, Btn=2, Released 181078 [Buttons] 7=P0,2,K120,10 181281 Button changed: bRef=0, Joy=0, Btn=2, Pressed 181281 [Buttons] 7=P0,2,K120,10 181281 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 181281 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 181297 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 181406 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 181422 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 181438 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 181453 Button changed: bRef=0, Joy=0, Btn=2, Released 181453 [Buttons] 7=P0,2,K120,10 181578 Button changed: bRef=0, Joy=0, Btn=2, Pressed 181578 [Buttons] 7=P0,2,K120,10 181578 SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 181578 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 181594 Sending WM_KEYDOWN, Key=120 (Scan code 67), Ctr=1 181688 SendKeyToFS(00020078=[ctl+F9], KEYUP) ctr=0 181688 Sending WM_KEYUP, Key=120 (Scan code 67), Ctr=2 181703 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 181750 Button changed: bRef=0, Joy=0, Btn=2, Released 181750 [Buttons] 7=P0,2,K120,10 184063 KEYDOWN: VK=27, Waiting=0, Repeat=N, Shifts=0 184063 .. Key not programmed -- passed on to FS 184078 Sim stopped: average frame rate for last 48 secs = 29.3 fps does everything look correct to u? was the key CTRL+F9 sent to FS? thx again fil
Pete Dowson Posted June 27, 2016 Report Posted June 27, 2016 2 hours ago, filippoporcari said: does everything look correct to u? was the key CTRL+F9 sent to FS? Er, yes, and it didn't really need hundreds of examples! Didn't you see any of these lines? SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 Guess what that means? As far as FSUIPC is concerned, the key combo was sent. Of course, after that who knows what happened to it? What did you expect to happen? Pete
filippoporcari Posted June 28, 2016 Report Posted June 28, 2016 hi peter, and thx for your reply. i didn't push the button "hundred" of times to create "hundred of examples" but just for personal testing purposes while sim was running. i reported the full log session with "hundred of examples" because i didn't know which lines could interest u or not (u know i'm not a programmer). to answer your question: yes i see that line! and NO i don't know the real meaning of it (i can guess it means the command was sent to FS ) because as stated above i'm a location sound mixer and not a programmer...that's why i was asking to the programmer. no one knows what happened afterwards...one thing is sure CTRL+F9 triggers the show/hide ivap panel....and pushing CTRL+F9 on the keyboard shows/hides ivap....pushing the joy button doesn't show/hide it even if the command is sent to FS. as stated in my very first post i didn't write u to "accuse" fsuipc of not doing its job...but just to make u aware of a potential issue other users could write about. as stated again never had problems with buttons-to-key in the past (win xp/fs9...win7/fsx, p3d 2 and steam) but now with p3d 3.3.5/win10 the problem is there and it is a fact: made two clean installations of win10 and the problem is still there. what i'm a bit astonished about is your way of face a potential issue: i imagine u get tons of messages, emails from people claiming for a solution....i fully understand your point "it's not fsuipc concerned, fsuipc does its job" and i would probably behave the same if i were in your shoes. what i didn't expect was all that rhetorical questioning and that pointing the finger as if the user is always responsible to have created a mess in the computer, the user can't read lines and the user has no programming skills to understand lines of code....well sadly peter the user is free not to be a programmer...and also if being a poor street man is entitled to get respectful answers as a customer. the fact u created and still fully support/update one of the MOST USEFUL AND POWERFUL utilities for flight simulation doesn't entitle u to threat customers like idiots. all the best fil
filippoporcari Posted June 28, 2016 Report Posted June 28, 2016 to add something...just did another test: assigned to a joy button the key Q.....as expected pushing the joy button did not toggle the sound...pushing the physical Q letter on the keyboard toggled the sound. the log: 73250 [Buttons] 1=P0,0,K81,8 73250 SendKeyToFS(00000051=[Q], KEYDOWN) ctr=0 73266 Sending WM_KEYDOWN, Key=81 (Scan code 16), Ctr=1 73359 SendKeyToFS(00000051=[Q], KEYUP) ctr=0 73359 Sending WM_KEYUP, Key=81 (Scan code 16), Ctr=1 73484 Button changed: bRef=0, Joy=0, Btn=0, Released 73484 [Buttons] 1=P0,0,K81,8 74625 Button changed: bRef=0, Joy=0, Btn=0, Pressed 74625 [Buttons] 1=P0,0,K81,8 74625 SendKeyToFS(00000051=[Q], KEYDOWN) ctr=0 74625 Sending WM_KEYDOWN, Key=81 (Scan code 16), Ctr=1 74734 SendKeyToFS(00000051=[Q], KEYUP) ctr=0 74734 Sending WM_KEYUP, Key=81 (Scan code 16), Ctr=1 74906 Button changed: bRef=0, Joy=0, Btn=0, Released 74906 [Buttons] 1=P0,0,K81,8 77656 KEYDOWN: VK=81, Waiting=0, Repeat=N, Shifts=0 77656 .. Key not programmed -- passed on to FS 77781 KEYUP: VK=81, Waiting=0 78563 KEYDOWN: VK=81, Waiting=0, Repeat=N, Shifts=0 78563 .. Key not programmed -- passed on to FS 78703 KEYUP: VK=81, Waiting=0 81156 Button changed: bRef=0, Joy=0, Btn=0, Pressed 81156 [Buttons] 1=P0,0,K81,8 81156 SendKeyToFS(00000051=[Q], KEYDOWN) ctr=0 81156 Sending WM_KEYDOWN, Key=81 (Scan code 16), Ctr=1 81297 SendKeyToFS(00000051=[Q], KEYUP) ctr=0 81297 Sending WM_KEYUP, Key=81 (Scan code 16), Ctr=1 81422 Button changed: bRef=0, Joy=0, Btn=0, Released 81422 [Buttons] 1=P0,0,K81,8 84344 KEYDOWN: VK=27, Waiting=0, Repeat=N, Shifts=0 84344 .. Key not programmed -- passed on to FS at my unexperienced eye i see a difference when physical keyboard buttons are pressed the line 77656 .. Key not programmed -- passed on to FS says PASSED ON TO FS....when joy button are pressed there's no PASSED word in the log but 81156 SendKeyToFS(00000051=[Q], KEYDOWN) ctr=0 ...is that still correct to your experienced eye? those lines in my unexperienced opinion look different from the lines in the log u posted above about your test on the win10 machine...i wanted to perform the exact same test u did because i'm not a programmer but a pragmatic person fil
Pete Dowson Posted June 28, 2016 Report Posted June 28, 2016 2 hours ago, filippoporcari said: i didn't push the button "hundred" of times to create "hundred of examples" but just for personal testing purposes while sim was running. i reported the full log session with "hundred of examples" because i didn't know which lines could interest u or not (u know i'm not a programmer). No, sorry, but I thought you might notice it is just the same stuff over and over again, so a sample would have done. Never mind. 2 hours ago, filippoporcari said: .one thing is sure CTRL+F9 triggers the show/hide ivap panel....and pushing CTRL+F9 on the keyboard shows/hides ivap That suggests it is being trapped by that program as a Windows "hotkey". But I don't know why that would also hook the messages -- it might do though, but not send the needs "hotkey occurred" message. To check this you could try without running ivap. 3 hours ago, filippoporcari said: i can guess it means the command was sent to FS Not really a guess when it says "SendKeyToFS" ;-) 3 hours ago, filippoporcari said: what i'm a bit astonished about is your way of face a potential issue: i imagine u get tons of messages, emails from people claiming for a solution....i fully understand your point "it's not fsuipc concerned, fsuipc does its job" and i would probably behave the same if i were in your shoes. what i didn't expect was all that rhetorical questioning and that pointing the finger as if the user is always responsible to have created a mess in the computer Sorry, I see no where that I am doing any such thing. As I said earlier, I do not understand why this is happening on your computer. It is NOT directly related to either P3D3.3.5 or Win10, as both of those are in use a lot and thoroughly tested with this mechanism. That's why I simply suggested that you'd need to do a process of elimination. Try to see which process or service might be responsible. I do try my best and if I'm at home I respond very quickly. Support occupies most of my days and it has been going on with FSUIPC now for 18 years, over many additions and improvements nearly all as requested by users. I don't expect thanks but I don't expect such nasty criticism from someone I've been trying to help. I'm sorry I failed to, and I'm sorry if I sometimes appear impatient with someone and point out things which might be obvious, but they are never intended to make anyone feel as you seem to do. It seems that I cannot help in this matter without know what is causing it. If you can find out what is doing it (by the process of elimination I mentioned), then maybe I could add whatever it is here and find out why. Finally, however: 1 hour ago, filippoporcari said: at my unexperienced eye i see a difference when physical keyboard buttons are pressed the line 77656 .. Key not programmed -- passed on to FS says PASSED ON TO FS....when joy button are pressed there's no PASSED word in the log but 81156 SendKeyToFS(00000051=[Q], KEYDOWN) ctr=0 ...is that still correct to your experienced eye? Yes, the keypress is not reaching FS. We know that. but we don't know why. If you look back to the log extract I included from my test, in the second message in this thread, you'll see that same for a button sending a keypress. Pete
filippoporcari Posted June 28, 2016 Report Posted June 28, 2016 hi pete, always appreciated your fast replies and work! i didn't want to appear "nasty" because criticism is far from my normal attitude...,i found your way of facing my statements a bit too critic. but nevermind...talking (writing) helps communication as it did in this occasion at least on my side. in your post sent late yesterday night (or early this morning) u said the key was sent to fs which is fully correct...could have helped if U wrote that it appeared the command was not received....but now everything is clear...and i can investigate and hopefully report to u all the best fil
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now