Jump to content
The simFlight Network Forums

John Dowson

Members
 View Profile  See their activity

  • Posts

    13,544

  • Joined

  • Last visited

  • Days Won

    283

 Content Type 

Posts posted by John Dowson

  3. sim stops responding after 7 hours

    in FSUIPC Support Pete Dowson Modules

    Posted

    There is a known issue in the SimConnect SDK since FSX that affects P3D (all versions) and also MSFS. It occurs when the number of SimConnect clients is exceeded, and tends to happen after long flights when using several simconnect clients (as they often close the connection and re-connect when the connection stalls).
    I haven't got time to dig out the references now, but there are various posts in this forum where I have explained the issue, given references and also how to improve (by increasing the max number of allowed SimConnect clients in a SimConnect config file).

    John

  4. FSUIPC 7 caused MSFS CTD

    in FSUIPC7 MSFS

    Posted

    @daern I'm surprised about those events as your log shows FSUIPC7 exiting normally and that it was MSFS that crashed. I guess they are non-fatal errors due to the MSFS error.
    Your problem is almost certainly due to MSFS and you should raise a zendesk bug report. Btw, can you please ALWAYS attach your full log rather than pasting extracts, as there is further information I need to see, such as devices being used and the build version of FSUIPC (and any dlls) that you are using.

    @rvroman As you have not attached any relevant information (i.e. your logs) I can't really comment, but if it is similar to your previous log (or that of daern's) then it will also be the same issue.

    Maybe worth checking the MSFS forums for any similar reports - I haven't had much time to check out any issues with the latest release yet....

    John

  5. FSUIPC with HidVanguard/Guardian Issues

    in FSUIPC7 MSFS

    Posted

    6 hours ago, pilotjohn said:

    Is the "Button Assignment" window supposed to react to these externally triggered offset changes? I assume yes, but want to make sure

    Yes.

    6 hours ago, pilotjohn said:

    And does it matter whether FSUIPC is connected to MSFS or not in this case (I know for physical devices it works without MSFS connection)?

    Currently FSUIPC7 has to be connected to MSFS for the virtual button offsets to function correctly. I can look into making such assignments available without an FS connection. I've made a note to look into this at some point in the New Year, but this will be low priority.

    John

  6. FS2020 Aircraft Model and ICAO

    in FSUIPC Client DLL for .NET

    Posted

    Hi Paul,

    this is a known issue with the ICAO and Model strings. It has previously been reported in this post: 

    To get around this for the time being, I have added the ICAO designator, manufacturer and model (read directly from the aircraft.cfg file) to the following offsets:
        icao_type_designator: 0x0618, 16 bytes (including string terminator)
        icao_manufacturer: 0x09D2, 16 bytes (including string terminator)
        icao_model: 0x0B26, 32 bytes (including string terminator)

    However, those offsets won't be populated for all aircraft (see that post for details).

    At some point I am planning to replace the language specific strings with the strings from the language pac files, but I've no idea when I will get around to this, its pretty low on my list.

    Cheers,

    John

  8. Issue with FS2020 1.12.13.0 and PFC driver

    in FSUIPC7 MSFS

    Posted

    @Aircom Yes, I'm afraid your thread was hijacked by a different problem. I'm pretty sure that the new version won't help you. I'm at a loss as to what could cause.

    12 hours ago, Aircom said:

    If my quadrant fails in FS2020, it will also fail in P3D if I try just after the failure. It's as if the COM driver was impacted. I have to restart windows to fix it.

    So it seems that the COM port driver in windows is failing/crashing. Its hard to see how an MSFS update can affect this, unless its also doing something with the serial ports.
    Maybe you can check the windows Event viewer,  to see if you can see any failures there that could be related. Otherwise, maybe try the Windows SFC (system file checker), and maybe check that your mobo drivers are up to date.

  10. Button Offset Condition with signed (negative) value

    in FSUIPC7 MSFS

    Posted

    16 minutes ago, jaxx said:

    Like with the Alpha Yoke I think I'll need quite some special handling in LUA as there are again buttons outside the 32-button range and to get it working with automatic profiles for the different commercial/GA lever setups.

    Yes, I have heard that both of those Honeycomb devices have buttons outside of the 32 limit and need lua to be used in FSUIPC. I should be getting both the Bravo and the Alpha sometime in January, also updating from the Saitek ones.

    Btw, are you now using MSFS 1.12.13.0? I've had some reports of FSUIPC7 crashing with this version when using those Honeycomb devices and lua (HidDemo.lua), but am still awaiting details.

  12. FSUIPC with HidVanguard/Guardian Issues

    in FSUIPC7 MSFS

    Posted

    8 minutes ago, pilotjohn said:

    The GUIDs look the same for the same device, but the numbering changes (e.g. the device order). This was causing re-lettering for some reason (e.g. YOKO+ went from D to R for example).

    But it is due to the changing joystick numbers that the joyletter facility was added. This then matches the name and GUID to the letter, and so if the joy id changes then the same letter is still in use and so the assignments (to the letter) still work.
    If its generating a new letter for your device, then its not recognising it either due to a name or GUID change.

    13 minutes ago, pilotjohn said:

    The GUIDs look the same for the same device, but the numbering changes (e.g. the device order). This was causing re-lettering for some reason (e.g. YOKO+ went from D to R for example).

    Maybe you can attach you Joyscan.csv file.

    I have not used HidVanguard/Guardian, so do not know how it is affecting your devices or registry entries for those devices. BUT, FSUIPC must be able to determine what each individual device is, and this is mainly done from the GUIDs, although the id numbers are also used, especially when not using the Joy Letters.

    17 minutes ago, pilotjohn said:

    I would be willing to fork/adapt the vJoy Plugin to support FSUIPC directly somehow. Do you have suggestions on how an external program can trigger FSUIPC functionality?

    Specifically, how could I cause a button input to trigger an assignable event in FSUIPC? FSUIPC only seems to have Keys, Buttons, Axes. Keys is not a good solution because there's just not enough of them to not interfere with something else (e.g. its management is a nightmare when you have 100+ assignments).

    Ideally there would be a "virtual' tab, in addition to Buttons, where I could simply send some device ID and button ID externally, and assign things the same exact way that I assign them in Buttons. Is this viable? That is, essentially duplicating your button handling code, and create a new tab where some external API could be used to trigger assignments. Then I could change the vJoyPlugin in StreamDeck to send these "virtual" devices IDs and buttons which FSUIPC would react to (e.g. press/release events or something).

    Do you have any other suggestions?

     Sorry, I don't understand what you are trying to achieve here. What would a new 'virtual' tab provide over the current button tab? Virtual devices are just devices as far as FSUIPC is concerned, and are handled the same (w.r.t buttons and axes) as any other device. Maybe @Pete Dowson can advise, I'm not sure.
    I think the best solution really would be for MSFS to fix this issue - is it known and/or have you raised a zendesk report?

    Also, please be aware that I am now on holiday/winding down (announcement yet to be posted). I will be covering support occasionally over the festive season, mainly for urgent requests.
    All other support issues will now have to wait until I'm back to full time work around January 11th.

    John

     

  13. A320neo

    in FSUIPC7 MSFS

    Posted

    10 minutes ago, melchior.masset said:

    Has someone got a PDF file with the offsets for the FlyByWire A320neo ?

    FSUIPC offsets are general and for all aircraft, except for the specific offset area for PMDG (not available in MSFS/FSUIPC7).
    So the general documentation is applicable - the FSUIPC7 Offset status.pdf together with the offsetStatus-v0.x.ods spreadsheet.

    However, I'm not sure what is available using the FBW mod. There has been at least one reported case of an offset not being properly populated when using the FBW mod, but is ok with the included A320Neo.

    John

  15. Button Offset Condition with signed (negative) value

    in FSUIPC7 MSFS

    Posted

    13 minutes ago, jaxx said:

    If I see that behavior correctly it would just use my forward throttle as reverse throttle while toggled? That is not exactly what I wanted.

    Yes, that's how that control works.

    But if you have managed to set it up how you want it to function, thats great. And thanks for posting your lua solution.

    I should be getting a Honeycomb Bravo soon (according to Honeycomb....), so I may use your lua once it arrives.

    John

  16. FSUIPC with HidVanguard/Guardian Issues

    in FSUIPC7 MSFS

    Posted

    13 hours ago, pilotjohn said:

    1. The order of devices returned by HidGuardian seems to be random so FSUIPC always reassigned letters (this was fixed AutoAssignLetters=No)

    I don't understand this. It will only re-assign letters if/when it detects a new device. It looks like different GUIDs are being returned each time you run, and so different letters will be assigned as they are detected as new devices. Changing that parameter means that they are still detected, but letters won't be assigned.
    This won' help as the numbers (joy ids) being used for each device will also change.

    13 hours ago, pilotjohn said:

    2. Some of the devices (VirtualFly) didn't show up on launch, and letters using them were marked as "missing". However when I went to Axes, they were recognized by FSUIPC, but this caused a refresh, and the devices received new letters.

    I'm not sure why this would occur. Could the device have been 'asleep'? Maybe check the power management (in Windows) for that device/hub, and if using an external hub make sure that it is powered correctly.

    14 hours ago, pilotjohn said:

    Is there a possible fix in FSUIPC for #2 (some different scanning behavior on startup that is similar to when I open Axes?). That would resolve the issue.

    I don't think this would help, as the initial scan is identical to the scan when opening the axis page.

    I am also reticent to add hacks to fix issues caused by using other programs, especially if this is a temporary work-around for issues in MSFS.

    John

  17. FSUIPC works only when is selected

    in FSUIPC7 MSFS

    Posted

    2 minutes ago, emilio said:

    I'm using a SCPascal Script to communicate SISMO MCP to FSUIPC and sendkey function to a FS2020 windows, I have change to FSUIPC Windows and works perfect.

    So you are using the FSUIPC SDK to send keys? Or are you using the windows SendKey function?
    I am confused now about your support requests in this topic. Do you require assistance or not? What are you trying to do?

    Your previous posts were (or seemed) to be about not seeing key presses when MSFS has the focus, and now you are talking about sending key presses.

    If you require any further support, can you please clarify what you are trying to do and what your issues is.

    Thanks,

    John 

  18. Custom Programing Help Requested for Switches

    in FSUIPC7 MSFS

    Posted

    7 hours ago, Travis1992 said:

    Does anyone know if there is a way to "record" pressing switches in the cockpit and getting the Offset and Parameter values for each position? Essentially what is sent to the sim. I have looked through documentation before asking here, and can not find anything(not saying it doesn't exist).

    I think you are referring to the Mouse Macro facility,  which was available in previous versions of FSUIPC. This is currently not supported in FSUIPC7 as the MSFS SDK does not yet provide facilities for this.

    7 hours ago, Travis1992 said:

    My best example right now is the Parking Brake.
    I want to get the true values of "Parking Brake On/Set" and "Parking Brake Off/Released" So I can have it repeating when pressed. That way when my sim is turned on, the parking brake is always in the correct position my switch on my quadrant is indicating.

    I also want to do this with other switches and such, so it would be nice if the recording function was possible. I have seen such a function in older versions of FSUIPC, however it does not seem to be here yet. Maybe I have to wait for this feature.

    If there is a better way to do this, please let me know. I have been looking, and I am sure someone is going to point me somewhere more than likely, thank you in advanced and sorry for the troubles.

    It is generally always better to use controls/events where possible, as such assignments apply to many aircraft. Mouse macros are always aircraft specific.
    For the Parking Brakes, there is the Parking Brakes control, which acts as a toggle. You can just assign that to a button. If its a sticky button or switch (with different positions indicating on and off), then you can also add an offset condition (on 0x0BC8) to only send the control when required.
    Generally, you will find that there can be toggle controls (for on/off) or set controls (where you send a parameter to indicate the state to set). Both can be used with offset conditions (if there is an appropriate offset!) to only send the control required to maintain the state of the button with the sim. Please see the Advanced User Guide on offset conditions (P22).

    John 

     

  19. Button Offset Condition with signed (negative) value

    in FSUIPC7 MSFS

    Posted

    12 hours ago, jaxx said:

    Same behavior from Lua. I'm now writing to the offsets with Lua Events and everything is working fine. 🙂

    So is it working now? I'm slightly confused...
    Have you looked at using the Throttle Reverse Thrust Toggle control? If that is supported in the aircraft you are using, this allows you to use the full range of your throttle axis for reverse thrust when set.

    John

  21. Can I get away with this?

    in FSUIPC Support Pete Dowson Modules

    Posted

    15 hours ago, Pete Dowson said:

    Perhaps it should carry on and look for other matches. Never thought of cases like yours where there'd be multiple events for the same function.

    As there is no way to specify which event to cancel, I think it should really continue and cancel all registered events for that function.
    I'll update this at some point, most probably for the next release (FSUIPC6 & 7 only though).

    John

  22. FSUIPC 7 caused MSFS CTD

    in FSUIPC7 MSFS

    Posted

    9 hours ago, rvroman said:

    This only seems to have started since updating to 7.02. I will try going back to 7.01 and advise.

    There really are no changes between 7.0.1 and 7.0.2 that could cause this.

    Your log shows simconnect failing, then FSUIPC7  exiting when it detects that MSFS has closed/crashed.
    I think the issue is almost certainly with MSFS or the SDK, as you say. Are you using any other SimConnect clients (or Track-IR)? It could be a known issue (since FSX) with the number of simconnect client connections being exceeded - you can activate SimConnect logging to determine this, and if this is the issue you could increase the allowed number of clients (or directly do this to see if things improve). However, if this was the issue, I would have expected to see some TransmitClientEvent errors in your log.
    You should also raise a crash report with Asobo (via zendesk), and include the crash report from the windows event viewer.

    John

  25. FLC Offset and event issue

    in FSUIPC7 MSFS

    Posted

    1 hour ago, fjgaspar said:

    After assign a key to FLC activate/deactivate, I have assigned that press key to a button in my panel (I use mobiflight for that). Don't work, the press on the button doesn't have any effect.

    If a key press works in the sim, AND it is one that is supported via a corresponding key input event string (not all keys are supported), then it should also work via a key press assignment (to a button, for example) in FSUIPC7. However, I cannot advise if using mobiflight for that,


     

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