Jump to content
The simFlight Network Forums

seippg

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

0 Neutral

About seippg

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    NC
  1. Hi Pete, I'm looking for solutions for an older aircraft and I'm wondering, hypothetically,...is it possible to call a mouse macro from an lua module? That might give me some flexibility I could use. Gregg
  2. Welp, shrugs then. I clicked on lots of stuff in each...how/why the other person had some success in those planes is a mystery then. I'd rather program hardware other ways anyway.
  3. Here's from the Turbine Duke... Console Started ... 157047 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 162164 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 167717 Mouse by function: RXedb0*X8bcc,14 (flags=00004000), Module="window.dll" 167717 *** EVENT: Cntrl= 66364 (0x0001033c), Param= 0 (0x00000000) TOGGLE_ALTERNATOR2 172631 Memory in use: 1956Mb, Avail=2140Mb 176235 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 179058 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 179058 *** EVENT: Cntrl= 66338 (0x00010322), Param= 0 (0x00000000) TOGGLE_PROPELLER_DEICE 181492 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 181492 *** EVENT: Cntrl= 65560 (0x00010018), Param= 0 (0x00000000) STROBES_TOGGLE 184550 Mouse by function: RXf230*X8bcc,14 (flags=00004000), Module="window.dll" 184565 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN 188528 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 191835 Mouse by function: RXedb0*X8bcc,14 (flags=00004000), Module="window.dll" 193957 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 197155 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 199401 Mouse by function: RXedb0*X8bcc,14 (flags=00004000), Module="window.dll" 199401 *** EVENT: Cntrl= 66855 (0x00010527), Param= 0 (0x00000000) VIEW_CAMERA_SELECT_5 202209 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 204097 *** EVENT: Cntrl= 66851 (0x00010523), Param= 0 (0x00000000) VIEW_CAMERA_SELECT_1 204097 *** EVENT: Cntrl= 65701 (0x000100a5), Param= 64 (0x00000040) VIEW_ZOOM_SET From the Q400... 412233 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 413122 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 413731 Memory in use: 2349Mb, Avail=1747Mb 425805 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 427162 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 427771 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 429331 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 430704 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 431998 Mouse,14 (flags=00004000), Module="" 434526 Mouse,14 (flags=00004000), Module="" 435867 Mouse: (flags=20000000), Module="" 435883 Mouse: (flags=20000000), Module="" 436476 Mouse: (flags=20000000), Module="" 437006 Mouse: (flags=20000000), Module="" 437583 Mouse: (flags=20000000), Module="" 438519 Mouse: (flags=20000000), Module="" 441171 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 442139 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 443433 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 444323 Mouse: (flags=20000000), Module="" 444853 Mouse: (flags=20000000), Module="" 445883 Mouse,13 (flags=00002000), Module="" 446522 Mouse,14 (flags=00004000), Module="" 446694 Mouse,14 (flags=00004000), Module="" 446897 Mouse,14 (flags=00004000), Module="" 448862 KEYDOWN: VK=70, Waiting=0, Repeat=N, Shifts=0 448862 .. Key not programmed -- passed on to FS 448862 *** EVENT: Cntrl= 65569 (0x00010021), Param= 0 (0x00000000) DME 448862 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_C 448909 *** EVENT: Cntrl= 66851 (0x00010523), Param= 0 (0x00000000) VIEW_CAMER 448909 *** EVENT: Cntrl= 65701 (0x000100a5), Param= 65 (0x00000041) VIEW_ZOOM 449003 KEYUP: VK=70, Waiting=0 452138 Mouse by function: RXedb0*X8bcc,13 (flags=00002000), Module="window.dl 453573 Mouse by function: RXedb0*X8bcc,14 (flags=00004000), Module="window.dl 464088 *** EVENT: Cntrl= 66851 (0x00010523), Param= 0 (0x00000000) VIEW_CAMER 464088 *** EVENT: Cntrl= 65701 (0x000100a5), Param= 62 (0x0000003e) VIEW_ZOOM 468097 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 469735 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 473994 Memory in use: 2353Mb, Avail=1743Mb 474010 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 475772 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 476740 Mouse,14 (flags=00004000), Module="" 477395 Mouse,13 (flags=00002000), Module="" 478346 Mouse,14 (flags=00004000), Module="" 478861 Mouse,13 (flags=00002000), Module="" 479891 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 481186 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 481872 Mouse,14 (flags=00004000), Module="" 482402 Mouse,13 (flags=00002000), Module="" 483448 Mouse,14 (flags=00004000), Module="" 484586 Mouse,13 (flags=00002000), Module="" 486162 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 486240 *** EVENT: Cntrl= 65751 (0x000100d7), Param= 1 (0x00000001) LANDING_LI 486880 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 489500 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 490358 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 490452 *** EVENT: Cntrl= 66379 (0x0001034b), Param= 1 (0x00000001) TOGGLE_NAV 491809 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 492683 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 493541 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 494149 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 494742 Mouse,14 (flags=00004000), Module="" From the Default C172 (tried in both 2D and 3D cockpit... 777915 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 783937 Mouse Event=65883 783937 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 0 (0x00000000) KOHLSMAN_I 785294 Mouse Event=65884 785294 *** EVENT: Cntrl= 65884 (0x0001015c), Param= 0 (0x00000000) KOHLSMAN_D 786043 Mouse Event=65883 786043 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 0 (0x00000000) KOHLSMAN_I 786698 Mouse Event=65884 786698 *** EVENT: Cntrl= 65884 (0x0001015c), Param= 0 (0x00000000) KOHLSMAN_D 789350 Mouse: (flags=20000000), Module="" 790114 Mouse: (flags=20000000), Module="" 791550 Mouse Event=65560 791550 *** EVENT: Cntrl= 65560 (0x00010018), Param= 0 (0x00000000) STROBES_TO 792205 Mouse Event=65858 792205 *** EVENT: Cntrl= 65858 (0x00010142), Param= 0 (0x00000000) PITOT_HEAT 793297 Mouse: (flags=20000000), Module="" 793297 *** EVENT: Cntrl= 66379 (0x0001034b), Param= 0 (0x00000000) TOGGLE_NAV 794841 Mouse Event=66239 794841 *** EVENT: Cntrl= 66239 (0x000102bf), Param= 0 (0x00000000) TOGGLE_BEA 795840 Mouse Event=66339 795840 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELE 797790 Mouse: (flags=20000000), Module="" 797790 *** EVENT: Cntrl= 66242 (0x000102c2), Param= 0 (0x00000000) TOGGLE_MAS 797790 *** EVENT: Cntrl= 66241 (0x000102c1), Param= 0 (0x00000000) TOGGLE_MAS 809755 Mouse Event=65877 809755 *** EVENT: Cntrl= 65877 (0x00010155), Param= 0 (0x00000000) GYRO_DRIFT 810582 Mouse Event=65878 810582 *** EVENT: Cntrl= 65878 (0x00010156), Param= 0 (0x00000000) GYRO_DRIFT 811190 Mouse Event=65877 811190 *** EVENT: Cntrl= 65877 (0x00010155), Param= 0 (0x00000000) GYRO_DRIFT 813265 Mouse Event=65880 813265 *** EVENT: Cntrl= 65880 (0x00010158), Param= 0 (0x00000000) HEADING_BU 813717 Mouse Event=65879 813717 *** EVENT: Cntrl= 65879 (0x00010157), Param= 0 (0x00000000) HEADING_BU 814872 Mouse Event=66240 814872 *** EVENT: Cntrl= 66240 (0x000102c0), Param= 0 (0x00000000) TOGGLE_TAX 815761 Mouse Event=66379 815761 *** EVENT: Cntrl= 66379 (0x0001034b), Param= 0 (0x00000000) TOGGLE_NAV 818397 Mouse Event=66317 818397 *** EVENT: Cntrl= 66317 (0x0001030d), Param= 0 (0x00000000) TOGGLE_ALT 835745 Memory in use: 2199Mb, Avail=1897Mb 837180 Mouse: (flags=20000000), Module="" 837195 *** EVENT: Cntrl= 66464 (0x000103a0), Param= 0 (0x00000000) COM2_TRANS 838116 Mouse: (flags=20000000), Module=""
  4. See, that's what I was thinking too. But when I saw that someone was able to create macros for the B60 and Dash 8 I thought that maybe there's something wrong. Also, another person told me that they have had success making mouse macros for the Citation X for their hardware (which is the only reason I'm trying this at all...this is not my preferred method of doing this stuff). Is there any clue in the fact that I am getting the log messages or is that just log noise?
  5. Ran across this thread today. I have been trying to make a mouse macro in some of these same aircraft (B60, Majestic Dash 8, Citation X, Default C172) and it's not working. I click "Create Mouse Macro", give it a name, click OK and then click on various switches, places in the aircraft but never get the dialog that's supposed to appear. I see log messages like "Mouse by function:" or "Mouse, 14". I have FSX SP2 and the latest version of FSUIPC, I rebooted my computer, Reinstalled FSUIPC twice to no avail. Any ideas? Gregg
  6. Yeah, PMDG does...and it's annoying LOL. But, yes, when you get it tuned it's great! I guess the trick would be to find the range of motion and have a threshold on each that, if exceeded, you disengage it. I guess I'd have to register for events or set a timer.
  7. Hey Pete, Is it possible for you to create an "Autopilot disengage" when control forces exceed some amount? Seems like FSUIPC would be the right place for it. I guess it would be up to people to know whether the given aircraft should have that feature. Gregg
  8. Holy cow...how did I miss that? All I needed to do was add a feature to my brain. LOL. Thanks Pete.
  9. Hi Pete, A while back you added a cool feature to "Use system time for flights". I was wondering if it would be possible to respect the timezone where the airport is with respect to the computer. For example, if your computer is in North Carolina and you're flying in England you would add 5 hours. If you were flying in California, you would subtract three hours. That way your view of the world would be the same as other online pilots. Thanks, Gregg
  10. Okay. Things are all good now. Just figured I'd let you know in case someone else chimes in with the problem.
  11. The solution was to delete my fsuipc.ini file. I deleted it and let fsuipc create a new one. Recreated my assignments manually and recalibrated. No spikes at all for two days.
  12. I should do something like that instead of fighting with this...this...thing. LOL. My yoke is OLD but USB. My throttle is young...6-7 months. PC's about a year old. Still...could be hardware. Common themes are 1) stressed out CPU 2) USB port issues. It's an i7 but FSX stresses everything. USB ports? Could be. I did futz with Delta some (I've futzed with everything.) I've gotten my hopes up before but that seemed to help if only by reducing the amount of throttle reads LINDA was getting. Have a great trip!!
  13. Hi Pete, I think I spoke too soon about VAFS (I think). Yesterday was perfect but today I have been getting the spikes again without it running. I uninstalled it as well. I did a bunch of troubleshooting, cleaned my controls just to be certain. Watching the processes, I notice that LINDA jumps up on the CPU just before it happens. I turned on the tracer and it has a VisibleRightThrottlePos thing it's writing to the log on a regular basis (left too). When the spike comes I see VisibleRightThrottlePos=100 and then usually the throttle restores back to its normal position...matching back to the hardware position again. I also notice another thing that changed. It used to be (talking last week and all throughout the past) the virtual controls on the screen would sit in some position that did not match my physical controls until I moved the physical controls...even a little bit. Now that's changed. If I start an aircraft, the virtual controls sync up to the physical controls right away without me touching them. Seems something is a lot more sensitive than it used to be. Again, not sure how useful that is but those are the two bits of information I've gotten since this weirdness started. I'm baffled again and just wondering if this gives you any clues. Gregg Edit: I notice that, usually, there is a EngineXThrottlePosition = blah when I move the physical throttle followed by some Visble RightThrottlePos stuff. But when I get the VisibleRightThrottlePos=100 there is no EngineXThrottlePosition = blah. It just pops up without the EngineXThrottlePosition = blah. Does that mean that the spikes are not coming from the physical throttle quad but someplace else?
  14. Yeah, that's what it is. I just did a 90 minute flight with it off and not a single issue. Usually they happen anywhere from 30 seconds to 5 minutes apart. Not sure why. Maybe it's polling too hard or just my system. The only thing I can do is keep it off until I get it resolved.
×
×
  • 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.