Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    13,265
  • Joined

  • Last visited

  • Days Won

    271

Posts posted by John Dowson

  1. 1 hour ago, N987PL said:

    First of all, I can't find another posting about FSUIPC and the DA62 in MSFS, so I'm posting here as a first pass attempt to be in the right place...

    If you can't find an existing topic, please create a new one with a relevant title, rather than posting in another topic that has nothing to do with your issue. I have moved your post to a new topic.

    2 hours ago, N987PL said:

    Everything works (not sure why my two throttles are mapped differently, but they work fine)

    Throttle2 (Direct) will use AXIS_THROTTLE2_SET, so the settings are basically the same. The only difference will be that Throttle2 will be calibrated before being sent to the FS, and Throttle1 will be sent uncalibrated, received back and masked, calibrated and then resent. Probably better to have them both assigned the same way though.

    Not sure why the Aileron assignment isn't working though - assigning direct to Aileron works fine here. If you go to the axis assignment calibration tab, do you see the axis/in-out values change for the aileron?

    You can also try logging Axis Controls (Log -> Axis Controls) open the logging console (Log -> Open Console) and see if you can see the aileron axis values being sent. You may see a lot of LIGHT_POTENTIOMETER_SET events logged - you can ignore these by adding
        DontLogThese=67227
    to the [Profile.DA62X] section of your FSUIPC7.ini file.

    Please report back what you find, and maybe also attach your log again, if relevant.

    I am finishing now for the day - I may take another look tomorrow, but if not it will be on Monday now.

    John

     

  2. 4 minutes ago, quintinm said:

    I didn't start Linda Yet ! Does it starts automatically wight FSUIPC ?

    It is probably started from your ipcReady.lua.... but it doesn't matter if you don't have any issues. Your log shows that offset A000 is being updated with the correct heading, you are just logging that offset incorrectly as far as I can see....

     

  3. 13 minutes ago, quintinm said:

    (I can see on top of my screen and it's written Monitor IPC:A000 (FLT64) = 0.000000

    It is not a FLT64 (8-bytes) but a an unsigned word - 2 bytes (U16) , as also used in the lua script (UW) - try logging it as that (i.e. U16), and also please send the offset logging to the normal log file as well.

    The logging in the lua is definitely showing the correct value:

    Quote

      1537546 LUA.2: Heading updated: 221
      1538156 LUA.2: Heading updated: 222
      1538828 LUA.2: Heading updated: 223

     

    18 minutes ago, quintinm said:

    Here included my log file since the beginning when I start MSFS until I close the simulator

    You still have Linda running and have not set only the logging asked for...

    John

  4. What is the issue? It looks like the script is working:

    Quote

       186469 LUA.2: Heading updated: 220

    ?

    Can you please explain what your issue is, and attach a full log file (i.e. always please exit FSUIPC7 before attaching a log file, and never use the New Log feature) with logging for lua plugins enabled (and no other logging set please) as well as offset monitoring for offset A000. Also please disable Linda for the time being - you can re-enable it after we have solved your problem. 

    John

  5. 12 hours ago, Mattie941 said:

    When restarting FSX, I sometimes get an error messaging saying the FSUIPC is the cause of the crash and that it is not recommended to run the software. 

    This can happen if/when FSX crashes, even though the crash is not related to FSUIPC. You can usually safely ignore this, but if it persists, please see this FAQ entry: 

     

    If the crash is not related too FSUIPC, I am not sure that I will be able to help. Can you attach an FSUIPC4.log file from when FSX CTDs and I can take a look.

    Does the crash still occur when not using Vatsim or vPilot? You could try setting FSUIPC to no receive Ai data to see if that makes a difference - to do this, set
           ProvideAIdata=No
    in the [General] section of your FSUIPC4.ini.

    There is a known issue that can cause CTDs with FSUIPC, which is a corrupt weather file. However, this usually results in a CTD soon after start-up. You can also eliminate this by using the following ini parameter (also as a test):
        NoWeatherAtAll=Yes
     

  6. Quote

          421 LogOptions=20000000 00000005

    You have Event logging acticated, as well as some other logging (00000005). If you don't want logging, deactivate it from the :Log menu.

    Please read the section on logging in the User guide.

  7. Please attach a full FSUIPC7.log file (i.e. do not use the New Log button) as well as your FSUIPC7.ini.

    2 hours ago, quintinm said:

    Since I made the changes for my HDG (see the other topic you answered me) the log continues to log some events (see file here included).

    I can't see how those changes could cause this logging to restart - looks like the DontLogThese isn't set, but your files should show the reason...

  8. 12 hours ago, cellular55 said:

    is there an offset to understand if the avatar mode is on or off to execute different actions respect that?

    Not by default.

    12 hours ago, cellular55 said:

    I have  tried to read the Sim variable 'AVATAR MOSE IS ATTACHED' with a LUA script, but with no success.

    How are you doing this? The only way to read a simvar not held in an offset in lua would be to execute some calculator code to write the simvar value to an lvar (local variable) and then read the lvar.

    However, the best way to read (and write/update) to the AVATAR MODE IS ATTACHED simvar would be to add it to a free FSUIPC offset and then use that offset. To do this, please see the Advanced User guide section Additional Simulator Variables (simvars) to FSUIPC Offsets on page 36.

    John

  9. 12 hours ago, quintinm said:

    I noticed that the A000 offset didn't change. I tough I was the same value than the heading ? but still valued 0.000

    Did you add the simvar AUTOPILOT HEADING LOCK DIR to that offset via the myoffsets.txt file? Do you see the following entry in your FSUIPC7.log file:

    Quote

        28781     Adding simvar 'AUTOPILOT HEADING LOCK DIR' to offset A000 (size 2, type 'F64') for read-only access

    ?

    12 hours ago, quintinm said:

    see picture here included

    Please attach files, not pictures.

  10. First, you posted in the User Contributions sub-forum where it explicitly states NOT for support requests. I have moved your post to the main support forum

    23 minutes ago, efeuslu said:

    Does anybody know how to assign shortcuts to my throttle quadrant such as HDG, SPD, ALT  increase or decrease

    What do you mean by shortcuts? Why not just assign to the standard controls? Or if the aircraft comes with an SDK and/or custom controls, you can try using them.
    Is this an add-on aircraft, and if so by who?

    If you look in your FSUIPC Documents folder, you will see a text file that contains a list if all available controls - open that in an editor and search for the controls you need. They are all available from the assignments drop-down menu. e.g. for heading try:
        65880   HEADING_BUG_DEC
        65879   HEADING_BUG_INC
    and/or the FSUIPC added controls (see Advanced User guide p 29)
       1024 Heading Bug Dec Fast (–10)
        1025 Heading Bug Inc Fast (+10)

    There are similar controls for SPD and ALT.

    John

     

  11. Not 100% sure, but it will probably be missed, but this depends when the event flag on the button press is cleared - either when the function is called (in which case the 2nd button press will be registered) or when the function is finished (in which case it will be missed). I think its the latter, but should be easy to write a simple test lua to clarify if needed.

    Anyway, the function should really finish before the second button press, and you can also use button repeats.

    John

  12. 11 minutes ago, Rajveerchandolia101 said:

    Trial License Please for this month.

    You have been using the trial license since April. If you want to continue using FSUIPC7, please buy a license.

    I have stopped providing one available to download as this is being abused by people, like you, who are continually using the trial license instead of purchasing. 

    Your request is therefore denied.

    John

  13. 20 minutes ago, Jeff Enlow said:

    Ok it appears to be connecting.

    Finally...

    20 minutes ago, Jeff Enlow said:

    No ailerons, elevators or throttle.

    Any ideas on this issue?

    No. Have you enabled and configured/calibrated these? Please read the PFC.dll documentation:

    Quote

    These pages are used to enable and calibrate the main flight controls, trims and steering tiller, if these are available and connected through the PFC system. These controls are not all enabled by default as they can produce unwanted interference with game port or USB connected joysticks and pedals if you are using those for any of the main flight control in Flight Sim. Only you know which devices you have connected where. There is no automatic way the driver can configure this.

    Please ALWAYS check the documentation before posting. I do not have any PFC devices - any questions you ask I will just read the provided documentation for an answer. It will save us both time if you read the documentation before posting for support.

    John

  14. 39 minutes ago, pipos said:

    Hello John! Could you send a trial version? Considering buing SPAD.next and FSUIPC (MSFS2020 mainly)

     

    14 minutes ago, florzando said:

    Hello John! I would like a trial license, could send me one please, THANK YOU!

    I have sent you both a trial license via PM.

    John

  15. 8 minutes ago, Jeff Enlow said:

    Ok I did both.

    No you did not...

    The PFCcom64.dll file should be in your FSUIPC7 installation folder, not in a sub-folder. it is not in the correct location....

    It also looks like you have saved the FSUIPC7.key file as FSUIPC7.key.txt - please check and correct this, This is probably also related to your windows explorer settings which you should change...

    Please also change your windows explorer settings to show the extensions of known file types. This will help you to identify your files when needed. This is explained both in the FSUIPC7 installation and registration manual and in the 'If you cannot see  the DLL...' text document under your PFCDLL folder.

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