Jump to content
The simFlight Network Forums

Fadamor

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Fadamor

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Manassas, VA
  1. It looks like it's doing a "one step back, two steps forward" routine. I sent it (0 - was here when the log started),1,2,3,4,5,6,7,8,7,6,5,4,3,2,1,0. I would think I'd want to see FSUIPC echo that and show those flap handle indexes in that order. The log shows 1,2, 1,2,3, 2,3,4, 3,4,5, 4,5,6, 5,6,7, 6,7,8, 7,8, 7,6,5, 6,5,4, 5,4,3, 2,3,2, 1,0. That's a very active flap handle index!
  2. Changed the lever to "Direct to FSUIPC Calibration"|Flaps. Here's the resulting log: ********* FSUIPC4, Version 4.934 by Pete Dowson ********* User Name="Larry *********" User Addr="**************@comcast.net" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 316656 System time = 01/06/2014 16:35:11, Simulator time = 11:56:40 (16:56Z) [Continuation log requested by user] Running inside FSX on Windows 8 Module base=5DEC0000 316656 LogOptions changed, now 30000000 00000001 321438 *** AXIS: Cntrl= 66534 (0x000103e6), Param= -11394 (0xffffd37e) AXIS_FLAPS_SET 321438
  3. Got it. ********* FSUIPC4, Version 4.934 by Pete Dowson ********* User Name="Larry *********" User Addr="**************@comcast.net" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 165156 System time = 01/06/2014 13:22:50, Simulator time = 11:54:45 (16:54Z) [Continuation log requested by user] Running inside FSX on Windows 8 Module base=5E210000 165156 LogOptions changed, now 30000000 00000001 177156 *** EVENT: Cntrl= 65678 (0x0001008e), Param= 0 (0x00000000) VIEW_REAR 177641 *** EVENT: Cntrl= 65678 (0x0001008e), Param= 0 (0x00000000) VIEW_REAR 177672 *** EVE
  4. I wasn't sure what data types to use, so I left them at S8. This log is too large to paste. (Firefox locks up) https://dl.dropboxusercontent.com/u/59191044/FSUIPC4.log
  5. OK. Once more into the breech, my friends!
  6. Axis Assignment and Calibration (Flaps): 1.) I enter FSX, select FSUIPC from the Add-Ons menu, then select the Axis Assignment tab. 2.) I move the lever I want to use for flaps control and verify FSUIPC detects a joystick axis in motion. While slowly moving the lever through its range (except for the "reverser" area at the bottom) I watch the raw data and make sure there's no obvious spikes or dropouts. With the handle in the up position (i.e. flaps 0) raw data is 16383 or thereabouts. In the down position (flaps 40) raw data is -16384 or thereabouts. 3.) In the "Type of action required" f
  7. Yes that's where it was for me. I didn't see the key he mentioned at the level he mentioned, so I continued drilling down and I saw the code that automatically untrusts software at the "Software Publishing" level. I changed that key to 0x23c00 in addition to changing the FSUIPC4 entry to "1". When I re-started FSX, I received a couple of additional trust queries regarding my CS 767 install, so changing that registry key seems to have worked.
  8. Here is the Offset, Raw, and Calculated PMDG 737NGX data for various Flaps-related stuff in FSUIPC. Screen shots were taken after the flaps had finished moving to their commanded position. The flaps position dial in the upper right corner of the picture and the flaps handle provide confirmation that the displayed FSUIPC data corresponds to that particular flaps setting. The positions that were "wonky" on this test run were Flaps 10 and Flaps 30 (Flaps handle Index 4 and 7, respectively): https://dl.dropboxusercontent.com/u/59191044/Flaps%200.PNG https://dl.dropboxusercontent.com/u/59191
  9. Will do. Found and deleted the following mentions of FSUIPC in the [Trusted] section of FSX.CFG: C:\FSX\Modules\Fsuipc4.dll.bctzzqowlenthaoclzohzoconhtcnhqbbbciolcr=1 C:\FSX\Modules\Fsuipc4.dll.ulwzoocwbtkckqrktqreqbelllnekehwiwzonuck=1 C:\FSX\Modules\Fsuipc4.dll.tbakrhlcwqwiqtihqttzziuntbqutlnoiwooqoio=1 C:\FSX\Modules\Fsuipc4.dll.citbwaouhkrbnktubhttiuwlqiuqwwebntowiezc=-1 FSUIPC still not showing in add-ons. That last FSUIPC4 entry in [Trusted] keeps reappearing after I've started FSX. I never get prompted whether I should trust FSUIPC4 or not. Proceeding to get the sim
  10. Once I get FSUIPC back to where it loads with FSX, I'll check those offsets. Here's the current dll.xml file: <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> <
  11. According to the PMDG 737NGX SDK documentation, only the Flaps dial has special coding. All controls not listed in the pertinent .h file use standard SimConnect access procedures. Therefore all other flaps functions should be using standard SimConnect offsets. I've deleted the two entries for FSUIPC from the DLL.XML file and then re-installed FSUIPC. There is now just the one entry at the bottom of DLL.XML. I'm at a bit of a standstill right now, though, as I can't get FSUIPC to load. A log file was not produced because the program says it installed correctly. I did a RE-install
  12. Can't seem to get FSUIPC to activate in FSX. Installation seemed to work fine and I got the "Installed Successfully" message, but when I start FSX I'm not seeing FSUIPC under AddOns. The DLL.XML file has two entries for FSUIPC4:
  13. All valid points. First, I will update to the current FSUIPC and re-run the tests. I'll report back here my results.
  14. I'm using Win 8.1 Pro x64, FSX w/Accel Pack, the PMDG 737-800NGX, a registered copy of FSUIPC 4.929, and the Saitek Pro Flight Yoke/Throttle quadrant properly set up in FSUIPC to use the Flaps Axis and calibrated accordingly. All axis settings inside the FSX control settings have been deleted. FSUIPC controls all yoke, throttle quadrant, and rudder pedal axis. We ran across a problem using our virtual airlines ACARS in that the ACARS was reporting that I was using Flaps 40 on takeoff when I actually was using Flaps 1. Just to see what I am sending out, I installed Monitor FSUIPC Data and
×
×
  • 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.