John Dowson

Hi, not sure what your issue is, but please check this post: Note however that if you are using a PMDG aircraft, then the offset will be different - check the FSUIPC PMDG documentation for this. John P.S. Note that you posted in the FAQ section, I have moved your post for you. Please post all support requests here in the main forum.

Ok, ADE is the 'Airport Design Editor' - I've not used this, but make sure that you are running it as Administrator if you are running your FS as Administrator otherwise it will not be able to communicate with FSUIPC. John

I do not know what ADE is, or Error#2. Does this mean that you fo not see the FSUIPC... entry in the Add-ons menu (as previously asked)? Please confirm or otherwise. FSUIPC does not install anything in your Documents folder. The FSUIPC documentation will be installed (from your install log) in: C:\steam\steamapps\common\FSX\Modules\FSUIPC Documents FSUIPC doesn;t install anything in your Add-on scenery - why do you think this? Your FSUIPC install folder is C:\steam\steamapps\common\FSX\Modules which is where your FSUIPC4.DLL file will be installed. If you do not have the FSUIPC menu entry, can you please check this folder to see if there is an FSUIPC4.log and and FSUIPC4.ini file, and if there please post them (make sure that you have 'Show hidden files' activated and 'Hide extensions for know file types' deactivated in your explorer options to see these files correctly). John

As we did not communicate the increase in lvar length from 32 to 64 characters, maybe the .net client dll needs updating for this? Just a thought. Maybe Paul could check this? Cheers, John

Ok, thats great. Thanks for the update. John

Just re-run the installer to register, no need to uninstall. The free/registered versions are the same, its just that some functionality is disabled in the unregistered/free version. Cheers, John

Wade through? You just run the installer.... Whats the actual problem? Your log shows that it is installed ok and that you haven't registered. Do you not see the FSUIPC... entry in the Add-ons menu? John

If you are willing to write some new FAQ entries based on your experience then that would be great! If you could email them to me when done, I will create some new FAQ entries from them. You can PM them to me, or email me directly. The forums are open to all and we actively encourage people to follow and post replies/solutions, so please respond to any requests that you are able to help out with. Currently no language files for FSUIPC. I am planning on updating the UI for future versions, and I would certainly like to include internationalisation in the UI when I do this. When I get around to this, I'll PM you for some help on the spanish files. I do speak reasonable Spanish, as I live in Spain, but not at a good technical level. I am also planning to refresh the User Manuals very shortly, to make them more general to support the various different planned FSUIPC versions (5 and later), and also add section/header numbers and maybe an index. We can maybe thing about translating these once done, although that would be quite a large job! Probably only worth doing initially for the User Guide, and maybe later the Advanced User Guide. Not sure about a specific Spanish section in the forum - let me think about it a bit more. We do occasionally get support requests in Spanish, as well as other languages, which we do our best to respond to. Maybe something worth looking into once we have the internationalisation in the UI. Thanks a lot for your generous offer! Regards, John

Hi, I think the first step would be to log what the strings are to see if this sheds any light on the problem. Could you try adding the following to the [General] section of your .ini file: Debug=Please TestOptions=x8000 (This is the TextMenu logging flag). You could also log offsets (from the FSUIPC UI) B010 (as U32) and B014 (as AsciiZ), sending the results to the log file. The logging of offset B014 will probably not be that useful, as it will stop after the first zero terminated string, but would be useful to see anyway. If you could post your log file exhibiting your problem with the above logging activated, I'll take a further look. Cheers, John P.S. I've not looked into the python module yet so this may take some time!

Further to what Pete has said, if you are reinstalling you do not need to re-register, you can skip and your previous registration (FSUIPC4.key file) will be used. If this is no longer available, you will have to re-register to generate this file. John

Looks like the documentation needs a minor update as it does refer to 'page 2 of 6', etc, where it should be 'screen 2 of 11' (or maybe just 'screen 2'). The documentation for FSUIPC4 will not be updated, but I'll check and update this for FSUIPC5. Thanks for pointing this out. John

I have added a new control to toggle the auto-save facility on/off. Using this, you should be able to write a lua script to turn auto-save off/on when required, for example on gear down/up, or on altitude. The new dll for this has been posted in this topic: John

I have added a new control to toggle the auto-save facility on/off. Using this, you should be able to write a lua script to turn auto-save off/on when required, for example on gear down/up, or on altitude. The new dll for this has been posted in this topic: John

You do not provide much information - how are you activating your flaps? Which aircraft? Can you try activating logging for Events (non axis controls) and Button and key operations and post the log file generated when you have your problem, together with your .ini file. If you are not using a default aircraft, you my also want to try with one as well. Thanks, John

Hi Bob, please try the following: FSUIPC5.zip Unzip this and you'll find an FSUIPC5.dll that you should use to replace your current one (in your Modules folder). You will see an additional control has been added called 'Auto-save' toggle. This only has an effect when the auto-save feature is activated, and will allow you to toggle this facility on and off. It is initially on (i.e. auto-save functioning). Let me know if you have any issues. Cheers, John

You install WideClient on the client PC, which can have no affect whatsoever on your main PC where FSUIPC is installed. You should then re-run the FSUIPC installer on your main PC to register your WideFS license. This should update your licence file (.key) and may install a new dll, but should not affect your settings (in the .ini file) in any way. And as Pete says, you should post your FSUIPC5.log and .ini files (and maybe your .Joyscan.csv file) if/when you are having problems. Cheers, John

Btw, you didn't mention which sim or FSUIPC version you are using. I'll add a new control to toggle auto-save on/off but this will be for FSUIPC5 only - FSUIPC4 is closed for future development. I'll post a new dll in this thread when ready, within a few days hopefully. Cheers, John

You cannot create an lvar - they are provided by the aircraft guages. You can use the provided control (or lua script) to list available lvars for the loaded aircraft (see the user guide). Why do you want to use an lvar anyway? If using in a lua script, use a global variable. You can also pass variables between scripts (see ). John

SPAD.next works well with FSUIPC. I haven't used SPAD, but that should also be ok. e.g. see here: https://www.spadnext.com/forum/viewtopic.php?t=209 Cheers, John

Above re-posted as a new topic here:

To add to what Pete has said, for the above please see the section in the User Guide User profiles for all control settings. John

It accepts a memory address, with the size as the second parameter (also offset size). You should define it to be the type you are actually reading. You should also maybe check-out Paul Henty's client dll for .net / c#, as this provides a higher level abstraction that many folks find easier to use (although its for c#). See https://forum.simflight.com/forum/167-fsuipc-client-dll-for-net/ Regards, John

Hi Dani, as the value is a 4 byte integer, try defining int flaps; and if (!FSUIPC_Read(0x0BDC, 4, &flaps, &dwResult)... ... printf("Flaps = %d\n", flaps); John P.S. For flaps position, you probably want offsets 0BE0 and 0BE4.

Hi Bob, currently its not possible to activate/deactivate auto-save on a control/event. This has also been requested before, either as a straightforward control (on/off) or to allow automatic enable/disable depending on the aircraft altitude, to basically allow automatic disable on take-off/landing and enable thereafter. I will look into this for a future release. Regards, John

If you are going to try unplugging and uninstalling both your Razer and HOTAS Warthog devices, apply the following .reg file after you have uninstalled to make sure all registry entries are removed: Windows Registry Editor Version 5.00 [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_0404] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_044F&PID_0404] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_0402] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_044F&PID_0402] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1532&PID_022B] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_1532&PID_022B] (as before, save into a file with .reg extension and run as administrator.). When you connect your drivers and reboot, let windows install default drivers but do not install any specific drivers or software for these devices for the time being. Remove your FSUIPC5.ini file (no need for JoyLetters and the moment, we can activate that once your problem is resolved), fire up P3D and then send us the .ini, .log and .Joyscan.csv files again please. Thanks, John