Thomas Richter

Hi, as always a FSUIPC4.log file would help. Just copy and paste the FULL content to your message. Thomas

Hi, I picked up a Switch panel (here from Shannon) to check with SPAD v0.5.1. The bug is introduced with 4.966 or just before, but anyway. As a workaround you can paste this Battfiddle.lua into your Modules folder and if you already run any Lua file then add into your ipcReady.lua file the following line to start the fiddle file ipc.runlua('BatFiddle') If you don't run any Lua file then just paste also the ipcReady.lua file into your Modules folder. The fiddle just checks the switch position (Offset 0x3102) and compares with FS Master Battery, if False then it toggles the FS Battery Switch. Thomas ipcReady.lua BatFiddle.lua

Hi, that will not be FSUIPC then but check the dll.xml and exe.xml. One of them will have the entries . Thomas

Why you want then remove something from the INI file that doesn't exists already anymore? If the section is not there then FSUIPC doesn't care and does nothing. Thomas

Hi, sorry I did misread. Just delete the section manually in the INI file, that's all to do. In case as I said before it is not created by default, so it will not be recreated. Thomas

Hi, can you copy and paste the FULL content of your FSUIPC4.ini and FSUIPC4.log files, after (try) to configure in FSUIPC4 to your message please. Thomas

Hi, Pete wouldn't have done that really very hard work if it wouldn't be worth It ! Please have a look as well into the containing pdf file as described before use. Thomas

Hi, which FSUIPC4 is installed, the log file always helps (copy and paste its FULL content, after FS was closed, to your message). Thomas

Hi, what version of SPAD are you using anyway? Thomas

Hi, what is it you are looking for? Thomas

Hi, the section is not there by default, so if it isn't there then add it manually in the FSUIPC.ini file (FS9) / FSUIPC4.ini file (FSX/ FSX-SE/ P3D). Thomas

Hi, choose 'Control sent when button pressed' and select the first selection <custom Control>. Enter the control 70320 for left cutoff lever and press Ok. Use Parameter 0 (zero) for IDLE and Parameter 1 (one) for CUTOFF. for ENG-2 <custom Control> 70321 and again Parameter 1 for CUTOFF and Parameter 0 for IDLE. Thomas

Hi, make sure you use latest FSUIPC4966n.zip Thomas

Hi, this is described in FSUIPC4 User Guide.pdf on page 19 and 20, changing the 'Reload FSUIPC data' from 'Never' to i.e. 'Menu' will add a menu in FS Add-ons tab 'Load Flight+Data'. Thomas

Hi, instead of assigning the axis to eng 4 you can use the free range of offsets 66C0 64 Free for general use, for example in button or keys programming. Thomas

Hi, no if there is nothing defined to rudder or nose-wheel then there is nothing you can read other then the value in axis assignment tab in FSUIPC. But as long nothing is assigned to that axis then nothing will be stored or used/ send to FS. What is the problem? Thomas

Hi, if the reverser axes are separate axes then you can just configure them in FSUIPC. In case you did the setup for the throttle axes already you only need to make sure the rev position for Throttle is higher than the usual value of -16383, i.e. -20000 and the idle value is the min throttle position -1 to get correct idle. The reverser axes you can select on page 11 in the same way you did for throttle, I mean the mapping boxes. Then set max reverse and idle but idle with enough zero-zone. Thomas

Hi, please download latest version, released today. Just copy and paste (overwrite the existing file) the unzipped files into .\Modules\ folder, please follow Pete's instruction below TEST update 4.966m (DLL module only): FSUIPC 4.966m.zip There are a few requested changes and fixes in this release, so you may want to try it, but it is mainly aimed at those who have been suffering joystick recognition and assignment problems, especially with Saitek X55 and X56 units. It features a totally re-written joystick scanning system which needs real exposure, but is ulitimately more logical and more understandable than the previous mess which grew like topsy to meets the needs as they arrived. Actual changes are listed in the included PDF document, as are requirements for the data to be supplied with any feedback about the joystick system. Thomas

Hi, in Logging tab and using the corresponding Throttle Offsets, display in 'Send to console window' and if no other programs do much writing check the 'IPC Write' Thomas

Hi, when you use Com 1/2 Tx Switch (by i.e. key control) and monitor Offset 0x3122, you will find that FSX/P3D always first sets the active bit to 0 (zero) before setting the wanted active Com bit. So when Com1 is active (Bit7) and you toggle to Com2 then FS changes Bit7 to 0 and after that it changes Bit6 to 1. For change from Com2 to Com1 FS does exactly the same with the corresponding bits. It is not a FSUIPC error or miss-function but a FSX/P3D behaviour. So for your program there are two ways to do: 1/ changing the active Bitx first to zero before setting the new Bit 2/ writing the value to Offset 0x3122 instead of dealing with Bits, having the selector panel selection code in one place, radioSelector = 0 if (adf1) radioSelector++ if (dme) radioSelector =+ 2 if (markereSnd) radioSelector =+ 4 if (nav1) radioSelector =+ 8 if (nav2) radioSelector =+ 16 if (comBoth) radioSelector =+ 32 if (com2) radioSelector =+ 64 if (com1) radioSelector =+ 128 //write radioSelector value to Offset 0x3122 Thomas

Hi, with FSUIPC4 you can toggle Aircraft labels (ON/OFF) but not change its content settings individual. Thomas

Hi, the answer is in the FSUIPC4 for Advanced Users.pdf document page 11 (\Modules\FSUIPC Documents\), Less used technical options AutoTuneADF: This controls an option to ‘auto-tune’ the ADF radio. If this is enabled, when FSUIPC detects no NDB signal being received it alternates the fractional part of the ADF frequency between .0 and .5 every seven seconds or so. This allows external cockpits built with only whole-number ADF radio facilities to be used in areas like the U.K. which have many NDB frequencies ending in .5. Thomas

Hi, please paste and overwrite the existing FSUIPC4.dll with this test version of FSUIPC: FSUIPC 4.966j and try again. Can you see the axis and buttons working correct in Windows GameController calibration/ test panel? Thomas

Hi, please install the latest FSUIPC4966c version. And after that also paste and overwrite with this test version of FSUIPC: FSUIPC 4.966j. Thomas

Hi, seems for what ever reason Windows might have re-installed the devices, nothing FSUIPC is responsible for or can force Windows to do. Please copy and paste the full content of your FSUIPC4.log file to your message. Thomas