John Dowson

One of those log files shows that there was a sSimConnect problem. There is a know issue with SimConnect having issues during long flights due to the number of clients being exceeded. You could try increasing the maximum number of SimConnect clients allowed - please see the following (from a related post):

Btw you have one profile called MSFS XBOX1 CONTROLLER. It is not a good idea to name your profiles after a controller, after all they apply to ALL your controllers. It is best to name them after a specific aircraft or an aircraft type (e.g. single prop, jet, etc). Also, for the xbox controller, I find it better to use this as set-up by default in MSFS.

I don't think so... If you are using LINDA you really need LINDA support. You could try without LINDA - just temporarily disable (i.e. rename your ipcReady.lua) and activate button logging in FSUIPC7 and see if it recognises your buttons reliably without LINDA. John Later: also make sure you are using the latest version of FSUIPC7 (i.e. download and re-install, just in case). May also be worth removing the contents of the [General] section of your FSUIPC7.ini and let that get re-built.

Hi Nigel, could you remove the contents of the [General] section from your FSUIPC7.ini. This will be rebuilt with the updated defaults the next time you run FSUIPC7. Your ini shows that you only have assignments to your xbox controller. Are these not working? Your log shows no other device is recognised, i.e. your X-55 Rhino stick was not connected. If you have installed the saitek software and/or drivers, you should remove these and try again. You should also check the power management settings on your usb hubs, to make sure windows isn't putting them to sleep. If you are still having problems getting your stick recognised, please show me your FSUIPC7.Joyscan.csv file.

@lauri1526 I have just sent you a message. Please follow the advices there. I repeat it here: SimMarket handle all sales. Ask them, but I doubt it - see their policy. You certainly haven't! I don't even know what your problem is at the moment. Please follow my advise and report back. And please use the forums for support. I do not provide support via private messages, and only use messages to verify keys. You key is obviously ok so you should first download the latest version and re-install and register. Once that is done, try running the FSUIPC7.exe, as advised, and any issues use the forums. John

As I keep saying, please contact SimMarket. They handle all sales.

If they are recognized by windows, they should be recognized by FSUIPC. Where are you looking? Usually rotaries are actually buttons, and have two buttons that register in each direction. So they should appear in the buttons & switches assignments tab. However, if they have been assigned button numbers > 32 they will not be seen in the assignments panels, and you will have to resort to lua if you want to use them with FSUIPC. There is an example lua script provided called HidDemo.lua that you can try if this is the case

Really? This problem relates to an old issue when the SimConnect.dll file was required to be installed. This has not been required for at least 3 months, so this is certaibly not your issue. Its a batch file, of course its not either 32 or 64 bit, but works on both systems (although FSUIPC7 is obviously 64 bit). Sorry, but I have no idea what your problem is. I suggest you at least read the provided documentation (Installation and Registration guide + the README.txt) and if you are still having issues then check the forums and post again giving details of your issue. Did you use exactly the same details as provided by SimMarket? Did you click the Register button? If so, what did the pop-up say when you did this? If not, do that. I am closing this topic. John

I just added it to the general [Auto] section to test. If you only want it in a profile, add it to the profile specific auto section (e.g. [Auto.xxxx] where xxxx is the profile name) instead. If the profile-specific Auto section doesn't exist (it won't unless already added), then add it.

Hi Dave, so the AI traffic tables are populated, but there is a problem with the From/To columns...I will look into it. But how come you are not able to read any data? It must be there if it is displayed in TrafficLook! John

Btw, I've noticed that when you go from Taxi -> LDG, MSFS sends a landing lights toggle followed by a taxi lights toggle. To duplicate this behavior, use the following lua instead (I've just added the extra taxi lights toggle control on your 12 button press (no delay needed): tbmLights.lua

Please try the attached simple lua script. Save it in your FSUIPC7 installation folder, then open your FSUIPC7.ini and add the following to the [Auto] section: 1=Lua tbmLights (change the '1' to the next free number if you have other lua's auto started). This only controls the TBM 3-way lights toggle. You can add further controls and/or keypresses for your other actions as you wish, or set those up via the UI assignments panel. Let me know how it goes. tbmLights.lua This just adds a 600ms delay between sending the landing lights toggle and sending the taxi lights toggle (on your button 12 release), which seems to do the trick. I'll look into allowing you to specify a delay for button and key assignments made via the UI.

I think you should try re-installing the VC++ redistributables. Uninstall the 2015, 2017 and 2019 redistributables and then re-install. first the 2015 and then the 2017 and finally the 2019. If that doesn't work, then I think you need to verify your windows installation.

Hi Javier, that's very strange - FSUIPC7.exe is an application/executable not a dll! When do you get this error? Is it when you double-click (i.e. launch) FSUIPC7.exe? If not, can you try that. Probably the first thing to try would be to download again and re-install.

You could try looking at macros instead, but it looks like the second command is being ignored - maybe it doesn't accept the input/control while the animation (i.e. switch moving down) is in progress, in which case a delay would be needed. If that's the case, then I think you would need to do this in lua at the moment. I am planning to implement a delay feature for controls and key presses (already exists for axes) so I may look into this pretty soon (and can use this example to test). I'll look into this in more detail later today (time permitting, if not on Sunday) and put together a lua example for you.

Just to be clear, FSUIPC7 is for MSFS only. John

I'm pretty sure these are still available (or were until recently), but are now produced by Logitech. Note that FSUIPC doesn't recognise this device as a standard devices - you need the SPAD or SPAD.next drivers, or to use lua.

Sorry, but I have no idea. Maybe someone else can help, but you are probably better off asking over on https://www.cockpitbuilders.com/. FSUIPC should recognise it if it is registered in windows as a HID device. John

It should be, and this has been on my list for a while, especially since the arrival of MSFS. I'll probably implement this in FSUIPC7 shortly, then later roll the changes into FSUIPC6. I may also update FSUIPC5, depending upon user request, but any such change certainly won't make it to FSUIPC4 and so Roman's solution can be used there. John

Same as where you previously got it...I've just replaced the downloadable zip....

Ok, finally.... Did you read the manuals yet? Of course not. Why would you expect it to? What 'application' did you click on to start? Was it the FSUIPC7.exe? I don't think so, as if you started this you would see the FSUIPC7 splash screen. Do not use the MSFSwithFSUIPC7.bat file as this, as its name implies, will also start MSFS. In fact, if you download the latest installer (updated a few minutes ago) and re-install, this file will no longer be installed when you uncheck the checkbox to install the desktop link. Sorry, but it does and I do not understand why you are having so many issues. As I have said many times, try reading (and understanding!) the provided documentation.

As well as what Pere says, maybe also worth checking you have the following set in the [General] section of your ini (and if not, add): SetForegroundOnKeySend=Yes and. if you are sending the keys on button presses, you could also try setting this: KeyboardFocus=Yes But again, these changes will only set the focus to the main FS window, so not sure if the focus would go to the hrml menu window....

Do you have the following option set in the [General] section of your FSUIPC6.ini: LuaTrapKeyEvent=No ? If not, could you first try with that please. I don't think this is possible as FSUIPC only has access to the main window, but if the main window has focus I would have thought any input would be directed to the current active child window (i.e. the menu window).

I could add this if you like, but it is documented as read-only, so cannot be used to update. I guess it could be writeable but documented incorrectly - I can add this locally to test. But if it isn't, would this still be useful? Unfortunately this happens with quite a few events, i.e. you can see them when activating from the UI, but sending via SimConnect has no affect, and this varies from aircraft to aircraft. Probably worth raising a zendesk issue to Asobo ib the aircraft in question. John

From Page 4 of the Installation and Registration guide: