Jump to content
The simFlight Network Forums

Luke Kolin

Members
 View Profile  See their activity

  • Posts

    351

  • Joined

  • Last visited

 Content Type 

Everything posted by Luke Kolin

  1. Luke Kolin
    I've seen this before, and can duplicate it right now. 5.123c with Prepar3D 4.1.7.22841. Cheers!
  2. Luke Kolin
    Certain payware aircraft (PMDG + LDS) allow one to read the transponder mode via their SDK. I would check the iFly documentation to see if it is the same. Cheers!
  3. Luke Kolin
    Thanks Pete, you are correct I had it disabled. Thomas, thank you for the screen shot. The challenge I had with the earlier log entry was that it just showed the P3D version and not the offset data. Cheers!
  4. Luke Kolin
    I disagree. I am running the same build but here is what I get: Cheers!
  5. Luke Kolin
    Pete, is offset 024C functional in Prepar3D v3? I am getting a zero in this area, both programatically and via an offset monitor. I understand it returns zero in v4, but is it expected to work in the 32-bit simulators? Cheers!
  6. Luke Kolin
    You went away on vacation, and even extended your absence from the forum, and P3D v4.2 still isn't out. LM clearly isn't holding up their end of the bargain. Just so I'm clear, are you saying it's a documentation only change and the existing P3D versions will work correctly once we have the right offsets? Cheers!
  7. Luke Kolin
    Pete and I have already discussed the fix: I expect it in 5.123 or soon afterwards, unless Pete has further questions. Cheers!
  8. Luke Kolin
    I think it looks good from this end. Cheers! Luke
  9. Luke Kolin
    Do you have the function name capitalized properly? Cheers!
  10. Luke Kolin
    Welcome back (when you read this).... just got feedback that correcting for the mis-sized offset fixes things. You can make the change. Cheers!
  11. Luke Kolin
    Unfortunately, this isn't a fact. I get reports of freezing with unregistered versions of FSUIPC, and I have a registered version that works flawlessly with PMDG 737 and 777 aircraft on flights of up to 16 hours. There's definitely something related to flight saving, but I'm pretty certain that it's not FSUIPC that is the cause, merely the trigger. Cheers! Luke
  12. Luke Kolin
    Keep in mind that you can encode both an int and a float in 32-bits. It looks like with SIOC you're taking a 32-bit floating point number from the offset and reading it like it is an integer. Cheers! Luke
  13. Luke Kolin
    I believe the SimConnect structs are all "packed", ie. not aligned on a WORD/DWORD boundary, but it's been a few years since I last poked at it. I have some calls out for feedback, we'll see what they say. Cheers! Luke
  14. Luke Kolin
    I'll give this a try. Because I'm slow this afternoon, everything after 65ED should be +2? Cheers! Luke
  15. Luke Kolin
    That's my point. The header file included with the SDK has this: // Rain Protection unsigned char WIPERS_Selector[2]; // left/right 0: OFF 1: INT 2: LOW 3:HIGH; INT applies only to 747-8 bool WASHER_Sw[2]; // left/right MOMENTARY action bool RAIN_REP_Sw[2]; // left/right MOMENTARY action, passenger only I *think* the rest of the file is OK. I can't actually check it, I am in the same boat as yourself not owning the 744v3. If you can create a beta copy I should be able to get some rapid feedback. Cheers! Luke
  16. Luke Kolin
    I've found.... something. When comparing your docs to the PMDG SDK documentation I've found the following discrepancies: 64F8 - FSUIPC: APU_AnnunLowPressure[2], PMDG: Wipers_Select[2] 64FA - FSUIPC: APU_AnnunFault[2], PMDG: Washer_Sw[2] 64FC - FSUIPC: APU_AnnnOverspeed[2], PMDG: Rain_Rep_Sw[2] The data sizes match, but I don't see anything in the PMDG docs for those specific indicators. Might just be a typo. The real issue (I think) is in offset 65ED: It's the brake pressure needle - PMDG has it as an INT, whereas you have it as a 2-byte WORD. Are you shrinking the size internally, or is this an error? That might explain why everything farther down is off. Cheers!
  17. Luke Kolin
    What do you mean? What error do you get? Cheers! Luke
  18. Luke Kolin
    Did you do what it told you to do and ran it with elevated permissions? Cheers! Luke
  19. Luke Kolin
    I can confirm that 5.121 prevented P3Dv4 from loading, and 121a appears to let it load. I am enclosing both logs. FSUIPC5.log FSUIPC5_prev.log
  20. Luke Kolin
    Now you have me curious. I'll take a peek on my end and see what's going on. Cheers! Luke
  21. Luke Kolin
    Pete, your FSUIPC4 installers have a manifest that requests escalated permissions; no need to run as admin as it will automatically request to do that. The FSUIPC5 installers do not appear to have this. Is there any chance this could be added to them? It makes running them out of the ZIP easier since I don't have to extract them from the archive. On a side note, when you do your list of changes would it be possible to list the version that each change was added? Cheers! Luke
  22. Luke Kolin
    No need to panic. The PMDG aircraft come with an aircraft SDK (in the PMDG folder under your simulator directory). There should be a .h file which at its end has a listing of the control names and their relevant IDs. As an example, I have a joystick button set to toggle the autopilot disconnect bar in the PMDG737. The event to toggle this is defined as EVT_MCP_DISENGAGE_BAR, and its value is defined in the file as (THIRD_PARTY_EVENT_ID_MIN + 406). THIRD_PARTY_EVENT_ID_MIN is 69632, so the control I need to pass to P3D is 69632+406 which is 70042. Cheers! Luke
  23. Luke Kolin
    Yes it does - when sending a custom control you just have to calculate and enter the control number manually. Cheers! Luke
  24. Luke Kolin
    I'll take a further look - based on what I see the autopilot mode offsets aren't being read either so the problem may exist farther up. I'll compare the include file with your offset documentation and see if the sizes match. Cheers! Luke
  25. Luke Kolin
    On a side note Pete, I've had several users report that the PMDG 744v2 fuel tank offsets appear to be reading zero. I've put in a workaround, but if you have an eval copy of the 744 would you be able to check that these offsets are in fact functional? The FSUIPC5 logs I've been given indicate FSUIPC 5.11; P3Dv4 build 21686 and have the "PMDG 747 offsets enabled" log entry. Cheers! Luke
×
×
  • 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.