Jump to content
The simFlight Network Forums

Jim Harnes

Members
  • Posts

    15
  • Joined

  • Last visited

About Jim Harnes

  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Jim Harnes's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Thanks, Pete. I thought as much. None of the links anywhere allow me to connect. I've also been on the road and unable to connect with pcs and macs other that my own from two different states here in the U.S. Will take the issue up with my ISP and post back results. Best, Jim Harnes
  2. I've been attempting to update to version 3.99 for about two weeks now, but am unable to connect to www.schiratti.com. That URL does not respond to a ping. I've cleared the browser cache and flushed DNS, to no effect. Is that site available? Best, Jim Harnes
  3. For what it's worth, I was unable to capture any panel variable for that QW757 function. Quality Wings did not respond to a request for a list of keyboard assignments. Using Key2mouse is most likely the only way to assign the function to keys then to a joystick button using FSUIPC. Best, Jim Harnes
  4. Hi John, There are no key assignments available in the iFly 737 for those functions. The SDK is now released so if you are into programming you might have a look there. The least complicated method to achieve what you want is to save a flight with ground air and electrical connected then use that as your iFly 737 start up flight. Best, Jim Harnes
  5. Thanks for the information, Pete. I do not recall earlier versions of FSUIPC altering the order of key press entry. I'll roll back to a prior version and let you know if my memory is correct :smile: . Best, Jim Harnes
  6. In FSUIPC 3.989t pressing CTL+ALT+1 when assigning key presses to a button results in ALT+CTL+1 appearing in the SET box. Is there a method to force the keys to record in the order pressed? Thanks, Jim Harnes
  7. Last post this subject for those who might be interested: QW staff stated: Quote: Its not a FS9 control. That variable is just true/false an indicator that tells the gauge that thrust mode is either on/off. So when the button is pressed again the reverse happens. Its a registered variable in FS so they could set from another gauge, so what you suggest would appear possible. Unquote. I've used the Lvar access facilities Pete so generously added to FSUIPC3, attempted mouse macro creation and wrote a plug in based on log lvars.lua output. I succeeded in causing the EPR button "on light" to switch on, but was never able to identify how to "set from another gauge". However, Key2mouse does the job perfectly. QualityWings is deep into a service pack development/testing so I plan to ask them again in a month or so. Pete, thanks for your outstanding support!! Jim Harnes
  8. That works quite well! Now on with identifying the call for EPR set. Thanks, Jim Harnes
  9. To close the loop on this topic: Turns out the XML gauge for setting EPR is using a custom variable (L:thrust,enum) so I'm left with key2mouse, which certainly works well. Should have done some more poking around before posting :oops: ! Jim Harnes
  10. Will need to check this. I do know that it is not the equivalent of setting "TOGA". No wonder the error message :oops: ! Will also have a look at this. Thanks, Jim Harnes
  11. As the developer does not provide the information, I've used FSUIPC's logging facility to capture events which occur when I click on areas of the 2D panel I want to assign to my yoke. That was successful for everything except the EPR button on the 2D panel. Here is the log: ********* FSUIPC, Version 3.952 by Pete Dowson ********* Running on Windows Version 5.1 Build 2600 Service Pack 3 Verifying Certificate for "C:\Program Files\Microsoft Games\Flight Simulator 9\MODULES\FSUIPC.dll" now ... SUCCESS! Signature verifies okay! Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="James J Harnes Jr" User Addr=(removed) FSUIPC Key is provided WIDEFS not user registered, or expired Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=68003709[68003709] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=15 39328 System time = 18/12/2009 13:49:51 39344 C:\Program Files\Microsoft Games\Flight Simulator 9\ 39344 System time = 18/12/2009 13:49:51, FS2004 time = 12:00:00 (00:00Z) 55406 FLIGHTS\OTHER\FLTSIM.flt 55484 AIRCRAFT\c172\Cessna172SP.air 55766 Aircraft="Cessna Skyhawk 172SP" 66312 Advanced Weather Interface Enabled 104125 AIRCRAFT\QualityWings 752 Passenger\QWSim Boeing 757-200WL Rolls-Royce RB211-535E4B.air 104156 Aircraft="QWSim Boeing 757-200WL American Airlines WV" 347562 WeatherOptions set, now 68003709 (timer=0) 376734 HotKey entry at 3210, VK=255, Shifts=255, Flags=0, Result=0 385297 KEYDOWN: VK=116, Waiting=0, Repeat=N, Shifts=0 385297 .. This key is programmed in FSUIPC 'Keys' options 385531 KEYUP: VK=116, Waiting=0 387047 *** EVENT: Cntrl= 65860 (0x00010144), Param= 0 (0x00000000) AUTO_THROTTLE_ARM 387109 HotKey entry at 3210, VK=255, Shifts=255, Flags=0, Result=0 391328 *** EVENT: Cntrl= 66094 (0x0001022e), Param= 0 (0x00000000) AP_AIRSPEED_OFF (NoAccel) 391328 *** EVENT: Cntrl= 66097 (0x00010231), Param= 0 (0x00000000) AP_MACH_OFF (NoAccel) 391328 *** EVENT: Cntrl= 66094 (0x0001022e), Param= 0 (0x00000000) AP_AIRSPEED_OFF (NoAccel) 391375 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE (NoAccel) 391453 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 391484 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 391516 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 391578 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 391609 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 391750 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 391781 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 391812 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 391891 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 391922 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 391984 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 392016 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 392078 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 392125 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 392219 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 392281 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 392312 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 392359 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 392437 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 392500 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 392531 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 392594 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 392625 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 392734 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 392797 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 392828 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 392859 *** EVENT: Cntrl= 65609 (0x00010049), Param= 0 (0x00000000) INCREASE_THROTTLE 397453 HotKey entry at 3210, VK=255, Shifts=255, Flags=0, Result=0 400125 KEYDOWN: VK=117, Waiting=0, Repeat=N, Shifts=0 400125 FSUIPC Control Action: Ctrl=1084, Param=0 400125 .. This key is programmed in FSUIPC 'Keys' options 400625 KEYDOWN: VK=117, Waiting=0, Repeat=Y, Shifts=0 400625 FSUIPC Control Action: Ctrl=1084, Param=0 400625 .. This key is programmed in FSUIPC 'Keys' options 400656 KEYUP: VK=117, Waiting=0 402031 KEYDOWN: VK=18, Waiting=0, Repeat=N, Shifts=4 402031 .. Key not programmed -- passed on to FS 402172 KEYUP: VK=18, Waiting=0 I assigned INCREASE_THROTTLE to a button, engaged the autothrottle (successfuly assigned to a button), advanced the throttles to a steady 1.1 EPR and pressed the button assigned to EPR. Nothing happened. Also used log lvars.lua, resulting in the following log when pressing the 2D panel EPR click spot: ********* LUA: "log lvars" Log [from FSUIPC version 3.952] ********* 385297 System time = 18/12/2009 13:55:37, FS2004 time = 13:50:37 (20:50Z) 385297 LUA: beginning "C:\Program Files\Microsoft Games\Flight Simulator 9\MODULES\log lvars.lua" 385297 *** LUA Error: ...osoft Games\Flight Simulator 9\MODULES\log lvars.lua:21: attempt to call field 'getLvarName' (a nil value) 385297 LUA: ended "C:\Program Files\Microsoft Games\Flight Simulator 9\MODULES\log lvars.lua" 385297 System time = 18/12/2009 13:55:37, FS2004 time = 13:50:37 (20:50Z) ********* LUA execution terminated: Log Closed ********* Given the above information, is there something else I might do to assign QualityWings 757 EPR to a button? Thanks, Jim Harnes
  12. I've had success using XP SP3 by assigning all axis in FS then calibrating with FSUPIC. Use FSUPIC to assign the F2 key press to the buttons at the bottom of the Saitek throttle lever range and you will have reverse. Jim Harnes
  13. Thanks! Attention to detail . . . :) Jim Harnes
  14. Am getting FS crashes to a black screen and system lock up with the new Pss777 release candidate and registered copy of FSUPIC. Following is from FSUPIC log: 40704 Module [M7] identified = "PSS-B777.GAU" 40704 Module [M7] "PSS-777.gau" access registration is invalid Pss state the gauge is registered for FSUPIC access. Please advise if that is correct. If the gauge is not registered for FSUPIC access, could this cause the FS and system crashes? Thanks for your help. Jim Harnes
  15. With FSUPIC set with defaults, my PMDG 737 performs perfectly. However, when changing to any other settings, the aircraft VNAV climb speeds and feet-per-minute rates and VNAV path altitude hold do not function properly. For example, with a cruise altitude of FL370 set in the MCP and VNAV path showing on the PFD, the altitude constantly varies +/-120-200 feet. Of course TAS chases altitude. When I reset FSUPIC to defaults, normal aircraft flight behavior returns. This happens with all weather setting cleared, i.e., clear weather, no wind. Having registered FSUPIC, I want to use its non-default features. BTW, this happens with 3.14 and the version provided by PMDG, 3.129. Are there log settings which might point to the cause? Thanks, Jim Harnes
×
×
  • 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.