Pete Dowson

What do you use it for? It's never come up in the 12 years of FSUIPC -- seems a little odd to see it requested now. Regards Pete

What version of FSUIPC, FSX? What method of assignment -- FS or FSUIPC? I can't help without information. Sorry. Pete

The cause could be bad hardware, bad USB ports, conflicting assignments in FS, bad or no calibration. Is this compatible with FSUIPC assignment? I'm sorry, but I don't know what CH Control Manager does. Maybe it does FS assignments too? All the rest of your details make no sense to me at a software level, I'm afraid. There is no way FSUIPC can get different inputs mixed up, it is using the same DirectInput interface as FS. And the code is identical for all axes, not specifically different for a small fixed selection. The fact that it is so specific in your case does point strongly to a hardware problem. Maybe, if you are still using that CH software is it possible that it is interfering with DirectInput? Otherwise, since it only affects a specific selected part of your hardware, my guess is that it is hardware. You say "CH FlightSim Yoke USB – three years old". Did you just purchase it second-hand, then, or was it working once in your possession? What were you using before this? The fact that it varies so much might point to a hardware fault which is timing related -- polling the device less often might help. FSUIPC4 polls axes 100 times per second by default. Try "PollInterval=100" in the main [Axes] section of the INI. That'll slow it to 10 times per second, closer to FSX's rate. If that helps, it's definitely hardware related, or a badly corrupted USB software driver. If you want me to check anything further I need to see the FSUIPC4.INI file please. And can you tell me why you are using FSUIPC axis assignment? Pete

You have a Network Issue? See above replies please. If you have a different question, please post in new thread with an appropriate title, and also please tell me what you are talking about. What you've said so far makes no sense. Pete

If you add that you must also add the Protocol parameter. You need add nothing at all if the two PCs are in the same workgroup. That's much easier usually than messing about with names or IP addresses. WideFS doesn't need any folder sharing, it doesn't read or write files except the Logs and INI files in its own folder. However, you either have to disable the default firewall on both or allow WideClient and FS access on both. It uses ports 8002 and 9002 by default. Regards Pete

It doesn't alter any order as such, it simply doesn't record the order. It has no way or recording the order and never has had. The format of the parameters allows one bit for each shift key, as documented in the Advanced User's guide. That's never changed. Regards Pete

If in normal flight mode there's no Modules entry in the menu, or there is one but it does not contain an entry for FSUIPC, then FSUIPC.DLL is not in the FS Modules folder. There's no "freeware versus payware" difference in the installation nor in the DLL. Registration merely unlocks the user facilities. There's no message relating to versions during Registration. The installer checks the version to make sure it doesn't overwrite a later one. But that's entirely separate from Registration, which is the (optional) last action at the end of the installation. There's nothing worth uninstalling. you can run the Installer again, that does no harm, but the only thing you can uninstall is deleting the DLL from the modules folder which is pointless if you are going to replace it. Replacement doesn't worry about one being there. The installer will only refuse to overwrite a later one with an earlier one. If you think you aren't getting it installed properly, please show me the Installer log, which is a text file in the FS Modules folder. You can paste it into a message here. Regards Pete

The format is actually described in the Advanced User's Guide, at the end of the list of all the added FSUIPC controls, but it would be much easier for you to assign in the way I described, using the FSUIPC options dialogue -- maybe to another button, then just change the button number in the INI. Regards Pete

Nice page. One small comment. For simplification, where you have this: If you are not using SerialFP2 and VSPE you can just omit the second COM port, so: [VRInsight] 1=COM4 2=COM5 This will save FSUIPC trying to open the virtual ports for you, and, worse, maybe succeeding because they happen to be real, and then wasting time trying to read them continually. Regards Pete

Double assignments need more than one line. One button can do lots of things, but you either have to have one assignment to a macro, then do all the things in a macro, or have multiple assignments in the INI file. Which you choose is up to you, it does not matter. That will execute lines 121 and 241 when the button is pressed, and 122 and 242 when released. What do you mean by "the toggle 66241 must be inversed..."? Toggle controls toggle -- i.e. invert the current condition. You can't invert an inversion -- or rather, you can by doing nothing. Just delete the second assignment to the control. Then it won't do anything. If you want more specific control over the Battery switch you need to access the FSUIPC battery switch offset instead. Assign to the "Offset Byte Set" control with offset x3102 and parameter 1 to turn it on, 0 to turn it off. Regards Pete

Look at what you have: First: if ((Throttle1 < 330) and (Throttle1 < -500)) then if the value is less than -500 it must be less than 330, so you can simplify that to if (Throttle1 < -500) then and all of your places like this: Throttle1Out = 0 Throttle2Out = 0 ipc.writeSW(0x088C, Throttle1Out) ipc.writeSW(0x0924, Throttle2Out) would be more efficient as: ipc.writeSW(0x088C, 0) ipc.writeSW(0x0924, 0) The next condition: if ((Throttle1 > 330) and (Throttle1 < 5800)) then leaves the gap between -500 and 330, but whwen it operates it sets 4000, which is then changed on the next loop by: if ((Throttle1 > 3500) and (Throttle1 < 5800)) then into 8000, which is then changed by the next one: if ((Throttle1 > 5800) and (Throttle1 < 8600)) then into 12000 and finally by if (Throttle1 > 8600) then into 16300. Thus you can only ever get -500 to 330, or 16300 resulting. To find bugs in code, work through it yourself as if you were the computer, making the changes. You will quickly see that in as few as 4 or 5 loops (200-250 mSecs) your values are restricted to those! Pete

I'll put it on my list to look at in my next 'idle' moment. No promises. Regards Pete

No. It isn't a recorder. It just sets a bit for each shift key, with bit definitions as defined in the Advanced User's manual. It would need a different shift state for each different order of Alt, Ctrl, Shift, Tab, Win and Apps key combos. That's a lot! Pete

Hmmm. Sounds okay. So what's the real problem? So can the programming languages you must use not call anything outside their own world, like Windows APIs, or similar things in a Library? How would they communicate with any other part of the PC without? FSUIPC's Lua facilities are well documented. Why not just download the documentation packages provided -- Lua and the SDK? And sorry, but i don't understand much if any of that reference. Regards Pete

But isn't Flash for playing video files? How does that relate to anything in FS or FSUIPC? I'm obviously missing the point somewhere. Is Ajax another language? I only know it as a disinfectant or cleaner. ;-) If you can write programs in Ajax/Java which can use regular windows APIs, then you can write an interface to FSUIPC. But I can't tell you. All the information you need to write applications to interface to FSUIPC is provided in the FSUIPC SDK. PHP being yet another language? Regards Pete

FSUIPC is the same whether free or paid for. Buying a registration merely unlocks all the User facilities, as documented in the user guide. Version 4.57 is out of date and unsupported. You need to download 4.60 at least. you should always install the latest because old ones are not supported. additionally, version 4.57 probably won't accept a new registration. Just run the installer, follow the instructions in the Installation guide. Regards Pete

Can you perhaps explain what your post is all about? I don't know "Adobe Air" and I've no idea what your link is for. Regards Pete

Don't they toggle anyway? You can only have one on at a time in any case. To make an ordinary push-button into a toggle switch you need to use the switches flag (in FSUIPC) to "latch" it, so it does one thing on one press and the other thing on the next press. You can only do that by editing the entries inthe FSUIPC INI file. Please refer to the section in the Advanced Users guide entitled COMPOUND BUTTON CONDITIONS. Take note of the statement that each button has a flag which changes from "true" to "false" or vice versa on each button press, so the button's own flag can be used as the condition for it to choose one action or the other. Two lines in the INI file. Have a read and come back if you have more questions, Regards Pete

I like the GoFlight stuff, but you need a way of mounting them. They do bays for 2, 6, and "many" units (the latter being the floor standing central console). The VRInsight stuff gives you a lot for your money and are good with default aircraft but can be a bit awkward for beginners to deal with some of the more complex ones. I do support both of these ranges with facilities in FSUIPC (GoFlight) and Lua plug-ins (VRI), Regards Pete

Okay. I'll look at doing this. Next week though. I have guests here still. Yes, that all makes sense. Regards Pete

But presumably it was you who placed those two files there? If WideServer runs at all it must create a log file. So, has it been used yet? Regards Pete

But in your earlier message you said "I wanted to attach the FSUIPC Log file" ... ? If there's no FSUIPC4.LOG file being created, then I don't think FSUIPC4 is ever running. Sorry, the Install log is fine. No hint of any problem there. Pete

Yes, i see that. The Lua flags are one way, but limited and not global like buttons. How about an added FS assignable control to simple create an "event", simply a numbered event (the number in the parameter, which can be handled in Lua by an ipc.test function and a new event. function? Then you simply design your Lua with button independence, defining event numbers which can be assigned? The problem then, of course, is that two persons might design Lua plugins to do worthwhile things which use overlapping event numbers. Really, the Lua specific Flags (32 of them) were intended to fulfill this function. Is perhaps ythe limit of 32 a problem? I could probably extend that easily enough. 64, 128, 256? Regards Pete

That DLL.XML file is doing nothing more or less than the one FSUIPC would have installed and which you deleted. Yet you say one loads okay and the other doesn't? Makes no sense to me -- same thing, different result? If i were you i'd delete that DLL.XML file and just re-install FSUIPC again. That worked for you. Did you not find the FSUIPC log file this time? Regards Pete

Windows 7 makes no difference. I run FS on three win7 systems and have never seen any difference which would account for this. If it writes it there it should read it there. I assume the Macro files and Lua plug-ins would also have to go there. But I don't understand, yet, how it gets there. It makes no sense to me. I'd need to work out a way of finding out. No. Where does the WideServer log file go to? Same place? No WideServer log in either? And the Key file in both places? I'm going to have to delay on this one for a few days -- guests here all this week and I'm not doing any development work. It's going to need additional logging to work out. Please remind me next Monday. Okay? Regards Pete