Thomas Richter

Hi, there are no specific Offsets or values for motion simulation. You need to calculate the motion with more values than just acceleration of those three Offsets. For yaw (rotation) the offset is 3088. The G-load is as well a factor, those Offsets are just below the ones you are looking for to use. Thomas

Hi, Thomas

Hi, first thing to note before going on at all, you are running a very old FSUIPC5.124 version. We are at FSUIPC5.152 please update first to latest suitable version. As you run already 5.124, which would not work with P3Dv4.0, I guess you run a later P3Dv4. Link is below Also make sure you run latest WideClient software on your clients, link is below Also your log file shows the correct operation, value 32767 to set and value 0 to release. 278000 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 32767 (0x00007fff) PARKING_BRAKES 290609 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES 292266 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 32767 (0x00007fff) PARKING_BRAKES 294422 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES 295547 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 32767 (0x00007fff) PARKING_BRAKES 297563 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES Thomas

Hi, Seems you didn't check either? If you would have checked the PM manual you have found that the offset info I gave, 5653 .7 is listed as so going to that file you will find 5653 .7 bellcutout more information about that you will find in their, Project Magenta, manual about what that means A little bit of search would have answered, or as well, as John already suggested, contacting PM support for more information. Thomas

Hi, by looking into Project Magenta stuff, what You use, you will find when searching 5653 .7 bellcutout . That Offset is related to fire system.How to link that to CPFlight you might find in their manuals. Thomas

Hi, best is to activate logging for Events (non axis controls) on FSUIPC logging tab. Do couple cycle for the parking brake operation and close fully P3D. For any help we would need then the FSUIPC5.ini and FSUIPC5.log files, you can attach or copy and past its FULLY and not altered content. Thomas

Hi, I just ran the Make Runwys4.873 and all files are correct produced. You run it inside P3D folder, correct? Thomas

Hi, also make sure you use always latest version from Download section on top of the the forum, Download Links Install complete FSUIPC version 5.152 Install FSUIPC5.152 Thomas

Hi, Prepar3Dv up to v3 works with FSUIPC4 as FSX/FSX-SE does. But Prepar3Dv4 requires FSUIPC5, what is a new product as it had to match the 64 Bit structure of P3Dv4. So you will need to buy a new licence of FSUIPC5 for Prepar3Dv4. If you have a licence for WideFS7 that will work as well with FSUIPC5 , doesn't require to buy a licence again. Your current settings from FSX you keep by just renaming the file from FSUIPC4.ini to FSUIPC5.ini. Make sure you have in the FSUIPC4.ini file the setting AutoAssignLetters= set to Yes. Thomas

Hi, make sure you installed everything with "Run as administrator", so everything runs with same privileges. You might have to start the programs maybe as well as administrator properties. Thomas

Hi, check the KeySend facility in the documentation. Thomas

Hi, mouse macros can be programmed with profiles. I think L:Vars actually as well by using macros but check the manual. Thomas

Hi, make sure you use latest version Make Runways utility version 4.873 MakeRwys.zip Thomas

Hi, that AC might not use standard controls but maybe L:Vars. You can check both via Logging tab, - - enable Send to console window and Events (non-axis controls) that will log the control when you press the button via mouse, if it is a control - i.e. set a Key to List Local Panel Vars to list all L:Vars for the currect AC, then find in what is listed the name (Lvar) for the function. You can send then the LVar with Lua Thomas

Hi, I don't have any download area to store and most email providers block attached files, special EXE or DLL files even when renamed. I can try if you send an email address that could work. Thomas

Hi, first thing. Pete asked to update to latest FSUIPC4.974, looks like you didn't, UpdatedByVersion=4972 ? Best is to use latest and also only latest version is supported. Your INI showsthat the general joystick use is for both connected joysticks the same, X and Y axis. But in profiles it is different and sometimes the X axis is assigned to Throttle or as well the Z axis (Bodnar card) Also remember when using Bodnar cards for axis that the last connected axis poti will activate any previous port. so i.e. if you have only 3 axes to connect then you use the first three analog ports of the card only. Also you should use [JoyNames] AutoAssignLetters=Yes Seems you need to clean up the profiles a bit and general definition for the existing controller, 1= Logitech and 2=Bodnar Thomas

Hi, as I said the position Card13 is hard-coded for that function, as well the layout /conection of the card is. Thomas

Hi, sorry this will be checked, something wrong on their system I guess. Thomas

Hi, just use for upper and lower EICAS the PM software as you do for PFD/ND. For the fire panel I think that it was clear enough. The System B737 software has to be minimum version 2.1.153.3 or above (2.1.153.>3) The location to have the card number 330989 is in Phidgets.xml file, located in Systems_B737\Config\ folder within this section ( I don't recall the other card functions) <Cards Card1="0" Card2="0" Card3="0" Card4="0" Card5="0" Card6="0" Card7="0" Card8="0" Card9="275566" Card10="131519" Card11="0" Card12="0" Card13="330989" Card14="0" Card15="0" /> Thomas

Hi, Maybe someone is still using it but it should have a manual that describes usage via Offsets, if I remember correct. If you use Project Magenta software please check their documentation, again the usage of their specific Offsets to control will be described. I don't think FS standard controls would work correct. I have no idea how that would work by using FS2Phidgets (I never used). If the fire panel is connected, at the time in 2014, to INST-3 PC then the System_B737 software min. version 2.1.153.3 had that hard-coded when the following line exists in Phidgets.xml file in cards section: Card13="330989" The number is the Phidgets ser/ID number. Nothing more I can do. Thomas

Hi, why is the head of the Log file cutout, it contains important information? So please send a complete and not modified Log file. As seen in the Log file you use Autosave option, i.e with PMDG or other add-on AC's which might save lots of state data you shouldn't use Autosave option as it can lead to such problems you have. FSUIPC has no control over the amount or which data will be saved, that is entirely up to P3D and the corresponding AC/ add-on Ac is used. Thomas

Hi, just make sure the changed FSUIPC4.ini file is correct saved and after restart it is still the same. Is a starter program used to start the FSX or just clicking on FSX? Thomas

Hi, as the INI file shows FSUIPC doesn't even look for controllers. Can you please try with a stock aircraft the behavior instead of using a add-on aircraft. Is there any third party software installed that is using FSUIPC, as FSUIPC would in un-registered version only make sense for other programs to communicate with FS? Thomas

Hi, as there is nothing listed in the INI file of a used or existing Lua file that means nothing is used on the FS-PC. 1. Where did you define buttons to TRIM offsets, as nothing is defined in the INI file? I put couple of defined offsets to buttons into bolt. But there is no 0BC0 offste defined in your INI fileat all. Defining a button in FSUIPC to an Offset that controls something in FS if an Control already exists for that function, doesn't make sense as the offset will be translated back to the control and send to FS. Btw - there are two (for) buttons assigned to offset 0x6DB9, they are to control ELEV TRIM via System B737 program. The 5002 in font of the definition indicates that the corresponding controller is running on a client PC, sent via WideClient. If System B737 is still in use then the corresponding checkbox for ELEV TRIM should be set. But if the controller is no longer correct recognized but the checkbox is set then it would override any other input for ELEV Trim. One or the other to use. In FSX the check for controls has to be un-checked to make sure all controller inputs are disabled. Thomas

Hi, not heard of that. FSUIPC will only do something if you tell it to do. In case you use a non registered version you will not be able to define even an controller that could do something at all. Can you please send your FSUIPC5.log, FSUIPC5.ini and (if generated) FSUIPC5.JoyScan.csv files. Thomas