John Dowson

As spokes2112 says, this is not an efficient way run such a large lua file. Each time you call this, it has to create the thread and compile the lua script before it runs. It would be more efficient to have the lua auto-started (and compiled!) and activated on an event flag. You can also consider breaking the script down into multiple smaller files. Cheers, John

No news of this as of yet. It is something that will be looked into in the future, but at the moment this is low priority so nothing for the time being. Regards, John

This is how it should look. Your assignments/calibration will now use the letters, but the numbers still appear in the JoyNames section to enable the mapping of the numbers obtained in the scan to the letters via the GUIDs.

Looks like your registry is in a bit of a mess and needs cleaning. The first thing to try to do this is: Disconnect your devices Uninstall the devices from the device manager Reboot your PC. Re-connect your devices - let windows install the default device drivers Start P3D. Once this is done, post the log, ini and joyscan csv files again please.

Hi, could you post the lua script please?

No, sorry - not heard of MobiFlight before. Just googled it though and it looks interesting...

Sorry, just posted a possible solution when I noticed the GUIDs for your two devices are the same! Can you post your FSUIPC5.Joyscan.csv file please?

You need to convert the decimal value to hexadecimal, so 4976 = 0x1370 which would correspond to a frequency of 113.70 (BCD format). Hope that helps, John

Hi, looks like your stick and throttle have both been assigned a joystick id of 1. You will need to change the id of one of the devices by following the steps Pete posted in this recent thread: Cheers, John

By the way, the key file should be in J:\Lockheed Martin\Modules and not 'J:\Prepar3d\modules' as mentioned....

Hi Erwan, the log file shows the mouse macro is being activated ok. There are a few things you could try: 1. Duplicate your macro file (giving it another name), and in the second file change the left mouse-click code (3) to a left release (13) [P38 of Advanced User Manual]. Then assign this macro to the key release. 2. Instead of using two macro files (as above), you could edit the existing macro to contain both the left click and the release - see the section entitled 'Multiple actions in one macro control' P37 of advanced user manual. 3. If the above two fail, add event logging to see whats being sent when you both click and release with the mouse in the sim. Cheers, John

Hi, did you try starting P3D and checking if FSUIPC is registered? If you key file is still in the modules folder it will check the registration when you start P3D.

Hi, what files are not being deleted? Try adding the additional logging flags to your FSUIPC5.ini file, as mentioned above: Cheers, John

Yes, of course it needs that. Its pretty simple - the first line gets the handle of the window that needs the focus, the 2nd line sets the focus to the window with that handle. You need to create a file with those lines using a text editor, such as notepad++ (better) or notepad. John

I believe the exe is Prepar3d.exe (but open task manager with ctrl-alt-del to check), so it would be h = ext.gethandle("Prepar3d.exe") --name is program name incl .exe, or program title (as listed in Task Manager) ext.focus(h) John

Hi, you could try using a simple lua script, such as: h = ext.gethandle("name") --name is program name incl .exe, or program title (as listed in Task Manager) ext.focus(h) Save the above to your modules folder as, say, "usexxx.lua" where xxx suggests the program you are switching to, then, in FSUIPC, assign your button or key to Lua usexxx. Cheers, John

my FSUIPC cant run in FSX steam, how to run it? What is the actual problem? Did it install ok (install log?)? Why can't you run it - what errors are you getting? Have you looked at the documentation in the documents folder? Regards, John

FSUIPC5 is a different product to FSUIPC4, so you will need to buy a new key via Simmarket. Your wideFS key will still be valid. WideSever is now built into FSUIPC5. Regards, John

Hi jwillyf, as NaMc0 says, please remove you key ASAP. If people see this and start to use this key it will be blacklisted, NEVER post registration details please. All three parts of the key must be correct and those used at the time of purchase: name, email and key. Copy and paste from the original registration email. If you do not have this email, you can retrieve your details from your simmarket account. Regards, John

There is a similar problem reported here in which the cause the loading of a 32-bit dll. However, the post is quite old and relates to SODE 1.5.3. Maybe worth checking though. Cheers, John

That depends on what you want to do! You could, for example, read/monitor it in a lua script, in a C/C++ program, or use the logging facilities provided by FSUIPC to display the value in the log file, main window or title bar.

Hi, you probably want offset 030C - from the offset status document: Vertical speed, copy of offset 02C8 whilst airborne, not updated whilst the “on ground” flag (0366) is set. Can be used to check hardness of touchdown (but watch out for bounces which may change this). There is a discussion on landing rate calculation here: https://www.avsim.com/forums/topic/524247-how-is-landing-rate-calculated/ Cheers, John

Check the offset status document: 0x0020 (4 bytes) or 0x0b4c (2bytes). John

Also i'm not sure that this will do what you want it to do. Control 1009 is the Traffic Density Toggle. Toggling this only works in one session, and if there is no known initial state then this will set/toggle the density to 100%. You may therefore want to add a 0 parameter or use control 1008 instead. There is a similar lua example included that may be useful - this freezes taxi-out AI traffic when you lower gear (or lower flaps) and releases when you land: -- NOTE: For use with FSUIPC 5 only -- This small plug in, which should be pre-loaded: for example, by adding -- [Auto] -- 1=Lua AIfreezer -- to your FSUIPC5.INI file. -- It freezes taxi-out AI traffic when you lower your gear, -- and releases them when you touch down. -- For aircraft with non-retractable gear, it checks the state of -- the Flaps instead, expecting full flaps for landing. (amend where -- noted for other flap settings). function GroundCheck(off, val) if ipc.val ~= 0 then ipc.control(1149) -- Freeze AI off if user landed ipc.log("AI taxiout traffic released") end end function GearCheck(off, val) if val >= 16383 and ipc.readUW(0x0366) == 0 then ipc.control(1150) -- Freeze AI on if gear just lowered (whilst in the air) ipc.log("AI taxiout traffic frozen") end end function FlapsCheck(off, val) -- See if gear is fixed first: if ipc.readUB(0x060C) == 0 then if val >= 16383 and ipc.readUW(0x0366) == 0 then ipc.control(1150) -- Freeze AI on if now full flaps set when in the air ipc.log("AI taxiout traffic frozen") end end end event.offset(0x0366, "UW", "GroundCheck") event.offset(0x0BE8, "UD", "GearCheck") event.offset(0x0BDC, "UD", "FlapsCheck") John

I think you want offset 0366, not 0336. Try with event.offset(0x0366, "UW", "trafficoff") John *update* You are also missing an end statement for the if: function trafficoff(offset, value) if value == 0 then ipc.control(1009) ipc.log("AI traffic turned off") end end event.offset(0x0366, "UW", "trafficoff")