Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Everything posted by Detlef_747

  1. Hello Thomas, using Lvars did the trick for me. I experimented using the following Lua code: local lvname={} local k=1 local disp, n, val local aircraft = "" local len, stop lvname[k]="AP_PWR"; k=k+1 lvname[k]="bAPPowerSwVar"; k=k+1 lvname[k]="Track"; k=k+1 lvname[k]="bAPEngageSwVar"; k=k+1 lvname[k]="Pitch Hold"; k=k+1 lvname[k]="IAS Hold"; k=k+1 lvname[k]="bAPBankSwVar"; k=k+1 lvname[k]="KBank"; k=k+1 lvname[k]="MotorA"; k=k+1 lvname[k]="CurBank"; k=k+1 lvname[k]="MotorE"; k=k+1 lvname[k]="bAPHeightIASSwVar"; k=k+1 lvname[k]="bAPTrackS
  2. Hello Thomas, thank you again for your advice. I did never use L:vars and ignored documentation about it until now. I tried arround a lot today. I think you are right, for some features the P3D autopilot at least for the C-130 aircraft seems to use L:vars. I don't like that so much since those variables probably differ between aircrafts. I have a very old self made hardware with switches and LEDs mainly that communicates via COM serial interface with the PC. That used to work fine for many years with FSX. Now, recently I decided to switch to P3D and I have re-programmed all my softwa
  3. Hello Thomas, thank you for your reply. I have not yet come arround to try your suggestion but will do. Thank you Detlef
  4. Hello everybody, I have difficulties to get a Lua script to set the heading hold mode of the C-130 aircraft. I have tried the 0x7c8 variable as well as using ipc.control(65798). If I press the heading hold button per mouse, I can activate the autopilot. So A/P power is on and the A/P master switch is on. However, if I try per Lua script, the A/P heading lock mode toggles on and off without even showing the A/P heading(track) lock light coming on. I try this Lua script: while 1 do has_ap = ipc.readStruct(0x764, "1UD") ap_masterswitch = ipc.readStruct(0x7bc, "1UD")
  5. Hi Thomas, yes I see. Thank you and here it comes. Detlef [General] UpdatedByVersion=5152 History=K8WWIYSSL0KJVKHEHSL64 InitDelayDevicesToo=No PMDG737offsets=Auto PMDG747offsets=Auto PMDG777offsets=Auto Annotate=Yes UseSystemTime=No UseMidMouseBtn=Yes MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 RestoreSimcWindows=No FixMachSpeedBug=No AutoScanDevices=Yes DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemov
  6. Hello everybody, I got it solved following your advice, so thank you. I changed every control within P3D that was assigned to a button to the same button, thus effectively removing all button assignments. I saved that configuration as buttons_deleted in case I need it at some time. Then I unchecked controllers in the P3D settings. Still after that I had trouble with elevator up button assignments. My impression is for elevator trim up I may have used the wrong control, since the aircraft control surface change from the trim fought against the control stick. In any case, I assigned the
  7. Hi everybody, I am trying to assign Joystick Buttons to Elevator trim down and elivator trim up. And trim down works but trim up causes P3D to cycle through the views. I tried to delete the Control assignment in P3D that I had set earlier in the P3D menu but somehow the sim still uses that old button assignment and ignores the FSUIPC button assigment. Do you know how I can delete all Joystick button definitions from P3D? I want to program them using FSUIPC. Thank you Detlef
  8. Hello John, that worked! Thank you again for your fast help. I am making progress with my project to get my old switch hardware working with P3D. The Lua script is 3000 lines long by now, and it seems to work ok. At least it is not working worse than my old Visual Basic solution. But I did not really do much flying with it until now. Some things, for example auto pilot functions, I can only test in flight. The FSUIPC documentation about ipc Lua functions and sim control variables is just great and very helpful. I will change to the new FSUIPC. Thank you Detlef
  9. Hello everybody, (I copied my question here originating from the user contributions forum which was probably wrong) I encountered the following problem today. Everything was working fine in my system two days ago. I have written a Lua script that was working fine. Now all of a sudden today after starting P3D, when I select FSUIPC Add-on from the menu the P3D window just shows black until I press the ESC key. I have no idea why that happens. I am not aware of any change in my system. The only thing I noted today when starting the PC, somehow P3D was already running and told me that
  10. Hi John, thank you again. 🙂 No, starting a script per L key was just a convenient way for me for my first steps with Lua. My flight sim computer is in one room, and I am sitting more comfortable in another room at a Laptop, which is connected per Windows 10 Remote Desktop . Actually I am planning to react on input from the serial interface (COM3) which is my switch console. And also on timer events. My time is limited so it will take quite a while till I get there and further with the project. Yes, thanks for pointing that out. I think I understand that now. Again, th
  11. Hi John, thank you very much for your fast answer. It got me thinking some more. Yes I am aware of the logging features. I start a Lua script by setting a key (L in my case) to start the script. So if my script has the name kevent.lua I set the key L to the control Lua kevent. I think that works fine. Thank you for pointing me to the fsuipc.ini file, though. I tried that too now. I found out, regardless whether I start a Lua script via [Auto] section or via pressing the L key: The events work when I just start the event at the end of a Lua program. But if I initiate the events, an
  12. *** Moved from FAQ Support Forum *** Dear fellow simmers, it is a long time since I last modified my flight simulator setup, about 10 years and more! I had built my own console with switches and LEDs, to interface with FSX. It was working until now with FSX and Windows 7. I had programmed it myself using FSUIPC (4 I think) and Visual Basic. Now, just 2 weeks ago I installed Windows 10 and also P3D V4.5. When trying my old program (called RealSwitches) some switches still brought the correct reactions in P3D as they did before in FSX. For example gear up and down still worked. Ho
  • 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.