Jump to content
The simFlight Network Forums

MartinP

Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by MartinP

  1. Hi Pete, thanks for speedy reply. I'll try and be a lot clearer. ECZA v2 has keyboard settings which when operated enable the user to move the camera view in use to any desired position, forwards, backwards, left, right, up and down. In the default settings for ECZA the up and down movement of the eyepoint camera is located to PageUp and PageDown keys. Without making any key assignments in FSUIPC, if I go to my keyboard and press PageUp key, the view in the sim will move up, conversely pressing the PageDown key will result in the view moving down the screen. So working satisfactorily. My expectations were that when I assigned these two keys to FSUIPC, that the result would be entirely similar to using the keyboard. However as previously stated, whereas the button assigned to PageDown key produced the downward movement, the button assigned to PageUp failed to produce any movement. As requested I instigated button and key logging (for brevity I have edited out all the cosiderable repitions whilst keys were held). Although it is of course for you to judge it appears from the log that the assignments have been set up correctly and that FSUIPC is sending key requests into the sim. Since my original post I have looked into this a little more. In ECZA I changed the default settings around so that PageUp was allocated to down movement and PageDown to up. The result was that moving up was now possible but no longer able to move down. I further reset the ECZA assignments using 1 to move up and PageDown to move down. Similar assignments were made in FSUIPC. The result is that now the ECZA cameras are moving as they should. The satisfactory response is also logged below. I have also been able to re-assign PageUp to Arm Spoilers (swapping this previous key setting to ECZA Up). So I am faced with the conclusion that ECZA does not like the re-assignment of the PageUp key and is blocking its use. The camera movements now work as they are intended, so unless you, Pete have any observations, please consider the matter satisfactorily closed. My thanks for a great product, which I have used for many years now. Martin COPY FROM FSUIPC LOGS: 328 Product= CH PRO PEDALS USB 328 Manufacturer= CH PRODUCTS 328 Vendor=068E, Product=00F2 (Version 0.0) 328 Serial Number= 328 Product= CH THROTTLE QUADRANT 344 Manufacturer= CH PRODUCTS 344 Vendor=068E, Product=00FA (Version 0.0) 344 Serial Number= 344 Product= CH FLIGHT SIM YOKE USB 344 Manufacturer= CH PRODUCTS 344 Vendor=068E, Product=00FF (Version 0.0) 344 Serial Number= BUTTON ASSIGNMENT TO PAGEUP - NO RESPONSE: 112165 Button changed: bRef=0, Joy=2, Btn=4, Pressed 112165 [Buttons] 36=R2,4,K33,8 112165 Repeating flag set: bRef=0, Joy=2, Btn=4 (RepeatDelayCtr=1) 112165 SendKeyToFS(00000021=[PgUp], KEYDOWN) ctr=0 112181 Sending WM_KEYDOWN, Key=33 (Scan code 73), Ctr=1 112196 KEYDOWN: VK=33, Waiting=0, Repeat=N, Shifts=0 112196 .. Key not programmed -- passed on to FS 112337 Button held, flags=X04, repeat set: bRef=0, Joy=2, Btn=4, (RepeatOk sets 2) 112337 [Buttons] 36=R2,4,K33,8 112337 Repeating flag set: bRef=0, Joy=2, Btn=4 (RepeatDelayCtr=11) 112337 SendKeyToFS(00000021=[PgUp], KEYDOWN) ctr=0 112337 Sending WM_KEYDOWN, Key=33 (Scan code 73), Ctr=1 112368 Button held, flags=X04, repeat set: bRef=0, Joy=2, Btn=4, (RepeatOk sets 2) 112368 [Buttons] 36=R2,4,K33,8 112368 Repeating flag set: bRef=0, Joy=2, Btn=4 (RepeatDelayCtr=11) 112368 SendKeyToFS(00000021=[PgUp], KEYDOWN) ctr=0 112368 Button held, flags=X04, repeat set: bRef=0, Joy=2, Btn=4, (Result 4) 112368 [Buttons] 36=R2,4,K33,8 112368 KEYDOWN: VK=33, Waiting=0, Repeat=Y, Shifts=0 112368 .. Key not programmed -- passed on to FS 112368 Sending WM_KEYDOWN, Key=33 (Scan code 73), Ctr=1 112399 Button held, flags=X04, repeat set: bRef=0, Joy=2, Btn=4, (RepeatOk sets 2) 112399 [Buttons] 36=R2,4,K33,8 113553 KEYUP: VK=33, Waiting=0 BUTTON ASSIGNMENT TO PAGEDOWN - SATISFACTORY RESPONSE 115285 Button changed: bRef=0, Joy=2, Btn=5, Pressed 115285 [Buttons] 37=R2,5,K34,8 115285 Repeating flag set: bRef=0, Joy=2, Btn=5 (RepeatDelayCtr=1) 115285 SendKeyToFS(00000022=[PgDn], KEYDOWN) ctr=0 115285 Sending WM_KEYDOWN, Key=34 (Scan code 81), Ctr=1 115316 KEYDOWN: VK=34, Waiting=0, Repeat=N, Shifts=0 115316 .. Key not programmed -- passed on to FS 115426 Button held, flags=X04, repeat set: bRef=0, Joy=2, Btn=5, (RepeatOk sets 2) 115426 [Buttons] 37=R2,5,K34,8 115426 Repeating flag set: bRef=0, Joy=2, Btn=5 (RepeatDelayCtr=11) 115426 SendKeyToFS(00000022=[PgDn], KEYDOWN) ctr=0 115426 Sending WM_KEYDOWN, Key=34 (Scan code 81), Ctr=1 115457 Button held, flags=X04, repeat set: bRef=0, Joy=2, Btn=5, (RepeatOk sets 2) 115457 [Buttons] 37=R2,5,K34,8 115457 Repeating flag set: bRef=0, Joy=2, Btn=5 (RepeatDelayCtr=11) 115457 SendKeyToFS(00000022=[PgDn], KEYDOWN) ctr=0 115457 KEYDOWN: VK=34, Waiting=0, Repeat=Y, Shifts=0 115457 .. Key not programmed -- passed on to FS 115457 Sending WM_KEYDOWN, Key=34 (Scan code 81), Ctr=1 115488 Button held, flags=X04, repeat set: bRef=0, Joy=2, Btn=5, (RepeatOk sets 2) 115488 [Buttons] 37=R2,5,K34,8 115940 KEYUP: VK=34, Waiting=0 303375 *** Entered Buttons option page *** 317509 FirstButtonChange res=00000204 (0.2, 4) 334888 FirstButtonChange res=00000205 (0.2, 5) 342485 FirstButtonChange res=00000204 (0.2, 4) 347493 FirstButtonChange res=00000205 (0.2, 5) 350269 *** Exiting Buttons option page *** BUTTON ASSIGNMENT TO PAGE DOWN - SATISFACTORY RESPONSE 388115 Button changed: bRef=0, Joy=2, Btn=5, Pressed 388115 [Buttons] 37=R2,5,K34,8 388115 Repeating flag set: bRef=0, Joy=2, Btn=5 (RepeatDelayCtr=1) 388115 SendKeyToFS(00000022=[PgDn], KEYDOWN) ctr=0 388115 Sending WM_KEYDOWN, Key=34 (Scan code 81), Ctr=1 388146 KEYDOWN: VK=34, Waiting=0, Repeat=N, Shifts=0 388146 .. Key not programmed -- passed on to FS 388256 Button held, flags=X04, repeat set: bRef=0, Joy=2, Btn=5, (RepeatOk sets 2) 388256 [Buttons] 37=R2,5,K34,8 388256 Repeating flag set: bRef=0, Joy=2, Btn=5 (RepeatDelayCtr=11) 388256 SendKeyToFS(00000022=[PgDn], KEYDOWN) ctr=0 388256 Sending WM_KEYDOWN, Key=34 (Scan code 81), Ctr=1 388287 Button held, flags=X04, repeat set: bRef=0, Joy=2, Btn=5, (RepeatOk sets 2) 388287 [Buttons] 37=R2,5,K34,8 388287 Repeating flag set: bRef=0, Joy=2, Btn=5 (RepeatDelayCtr=11) 388287 SendKeyToFS(00000022=[PgDn], KEYDOWN) ctr=0 388287 KEYDOWN: VK=34, Waiting=0, Repeat=Y, Shifts=0 388287 .. Key not programmed -- passed on to FS 388287 Sending WM_KEYDOWN, Key=34 (Scan code 81), Ctr=1 388318 Button held, flags=X04, repeat set: bRef=0, Joy=2, Btn=5, (RepeatOk sets 2) 388318 [Buttons] 37=R2,5,K34,8 388536 KEYUP: VK=34, Waiting=0 BUTTON ASSIGNMENT TO 1 - SATISFACTORY RESPONSE 391454 Button changed: bRef=0, Joy=2, Btn=4, Pressed 391454 [Buttons] 36=R2,4,K49,8 391454 Repeating flag set: bRef=0, Joy=2, Btn=4 (RepeatDelayCtr=1) 391454 SendKeyToFS(00000031=[1], KEYDOWN) ctr=0 391454 Sending WM_KEYDOWN, Key=49 (Scan code 2), Ctr=1 391485 KEYDOWN: VK=49, Waiting=0, Repeat=N, Shifts=0 391485 .. Key not programmed -- passed on to FS 391594 Button held, flags=X04, repeat set: bRef=0, Joy=2, Btn=4, (RepeatOk sets 2) 391594 [Buttons] 36=R2,4,K49,8 391594 Repeating flag set: bRef=0, Joy=2, Btn=4 (RepeatDelayCtr=11) 391594 SendKeyToFS(00000031=[1], KEYDOWN) ctr=0 391594 Sending WM_KEYDOWN, Key=49 (Scan code 2), Ctr=1 391625 Button held, flags=X04, repeat set: bRef=0, Joy=2, Btn=4, (RepeatOk sets 2) 391625 [Buttons] 36=R2,4,K49,8 391625 Repeating flag set: bRef=0, Joy=2, Btn=4 (RepeatDelayCtr=11) 391625 SendKeyToFS(00000031=[1], KEYDOWN) ctr=0 391625 KEYDOWN: VK=49, Waiting=0, Repeat=Y, Shifts=0 391625 .. Key not programmed -- passed on to FS 391625 Sending WM_KEYDOWN, Key=49 (Scan code 2), Ctr=1 391656 Button held, flags=X04, repeat set: bRef=0, Joy=2, Btn=4, (RepeatOk sets 2) 391656 [Buttons] 36=R2,4,K49,8 391812 KEYUP: VK=49, Waiting=0
  2. Hi Pete I have a registered copy of fsuipc v4.4959e. Using FSX steam (DX10), PMDG 737NGX with ECZA v2 on Windows 7. Following installation of the new ECZA v2, I have allocated various keyboard commands to fsuipc including arrow up down, left and right arrows and PageUp and PageDown keys. All work well except the button allocated to the PageUp key. The PageUp key on the keyboard functions correctly but as stated not when using the allocated button. Also the PageUp command is setup in ECZA v2. I have carefully checked the settings of the allocation and all appears correct. Fsuipc recognises the button and just to confirm the box to continue the action whilst the button is pressed is ticked. In addition just to check that there is no problem with the button I have allocated alternative fsuipc commands without a problem. This problem was also present when using 4.4959 before upgrading to 'e'. Any help or thoughts, please. Martin Plain
  3. Pete I'm pleased some others have come in on this one. I had come to the conclusion that windows had decided unilaterally to run fsx in compatibility mode. Being unable to resolve it even through the registry I had determined to do a fresh clean install. However now.... Looking at the registry entry, I find: Current version = 6.3 Current Build = 10586 Product Name = Windows 10 Home So presumably it would very much appear that as stated above, the version number for W8 has not been updated by Microsoft during the upgrade process. Also having looked at a full (purchased) installation, the version is still 6.3. Thanks for all your help. Martin
  4. I have just updated to Windows 10 from Windows 7. All appeared to go well. However after completing a flight and checking the fsuipc log, it shows my operating system as Windows 8. I will admit I cannot detect any issues when using the sim and I can confirm that my O/S is definitely Windows 10. I have also checked the properties of fsx.exe and steam.exe for any compatability flags - there are none. The fsuipc version is 4.948e Is this as it should be or do I have an issue? Martin
  5. Hi Kiko Does the Combo actually do what it should be doing in the flightsim? The VSPE does not change the com port (in your case 3) to which the Combo is set. A I understand it, in simple terms FSUIPC stops the Combo port from communicating directly with the flightsim. FSUIPC takes control and communicates with the flightsim using your virtual com ports 2 and 4. So the Combo will always remain on the original port, in your case 3. I attach an extract from my fsuipc log to demonstrate: 359 SimConnect_Open succeeded: waiting to check version okay 359 Trying to use SimConnect Steam 406 VRI port 1 "com3" opened 406 VRI driver port 1 "com2" also opened 1389 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0) 1389 Initialising SimConnect data requests now 1389 FSUIPC Menu entry added 1420 \\PLAIN-PC\Users\Martin Plain\Documents\Flight Simulator X Files\Transavia B738W.FLT 1420 \\PLAIN-PC\Steam\steamapps\common\FSX\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.air 8752 Weather Mode now = Custom 62479 Aircraft="Boeing 737-8K2NGX Transavia Airlines Winglets" 62479 System time = 12/11/2015 20:17:50, Simulator time = 12:06:35 (11:06Z) 110948 Sim stopped: average frame rate for last 48 secs = 22.2 fps 126018 Starting everything now ... 126080 ASN active function link set 126080 Ready for ASN WX radar 126096 Run: "c:\Program Files (x86)\VRInsight\bin\SerialFP2.exe" 127048 VRI FMER ("MCP Combi") detected on port com3 Is this similar to what you are seeing in your log file? Martin
  6. Hi Kiko You appear to have the fsuipc cfg entry incorrect. If you have set up vspe ports 2 and 4 - and your mcp combo is on port 3, then your fsuipc cfg entry shoud be: [VRInsight] 1=com3, com2 Just in case - VSPE needs to be running prior to FSim. Also - not to sure if it makes any difference but perhaps you should run the Serial FP2.exe rather than the vrinsight.exe. But as I say not to sure on this one, but it is the one I use with NGX and my combo. Hope this helps. Martin
  7. Peter From time to time I have been losing the Visibilty Upper Altitude Limit setting in 3.98. Having set an altitude of 6000, it would go to 0. This puzzled me for a time until I discovered that it occurs when you open up the FSUIPC module in FS9 perhaps checking a setting or making an adjustment but exit by pressing CANCEL. This action resets the VisUpperAltitudeLimit to zero irrespective of what tab you have been in. Pressing OK retains the setting. Really just drawing this to your attention as now I know about it, it isn't a huge issue.Just hope the info may help others. Martin Plain
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.