Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    11,149
  • Joined

  • Last visited

  • Days Won

    220

Posts posted by John Dowson

  1. It looks like your macro is assigned and being called:

    Quote

       303312 Mouse Event = [rect x40000137, action 3]
       316312 User Macro: engine1=:

    engine1_________
    ...
     

       373468 Mouse Event = [rect x40000136, action 3]
       381843 User Macro: engine2=:

    engine2_________
     

    Maybe you can show me your macro file?

    But, rather than using mouse-macros, you should first try either the standard controls and/or lvars. From this post, it looks like there are lvars available for both the engine start and the ignition: 

     

    John

  2. This would be a very complex lua script as it would basically have to implement the IAS hold function of an auto-pilot. Why don't you just use an auto-pilot?
    If the aircraft you are using does not have an auto-pilot (or the AP doesn't have an IAS-hold feature, which is not all that useful in prop aircraft IMHO), you could look into using the ATIasHold. freeware program - see 

    - main web page here: http://www.intrasystem.it/ATIas/ATIasHold.html :
        
    - ATIasHold: Hold the Speed with any Airplane. No need of any Autopilot. Using only the Engine Pressure.

    John

  3. Sorry, I have no idea -  there is no functionality for audio control in FSUIPC. I think you would be better off asking this question on the Asobo forums or the forums for the 3rd party software that you are using.

    Regards,

    John

  4. 2 hours ago, rxezz said:

    did find the files, I ran the sp1a but it closed prematurely.

    Did you try running as admin?

    2 hours ago, rxezz said:

    Ran the the simconnect but it closed too.

    What do you mean by this? SimConnect is an API, how can you run this? The fsx_sdk_sp1a.exe file is an installer that should install the SimConnect API version you need for the version installed.

    HOWEVER , your latest FSUIPC4 Install.log now shows that you DO have the correct SimConnect version installed for your build of FSX:

    Quote

    INSTALLATION FOR FSX:
    SetupPath="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X Steam Edition\"
    Checking version of the FSX EXE:
    ... Version 10.0.62607.0  (Need at least 10.0.60905.0)
    ...

    Found SimConnect build 10.0.62607.0
    ...

    What happens now when you run FSX? Can you show me your latest FSUIPC4.log file please.

    John

  5. 3 hours ago, 777GE90 said:

    Out of interest, what is the FSUIPC update for PMDG offets for exactly? Have you partnered with PMDG to get special offsets for their custom functionality? Or are you specifically finding new memory addresses for PMDG aircrafts yourself and then introducing offsets for them?

    PMDG provide an SDK for many (if not all) of their aircraft, which provide additional data for 3rd party programs by the use of a SimConnect facility called 'Client Data Areas'. This is quite technical, but it enables developers to request additional data for PMDG aircraft by the SimConnct API which is supported by most major flight simulators (e.g. P3D, FSX. XPlane, MSFS, FSW, ...). Unfortunately, althought the 737 for MSFS does have this facility, the actual details of the SDK (i.e. what data is provided) has still not been finalised.

    3 hours ago, 777GE90 said:

    Was curious as was thinking if you are partnering with PMDG then perhaps they can introduce a custom offset for this if it's not possible via simconnect / events?

    I have no partnership or special connection with PMDG (although they have kindly provided me with a license for the MSFS 737-700) but I can enquire about this via their support forum - as can anyone.

    The FMC pushback looks to be something implemented in the aircraft itself and looks to bypass the MSFS ground services, so the pushback information is not available. They should either provide this additional information via the SDK, or (better) also update the MSFS variables so that the pushback state can be detected. I will report this to them.

    John 

  6. 2 hours ago, rxezz said:

    i have done all you said

    Can you please be more specific...did you find such a folder an SDK installer and if so what were they called? Did you re-install FSUIPC4 - and if so, where is your new installation log?  Did you try using the loader? If so, what happened - and can you show me your FSUIP4.log file from when using that...

    John

  7. The FSUIPC7 separate documentation package is quite out-of-date at the moment. I will update it in the coming days. For now, to get the latest documentation, download and install FSUIPC7 and just select the Documentation component to install. This will also install FSUIPC7, but you can remove or just not use that if not needed. If using the SDK, it is also better to install that using the FSUIPC7 installer as that will also be more up-to-date.

    John

  8. What ACARS and virtual airlines system are you using? Have you tried their support first? How is FSUIPC involved?
    There are now many support topics on ACARS systems with MSFS and FSUIPC7 - try searching the forum to see if any of these previous reports are applicable.

    Otherwise, please supply more information - ACARS system and virtual airlines software you are using, what you are using FSUIPC7 for with these, and attach your FSUIPC7.log and FSUIPC7.ini files (both located in your FSUIPC7 installation folder).

    John

  9. On 8/23/2022 at 2:26 PM, michel78320 said:

    Can you explain to me what is the number returned by "com.writefeature"   ?
    Is it sent by the device?

    It is as documented: The returned value gives the number of bytes actually sent (or at least, placed in the buffer).

    On 8/23/2022 at 2:26 PM, michel78320 said:

    By the way, com.writefeature does not use "wrf"
    With Switch Panel, wrf = 2

    s = string.char (0 , 3 , 2 , 2, 0 , 0 , 0 )
    n = com.writefeature (dev1, s, 1)

    returns n=2 !

    The com.writefeature function just passes through to the windows HidD_SetFeature function. There are some 'correct size' checks and the passed in size may be adjusted - you can skip this parameter and the correct size should be used (I think!). The returned value will be what was actually written to the device' buffer.

    You could try logging HID activity to see what is happening. From the Log->Custom menu, enter 0x200. This should then log all HID activity.

  10. 4 minutes ago, John Dowson said:

    I am not familiar with how to request pushback via the FMC - if you could let me know I can test that here...

    Ok, I managed to request pushback via the FMC and I can see that that offset is not changing when using the FMC for this. I am afraid that this needs to be addressed by PMDG. They should either update/use the same simconnect SDK simvars/events or provide this information in their SDK.

    John

  11. 20 hours ago, 777GE90 said:

    Has anyone managed to figure out how to get FSUIPC to detect a PMDG 737 pushback when it's done via the PMDG FMC (perhaps another offset I can try?) Or is this something for their developers to fix?

    Offset  0x31F0 contains the correct pushback state when requesting/using the MSFS ground services. I am not familiar with how to request pushback via the FMC - if you could let me know I can test that here...

    John

  12. I have just checked assigning and calibrating as you do for the 747 and it works as expected here. I am therefore wondering if the following button assignments could be interfering:
     

    Quote

    1=RB,8,C65966,0     -{THROTTLE1_DECR}-
    2=UB,8,C65967,0     -{THROTTLE1_CUT}-
    3=RB,9,C65971,0     -{THROTTLE2_DECR}-
    4=UB,9,C65972,0     -{THROTTLE2_CUT}-

    5=RB,8,C65966,0     -{THROTTLE3_DECR}-
    6=UB,8,C65967,0     -{THROTTLE3_CUT}-
    7=RB,9,C65971,0     -{THROTTLE4_DECR}-
    8=UB,9,C65972,0     -{THROTTLE4_CUT}-

     

    Check your log (when Events logging activated, and maybe also Buttons & Keys) and see if button 9 is beunf detected as pressed and so sending decrease controls.

    Maybe also check the calibration of those axis in the Windows fame controllers panel to check they are the same there.

    Other than that, please show me your FSUIPC7.log as previously requested.

  13. Can you also activate logging for Events and Axis controls, and produce a short log where you load your aircraft and then move throttle 1 to full power anf then throttle 2. Then exit FSUIPC7 and show me your FSUIPC7.log file - you can zip/compress it if too large to attach.

    John
     

  14. When using two throttle axis to control four engines, it is more standard to assign one axis to Throttle1 and the second to Throttle2, and then calibrate for Throttle1 and Throttle2 and map the Throttle3/Throttle4 calibration using the map checkboxes (and not calibrate throttle3 or throttle4).

    Having said that, you should be able to use one axis for throttles 1 and 3, and the other for 2 and 4, so I am not sure why this is not working. Are you using the Asobo 747? If do, I can check this...

    John

  15. 12 hours ago, chanchu81 said:

    I wanted to know if this offset is supported on MSFS as I am doing some test and I manage the data thet I read from that offset to identify current visibility.

    Documentation says: 0E8A 2 Current visibility (Statue miles * 100) Ok Ok

    Why don't you just check the offset status document for FSUIPC7 / MSFS rather than quoting the documentation for other versions?
    This offset is clearly marked in red, i.e. not available or working.

    The old SimConnect weather interface has been deprecated in MSFS and is no longer available. 

    You could try offset 0x2DF0, which holds the simvar AMBIENT VISIBILITY, documented as 
        Visibility at the aircraft, in metres, as a 64-bit double floating point – for reading.
    (and in MSFS documentation: Ambient visibility (only measures ambient particle visibility - related to ambient density).

    John

  16. You are using FSX version 10.0.62607.0, but you only have the following SimConnect SDKs installed:

        Found SimConnect build 10.0.60905.0
        Found SimConnect build 10.0.61242.0
        Found SimConnect build 10.0.61259.0

    Could you check and see what is in the folder
        C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X Steam Edition\SDK
    One of those folders should be named after the FSX or SDK version number (mine is called SP1a) and inside that folder there should be an installer for the SDK - the one I have is called fsx_sdk_sp1a.exe. Could you find a similar file on your system (let me know the folder and file name please) and try running that. That should install the SDK valid for your FSX version.
    Once that is done, re-run the FSUIPC4 installer and try again. Any issues, send me your latest FSUIPC4 Install.log again as well as FSUIPC4.log file, if available.
     
    You can also try using the FSUIPC4_Loader.dll. I don't know much about this (before my time!). but the Installing and Registering FSUIPC4.pdf states:
    Quote

    The ‘emergency use only’ FSUIPC4_Loader
    The Loader DLL is an optional component which may help get passed the strange SimConnect
    crashes after initially installing FSUIPC4. If you've had these before, then try copying the
    FSUIPC4_Loader.DLL into the FS Modules folder and then re-run the Installer.

     

    John
  17. Are you using the LorbySceneryExport program?  Scenery installs abiding by the new L-M system for addons will NOT be seen by MakeRunways unless you use this program. Please see the provided MakeRwys README.pdf section on how to use this utility for P3Dv3,4 and 5.
    Also please check that you are using the latest version of MakeRwys, v5.13.

    If that doesn't resolve your issue  you can post again and @Pete Dowson may take a look.

    John

  18. 10 hours ago, Dreamflight767 said:

    Please close this.  I was able to edit by saving a copy of the .ini, made changes and copied those changes to the saved copy and pasting into my FSUIPC folder.

    Your assignments are always saved to the ini file. If this is not happening, then it could be due to windows (or anti-virus) protection on the FSUIPC7 installation folder. Check that you have not installed into a windows-protected folder such as Documents or Program Files.

    Note that if you are editing the ini file manually, you should do this either with FSUIPC not running, or for editing button and assignments sections, you can have FSUIPC running but with the assignment panel already open, then make your changes and click the Reload all buttons or Reload all assignments button. If you  manually change the ini and then open an assignments panel, your changes will be overwriiten.

    John

  19. 11 hours ago, Dreamflight767 said:

    I fixed this issue.  I just wasn't hitting "rescan" enough I guess.

    The first axis value change on any known axis will populate the axis assignment dialog with those details. You press the Rescan button to scan for a different axis. Sometimes a sensitive/jittering axis can make other axes difficult to be recognised - if this happens, you can click the Ignore Axis  button which will then ignore any values from that axis for the rest of the assignment session, i.e. until you close the Axes Assignment panel.

    John

  20. 39 minutes ago, 777GE90 said:

    Has anyone managed to figure out how to get FSUIPC to detect a PMDG 737 pushback when it's done via the PMDG FMC (perhaps another offset I can try?) Or is this something for their developers to fix?

    Presumably you have tried the standard offset for this at 0x31F0? There is a simvar called PUSHBACK ATTACHED, but this is not available by default in any offset - you can add this to a free user offset and check to see if the PMDG 737 is using/updating that simvar.

    The specific PMDG offsets are not available in the current release (v7.3.7), but will be available in the next release (v7.3.8) and there is a beta version out of this release that you can try, available here: 

     

    However, I don't see any offsets relating to pushback state in those offsets either.

    You can also try listing the available lvars to see if any look applicable, and if so then they can also be added to a free FSUIPC offset.

    Pushback and ground service handling in MSFS in general is quite different from other sims and I am not sure what is available without checking...I will rake a deeper look later in the week to see if I can see anything.

    John

×
×
  • 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.