Jump to content
The simFlight Network Forums

aua668

Members
  • Content Count

    313
  • Joined

  • Last visited

  • Days Won

    6

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
    Male
  • Location
    LOWG
  • Interests
    Flightsim ;-)

Recent Profile Visitors

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

  1. 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
  2. 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
  3. 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
  4. 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:
  5. 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
  6. 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
  7. 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
  8. 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
  9. Hi, A better way to toggle these switches is by setting the following Lvars to 0 or 1: L:AB_PDS_Eng1Master L:AB_PDS_Eng2Master You can do this either by a small LUA script or by creating a "normal" macro toggling these variables. See page 39 in the Advanced User Manual. Then you simply can assign this macro to your button. Also many other switches can be operated by that method. It's way better compared to the mouse macro, as this method works across engine variants on all A3xx planes from AS. Rgds Reinhard
  10. Hi, There is an easy solution, which I use since the beginning: When I download the ZIP file, I save it as FSUIPC_xxx.zip (with xxx being the version). By that I always know, which version I am installing and I can step back if there is a problem with the latest release (which did not happen as the tool is perfect). So this can be solved easily. Rgds Reinhard
  11. John, Thanks - no hurry and prepare for the future 😉 Rgds Reinhard
  12. Dear Pete, Dear John, Is there any chance to get in a future release of FSUIPC access to these Simconnect functions: SimConnect_DockView SimConnect_UndockView The reason: If you want to move views (e.g. panel pop-ups) to different screens dynamically in a multi-monitor environment, they must be unlocked. While you can save such views in P3D 4.5 on the main monitor as undocked window, this doesn't work for example on already undocked windows on a secondary monitors. There these panel views are always docked - even if you save the scenario as undocked. Loading them dock thes
  13. Hi, Thanks for sharing the LUA. Now I know, where you are coming from. You are using the relatively old FSX NumPad Control Utility from Al Klayton, which can be found here: https://simviation.com/1/browse-Utilities-65-5?mark=49328#49328 This is a set of LUA files, which provide the possibility to enter values for the radios via the NumPad. But checking the ZIP file I found, that there is also an ADF routine included to set the ADF. Why aren't you using this routine? Has your aircraft two ADFs (ADF1 and ADF2)? Be aware, that these modules typically will work with standard ai
  14. Hi, If you could share the file "NpCsetOBS.lua" here, there is a good chance to modify it in a way that you can use it. Rgds Reinhard
  15. Hi, Thomas answered already perfectly - the screenshot showed the misunderstanding clear. For the OBS: In that case you are triggering a LUA routine "NpCsetOBS.lua". That's a complete different way to trigger an action. You could also experiment with the Inc and Dec commands to check, if the ADF is reacting. If this is an commercial add-on plane, it's not always guaranteed, that they use the standard simulator functionality in their gauges. Rgds Reinhard
×
×
  • 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.