John Dowson

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

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