Jump to content
The simFlight Network Forums

Thomas Richter

Moderators
  • Content Count

    1,431
  • Joined

  • Last visited

  • Days Won

    24

Thomas Richter last won the day on September 2

Thomas Richter had the most liked content!

Community Reputation

29 Excellent

5 Followers

About Thomas Richter

  • Rank
    Advanced Member
  • Birthday 12/08/1962

Profile Information

  • Gender
    Male
  • Location
    : EINN
  • Interests
    AMT CAT 1, Cockpit building & Setup, Programming C/C++ / C#, Computertechnic, electronik (TTL-logic)

Recent Profile Visitors

6,041 profile views
  1. Hi, best is always to read as well the additional information from the download page or as the same information is included in the ZIP file you downloaded as README.txt file, you can read it from there. Thomas
  2. Hi, at the moment I think SimConnect and MSFS are not really in line at all and we start to try to make too many things work they might (hopefully) partly fixed or implemented with the next SimConnect update. As we found there are even Controls working they are neither listed or tested by Asobo and it was just a very time consuming try and error way to find out. As you will find in different places of announcements of the MSFS state by MS/Asobo they more and more tell this or the other is not working correct or at all or should not be used. Special automated systems like AP/ AT are often mentioned already by MS/Asobo as "partly" working . . . As long the Systems itself are not fully replicated in their basic functions, the incomplete SimConnect interfacing wouldn't help even if it would work more as it should. Lets hope the next Update has something more that the last 1.8.3.0 Thomas
  3. Hi Trev, that are errors in MSFA/Asobo flight models/ avionics. Some AC sending constant those or other controls. Not related or controlled by FSUIPC. Btw- P3Dv5 has in some AC the same error. Thomas
  4. Hi, if it starts it will create a FSUIPC7.ini file and a FSUIPC7.log file, both located in the folder where you run FSUIPC7. Copy and paste those files or its content to your message. Thomas
  5. Hi, as the manual clearly describes the both commands are only used when FSUIPC starts and at what state they will start the containing Lua files. To Run / Stop Lua files you use the respective Lua controls. Please check the FSUIPC Lua Plug-Ins.pdf and FSUIPC Lua Library.pdf from one of the other FSUIPC installation Documents, FSUIPC4 / 5/ 6. Thomas
  6. Hi, it might be that when you installed FSUIPC6 for P3Dv5 that you selected install for both, P3Dv4 and P3Dv5. But good you are sorted. Thomas
  7. Hi, you can but most likely there is nothing that can be done as long the SDK doesn't support those functions. We report those things we find and are not related to FSUIPC direct to MSFS/ Asobo support. Thomas
  8. Hi, Toggle Pushback control will only toggle Pushback ON or OFF, the value has no effect. To send Left(1), Right (2), Straight(0) or OFF(3) you need to send the value to the Offset 31F4. Instead of selecting Toggle Pushback you choose Offset Dword Set, see pic. This would need 4 buttons or you use instead for Straight and Off the Toggle Pushback control but that would then switch from Left or Right to OFF and needs another press. Thomas
  9. Hi, make sure you have an actual folder created and not starting FSUIPC7 direct in the ZIP file. Thomas
  10. Hi, I requested, as we always ask for, the content of your FSUIPC6.ini file unaltered (the complete file/ content). Flaps UP / 1 /2 / 5 / 10 / 15 / 25 / 30 / 40 = 9 detents. -16384 to 16384 = 38768, 38768 / 9=4096. FSUIPC knows the number of detents from the current AC and the spaces are always even in-between. As you didn't calibrate the flaps lever nor set detents it depends on your controller and PMDJ only. PMDJ might interpret the lever position different. Here you can define the positions and detent spaces Thomas
  11. Hi, this is neither a famous message nor a dummy message. It is an info that it seems there is a second installation of FSUIPC that starts. As you say AFVACARS wanted to update FSUIPC it is more likely that it did a second installation of just the DLL in some entry instead of using the FSUIPC installer. As it is possible to have more than one copy of FSUIPC running, you would see two menu entries in P3D, do you? Also on FSUIPC Logging tab on the center bottom you can press Open Folder to open the FSUIPC installation folder. Thomas
  12. Hi, those controllers are vJoy - Virtual Joystick, not physical devices. Maybe multiple installations have been done by mistake? Thomas
  13. Hi, since FSUIPC5 this option doesn't exist anymore as it was a problem with older FS versions and I think as well with P3Dv1-v3. Thomas
  14. Hi, why posting this in two different threads, that is confusing for no reason ?? As I said already, you might first fix the controller problem in your registry. 109 System time = 20/09/2020 17:22:28 109 FLT path = "C:\Users\janos\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\" 188 ------------------------------------------------------------------- 203 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) 297 FS path = "C:\Users\janos\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\" 313 ---------------------- Joystick Device Scan ----------------------- 313 Product= vJoy - Virtual Joystick 313 Manufacturer= Shaul Eizikovich 313 Serial Number= 2.1.9 313 Vendor=1234, Product=BEAD (Version 2.25) 328 GUIDs returned for product: VID_1234&PID_BEAD: 328 GUID= {675FFD60-DD8E-11EA-8004-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67604B80-DD8E-11EA-800A-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67602470-DD8E-11EA-8006-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67602470-DD8E-11EA-8008-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67607290-DD8E-11EA-800C-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {675FD650-DD8E-11EA-8002-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) 328 Product= VirtualFly - RUDDO+ 328 Manufacturer= 328 Vendor=16D0, Product=0DA3 (Version 0.2) 328 GUIDs returned for product: VID_16D0&PID_0DA3: 328 GUID= {225074A0-E19B-11EA-8001-444553540000} 328 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U4096,V4096,X4096,Y0,Z0 328 Product= VirtualFly - YOKO+ 328 Manufacturer= 328 Vendor=16D0, Product=0DA0 (Version 0.2) 328 GUIDs returned for product: VID_16D0&PID_0DA0: 328 GUID= {25CD3F50-E19B-11EA-8002-444553540000} 328 Details: Btns=7, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X4096,Y4096,Z0 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) . . . 344 ------------------------------------------------------------------- 344 WARNING: Joystick ID 6 is duplicated in Registry 359 WARNING: Joystick ID 7 is duplicated in Registry 375 WARNING: Joystick ID 8 is duplicated in Registry 484 WARNING: Joystick ID 10 is duplicated in Registry 484 WARNING: Joystick ID 11 is duplicated in Registry 500 Device acquired for use: 500 Joystick ID = 3 (Registry okay) 500 3=vJoy Device 500 3.GUID={675FFD60-DD8E-11EA-8004-444553540000} 500 Device acquired for use: 500 Joystick ID = 4 (Registry okay) 500 4=vJoy Device 500 4.GUID={67604B80-DD8E-11EA-800A-444553540000} 500 Device acquired for use: 500 Joystick ID = 5 (Registry okay) 500 5=vJoy Device 500 5.GUID={67602470-DD8E-11EA-8006-444553540000} 500 Device acquired for use: 500 Joystick ID = 6 (Registry okay) 500 6=vJoy Device 500 6.GUID={67602470-DD8E-11EA-8008-444553540000} 500 Device acquired for use: 500 Joystick ID = 7 (Registry okay) 500 7=vJoy Device 500 7.GUID={67607290-DD8E-11EA-800C-444553540000} 500 Device acquired for use: 500 Joystick ID = 8 (Registry okay) 500 8=vJoy Device 500 8.GUID={675FD650-DD8E-11EA-8002-444553540000} 500 Device acquired for use: 500 Joystick ID = 2 (Registry okay) 500 2=VirtualFly - RUDDO+ 500 2.GUID={225074A0-E19B-11EA-8001-444553540000} 500 Device acquired for use: 500 Joystick ID = 10 (Registry okay) 500 10=VirtualFly - YOKO+ 500 10.GUID={25CD3F50-E19B-11EA-8002-444553540000} 500 Device acquired for use: 500 Joystick ID = 11 (Registry okay) 500 11=VirtualFly - TQ6+ 500 11.GUID={F2A26C20-E19C-11EA-8003-444553540000} Thomas
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.