Thomas Richter

Hi, make sure you use latest FSUIPC5 version and also you have the latest update for PMDG installed. Please also attach the FSUIPC5.log. Thomas

Hi, in case you downloaded the installer ZIP file, it includes a document 'Installing and Registering FSUIPC4.pdf' that gives you already the answers. Please check that document first to already avoid a possible wrong installation that could give problems. If a registration key is needed, for using additional user facilities in FSUIPC, you can buy it with SimMarket.com Thomas

Hi, you configure / define your controls for the NON Homecockpit scenario as needed. In FSUIPC5.ini file use ShortAircraftNameOk=Yes Then decide a livery of the PMDG you want to use in your HomeCockpit ONLY and configure / define your controls under a specific profile. When you then select this AC the controls defined in the profile will be used. Any AC you would like to define different than the default setup can have its own profile. Thomas

Hi, that is far out of date, please use latest version what is Install_FSUIPC4971.zip Thomas

Hi, in case there is no other report (yet) it might be related to your setup. I don't and didn't see that before. That means you will have installed P3D in Programs folder with limited access for writing. The Error 1332 is a Windows reported error (not a internal FSUIPC error code) and means: Error 1332: No mapping between account names and security IDs was done. Cannot find Approved_Groups Did you install Both with same privilegs? I.e. As administrator, right click on installer. Maybe you also use Winows 10? Best is to supply a Install.log file and the currect FSUIPC5.log file. Thomas

Hi, which FSUIPC4 version are you using? Defining as Trottle 1 will of course result in controlling only Engine-1, where Throttle controls all Engine. For PanView definition and also for Calibration please check the FSUIPC manuals, located in ..\Modules\FSUIPC Documents\ folder, well described. Thomas

Hi, with a profile specific you don't want genral functions belonging to all other AC for the specific AC but that's what you try to do. To have the other both functions to the same button for the specific AC you need to have them as well in the specific profile section of that AC. By using specific profiles assignments done in it forces assignments of the same button / axis / key in general section to be ignored, that is the whole idea behind it. If your setup would work as you expect then the specific profile would be senseless and not functional. Thomas

Hi, yes you need to buy a new key for FSUIPC5 from SimMarket. Thomas

Hi, macros have been a hack into FS/P3D (32 Bit version). That doesn't exist in P3Dv4 as a better way is to use Lua plugin with Lvars. Check the documentation for that. Thomas

Hi, first question is did you get a key from SimMarket for FSUIPC5? A key for FSUIPC4 does not work for FSUIPC5 as it is a different new product. Thomas

Hi, that is already not a fresh start as there is no C172 in P3D at all, Default AC's in P3Dv4 , must be already some type of add-on. Best is to use a real default AC to start with, also make sure you don't have automatics like AutoMixture turned off. Still you never send a log file as requested? Thomas

Hi, It dosen't. It is always a full version. Reguistered or not are as well the same but the difference is that the registered version gives you user facilities i.e axes and buttons definition/ programming and using of lua addins. Using of offsets via programs don't need a registration but using a lua addin like you do will need a registered version. Thomas

Hi, make sure you use the correct key. 1/ FSUIPC4 key does not work for FSUIPC5 and vice versa 2/ best is to copy and paste the information for registration, Name/ email/ key, rather than typing because of possible errors Thomas

Hi, you calibrate or better define axis in FS or in FSUIPC but not in both at the same time, one or the other. To start from scratch just delete the FSUIPC4.ini file in \Modules\ folder. When starting FS then FSUIPC will creatre a new fresh INI file. Don't delete any other file, no need to do so. Thomas

Hi, yes that is as it should be. Those were hacks into FS and as there are couple add-ons they can do that, there was no need to hack into P3Dv4 anymore. Thomas

Hi, just delete the existing FSUIPC4.ini file and start FS, then it will create a new one. Thomas

Hi, first you need to update to latest FSUIPC version, which is FSUIPC4.971. Try then again. Thomas

Moin Moin, >>> /3 I'd am sorry but you come across really condescending to me. It felt the same way in my rebuy post, with all the red markings and such and now EXCLAMATION MARK, you NEED TO SHOW. Might be just me, but I'd really appreciate it if this were not the case. Otherwise I'd like to ask you to not answer to my posts anymore. <<< Viel Spass dann mal. Thomas

Hi, 1/ can you confirm Controls are switched to OFF in P3D ! 2/ you need to show your FSUIPV5.ini and also your FSUIPC5.log file, after your calibration and closing FS with a short session Thomas

Hi, as long you don't use any user facilities of FSUIPC you don't need a registration key (available at SimMarket only). Some add-on programs request a registered version of FSUIPC but checking the Superbug home page, they don't even mention FSUIPC in their requirements. Thomas

Hi, both links work correct. Thomas

Hi, any older version of FSUIPC5.113 will not be supported, the one should update first to FSUIPC5.113 and send a log file. Thomas

Hi, FSUIPC doesn't know AS CRJ 700/900 aircraft. So it cannot handle anything of it. If, as aerosoft claims, FSUIPC is the problem why it doesn't happen with other add-on AC's? Anyway. First thing to do is to disable FSUIPC and test the aerosoft aircraft. Disable FSUIPC you can do in the XML.dll or just by renaming the FSUIPC5.dll to i.e. FSUIPC5.old , so it will not be loaded. Thomas

Hi, - Options -> Controls - bottom left 'Other' then you will see the headline 'Use controller' and below the box to 'Enable Controller(s)' It's a bit hidden in v4. Thomas

Hi, not in conflict but i.e. SIOC and IOCP uses FSUIPC, as far as I know when I used OpenCockpits hardware. So what I would suggest to run P3D with FSUIPC and without OPUS, SIOC and IOCP. If that works you start with one after each other to find out what causes the problem. If just FSUIPC would be the problem you would find reports about that but I never saw/ got any, other than yours. Thomas