Jump to content
The simFlight Network Forums

kaha

Members
  • Posts

    124
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by kaha

  1. May I follow up on this please: I have a similar issue, maybe caused by my non-standard "Official" and "Community" folder paths? Both are located at E:\MSFS2020.

    Copying the content of your posted fsuipc-lvar-module.zip to the Community folder worked. However, I can enable WASM in the FSUIPC menu, but all other options (like "List Lvars", "Set Lvar...") are inop. 

    Karl

    InstallFSUIPC7.zip

  2. I want to share my lua script for trimming. It works as follows:

    https://www.dropbox.com/s/2ceuy2jj8hfftib/Surface_Trim.lua?dl=0

     

    To a button assign the control "Lua Surface Trim" after you have copied the file into your FSUIPC folder. The Parameter entry consists of 

     

    100000 for Elevator trim

    200000 for Aileron trim

    300000 for Rudder trim

     

    To this add the amount you want to trim:

    1 for very small trim

    a maximum of 16383 for full trim

     

    add this to the base:

     

    100000 + 300 = 100300   that would be a moderate trim up for the Elevator.

    300000 + 2000 = 302000  that would be a large trim for the Rudder in one direction.

     

    To trim to the other direction just make the number negative (-100300, -302000)

     

    In order to center the trims you use:

    100000  center Elevator trim

    200000 center Aileron trim

    300000 center Rudder trim

     

    This is very handy as you can have different trim amounts for different aircraft. I even use small trims and large trims simultaneously.

     

    Feel free to use this script to your likings.

     

    Karl

    Elevator up trim.png

    Elevator down trim.png

    Surface_Trim.lua

    • Like 1
  3. Just to mention this:

    I had a bug in a lua script. This caused FSUIPC to crash. The tray icon was still there but did not respond. Restarting MSFS told me that FSUIPC is already running. In TaskManager FSUIPC 7 is not visible. I had to reboot.

     

    I attached the .log file (which just says that my lua script had to be terminated).

     

    So, no worries, this is just to let you know, John.

     

    Karl

     

    Windows 10 20H2 Build 19042.867

    FSUIPC 7.0.8

    FSUIPC7.log

  4. My question aimed at finding a possiblity within lua to clearly identify the Arduinos I have connected to my rig, they are not HIDs. I use Teensy 3.2, 3.5, 2.6, 4.0 and 4.1. Anyway, I stick to what I have. I wanted to be able to identify the Arduinos automatically regardless on which port they connect. The main criteria I use for recognition is the baudrate of 115200 that I use for all my connected Teensys.

     

    Anyone wants to share how he handles this?  Here is my code (Identify_Arduinos.lua), but it's surely far from being an ideal solution. I'm more a C/C++ coder, not a lua coder. Also my string tweaks (String_Tweak.lua) are needed to run it.

     

    Karl

     

    String_Tweak.lua Identify_Arduinos.lua

  5. I think I'm all set now.

     

    It was quite a challenge. The log file told me that joystick id 0 is registered twice in the registry, so I had to clean that out. I switched to Letters, adjusted the button and axis actions and now everything works.

     

    https://www.dropbox.com/s/w30ipn5rlfng034/FSUIPC6.ini?dl=0

     

    https://www.dropbox.com/s/ysd8q262pa45lun/FSUIPC6.log?dl=0

     

    I still have to take a look to FSUIPC 7 in MSFS now.

     

    Thx,

    Karl

  6. Thank you Pete. 

     

    Button presses and axis movements on the Hotas Throttle do not arrive in FSUIPC. They arrive in P3D, though. 

     

    Here is the .ini file form before my hardware change, I made a backup before I started to change hardware.

    https://www.dropbox.com/s/ikzjoawn2ariiif/FSUIPC6_original.ini.txt?dl=0

    At that time I had connected:

    - Logitech G920 Racing Wheel

    - Logitech Extreme 3D Joystick

    - Thrustmaster T.Flight Stick X

    - Thrustmaster Hotas Warthog Throttle

     

     

    And here is the new .ini file

    https://www.dropbox.com/s/kiqydv5itil4poz/FSUIPC6.ini.txt?dl=0

    after the hardware change. Now I have installed:

    - Logitech G920 Racing Wheel

    - Thrustmaster T.Flight Stick X

    - Thrustmaster Hotas Warthog Throttle

    - Thrustmaster Hotas Stick (with F/A-18C Grip)

    -Thrustmaster TPR pedals

     

    Karl

     

  7. I installed new hardware today, here's what I did:

     

    - removed Logitech Extreme 3D Joystick

    - added Thrustmaster TPR pedals

    - added Thrustmaster Hotas Joystick

     

    unchanched: Thrustmaster Hotas Throttle and a Thrustmaster T.Flight Stick X.

     

    After that FSUIPC does not recognize any button or axis of my Thrustmaster Hotas Throttle. What could be the reason for that?

     

    Thx,

    Karl

     

    P3D V5.1, FSUIPC 6

  8. Hello,

    as there is no offset location for this and no L:Var for the aeroplane I want to control (Just Flights C-46) and also no K:Var in P3D, I assume that getting this variable is only possible by reading the "TAILWHEEL LOCK ON" boolean from simconnect in a lua script?

    Has anyone done it yet? That would save me some time and be very much appreciated. I'm on P3D V5.1HF1.

     

    Thank you for your help,

    Karl

  9. Hello,

    I'm new to the forum. I use FSUIPC since long already and now got WIDEFS in addition. The user manual tells me I have to run the FSUIPC installation utility for entering the registration for WIDEFS. 

    The FSUIPC installation utility then tells me it needs to be uninstalled before it can be installed.

    Anyone knows if I uninstall FSUIPC and then reinstall it, will all my setups and configs be gone? Do I have to have a backup of any files?

    Thank you,

    Karl

×
×
  • 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.