John Dowson

Hi Ron, could you provide your order number and date of purchase, together with the name (Ron Kolesar?) and email address (kolesar16417@roadrunner.com ?) you used for the purchase. Thanks, John

Hi Bjarne, although you have not responded to my previous post, I don't think it matters to much as the result is the same: you need to uninstall, remove registry entries and re-install. To do this 1. Find the device in the Control Panel – System – Device Manager, right click and uninstall, including driver if option presented. 2. Unplug the device. 3. Create and Execute a .reg file containing the text highlighted below, then run this “as administrator”: Windows Registry Editor Version 5.00 [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1150] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_1DD2&PID_1150] You may want to back-up your registry before running this file. To do this, start regedit and 'Export' your registry to a (backup) file. 4. Power off. 5. Re-connect the device 6. Re-boot and test again. We're not 100% sure this will fix your issue though, but maybe worth a try. Regards, John

Hi Emerson, there are no assignments in your ini, so I guess all your assignments are done through Linda, no? Your problem looks to be caused by duplicated registry entries. Could you add the following to the [General] section of your FSUIPC5.INI file, generate another log and post that: Debug=Please LogExtras=x200000 Thanks, John

If its only sometimes, maybe its a dirty button connection? Try switching the button release assignments. You can also activate logging of button events and axis controls (and maybe also non-axis controls), and check what the log says when you have this issue - this should give some insight into what could be happening. You can post such a log, together with your ini file, if you need further assistance. Cheers, John

You need to go to 'Your Orders' page, available here: https://secure.simmarket.com/account_history.php From there, you select your order for FSUIPC. Cheers, John

Then again I'm not sure - maybe you are correct and I misunderstood...maybe I need more coffee! John later: yes, of course, as the script is expecting the 0..4096 range. I originally read that the pot was supplying this range - sorry for the confusion!

Roman - the inputs are from the pots in range 0-4096 which need converting to the sim accepted range of -16384 to +16383. More coffee?

Hi Simone, Ramon, I think Ramon got his calculation the wrong way around, and is converting from +-16k to 0-4096., so it should be [Axes]PollInterval=10RangeRepeatRate=100=2X,256,F,x030066D8,0,0,0,*8,-16000 -{ FSUIPC: offset dword set, offset 66D8 }- ; ASI SPEED1=2Y,256,F,x020066D0,0,0,0,*8,-16000 -{ FSUIPC: offset word set, offset 66D0 }- ;SALMON BUG2=2Z,256,F,x030066D4,0,0,0,*8,-16000 -{ FSUIPC: offset dword set, offset 66D4 }- ; BARBER POLE John

Also, If you really want to run WideClient on the same machine as the FS, you have to change the "ClassInstance". - please read the section in the WideFS Technical document about this parameter. John

Why would you want to do that, with the overhead that a VM would use? If you want to connect your Simkits instrument panel to the FS machine, why do you need WideClient?

There are no changed in the FSUIPC 4.974c version accept for the facilities that have been disabled (see post mentioned previously). We have had no detailed reports of problems with FSUIPC4 relating to recent windows updates, and so cannot investigate. Note also that FSUIPC4 is now closed for further development. However, if a windows update did seriously affect FSUIPC4 then we would certainly investigate. Cheers, John

If you are going to use the FSX-SE beta, please see this post as the FSUIPC version for this release has some restrictions: John

If you are using FSUIPC, you can take a look at the offset document which will give you the data available through using FSUIPC, but how you use this to implement a force feedback response is up to you. Someone else may have looked at this before, but you are probably better off asking over on cockpitbuilders.com, or possibly avsim. Regards, John

By WideFS, do you mean WideClient? If so, this is meant to run on a separate machine to your FS. WideServer, the server part of WideFS, is built into FSUIPC4 and the text shows that WideServer is running and waiting for clients. If you want to run Wideclient on the same machine as the FS, you have to change the "ClassInstance". - please read the section in the WideFS Technical document about this parameter. Regards, John

What do you mean by this? FSUIPC is always optional! If you mean an update/fix, then I do not think so. There is already a specific version available for the latest FSX-SE beta. No idea what your problem was or if it was FSUIPC related, but as you have supplied no logs or detailed information of the problem, and you have restored, we cannot really help. John

Are you using profiles? If so, you can just change the calibration (or assignment) for that axis for that aircraft. If not, and you are using the same assignments/calibration for all aircraft, then you can create a profile for your King Air 350. When you do this, the general axis assignment will be copied across to the profile for that aircraft, which you can then update. Please see the User Manual section User profiles for all control settings (P18). If you require further assistance, please post your FSUIPC ini file. Cheers, John

Are you sure those are the correct logs for 'without'? Both the log and the JoyScan.csv indicate that the device is acquired for use and working, although with some issues (as in your 'with' log). John

Hi Bjarne, your logs show that you have some dodgy registry entries that will need removing (which have a null GUID for your problematic device). To get further details, could you add the following to the [General] section of your FSUIPC5.ini file Debug=Please LogExtras=x200000 repeat your tests and re-attached the generated log files. This will add further information on your registry entries which will indicate to us what needs to be removed. You could alternatively try disconnecting the device, removing any drivers or software and then clean the registry yourself for all your Button Box Interface entries (take a backup of your registry first!) before rebooting and reconnecting/reinstalling. Cheers, John P.S. Please also attach your FSUIPC5.ini file when you next upload your log files, thanks.

Hi, first, please update to the latest version of FSUIPC, v5.153. For your mouse macro question, you could try a multi-action mouse macro, with both a button click (code 3) or a left click and drag (code 9) followed by a left button release (code 13). Multi-action macros are documented in the Advanced User Manual in section Multiple actions in one macro control (P36). For your other questions: 1. You can use the 'Reload all buttons' or the 'Reload all keys' buttons in the Buttons / Keys tabs to reload the macros. 2. There are two methods to achieve this. The easiest is to assign a button or key press to the control 'List local panel variables' - see the Advanced User manual un section Guage local variable access (L:vars), by macro (P38). Alternatively, a lua script called log lvars.lua is also provided - drop it into your Modules folder and assign a button/keypress to activate. Cheers, John

Strange as it should have been working in 5.151, although there was a minor update to this functionality in 5.152 as well. Anyway, I was going to suggest that you update to the latest version as we only support the latest version of each product. Cheers, John

Please see the section FORMAT OF BUTTON DEFINITIONS in the Advanced User Manual, located in the FSUIPC Documents folder, under your Modules folder. John

Please see this FAQ entry: John

You can in FSUIPC5 but not in earlier versions. The event.textmenu function was added to FSUIPC5 in version 5.151, released February 2019. Cheers, John

It could be a corrupt weather file - could you first try adding the following to the [General] section of your FSUIPC4.ini file and try again: NoWeatherAtAll=Yes If that solves it, it will be a corrupt .WX file in your Flight simulator Documents folder, or more usually the wxstationlist.bin file in the same folder as your FS-SE settings (the AppData folder). deleting both would help in that case. The reason is that FSUIPC reads weather through Simconnect and a corrupt file causes crashes and other errors. If that doesn't work, could you also post your DLL.XML file (located under C:\Users\Colin\AppData\Roaming\Microsoft\FSX\) so we can see what else is running. Thanks, John

Is the rotary acting as an axis? FSUIPC doesn't know the position of your rotary when it starts, and will only receive the axis position and sent the relevant event/control with the position once it has moved. You shouldn't have to "turn the rotary to the full left/full right a few times in order for it to work" though. Maybe you can try activating logging for 'Axis Controls' and generate a short log file of your start-up procedure to see what is being sent. Post/attach this, together with your ini file. Cheers, John