-
Posts
150 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by kaha
-
Of course you are right, John, it's the axis assignment window. Here is my use case: I connected hardware potis to change the cockpit light in the Cessna 310. For this I made some profile specific axis assignments (see attached screenshot) and then set the appropriate cockpit lighting in a lua script. This works. Now I want to utilize those potis for other aircraft as well. Therefor I need to get rid of the profile specific nature of the axis assignment. The corresponding lua code is in the attached file lua.txt. Karl lua.txt
-
Thank you. Karl
-
Is it not possible yet? Karl
-
With an aircraft loaded that has profile specific controls defined I want to define an additional control that is not profile specific, in contrary it should be available for all aircraft. Now, bringing up the Button Assignment window the checkbox "Profile specific?" is checked and greyed out. How can I uncheck? Karl
-
Thank you. I use the store version. I found two FlightSimulator.exe files on my ssd. I changed both to be started as admin, and now it works! I searched for FlightSimulator*.exe on my C drive and then changed to "Start as Administrator" in settings->compatibility. I use the software "Agent Ransack" for searching my drives. Karl
-
Since some time (already happened with v7.3.8) FSUIPC does not start when I use the desktop shortcut. The sim starts, but not FSUIPC. The shortcut and FSUIPC.exe are set to "Start as Administrator". There is not even a .log file, so FSUIPC does not start at all. Once the sim runs and I start FSUIPC.exe it runs. What can I do, what additional info do you need? Thanks, Karl
-
Thank you John. I got it to work. Not sure what caused the irregularity, I guess it was my frequent switching between different aircraft for testing and not restarting the sim. Everything is perfect now. Thank you, Karl
-
Sorry, if FSUIPC is not the reason for my problem, but I don't know where to look for a solution. I try to assign this event "Starter 1 Held" to a switch, but nothing happens. The event "Set Starter 1 (Hold)" in plain MSFS works. "Starter 1 Held" works with other aircraft, though. Where is the issue? MSFS, FSUIPC, that specific aircraft? I'm at a loss. Best, Karl
-
7.2.3 doesn't load my .lua scripts specified in the [Auto] section
kaha replied to kaha's topic in FSUIPC7 MSFS
Thank you! -
7.2.3 doesn't load my .lua scripts specified in the [Auto] section
kaha replied to kaha's topic in FSUIPC7 MSFS
Maybe 7.2.3 did not install the WASM module? Anyway, it now works. Thanks, Karl -
7.2.3 doesn't load my .lua scripts specified in the [Auto] section
kaha replied to kaha's topic in FSUIPC7 MSFS
Thank you. It worked before, I didn't change anything in the .ini The logs I sent are from 7.2.3 were with the 7.2.4b exe file. I now updated to 7.2.4, did not change the .ini file (still EnableWAPI=Yes) and did not install the WASM module. But now everything works again. Files attached. logs_724.zip -
7.2.3 doesn't load my .lua scripts specified in the [Auto] section
kaha replied to kaha's topic in FSUIPC7 MSFS
Thank you John, here it is. Karl logs.zip -
Thank you John. Would it also be ok to just exit FSUIPC as soon as MSFS has loaded? What about the lvar moduke in the Community Folder? Do I have to delete it when not using FSUIPC? Karl
-
Sometimes I want to start MSFS without FSUIPC. So I start up the sim from the Windows Start Menu. At some point of the MSFS startup process FSUIPC starts up by itself. Why is this? Karl
-
I can edit, change and save it. I have all rights: Read, Edit, Change, Execute, Write. What does the FSUIPC installation process need to do with it? Karl
-
Thank you John, that was it. I did not finish to load the flight. Once in the cockpit it works. The installation doesn't work, though. I reinstalled with admin rights, to no avail. Anyway, using your .zip file it works. Karl
-
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
-
Ok, that's at least something. Thx, Karl
-
Great news! No mouse macros is a significant drawback, however. Karl
-
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 Surface_Trim.lua
-
- 1
-
-
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
-
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
-
Thank you Pete. Karl
-
Quick question: With the possibilities of FSUIPC and lua only, how could I get a list of devices that have an active com port? It basically would be the list delivered by HidScanner.exe with the addition of a com port number for devices where it is available. Thank you, Karl