John Dowson

Yeah - I had problems on my KIM-1 as well.... 🤣

If using FSUIPC with the Alpha or Bravo, make user that you are using the latest version of FSUIPC6 which has support for up to 128 buttons. If still using FSUIPC5, there are lua scripts available for both the Bravo and Alpha to handle the buttons outside the normal 0-31(or 1-32) button range. There is also a user contributed lua script to handle the Bravo lights (which I think is what the Aerosoft AFC Bridge / WASM is supposed to do), but I haven't tried this yet. I mat try this in the next few days (as my Bravo has just recently arrived!). John

To confirm it is a simconnect issue, you can activate simconnect logging by using a simconnect.ini file - see https://forum.simflight.com/topic/45074-help-logging-simconnect/. There is also a known issue with simconnect in that it fails when the maximum number of clients have been exceeded. If you have a simconnect.log file generated, you can count the number of connections used up to the point when it fails, and see if this number matches the number of simconnect connections used. You can increase that number using the maxClients attribute - see https://www.prepar3d.com/SDKv4/sdk/simconnect_api/configuration_files/configuration_files_overview.html.

If using FSUIPC, there is a user contribution to control the Honeycomb Bravo LEDs. Please see https://forum.simflight.com/topic/91539-lua-scripts-for-honeycomb-bravo-leds/ John P.S. There are also lua scripts to handle the buttton numbers > 32 for both the Honeycomb Bravo and Alpha Flight Controls. See https://forum.simflight.com/topic/91599-lua-scripts-for-honeycomb-bravo-quadrant-and-alpha-flight-controls-buttons-32/

This does nothing. This file is for information only (to trouble-shoot device issues) and is re-generated each time FSUIPC is ran. The first bit is correct (the .ini is the only important file, the rest are re-generated), but it shouldn't be located there.... Thats the location of the add-on.xml, and you should really change the actual installation folder to a different location during the installation process, as advised in the Installation guide. Unfortunately as this is the default it seems that most folks don't change this. You could always raise a feature request for this (over on the FSUIPC forums) and I will look into it. However, its simple to implement functionally but a bit of a pain to add to the current UI. I'll add it to the 'todo' list and have a think about it when things on MSFS/FSUIPC7 have calmed down a bit... John

if you are using FSUIPC, you can also use this to launch (and stop) this (or any other) application when needed. John

What do you mean by 'button tag'? If you mean that you do not see a button number in the assignment panel when you press the button (and your device is recognised), then it could be that the buttons are outside the assignable range (0-31). If that is the case, then you would need to use Lua to assign your button. There is a lua provided, called HidDemo.lua, which you can use and adapt to your needs. If you mean the L:var to control the action, then that would be dependent on the aircraft being used and may not be available. If there is no suitable lvar available, you can use mouse macros instead. If you require further help with FSUIPC6, please use the FSUIPC support forum: https://forum.simflight.com/forum/30-fsuipc-support-pete-dowson-modules/ John

You can just leave the entry field for WideFS blank - it shouldn't be a problem.

Or you could enable the logging of events and axis controls in FSUIPC to see whats happening.

Not quite correct @Ray, as a Target Frame Rate has been set in this case. Traffic will only be deleted to maintain the 30FPS frame rate, so can go higher. Then the Target frame rate is set, the 25 is the lower limit, so FSUIPC will not delete any traffic below 25 to maintain the target FPS.

Yes.

I'm just sorting out the key generation mechanism with SimMarket, Should be available to purchase by tomorrow. Pete hit the nail on the head really - I do not want to move to a subscription model but also have to generate some income or I cannot continue to support and develop FSUIPC. I did consider a donation model for this release but I'm afraid it just wasn't possible. I really don't think I need to justify the upgrade price any further (although I'm willing to discuss with anyone over a pint!). If you are not happy with the upgrade price, then don't purchase! FSUIPC5 will continue to be supported. And thanks to all those for their support and kind words. Regards to all.

No problems having both installed. For FSUIPC, for example, the new installer will allow you to have one FSUIPC installation for both sims, sharing the settings/config, or you can install twice to have separate copies for each sim. I've also manually installed some other add-ons to be shared between v4 and v5, and have not encountered any issues so far. John

Deleting the DLL.XML will prevent FSUIPC from loading. As Pete says, could you post over on the FSUIPC support forum (https://forum.simflight.com/forum/30-fsuipc-support-pete-dowson-modules/). When you post, could you attach your FSUIPC4 .log and .ini files (both located in your Modules folder). Also check the Windows Event Viewer to see if there is an error relating to the P3D crash, and if so also please paste that. Are you using any 3rd party programs that use FSUIPC? John

It could be a corrupt weather file. Try adding NoWeatherAtAll=Yes to the [General] section of your FSUIPC4.ini file. If that works, you have a corrupt weather (*.wx) file, or more usually the wxstationlist.bin file - try deleting that from your APP Data Roaming P3D folder if it is there. It will be regenerated the next time you run P3D. John