Pete Dowson

Yes, and then ...? I think it allows you to assign different keystroke combinations, doesn't it? I'm glad you found some references. Have you followed them up to see how to use HidMacros? Regards Pete

Possibly, then, it uses local panel variables ("L:Vars") which can be written to via macros and read and written by Lua plug-ins. there are plenty of examples of using these in the User Contributions subforum. Maybe. I think it is capable of using mouse macros and L:Vars as needed. Check with the authors on that. There's a pinned thread on LINDA at the top of this Forum. Regards Pete

The FS Zulu date and time are already included in those NMEA signals which provide for that. RMC has both time and date GLL has time and GGA has time Pete

Since FSUIPC has no way of distinguishing them as different types of input, the differences you observe must be entirely in the province of Saitek's hardware or its drivers. Have you tried their support, or even posting in their Forum where I'm sure there must be many other users? If nothing else works and Saitek cannot fix it I can only suggest that moving the throttles back and forth is part of your FS startup checklist. Regards Pete

I don't know HidMacros that well, but you already stated, did you not, that it could allow you to program different actions from different keyboards? Isn't that the point? FSUIPC will accept many different keyboard input combinations so I'm sure you can find enough for many keyboards. I do not use HidMacros so I really cannot tell you how to use it. Sorry. Is there documentation with it? I did experiment with it once a long time ago, but not enough to remember and I cannot locate its details at present. Regards Pete

Yes. Also see the thread entitled "About bits, numbers and hexadecimal ." in the FAQ subforum. The later one. The only differences are in the new commands like NW_GLOBAL and the field for dynamic change rate, I think. Pete

The syntax looks okay. I can try it here if you paste in your Lua program, or at least the smallest part which demonstrates your problem. Did you not find the boxed section in the Axis Assignments section of the FSUIPC user guide? Search on "tiller" and you'll find it directly. Pete

Copy your FSUIPC INI from FSUIPC3 into the Modules folder for FSX, delete the FSUIPC4.INI and rename the FSUIPC.INI to FSUIPC4.INI. However, it would be a good idea, if you've not already done it, to first change FSUIPC's joystick numbering to its "joy letters", where you have letters assigned to the joysticksd instead of using the base number IDs from the Windows registry. If you do that then FSUIPC can still track the devices even if they look to be connected differently. If you've assigned joystick axes in FSUIPC, the only additional likely thing to go wrong is that some axes may be differently named -- X Y Z will be okay, but sometimes R U or V will get reassigned. This is a result ogf FSUIPC3 using the original Windows "joy" interface and FSUIPC4 using DirectInput. You'll need to be aware of that (check by waggling all the axes) and then edit the appropriate lines in the [Axes] section(s) of the INI file. Regards Pete

I've never known FSX / SimConnect to "choke" with too much AI data using FSUIPC, and I've got lots of traffic (MyTrafficX plus UT2). FSUIPC4 does it's best to regulate the updates in any case, and being internal to FSX it has no process-crossing delays or overheads. Regards Pete

Try the current version, 4.742 or 4.743, as I'm pretty sure that's fixed already, some time ago. See Download Links subforum. Pete

I'm surprised they work at all the other settings. PMDG's flap positions are different from the default (and everyone else too, I think). You'd need to calibrate specifically for the aircraft. Regards Pete

i think this was discovered and fixed some months ago. Please check with the latest update -- see the Download Links subforum. Pete

That would be pretty complicated. Best to have one Lua for each. The name "ipcReady.lua" is special in that it is automatically loaded and run by FSUIPC as soon as FS is ready to fly. That won't occur with "ipcReady1.lua". To run several Lua plug-ins automatically there are two ways. But first name the Lua files something other than "ipcReady.lua" -- eg BU0836_1.lua, BU083621.lua, and BU0836_3.lua in your case, or something more descriptive if they have specific roles. The first way is to create and ipcReady.lua which has the sole job of running other Luas, thus: RunLua("BU0836_1") RunLua("BU0836_2") RunLua("BU0836_3") The second way it to edit the FSUIPC INI file and add a new section: [Auto] 1=Lua BU0836_1 2=Lua BU0836_2 3=Lua BU0836_3 If you use the latter method don't forget to remove the ipcReady.lua file you are currently using. Regards Pete

No, not for the GPS controls. Most FS controls are via events which you can fire via buttons or keypresses. If you must use FSUIPC offsets you can sent control events via offset 3110. Regards Pete

Yes if the Simkits driver is an EXE file which interfaces to FS via FSUIPC, because WideFS simply reproduces that interface on the networked PC. The SimKits driver won't notice the difference. Regards Pete

It does in earlier versions of FS -- in FSX there's no way to specify cloud thickness. Instead it is worked out by some algorithm internally according to cloud type and base altitude. Very annoying, as you can't read the cloud thickness either, so you cannot really determine programmatically whether you are in cloud or not! That's something you would have needed to ask the Microsoft FS team. I assume that when they originally set the type numbers they were going to implement a whole lot more. Thanks. But how are you measuring the results? If you are using the values returned by FSUIPC, they are arbitrary guesses. The only way to measure if slew up through the layers and check the alititudes. Pete

What else do you need to know? I'm assuming HidMacros can send keypress combinations, which you can assign in FSUIPC, as you already said. What are you missing? Regards Pete

There's a much later one, 4.743, now available -- see the Download Links subforum. The usual cause of that is the controls "going to sleep" because Windows turns the power off to save it. You need to go into the Device Manager, find all of the USB hubs listed there, right click, select properties, power management, and turn it off. I've never heard of a problem which stops the FS-assigned keypresses working. Are you sure they are still assigned? Certainly you can log Events (for the key controls) and Axis events (for the joystick controls) to verify they are being sent. If they are and the aircraft still doesn't respond then there's something amiss with the aircraft code. Regards Pete

There's no change in the registration. You MUST use the same email address and name as originally. Either you are making a mistake somewhere, or it is part of the problems caused by recent changes in Windows security checking. For the latter please try the update from Download Links subforum, as that particular problem was fixed a few months ago. Regards Pete

Yes -- almost all offsets can be written to, but that doesn't mean they'll do anything. Exactly. "No" is correct then, isn't it? Pete

Is this really anything to do with FSUIPC? You can assign those in FS itself, FSUIPC is only using the same controls. Test with default aircraft. Regards Pete

Check the download links subforum. It's due to a change in how windows applies security checking, and was fixed by an update earlier this year. Pete

Depends when you go to your SimMarket account and retrieve it. It probably takes forever unless you go get it! ;-0 Pete

I don't know. I'll take a look when I get time -- maybe next week. i have a lot of catching up to do after my holiday and I'm away this weekend too. I don't think it is "most" any more. It was about 50:50 a while ago, but with the new cheaper faster Intel processors a lot more are moving to FSX now. My cockpit runs beautifully with FSX. Regards Pete

Sorry, I'm not with you. Lua events on offsets trigger when the offset changes. That's the whole point. If you want different actions on the values, check it -- it is supplied to the event function. Pete