Jump to content
The simFlight Network Forums


  • Content count

  • Joined

  • Last visited

  • Days Won


aua668 last won the day on May 19

aua668 had the most liked content!

Community Reputation

5 Neutral

About aua668

  • Rank
    Advanced Member
  • Birthday 10/03/1960

Profile Information

  • Gender
  • Location
  • Interests
    Flightsim ;-)
  1. Sub Folder to hold Lua Files

    Hi Glenn, I solved my problem with the limit of 127 LUA files very pragmatic: I made a sub-directory per plane type with all my necessary plane-specific LUA modules and one with the generic LUA modules. I start P3D with a CMD file. In this file I delete all *.LUA files in the FSUIPC directory. Then I copy the generic modules and the plane specific modules into the FSUIPC directory. In the FSUIPC.INI file I delete the LUA files section and add a plane specific section to the INI file. Then I start P3D. So I simulate something like profiles for LUA files. By that simple method I can use the maximum number of possible LUA files per plane without breaking the limits if I use different planes. I also decide out of a config file, which LUA modules I have to start for a specific plane type. @Pete: As I have a solution, for me there is no immediate need for the profile based version, if it's complicated. But It would be very elegant, as the profile specific setting are a really good way to define things differently per plane. So if this comes in future versions, this would be a nice enhancement of this already great piece of software. Rgds Reinhard
  2. Sub Folder to hold Lua Files

    Hi, Just one idea for the LUA path as planned. It would be great, if this could be combined with the profiles implementation. If we could get the active LUA path and the LUA modules out of the profiles INI file instead out of the FSUIPC INI file (if profiles are used) like you do this for buttons, axes etc., this would allow to have several setups dependent on the plane used. This would be really great! Rgds Reinhard
  3. Sub Folder to hold Lua Files

    Hi, Just to provide some information about LUA modules. I have a similar setup with around 80-90 LUA modules running fully event driven to connect my GoFlight Hardware to some complex airplanes. I wrote them for being able to run them independent per function. So one module is for transponder, one for COM1 etc. I can start and stop them independently, which is good during development phase. I once tried to combine them in one single LUA module. As I use naming conventions in my code, which didn't create conflicts, this was quite easily done. Interestingly the modules have been working but the responsiveness to events have been worse compared to the single modules. You typically won't see this with single switches, but if you have radio knobs creating a lot of fast repeating events you could see, that they are reacting much slower. So my experience out of this experiment was, that it's better to have more small and independent LUA modules compared to have only a few big ones with a lot of event triggered functions. And of course the code can easier be maintained. Rgds Reinhard
  4. Hi, Mouse macro creation in P3D 3.4 works as expected in my configuration. So it must be something locally in your installation. Rgds Reinhard
  5. Hi, For the scroll wheel check the FSUIPC documentation for mouse macros and the parameters, which you can apply. Rgds Reinhard
  6. Hi, Did you already use the function ipc.testbutton(joynum,btn) in LUA to check the sate at the beginning and set the simulator equivalent to the current position of the hardware switch? Rgds Reinhard
  7. Hi, The Feelthere E195 can only be programmed via mouse macros. So record a mouse macro for the knobs you want to press. An then assign these macros to your joystick buttons. Rgds Reinhard
  8. Hi, You are right ;-) The first article I ignored, as I thought that this was - according to your comment - introduced by FSUIPC5. I am still on FSUIPC4. And the user used the syntax in the same way I tried (parameter within the string). And this was not working for me. The second article I also found. But the error in that case was simply, that the user specified a wrong path. That was not the case with my problem. Anyhow - it works perfectly now. Rgds Reinhard
  9. Pete, Thanks for looking into that topic. I will go vor the BAT solution as proposed. I searched prior to my posting but I didn't find a similar problem. But I will try to find the topic. Rgds Reinhard Edit: I tried now first RunIf1=READY,CLOSE,"C:\<complete_path_here>\vpilot.exe" -host and BINGO - it did work. I would never had thought, that this will work. Great idea!
  10. Hi, I use FSUIPC 4.974b with P3D v3.4 under Win 7-64bit. I tried to start vPilot (a VATSIM client) on my P3D PC via RunIfN in the host mode, as I run the user interface of vPilot on a second PC. Starting vPilot in host mode is accomplished by adding the parameter "-host" after the program name. As written in the documentation for the RunIfN command, I enclosed the command by ". This should enable the usage of parameters and blanks in the command line. RunIf1=READY,CLOSE,"C:\<complete_path_here>\vpilot.exe -host" BUT: vPilot is not starting and in the FSUIPC log it shows an Error #2 telling, that the program couldn't be started. As soon as I remove the -host parameter, the program is starting fine - of course not in the host mode. It's not a critical issue, as I can start vPilot out of a command file used for starting P3D too. But maybe you could check, why it's not possible to pass a parameter with a "-". The same command in a CMD file works perfectly. Best regards Reinhard
  11. Hi, You should look for the documentation of the Majestic XML interface. Search for the file "MJC84_XML_IF_1008.zip" . The interface works in a way, that you specify the parameter in one L:Var variable and the call the function (via a hash value generated with a provided program) in a second L:Var variable. This only can be realized via LUA code. So to use the Majestic interface (only if you own the PRO version), you must be able to program in LUA. Then you are able to mapt this via events to buttons. Rgds Reinhard
  12. Hi, Check in the Advanced User Manual the section about MaxSteerSpeed. There you will find the solution and the reason for the behaviour. Rgds Reinhard
  13. Hi, You could use or Android tablet as a second monitor to your PC as described here: https://www.howtogeek.com/279069/how-to-use-an-android-device-as-a-second-monitor-for-your-pc-or-mac/ Then move your wideFS button window on that display and you can use the touch functionality on the Android tablet to trigger the WideFS buttons. I have not tried this solution, but it should be simple and working. Rgds Reinhard
  14. Pete, Thanks - I also have no idea, how the aircraft can influence this. I could at least identify one single gauge, which is programmed as a DLL, as the reason. When I remove this gauge from the panel, everything is loaded as planned (of course with the missing gauge). Also an aircraft id is shown. adding this gauge again produces this strange error. So it must be something in this DLL. With your input on reason for the error message I will contact Blackbox Simulation. Best regards Reinhard
  15. Pete, I have a problem with a third-party addon (Blackbox Simulation Airbus A2320). When I try to load this aircraft imn P3D 3.4 (latest hotfix) under WIN 7/64 P3D crashes. Crash log shows sometimes ai_player.dll but sometimes no crashlog is generated at all. P3D just terminates. I use FSUIPC 4.966c. This is obviously not a problem of FSUIPC but a problem of this specific aircraft. Analyzing the FSUIPC log file I have one difference compared to the other aircrafts I use, which work without problems. I found this entry in the logfile: User Aircraft ID not supplied -- trying default With other planes it shows an ID number. Under which circumstances this message is generated? Any hint from your side might help me to track the problem down on the BBS side. Many thanks in advance for your information. Reinhard

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.