Pete Dowson

There seems to something of ASN loading. Take a look at your DLL.XML file,, or show it to me please. Pete

check the LuaFiles section in the FSUIPC INI file. if there are more than 127 there you will nee to delete some in the list, ones you no longer use. also be aware that there's a maximum length on the name -- 12 or 15 characters i think. Pete

Offset 2138 is a direct copy of the SimConnect-supplied value TURB ENG ITT:2. As documented both in SmConnect and in the FSUIPC offsets list it is in degrees Rankine. If you want to display is in Celsius or Fahrenheit you need to convert it. 817 R = 212 C = 357 F. Not sure how the gauge arrives at 715. What units is that in? To check the actual exact figure provided by SimConnect, use the Monitor facility on the right side of FSUIPC's Logging tab. It will log the received Simconnect values as well as the offset. Pete

Not that I'm aware of, but I don't deal with sales at all, only development and support, so you might want to direct your query to SimMarket. You probably have to open an account and raise it as a ticket. Sorry, I don't know it at all. I can help with specific questions about FSUIPC facilities, though. Maybe there's some more help for that device in User Contributions subforum? Otherwise maybe there' a Thrustmaster forum? Pete

Just edit the macro file. It is in plain text! you can edit it as you like!

As with any Lua plug-in, it only does anything if it is loaded. Just putting it into the Modules folder doesn't make it run. Please see the Lua documentation, in your FSUIPC documents folder. Pete

Of course you can update. In fact you MUST if you want support -- I can't support old versions! You can get the latest version from the Download Modules subforum here, or over in the usual www.schiratti.com/dowson place. The places you can get FSUIPC from have not changed for many many years! Installation of updates changes no settings whatsoever. From the crashes you are getting I doubt whether it is FSX itslef, more likely add-on scenery, or even more likely some Windows driver. Pete

Such information isn't supplied by FS for the user aircraft, only for AI You'd need to read the Lat/Lon and look up the airfield in a database. Pete

Now the crash is in the Windows Kernel Base! Certainly FSUIPC cannot have anything to do with that. I think you might have a bad driver there, somewhere. Sorry I cannot help. Why not try the crash forum over on AVSIM? I think you need to go through a thorough process of elimination till you find the problem. Pete

Just delete the macro file from the Modules folder. The keys assigned to them will then not work. You want three different buttons all to do the same thing? That makes no sense to me -- a waste of buttons -- but there's nothing stopping you assigning as many buttons or keys to the same action, whether it be macro, control or keypress. Just back up the files in the FS Modules folder. They are all there. You should always backup your INI, KEY, MCRO and LUA files. They contain the entire settings for FSUIPC. Oh, plus the "Profiles" folder if you have opted for seaprate Profile files. One Profile can be used for any number of aircraft. Or you can simply assign to the macros. They don't disappear from the list just because you've used them once! The dropdown assignments list will contain all your Macros and Lua plug-ins no matter what you've used them for before -- provided those files are still in the Modules folder. Pete

They are not implemented in FS. FSUIPC is an interface to FS,. For add-on aircraft you may find additional ways you can operate such things, maybe via additional custom controls or by using mouse macros or L:Vars (local panel variables). Pete

Okay. 4.937b is now available, Download Links subforum. Pete

The MIXTURE LEAN and MIXTURE RICH controls are the only controls for operating the cutoff/idle levers. They most certainly do NOT operate any trims unless you have a very corrupt FS installation! The FS keyboard short cut is Ctrl+Shift+F1 for cutoff and Ctrl+Shift+F4 for idle. On props they move the mixture lever to full lean or full rich. On jets they operate the fuel valve levers. There are separate controls also for each engine -- Mixture1 lean/rich, Mixture2 lean/rich and so on. I suspect you are making mistakes in your assignments. Pete

The earliest supported version of FSUIPC is 4.937. Your crash is in NTDLL which could be due to any sort of corruption. Mostly in the past I have found them due to either corrupt scenery files or corrupt aircraft gauges or bits maps. It isn't FSUIPC. I can only suggest you try a process of elimination until you find the issue. Pete

Two things: 1. Normally the start/cutoff action is simply operated by the FS controls "Mixture Rich" and "Mixture Lean". Why use mouse macros? 2. Version 4.91 of FSUIPC is very old and unsupported. Current is 4.937. Pete

Ah, ouch! If you are sending an ordinary 32 bit value to 0892 you are also writing to 0894. Writing 0 to 0894 (the combustion flag) turns combustion off! So yes, you must only write two bytes, or a short. The lengths defined in the list always need to be respected. Pete

The built-in controls for EFIS in FSUIPC only apply to the default FS 737 and Airbus. These are actually "hacked" in FS code, because almost all the EFIS functions on all aircraft are local to the specific aircraft gauge, they are not assignable FS controls. And they certainly will NOT be the same for either the PMDG 737NGX or the iFly. PMDG have supplied a full range of specific custom controls which can be assigned. You need to refer to their SDK header file for the list. For IFly737 I believe someone made a program, iFly2FSUIPC or similar to map offsets onto iFly functions, but I'm not sure about this. You'll need to consult the respective forums for any add-on aircraft. The process is not necessarily all via offsets. Many things use controls and simple assignments. And it will be completely different from aircraft to aircraft. building a cockpit is a long and complex process, and one that is generally never quite finished! You might want to consider going for one of the ready-made cockpit solutions. iFly Cockpit Edition is one, but there 's also Project Magenta, ProSim737 and SimAvioics to consider. For the standard ones, of course. Have you not looked in your FSUIPC Documents folder? For add-ons they are responsible for their own offset assignments and documentation. The SDK is for writing programs to interface to fSUIPC (SDK = Software Development Kit). I advise you to learn programming first,. Sorry, I can't comment on the Aerosystem software. I've used Project Magenta up to now, which isn't limited to one aircraft type -- but you can't use it with either PMDG 737NGX or iFly737. In fact you can't use any other control software with those two. I'm currently toying with ProSim737, which is limited to 737NG only, but that's what my cockpit is in any case. If you are 737NG specific it is worth a look. Again, not cheap though. Pete

Yes, of course it is all possible. The axes should be pretty easy. Using an axis for Gear is one of the examples on Ranges shown in the user guide. For switch assignment to PMDG 737NGX functions you'd need to assign to their custom controls, as listed in their SDK's Header file. I don't use PMDG aircraft and cannot help more directly, but the information is all there, and there is lots of stuff around -- check the User Contributions subforum here, for a start. Pete

Can't you make the rotary look like a pair of buttons instead, like most all rotaries -- i.e. they pulse one button turned one way and another turned the other. Then it's just a matter of assignments to INC/DEC controls. I use Leo Bodnar boards which allow this, along with analogue inputs and lots of plain buttons. I think they are cheaper than Arduino too. Regards Pete

OK. It looks like a problem interfacing to ASN. Could it be that you have an out of date install of ASN? Pete

Yes -- as the Log shows: Running inside Prepar3D v2 ... Prepar3D has been renamed as "fsx" It also shows you are using an older unsupported version of FSUIPC. The current version is 4.937. Pete

Not at present, but it is easy to add. I'll provide "OOMcheck=Quiet" for this. It'll be in 4.937b, some time this week. Up to my eyes in other stuff at present. Pete

One thought. I'm not terribly familiar with these aircraft, but with an ordinary prop the Starter position is #4 and when you release it it returns to one or other of the Magneto positions. If it returns to Off then the engines lose ignition and will cut. With jets the ignition is a separate switch but normally on. How does the King Air work in this respect? Pete

Something is missing, then. Have you turned the fuel on? All FSUIPC does with the offset is send the same control to FS as you would effecitvely be doing wiith mouse or keyboard. It has no idea what it is for or what it does. Try using logging to see what you have different in the two cases. The "General Engine" starter at 3B00 is not exactly the same. In fact I've no real idea what it does in comparison to 0892. Pete

You can program almost anything if you really wish to. It isn't easy, and the first job would be to work out how you distinguish between two mice -- mostly Windows treats them all the same, just like multiple keyboards. You'd need to delve into DirectInput and HID device interfaces to distinguish between them, but how you stop Windows and FS treating them the same is a bigger problem, needing some sort of low level privileged driver interception I should think. Pete