Pete Dowson

Yes. Please check the "SendKey" facility out, documented in the WideFS documentation included in the package. Pete

The very first control in the assignments drop down list, in FS controls, is <custom controls>. Have you not looked. After you select that you can enter the custom control number (which you have to wok out from the PMDG DDK document I told you about), and, if needed, a parameter to go with it. Their control list (controls are also called "EVENTS") will probably be different for each of the three aircraft, so you probably need to assign them in profiles, one for each aircraft type. Who mentioned anything about Lua in this context? Pete

I refer you to page 36 of the FSUIPC4 User Guide, where it clearly says: "These “mouse macros” do not actually use the mouse at all, but use a set of “mousetraps” to identify how your own mouse use calls routines in the panel coding, and then attempts to replicate it." Now, since they do not use the mouse at all, why would it matter where it was? The whole point of them is to do the same thing as what you can do with the mouse, but even without the relevant switch being displayed, or off-screen in a virtual cockpit. For more information I suggest you read the User Guide, at least. There's also more details in the Advanced User's Guide. You should also note that mouse macros aren't usable on most modern add-on aircraft. Even the PMDG aircraft will not support them on all switches and knobs. But in the case of the three aircraft you mention, pretty much ALL of them are definitely accessible using the PMDG <custom control> numbers which can be worked out from their published SDK -- in the .h file in the aircraft's SDK subfolder. Pete

Exactly as you already said on Sunday -- see your message above, Sunday at 04:02pm. Pete

No. Memory is nothing to do with it. Why would you even suggest such? where does 'memory' come in? Without knowing what "ipcinit.lua" is doing I cannot help at all. I don't know why it is so secret! Nor do I understand why it needs to run before much else is ready in FS -- most everything should be started at ipcReady or later. When ipcInit is executed FS isn't ready at all. All it is suitable for is initialising some FS offsets. Pete

Ah, you mean the DLL.XML file, not FSUIPC4.DLL which is a DLL file!!! All you proved is that something is wrong with that DLL.XML file, or it is loading something bad! Just start with the one made fresh by FSUIPC, and add the items you need one by one and test each time. Do NOT include Vistamare! You've also proved you do NOT have a problem with FSUIPC, but with something else you've added. Pete

Well, you did something wrong because the file was not only written BUT THERE WAS ONE BEFORE -- even though you say you deleted it!!! See: Found Prepar3D.CFG in "C:\Users\riis1\AppData\Roaming\Lockheed Martin\Prepar3D v3\Prepar3D.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. (for FSUIPC4, without Loader) ... FSUIPC4 section of DLL.XML written okay The full folder name is C:\Users\riis1\AppData\Roaming\Lockheed Martin\Prepar3D v3\ Okay. FSUIPC4.DLL, FSUIPC4.INI and FSUIPC4.LOG, and the FSUIPC Documents subfolder, are all absolutely guaranteed to be there, if it appears in game. So now I'm sure you are not looking correctly. This confirms you are really in a mess when it comes to dealing with files and folders: Exactly HOW did you do this "switching"? Pete

Ah, that's different. So the installer is not making one? Either you forgot to rerun the FSUIPC Installer as I told you, or you are looking in the wrong folder. Look at the FSUIPC install log. Pete

Okay. In that case it seems that SimConnect is not loading it. Please look in the FAQ subforum for a thread which tells you how to make a SimConnect log file. Do what that says, then try again, and show me the SimConnect log it produces. Pete

Why haven't you deleted the Vistamare entry? Try deleting or renaming the DLL.XML file completely, then re-running the FSUIPC installer. Pete

I don't have FSX as such any more, only FSX-SE. However, the control list didn't change from how it was in FSX ACC versions. Your controls DLL is SP2 I think. You didn't answer me about how you determined the drop down doesn't go further than 66860 when it isn't ordered by number. Didn't you just look in the B's? There's no later version for FSX other than that installed for Acceleration., which would be build 61637. I think there must have been new controls added in Acceleration to support the new aircraft and their cockpits. But my only version of FSX for a long time had been Acceleration. When I made the controls list that was all I could go on, so I'm sorry if it doesn't differentiate between FSX RTM, SP1, SP2 and Acc. The base control list I started with was the old one, dating to just after Acceleration. I'll add a warning about that. You can't just change one module in FSX. To get the later version you'd need to update to Acceleration, or change to FSX-SE. If there's a control missing in CONTROLS.DLL it means it doean't exist, isn't supported, isn't implemented. This is why FSUIPC doesn't have a fixed list but one generated for the version of FS you are using. Pete

Vistamare crashes here with P3D. Why haven't you deleted that? Migration tools are a menace. Why are you using one? Pete

4.961 is out of date and unsupported, and the list of controls currently spplied was updated some time before, last year I think. It includes the new ones for P3D versions 3 and 4. The drop down in FSUIPC isn't in numerical order, but alphabetic, so how do you work that out? The drop down list is obtained directly from the CONTROLS.DLL installed as part of FS. Is your FSX out of date too? Pete

If you have all aircraft in profiles, just use the appropriate [Auto.profile] sections to say whether to load it or not. Otherwise, add an aircraft identity check at the start of the Lua plug in, restoring instead of changing the values if the aircraft name matches one you don't want it applied to. An event triggered by changing aircraft name would ensure it knows. Pete

That should be taken care of by selecting only parked aircraft without clearance or in closing down stages. I do that already. Currently I don't know the gate nmuber. I'm not sure if Parking ad Gates are always clearly differentiated. It spoils the point moving the ACTION to a client PC, because it can't act immediately so it wouldn't be so smooth an immediately effective. It would be the same as the external limiter already available. Better to accomplish what you want, surely, by having offsets with the parameters which can be changed by program or Lua scripts run from anywhere. Pete

I've never really noticed any worrying measurable hit on VAS from AI. I suppose it depends on the quality of your AI model graphics. I use MyTraffic mainly, plus UT2 (to give me more traffic on Airways). I think WOAI models are heavier, from what I've read. It may be that arriving at EGLL with other large airports not far away (Gatwick, for instance), they limit of 100 is just too low. By all means experiment. I've implemented the Frame Rate target mechanism I mentioned above, and that seems to work well for me. It'll be in 4.963 to be released within a day or two. Pete

Thank you for the donation! Very kind of you. I don't have a website. When I first started with FSUIPC3, before it went "payware", donations were sought, but they weren't enough to justify continued development. I tend to feel asking folks to pay for the user facilities is enough. If I ever make a new version then there will br a new registration charge. Thanks for the idea though. Maybe I should ask Enrico Schiratti (owner of the so-called "Dowson Page") to add one. Pete

It doesn't count them. It uses a bit mask, as in fact in the quote you included Please read that. It tells you how to make the mask either way you like to count them! Pete

Well, yes -- COATL is crashing by the look of it. You need to go get the latest DreamTeam / Virtuali Add-On Manager. It will install updates for both COUATL and BGLMANX. Neither of the crashes into Windows are related to FSUIPC. And the DLL.XML looks like it came from FSX, not P3D -- Vistamare.DLL is certainly not compatible with P3D, for example. That's the DLL supporting Aerosoft's AES which isn't P3D compatible (nor FSX-SE in fact). It isn't an FSUIPC problem in any case.

Okay. So either the DLL.XML file is corrupted -- the one in C:\Users\riis1\AppData\Roaming\Lockheed Martin\Prepar3D v3\ or it is crashing on load. Show me the DLL.XML file, and see if there is an FSUIPC4.LOG file produced in the Modules folder -- if so, post it here. And check in Windows Event Viewer for an Application Log error showing a crash in Prepar3D.exe. If so, grab the details and post here. You might also try replacing the DLL with the latest interim update available in the Download Links subforum. Version 4.963 is due to be released tomorrow, and the day after. Keep an eye out for that in the Download Links subforum. Pete

Maybe it does have a mode which emulates a proper joystick device, and the mode has been changed. I really do think you need to find the support place for the device itself. Pete

I use UT2 AND MT6! ;-) Pete

Did you actually install FSUIPC? Did the install succeed okay? Where's the Install log? What version of P3D? What version of FSUIPC? It really is a waste of time posting questions like this with zero information! Pete

FSUIPC won't be touching the battery if that option is disabled. Are you sure the APU isn't running? See if the fuel is being used, gradually. Pete

The only possibly relevant Lua plug-in example available from my installs (in your FSUIPC Documents folder) is the "HidDemo.lua". But that's really for joystick types which have more facilities than the standard joystick interface supports. For non-conforming devices you need to be a good detective. In the past I've used USB monitors to examine the data flow from and to the device whilst using it in its normal way. Then it has to be programmed without many aids available to a standard joystick. Use the HidScanner utility, downloadable from the Download Links subforum, to see what sort of problem you miht be facing, without help from the makers. I'm afraid that if you aren't an experienced programmer or hardware engineer it's going to be quite a task. I supsect there are much more productive routes to get the sort of control you want. Pete