Thomas Richter

Hi, as it is stated very clear, FSUIPC5 needs its own registration key via Simmarket but that is not available yet. Also FSUIPC5 is not in a Beta state, it is a release version 5.10 and as before an ongoing development. Thomas

Hi, that's correct. You register when you use the Installer, the last thing to do is to register, or not. Make sure when you got your registration details to use then exactly as you got them, best practise is to copy and paste them instead of typing, typing gives often misspelling errors. Thomas

Hi, it is in the sub-forum above, FSUIPC Client DLL for .NET Thomas

Hi, but that means it is not possible to use the LT and RT for left and right brake. It would be only possible to use one for both brakes, the other one would be useless. The reason is that only if one is pressed the value changes from 0 to 16383 or 0 to -16384 but in case there are two poti used that the value will be 0 (zero) as well when both, LT & RT, are pressed at the same time (what is your problem). So if none is pressed or both are pressed results in a value of 0 (zero), brakes released. I don't see a possible solution for that because if you i.e. press both slowly in synchron down then already the Z value will be around 0 (zero), as said the both poti will electronically equalize. Thomas

Hi, what is the working/ usable range value of your 'Z' axis, -16384 to 16383 or 0 to 16383 (ish), and what is the value of the 'Z' axis for brakes OFF/ released? Thomas

Hi, no. Please i.e. rename the existing dll.xml to _dll.xml so it will be ignored. Then run the Installer of FSUIPC4.966c, that will create a new dll.xml file with only FSUIPC4 to load. Now run FSX and close down to make sure it runs OK. Then paste and overwrite, as before, the installed version with the latest interim FSUIPC4.966n version and run FSX to see if it runs still OK, without any other loaded add-ons from the original dll.xml. That is just to test if the latest interim version already causes FSX to crash on its own or in combination with one of the other add-ons. If FSUIPC4 produced a log file with the latest 4.966n version on this test, please copy and paste it into your message. Thomas

Hi, run FS and close it after a short session. Then please copy and paste the FULL Content of your FSUIPC.ini file and FSUIPC.log file to your message. Thomas

Hi, That can only answer their Manual or SDK, if available. Thomas

Hi, switching screen mode is the Alt+Enter key combination. Calibration is only available in registered version, is your correct registered? FS should always be installed in a separate folder other than the Windows C:\Progarms(x86)\ or C:\Progarms\ because of limited write access (Windows security ...). Thomas

Hi, that is most likely a graphic card driver problem. Happend often with Radeon Graphics cards but always only if you are in Full Screen mode, it will work when you switch to windowed mode before access the FSUIPC panel. It is not to FSUIPC error, check as well you use maybe the latest graphics driver for your card. Thomas

Hi, can you please send your FSUIPC4.ini and FSUIPC4.log files. Thomas

Hi, no one reported a crash up to now with latest version (4.966n). Try renaming your original FSUIPC4.ini file, e.g. _FSUIPC4.ini, so it will create a new one on next FS start (with FSUIPC4.966n version). Maybe something corrupt in the INI file. If FS crashes there will be a Win crash report (Event Viewer) that would help. Thomas

Hi, did you try to connect the missing one on a different USB port, not swapping with the recognised ones? Thomas

Hi, always use latest FSUIPC4 version because any older than the current version is not supported, internal code has been changed of course. Latest version is FSUIPC 4.966n.zip It will not change the behaviour of the flickering because that is related to the way FSX/P3D handles the display and FSUIPC logging does interfere with it. I would use instead of FSUIPC logging option on screen the Lua display facilities, you will find useful stuff for it in Example LUA plugins.zip, i.e display vals.lua displays Offset values. Just change that a bit to your needs. Thomas

Hi, you said you use latest FSUIPC4 but as the log shows you use 4.966c, the latest Installer. The latest FSUIPC4 version is 4.966n, where Pete did rewrite over weeks the whole Controller-Input part special because of the problem with Saitek X-55 and some other Saitek products. See below the Quote from download section Please install this version FSUIPC 4.966n.zip Thomas

Of course it has Simconnect, that's what they said as well is to use but their Simconnect has nothing to do with the ones are used in FSX/P3D. Also it has only couple public function calls implemented yet ... As well as the folder says it would be a 32 bit Simconnect !? Thomas

Hi, that is not possible because it is not just a conversion to 64 bit but also the related Simconnect of FSW has nothing to do with FSX or P3D Simconnect, it will be completely different structured and functional. Also in case FSW is very far from 'ready' I think it is much too early to even think about a possibility. (I have FSW myself installed, :-( ) Thomas

Hi, FSUIPC reads the keyboard input but doesn't change anything to its behaviour in Win or to other programs. When Buttons are assigned to send Key presses then it will send those as Keyboard inputs to FS, also when FS doesn't has focus but only if that option is set to Yes. Is there maybe some other program that runs, started by FSUIPC, like vPilot or something? Thomas

Hi, please add the following in FSUIPC4.ini [General} section, just as the last lines in that section. Debug=Please LogExtras=x200000 Also change here to Yes [JoyNames] AutoAssignLetters=Yes Then run again P3D and wait until fully closed. Please copy and paste the FULL content of your FSUIPC4.ini file and FSUIPC4.log file to your message, please attach the FSUIPC4.JoyScan.csv (found also in Modules folder). I have here two Logitech Extreme 3D PRO joysticks running, without any trouble. Thomas

Hi, you can do that by using Lua. It is different to what you normally do in FS because PMDG control things different. Attached are the ipcReady.lua file to load/start Lua files and a KeyToControl.lua file that controls the Cutoff lever L/R in PMDG 737NGX. If you use already Lua files you only need to add the line to start the additional lua file, ipc.runlua('KeyToControl'). Otherwise paste both files into Modules folder. The KeyToControl.lua is set to key '8' and '9' on main keyboard, they can be simple changed with the value (KeyCodes) of its variables: -- variables cutoff_L_Key = 56 -- '8' on mein keyboard cutoff_R_Key = 57 -- '9' on mein keyboard KeyCodes are all listed in ..\Modules\FSUIPC Documents\FSUIPC Lua Library.pdf file, page 19. Thomas KeyToControl.lua ipcReady.lua

Hi, first please copy and paste the FULL content of the FSUIPC4.log to your message after a short flight session. Thomas

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