Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


aua668 last won the day on December 10 2018

aua668 had the most liked content!

Community Reputation

13 Good

About aua668

  • Rank
    Advanced Member
  • Birthday 10/03/1960

Profile Information

  • Gender
  • Location
  • Interests
    Flightsim ;-)

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Dear John, It works perfectly again. Thanks for fixing this so quick! I did run it with EnableExtraButtons=Yes and it's working again from LUA with the event.button triggers. Best regards Reinhard
  2. Hi, Thanks for checking my problem. I did a quick test with EnableExtraButtons=No . It does not change the behavior. The POV buttons are recognized in the button assignment tab of the FSUIPC UI but not within LUA using the event.button trigger. So as I could stay on 6.0.13, there is no problem for me, until you find the reason. Following the thread about the beta pre-release of the 6.1.0 version, there are a lot of references, that some adjustments in the code have been made for the POV buttons. Maybe the LUA part also has to be adopted accordingly. Rgds Reinhard
  3. Hi, I upgraded from FSUIPC 6.0.13 to 6.1.0 (Win 10, P3D 5.1 latest HF) and suddenly my coolie on my Saitek yoke, which I use to switch camera settings via LUA code, did not work anymore. Other buttons on the yoke work normally. The buttons are also recognized, if you check them in the FSUIPC UI (button assignments). Only in LUA programs using the event.button trigger the buttons are not trapped anymore. The buttons, which are not recognized, are buttons 32 to 39. I stepped back to 6.0.13 and everything was working again. Upgrading to 6.1.0 and functionality is broken. So I reverted b
  4. If you want to check your USB devices I recommend to use USBDevView: https://www.nirsoft.net/utils/usb_devices_view.html Rgds Reinhard
  5. Definitely - I use GF-Modules since many years always with the latest FSUIPC version. And it works with the versions mentioned by John. RGDS Reinhard
  6. Hi, LUA scripts are not executed automatically per default. You have to put a line into the [Auto] section of the INI file or you have to start the LUA procedure by assigning it to a button or key. Details are found in the manual for advanced users. Rgds Reinhard
  7. Hi, One question, which might be stupid, as I am not aware about the hardware you are using: Why are you not using four simple button assignments triggering the controls with the desired parameter? Rgds Reinhard
  8. Hi, You should look for LINDA, which provides out-of-the box functionality for most buttons. If you are an advanced programmer, you can check the coding of LINDA for the relevant mapping of buttons to LVars. A list of all LVars can be produced via the LUA sample code provided with FSUIPC. I enclosed the list for your reference. Here you find a small function toggling the APPR button: -- APPR function APPRToggle (joynum, button, downup) -- toggle APPR ipc.writeLvar("L:AB_AP_LOC2", 1 - ipc.readLvar("L:AB_AP_LOC2") ) ipc.writeLvar("SmallOverheadPushButtons", 1) end Rgds Rein
  9. Hi, Just to add: In the meanwhile I make it much easier: I have the LUA files per aircraft in a separate directory: <FSUIPC folder>\LUA\A320 <FSUIPC folder>\LUA\DH8D : In my master start routine I first determine the aircraft type out of the name read out of the FSUIPC offset. Then I start the necessary modules directly out of the subdirectory: ipc.runlua ( "LUA\\A320\\A320_GF_EmergLt" ) Attention: use the double \\ for subdirectories ! In fact I have a LUA table defined in a profile module and run each module out of a loop: -- init all
  10. Hi Al, As my solution was mentioned: I had a similar problem like you with coupling several aircraft types to my GoFlight hardware. But by moving the necessary routines to sub directories per aircraft and by having a generic startup routine, which starts the necessary modules depending on the aircraft type loaded out of the respective subdirectory, the limit was no problem anymore. So I can definitely recommend to go for that approach. Rgds Reinhard
  11. Hi Rhys, The MD530F from Milviz only has a VC. But defining views with dedicated cockpit cameras (showing only the interior) is a very simple task. So if you have a separated outside view (what I assume that you have, as you are building a small cockpit), then you can arrange your camera views on your cockpit monitor(s). I am Using a Samsung ultra-wide 32:9 screen for the outside view and below two touch screens for the cockpit view (pilot/copilot) beside some GoFlight hardware. Here you find the manual: https://milviz.com/Online_products/Manuals/MV_MD530F_rev.pdf An here a review:
  12. Hi, Which helicopter add-on are you using as a base for your implementation? I own the Milviz MD500 and in that product the start procedure is exactly implemented according to the video. Rgds Reinhard
  13. Hi, In the documentation folder of the Aerosoft Airbus you will find a document "Vol7-Thrust Lever Setup.pdf". In that document two methods of setting up your controls are described: Without and with FSUIPC. Follow these instructions and it will work. The most important sentence: Rgds Reinhard
  14. Hi, I think, you clicked on the tag instead of going into the subsection of the useful programs and download the latest ZIP from there. I have just tested it and it works as planned. Rgds Reinhard
  15. Hi, Some things you might check, if you have an ON/OFF switch but only found a toggle command in the command list: Check, if there is an corresponding offset available, which you could use to invoke set/clear instead toggling If the offset is read-only, you might consider offset conditions in your button programming Check if there are Lvars available in the specific plane, which you could use to set/clear the respective switch If nothing else worked, you could check, if there are distinct click spots available in the gauge for on/off. Or if on/off is triggered by d
  • 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.