John Dowson

This shouldn't be the case. If you have correctly added the ProvideAIdata=No to the correct place, you should see the following informational message logged near the beginning of your FSUIPC7.log file, after the device scan log: 641 ### Note: AI Traffic related facilities and data are inhibited! and there should be no other log messages relating to the number of AI traffic. Can you check again please, and if you see such a message can you post your FSUIPC7.log and .,ini files and I'll take a look. John

@ark1320 You can try the attached lua script and adjust as needed. It pops up a window asking for a number, terminated by an enter/return key. It just logs the number entered. John askTest.lua

Yes, the easiest way to do this is to just create a new profile for each of your controllers as new profiles are empty. It all depends on how you want to set things up, and can also depend upon which aircraft you are using, but generally its something in between. Currently there are quite a few controls/events that aren't working via the SDK (e.g. to control views), and there are also quite a lot of controls available in MSFS that have not been exposed via SimConnect, and so are currently not available directly via FSUIPC. There is no problem mixing-and-matching assignments between MSFS and FSUIPC7, but just make sure that you are only assigning each axis and/or button/switch in only one place. For controls that are available in MSFS but not exposed via the SDK, you can assign a key press to this in MSFS and then assign a button/switch to that key press in FSUIPC7. This is how I control my views, for example. So, my advice would be to create empty profiles for your controllers initially and try to assign using FSUIPC7, but where you need to either assign to a key press in MSFS and then to that key press in FSUIPC, or assign directly in MSFS. John

Which products did you update? It may help others that are also affected by this issue. John

Hi Gary, no, sorry - the discount is only for holders of FSUIPC5/6. John

Hi Emilio, Sorry, I have no idea. Is the 'OnFSUIPCChange' function from the the SC-Pascal SDK? If that is the function that isn't working as expected, you need to contact the author of that for assistance. John

To recognise buttons outside of the 0-31 range, you have to use lua. There is a lua script provided called HidDemo.lua (in the lua examples zip in your documentation folder). Add that to your FSUIPC7 installation folder, and edit to provide your devices vendor and product ids. Also, auto-start the lua by adding it to the [Auto] section of your FSUIPC7.ini file. There are many posts on how to do this - try checking the forums if you require further help before posting again. John

What version of FSUIPC7 are you using? Current version is v7.0.3. The Alt modifier was reenabled in v7.0.2 so should be available. Key combinations are only possible in FSUIPC key assignments with the modifier keys Alt, Shift & Ctrl. Ok, thanks. Just register with your new key details during the installation process. This will re-write your FSUIPC7.key file. John

If its not there, add it, if its there with 'Yes', change to 'No'. It goes in the [General] section. John

There is already the option ProvideAIdata=No Maybe you can try with that to see if it makes a difference? John

Can you check your FSUIPC7.log file. You should see these lines near the beginning: If you don't see that, you are either using the wrong file or have placed it in the wrong place. Under the Assignments menu. this will not be available if your FSUIPC7 is unregistered. Yes, there is a know issue with both the Honeycomb Alpha yoke and the Bravo throttle, with certain switches always sending state.... There are quite a few honeycomb users using FSUIPC7 to get around this, so should be possible. Just see you have responded again and now have it working....good lucjk with setting it up! Still waiting for my Honeycomb Alpha.... John

These errors have been known to be caused by the number of SimConnect clients being exceeded. Its a known problem in all ESP based sims since FSX. To verify if this is the cause, you could activate server-side SimConnect logging (via a SimConnect.ini file) to see if the number of clients/connections is being exceeded, and if so increase the maximum number of clients available via your SimConnect.xml file. John

As Pete says, just use the same FSUIPC7.key file. However, if its failing validation it could be due to your VC++ redistributables. Can you try to see if you can actually run FSUIPC7 on your 2nd PC (registered or not)?

Maybe that could work, although you would have to terminate the event.key function on an enter or return key press. Are there any standard lua library functions that can get keyboard input? I tried with io.read but this doesn't seem to get any input. I'll take a look using event.key for this in the next few days. John

No problem - sorry for the late reply as I took a few days off over christmas... Would be useful to other users who have the same issue if you could also post your solution to your problem... Thank, John

The saitek mode switch on the X52 uses three buttons which you can check with offset conditions. See this post: John

Hi Robert, there is no difference running the downloaded stand-alone exe than running the one installed by the installer. They are one and the same exe. The installer will just add a couple of registry entries which are used by the installer (and not the FSUIPC7.exe) to check what is installed before re-installing. So I'm pretty baffled by this... This issue seems to be due to a server-side issue with SimConnect. For now, its best to report all CTDs to Asobo, including the relevant crash report. John

@underdogdjr Glad you found your issue, and thanks for reporting back. John

There are several such reports now. It is really not worth creating a separate topic for this when it has been reported several times already. The problem is with MSFS and needs to be reported to them, with any details from the windows event viewer included so that they can investigate. John

@lonesbeats@gmail.com First, you posted in a topic that has been closed for over 5 years and is not really related. You would be better off creating a new topic with an appropriate title. What you would like to do is quite straightforward using the event.button function and a global variable to hold the current state (or number of button presses). You can use and adapt the following lua script. Makle sure to add it top the [Auto] section of your FSUIPC ini file so that it auto-starts. John

There is currently a time-limit key file valid until the end of the year available for download in this topic: John

There doesn't seem to be any control, either internal or external, to control this at the moment. You may want to raise a new feature request with Asobo for this. John

Toggle your switch and assign the PARKING BRAKES control to both your button press ad release. Then located those assignment lines in your FSUIPC7.ini. I have just assigned to a spare switch, and these are my lines (where '109' is my device id, and button id is 15): To add an offset condition on 0x0BC8 (BRAKE PARKING POSITION), I would change those entries to Then the control would only be sent on the switch on position if the parking brakes were off (0x0BC8 contains 0), and sent the toggle control on release only if the parking brakes are on (W0BC8 is equivalent to W0BC8!0). John

Why are you posting the same question multiple times? See John

FSUIPC7 does not have a native web-service interface. However, there is a websocket server provided (and included in the FSUIPC7 installer) by Paul Henty. See http://fsuipcwebsockets.paulhenty.com/ John