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. Could you add the following to your FSUIPC4.ini file in the [General] section please:
        NoWeatherAtAll=Yes
        Debug=Please
        LogExtras=x400
    and generate and show me a log file with that logging enabled. Also, after the crash, can you check the windows event viewer and paste any crash event information you find there.

    But unfortunately I don't think I can do much about this... FSUIPC4 has been closed for development for many years, and it will be difficult for me to track down this issue without purchasing this aircraft...I will look into this further though if you can provide me with the above information.

    You also don't seem to be using FSUIPC4 for much, if anything...

     John

  2. I know that you weren't blaming FSUIPC. Looking at the file you posted, 2 things stand out:

    1. You are using an old unsupported version of FSUIPC - 7.3.3. The latest and only supported version is 7.3.8 (as well as the 7.3.9 beta available in the announcements sub-forum). Please updated to a supported version,

    2. Your FSUIPC7.ini file shows that you are not using FSUIPC7 for anything at the moment - you have no assignments and your VRI instrument radio stack is not even detected.

    So as FSUIPC7 is not involved at all, I cannot really help. I suggest you try support from VRI or Aerosoft for this issue.

    I have updated the title of your post so that it may attract other users of this hardware who may be able to assist.

    John

  3. Hi Joe,

    better search functionality for the controls/presets drop-downs has been requested many times already, but its not that easy to implement with the current toolkit used. FSUIPC uses the old Win32 API, not javascript, and doesn't filter the drop-down list - it just positions. I did look into filtering the list a few years ago, but it was messy and slow - too slow to use. This type of filtering is just not a natural fit for the win32 combo box (see https://stackoverflow.com/questions/71584954/how-to-filter-combobox-by-textsearch-input-win32-api).

    I will look at this again, when time permits, but for now I recommend using the MF HubHob site to search for presets (https://hubhop.mobiflight.com/presets/), and the automatically generated text file (Controls List for MSFS Build 999.txt) to search for NSFS controls/events. Not ideal, I know.

    Also, for presets, you can always copy the presets for the aircraft that you use from the events.txt file to a myevents.txt file, and then remove the events.txt file. This will restrict the presets available to the aircraft that you fly.

    Thanks for taking the time to provide an example, but it is of little use due to the way drop-down menus are implemented in win32.

    Regards,

    John

  4. "ctrl+4" default assignment is to Toggle Instrument View 4. So it sounds like its only functioning when the radio panel is displayed, as well as having to trigger it with the mouse.
    I don't see how FSUIPC can be involved - but how are you using FSUIPC? Can you show me your FSUIPC7.ini file and an FSUIPC7.log file and I will take a look.
    I can then maybe suggest some logging to see if that sheds any light on the issue.

    John

  5. 20 minutes ago, Keight said:

    yes as I wrote this works but I am trying to set the "5" part of the  "L_CDU_5" by variable n.

    But you cannot do this, as cdukey is a string - just because that holds the variable name, it is not that variable.
    You could try with:

    ipc.control(_G[cdukey], Click_L)

    see https://stackoverflow.com/questions/43776809/how-to-use-string-as-variable-name-in-lua, or google further...

    John

     

    • Thanks 1
  6. First, you posted in the Download Links sub-forum where it explicitly states Not for support requests. I have moved your post to the main support forum, where it belongs.

    As for your issue, I cannot say as I don't have that controller, but I don't see why it wouldn't work. I can provide you with a tine-limited trial license if you would like to try.

    John

  7. I don't have the PMDG 737-800 so it is difficult to advise... Try activating logging for events, open the logging console window, click the button in the UI and see what, if anything, is logged. It is probably using the Rotor Brake control with a specific parameter indicating the action.
    The 737-700 uses the following, which is available as a preset:
        PMDG_B737-7_MCP_ALT_INTV_BUTTON : 88501 (>K:ROTOR_BRAKE)
    i.e. the Rotor Brake control with a parameter of 88501. Use logging, as advised, to check the same parameter is used, or use the one logged.

     

  8. You could use lua. If the values you want to change are held in simvars that are writeable, then check if the simvar is already held in an offset and if so you can just write/update the offset value using the lua library. If the simvar isn't writeable, then there is most probablt an event you can use instead, which you can also send using lua ipc.control, e.g. for changing the time you probably need to use the Zulu Hours/Minutes/Day/Year Set control.

    See the Offset status document to see what simvars are held in what offset, and whether writeable or not. You can also check the MSFS/Asobo documentation on available simvars and events, and there is a file called Controls List for MSFS Build 999.txt which also lists available events/controls. For lua, check the FSUIPC Lua Library.pdf document, and maybe the FSUIPC Lua Plug-Ins.pdf and the provided examples (in Example LUA plugins.zip).

    John

  9. On 9/16/2022 at 5:36 PM, kaha said:

    "Starter 1 Held" works with other aircraft, though.  Where is the issue? MSFS, FSUIPC, that specific aircraft? I'm at a loss.

    Well, if it works with other aircraft it sounds like its an issue for that specific aircraft, but as you don't say which aircraft this is I cannot help...
    Some controls work when assigned in MSFS but not wen sent from external applications, and this can be aircraft dependent., There are usually solutions around this issue, but I need to know what aircraft you are using.

    John

  10. Your log shows there are issues with duplicate ids in your registry, as well as a missing device:

    Quote

          188 Product= <not readable at this time: maybe device disconnected?>
          188    Vendor=1532, Product=0208 (Version 1.1)
          188    GUIDs returned for product: VID_1532&PID_0208:
          188       GUID= {3B622070-5FA2-11EC-8001-444553540000}
          188       Details: Btns=1, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
          188       GUID= {3B622070-5FA2-11EC-8002-444553540000}
          188       Details: Btns=24, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X255,Y255,Z255
    ...
          203    WARNING: Joystick ID 2 is duplicated in Registry
          219    WARNING: Joystick ID 4 is duplicated in Registry
          219    WARNING: Joystick ID 0 is duplicated in Registry
     

    But your yoke and VPC joystick are detected, and the latter acquired for use, but with the same id as your Razer Tartarus Chroma:

    Quote

          188 Product= GoFlight YOKE
          188    Manufacturer= GoFlight Technology Inc.
          188    Vendor=09F3, Product=0029 (Version 0.1)
          188    GUIDs returned for product: VID_09F3&PID_0029:
          188       GUID= {97185C40-98C8-11EC-8001-444553540000}
          188       Details: Btns=13, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
          188 Product= L-VPC Stick WarBRD
          188    Manufacturer= VIRPIL Controls 20220304
          188    Serial Number= FF
          188    Vendor=3344, Product=80CB (Version 1.0)
    ...
          219 Device acquired for use:
          219    Joystick ID = 6 (Registry okay)
          219    6=Razer Tartarus Chroma
          219    6.GUID={3B622070-5FA2-11EC-8002-444553540000}
          235 Device acquired for use:
          235    Joystick ID = 6 (Registry okay)
          235    6=LEFT VPC Stick WarBRD
          235    6.GUID={3B622070-5FA2-11EC-8002-444553540000}
     

    That is very strange,,, Could you also show me your FSUIPC6.ini file please - we can try using that to change/reset the ids.

    On 9/15/2022 at 9:47 AM, VERTSPD said:

    Also worth mentioning maybe, I am running FSUIPC 7 on another disk with MSFS 2020.

    With the same devices? And all is ok there? If that is the case, maybe also show me your FSUIPC7.ini and an FSUIPC7.log file for comparison.

    John

  11. Your ini shows multiple assignments, which is why they are grayed-out in the assignments tab:

    Quote

    ...
    19=PD,6,C65752,0     -{PARKING_BRAKES}-
    20=UD,6,C65752,0     -{PARKING_BRAKES}-
    ...
    76=PD,6,C65752,0     -{PARKING_BRAKES}-
    77=UD,6,C65752,0     -{PARKING_BRAKES}-
    78=PD,7,C65752,0     -{PARKING_BRAKES}-
     

    So when you press button 6, assignments 19 and 76 are triggered, so toggles twice resulting in the same state. and when you release, assignments 20 and 77 are triggered, again two toggles resulting in no change to the parking brake state.

    On 9/14/2022 at 7:57 AM, ArJuna said:

    Here you can see the other side of the rocker:

    19=PD,6,C65752,0     -{PARKING_BRAKES}-
    20=UD,6,C65752,0     -{PARKING_BRAKES}-
    21=RD,7,C65588,0     -{PARKING_BRAKES}-

    It has worked great for me for years. 

    But I don't see how this could have worked with FSUIPC5, as the assignments are still the same.

    You can always set logging for Buttons & Keys as well as Events, open the logging console and you can see what is being sent when you press or release the button in real-time. This should tell you what is going on.

    Note that as you have overloaded/multiple assignments, you will have to adjust/remove these by editing the ini file directly rather than using the button assignments panel.

    John

  12. First, you posted in the sub-forum for FSUIPC7 / MSFS2020. As you are using FSUIPC4 and FSX-SE, I have moved your post to the main support forum.

    Which throttle axis are you using? Did you try other throttle axes? If not, please do. And are you calibrating with a reverse zone or not?

    I am not familiar with the Eaglesoft C750 2.0, but maybe check the configuration for that aircraft, as some Eaglesoft aircraft require to be configured, e.g. see this for the Eaglesoft Citation: https://www.avsim.com/forums/topic/377514-eaglesoft-citation-x-problem-with-idle-and-throttle/

    Otherwise, please show me your FSUIPC4.ini and FSUIPC4.log files, the latter with axes logging enabled and move the throttle through its full range and exit.

    John

  13. The issue seems to be that the name of the device (T.A320 Pilot) is now missing. Not sure why this is...do yo have any specific drivers installed or any additional software for this controller?
    If so, you could try uninstalling and using the windows default drivers to see if that makes a difference.

    On 9/12/2022 at 8:29 AM, Nikolaj.Delaney said:

    The "Autoassignletters=no" does nothing, it always shows up with a different ID.

    This controls automatic assignment of joyletters, not ids. If you can't get FSUIPC to read the name of the device from the registry correctly, then you could try without using the joyletters facility. To do this, try the attached ini where I have reverted your assignments to use the joy ids rather than the letters.,

    John

    FSUIPC7.ini

  14. On 9/12/2022 at 2:31 AM, ark1320 said:

    Q1.  Is there a way to insert a timed delay into a multi-line macro? I thinking of something like using ipc.sleep() in a Lua script. So you might have:

    Yes - there is an FSUIPC-added control that you can use for this - from the Advanced User guide, P29:
       

    1152 Pause (ms) – this adds a delay in ms. It can be used to insert a delay between key press/releases and mouse
    operations (where needed)

     

    On 9/12/2022 at 2:31 AM, ark1320 said:

    I take this to mean that the multi-line Lvar macro can only take different actions with the same Lvar, e.g, you could set the Lvar in one line, and then maybe Inc that value in the next, and then maybe toggle the lvar, etc. So all (any) actions have to be on the same Lvar. Or do I misunderstand the line from the Advanced users guide?

    Yes, this is correct.

    John

  15. 8 hours ago, Veefe said:

    I've upgraded the FSUIPC from 7.3.7 to 7.3.8 and now the custom presets as PMDG B737-7 Fuel cutoff levers are missing.
    The events.txt (with the presets for PMDG and other aircrafts) are in the FSUIPC7 folder at C:/FSUIPC7
    there is any solution? or something I am missing?

    There is an issue with 7.3.8 in that the presets won't load unless you add the following to your FSUIPC7.ini:

    [WAPI]
    EnableWAPI=Yes

    Alternatively, try with the latest beta available here: 

     

    8 hours ago, Veefe said:

    The presets for PMDG 737-7 will work with the PMDG 737-8 ?? I just have the 738 installed.

    I don't know, I don't have the 737-800. Maybe they do, otherwise I would expect to see new presets for this aircraft on the MF hub-hop site. Try them and see...

    John

  16. On 9/11/2022 at 6:03 PM, nightbeast said:

    I tried updating to 7.3.0.8 and I still ran into crashing...  I've looked in my FSUIPC folder, but I don't see a FSUIPC7.log file.  Where would that be located so I can get that over to you as well?

    The FSUIPC7.log file will certainly be in the FSUIPC7 installation folder. You probably have windows explorer set to hide extensions of known file types. Change that - see the appendix in the Installation and registration guide for details.

    If FSUIPC7 crashed, was MSFS still running? MSFS crashing on long flights is a long standing issue (check the Asobo forums for details), and when MSFS crashes that can cause FSUIPC7 to close down. Are there any MSFS crash events before the FSUIPC7 one? Your FSUIPC7.log file would confirm if it was FSUIPC7 that crashed or MSFS.

    Note that there is also a beta that you could try that has a fix for a CTD relating to lvar/hvar reloading, but I don't think this is your issue. The latest beta is available from here: 

    John

     

  17. On 9/11/2022 at 2:23 PM, mroschk said:

    But when i start MSFS, FSUIPC starts also, and the no Axis are working.

    You need to show me your FSUIPC7.ini and FSUIPC7.log files, the latter with Axis logging enabled - start MSFS and FSUIPC7, load an aircraft and move an assigned axis or two, then exit FSUIPC7 and show me the .log and .ini.

    On 9/11/2022 at 2:23 PM, mroschk said:

    Then i have to click on the FSUIPC Symbow and then on Axis. 
    Then move some axis and click ok.

    But this will change/alter an axis assignment...what happens if you click cancel?

    On 9/11/2022 at 2:23 PM, mroschk said:

    In MSFS i have checked "fast WASM ..." ... could that be the Issue ?

    I haven't seen that option...I will take a look, but that certainly wouldn't affect assignments. The WASM is only used for lvars, hvars and calculator code.

    On 9/11/2022 at 2:23 PM, mroschk said:

    The second Issue is when i open FSUIPC Window and click on "Reload all assignments", then the Axis of the Rudder as example, changes from 

    "send direct to FSUIPC calibration" to "Send to FS as normal axis"

    I can't see how that can happen...can you show me a screenshot of before and after you click the reload button please.

    John

    P.S. Sorry for the delay - I was on holiday for the week.

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