Pete Dowson

You should not have to do anything at all. It is all automatic between FS Commander and the FSUIPC4, module, once the latter is correctly installed. You certainly do NOT have to pay for FSUIPC to be able to usde its interface for applications. You really should have read the documentation for FS Commander first! It uses FSUIPC as an interface only, it is completely invisible to you. You do not need to do anything but install FSUIPC4 and install FS Commander, and follow the instructions for FSCommander in its own documentation. I'm sorry you wasted your money on FSUIPC. You did not need to. And, incidentally, I assume you used a different email address when purchasing it, as "pj.hack@btinternet.com" is not listed as a registered user as far as I can tell? What could be clearer? You run the FSUIPC installer. It installs into FSX. That's it! There's nothing else for you to understand! There's no "linking up" or "initialising" for you to do, and most certainly absolutely nothing whatsoever for you to do in FSUIPC. You need to follow whatever instructions you get for FS Commander! There are none for connection to FSUIPC because you don't do anything. It isn't up to you to do anything at all! Once FSUIPC is installed the interface it provides is already automatically asvailable to programs like FSCommander. You sent one public message here which I replied to privately asking you to repost without publishing your private details. I then had to DELETE your first message because you included your private registration details, which makes them open to use by pirates! I shall probably have to disable your registration key in any case if it looks like it is being used illegally. You don't need one in any case for FSCommander. I think you do seriously need to read the documentation which comes with FSCommander, not FSUIPC. If you don't understand it, please ask FSCommander support. I cannot undertake to support other folks' programs, especially ones I haven't even got! Regards Pete Dowson

LuaSocket? I don't think that is part of any of the Lua libraries I've included in the FSUIPC implementation. Are you somehow adding it via external access? "Require" tries to load a module, right? I've not done any testing with external Lua modules. What do they look like? What isd this 2sockets" module -- a DLL or what? Sorry, this is any area as yet unexplored in my FSUIPC implementation. Maybe it is something I can improve. Have you managed to get any external Lua modules loaded at all? Regards Pete

There won't be anything like that without adding logging parameters, but that is not the point. I would be able to confirm that WideFS and FSUIPC were all okay and that it was a problem with vasFMC -- or not, as the case may be. Include the FSUIPC log as well please. Pete

But why not look at the WideServer and WideClient log files, as I already suggested? Or let me see them -- they won't be long, you can paste them into a message here. Whilst you are at it post your FSUIPC log file too. I can help, but not without information. I did ask you to look in these files before. Both FSUIPC and WideFS always post details of what they are doing, including whether there's anything wrong, in the Log files. That is why I suggested looking there rather than going around in these circles. Regards Pete

Okay. A bit messy but a workable compromise I suppose. Good flying! Regards Pete

If both Server and Client say they are connected, then they are connected. Are there any problems reported in the WideServer.log or WideClient.log files? Those are the places to look if you suspect anything wrong. If this VasFMC program says "NO FLTSIM CONNECT" you really need to find out from their support exactly what that program is checking before it gives such an error. Maybe it is not related so much to the connection but to things like version numbers. There's no configuring to do in WideFS normally, and most certainly not if your are getting a connection. Well, that's the opposite of what most folks complain of, that I write too much documentation so they can't be bothered to read it all! Did you actually look inside the WideFS ZIP file for the WideFS User Guide, the WideFS Technical, and the WideFS History documents? If you've not actually bothered to look in the downloadable ZIP for WideFS then naturally you won't find the documentation! Pete

FSUIPC doesn't do anything unless you or an application program has asked it to. It most certainly doesn't touch either autopilot or trim. It sounds like you've made some settings or changes which you've now forgotten about, or you are using an add-on which is influencing those things through FSUIPC's facilities. If you don't know what you've done with FSUIPC's facilities, first try removing your FSUIPC4.INI file before starting FSX -- save it somewhere separately. That will render all of its actions to default -- i.e. nothing. If that doesn't fix it, you need to start eliminating add-ons using FSUIPC one by one. You could also try to find out exactly what is happening by using FSUIPC4's logging facilities. Enable the event logging to start with, to see what controls are being sent. Regards Pete

Version 3.81 is not available, is not supported, and will not cure the problem. I suspect you have a different problem altogether. First, tell me, did you purchase a registration for fSUIPC? If so, see if the MD11 works with the FSUIPC.KEY file temporarily removed from the FS Modules folder, to effectively render FSUIPC unregistered. Either way, registered or not, it would help me diagnose your problem if you would please show me the FSUIPC.LOG file, which you will also find in the FS Modules folder. You can paste it into a message here. Do not post your registration details, though. Regards Pete

Ah, so the 2D gauges are written using standard methods. Have you any reason to keep the 3D cockpit (I assume that's the virtual cockpit view you mean?). Obviously if you use something like TrackIR you need that, but if you are using hardware for most of the controls I would have thought an undocked set of 2D panels was better? I don't know if Key2Mouse would be very useful on a Virtual Cockpit, unless it is kept static in position, which seems to spoil the point. Regards Pete

Okay. Version 4.09 was certainly very old -- not even the version built for the FSX update SP1 (4.10) -- but there still should have been information in the ATC details, just not the Model if that was not selected. Good. However, your report has shown me a small error in FSUIPC4 which I shall have to correct, so thanks for that. In FSUIPC3 the ATC selection (like "Model") did affect both ground and airborne traffic. In FSUIPC4 it currently only affects airborne traffic, which is evidently wrong. I will fix this in the next update. Regards Pete

The only time FS actively assigns anything itself is when it sees a new joystick device attached. It sounds like your joystick is not starting connected and appears newly-connected each time. I do not know of any way any programme can do this. It is more likely to be a hardware problem. If you are not assigning anything through FS, only via FSUIPC, then disable the joystick altogether in FS -- you then do not have to un-assign anything. Pete

Sir, you posted your private key for FSUIPC in a public forum! I've deleted it now, but I may have to disable it if we find other people using it illegally. NEVER post private unlock data openly! If I have to disable it you will need to buy another, or appeal for sympathy to SimMarket. Pete Dowson

Sorry, that confuses me. On the one hand the "green programming window" appears, and on the other it doesn't? Are you talking about clicking on different things? Probably the CS 757 cockpit is programmed without using the C/C++ gauge programming methods -- as described in the FSUIPC documentation, the Mouse Macro facility only works with certain ways of gauge programming. If you are talking about FSX or ESP here, then there's a remote possibility you might be able to do it using L:var macros, but that gets quite complicated and again depends on how the gauges are written. In the end, if the CS 757 does not provide any key or button programming facilities, only mouse operations, your only recourse might be "Key2Mouse" by Luciano Napolitano. Regards Pete

Sorry, I don't know that program. I think you'll need to contact their support. You could easily check the data FSUIPC provides by running the utility I provide to check such data -- TrafficLook (available in the Updates and Goodies Announcement above). I've just done that here. I suspect the information you want is more likely to be "model" which is the actual aircraft model more like that usually used by ATC. The "Type" is usually the Make, though all this depends up the definitions in the Aircraft.CFG file. I have just noticed that the selection of type/model/flight etc only operates for Airborne aircraft -- Ground aircraft continue to show airline (+flight number when assigned). I'm not sure at present why that is. Of course TCAS is normally only for airborne aircraft so this may be a mistake which has gone long unnoticed. I've made a note to check into that -- but it won't be till next week now, as I'm away from now till some time on Sunday. Regards Pete

Ah, I'm sorry -- that is something I do not know. Was there ever a version of SB which worked with FS2002? You are going back so many years now I don't even recall if we had an on-line ATC back then! I think you need some SB forum or support website for answers! Regards Pete

There's absolutely no difference for FSX or FSUIPC whether you use WinXP, Vista or Win7. There is no calibration facility in FSX at all -- there's only the main windows Game Controllers calibration, which is the basic calibration for any joystick device you should always check before using in any program, FSX or otherwise. (In Win7 i think that is "Game Controller Settings", in the properties of the device in the "Devices and Printers" part of the Control Panel). FSUIPC's calibration is NOT working on the hardware joystick but on the controls inside FS itself -- in other words it is applying precise adjustments inside FS to whatever the externally calibrated joystick inputs provide by way of numbers. This is how it has always been. It has never changed since the facilities were added to FSUIPC some 9 years ago. If you want to use FSUIPC calibration with axes assigned in FSX you should ensure that the sensitivities are all set maximum (full right) and the null zones minimum (full left), otherwise you will be wasting much of your joystick's capabilities. You can assign your joystick axes and buttons in FSX or in FSUIPC4 -- that is a different matter. Do not assign in both as then both will be active at the same time. FSUIPC's axis assignment facilities were added some 5 or 6 years ago. Regards Pete

No, and iin fact it doesn't really matter. You cannot actually exceed the maximum in any case, as close settings get replaced. With a range of 126 positions (other than the 0 and 127 min and max) if you ever achieve the 63 synchronised ones they will be as close as allowed! I actually doubt that you could get more than about 15 or 20 no matter how much you tried! ;-) Glad it works well for you! Incidentally, a small bug was found which could cause a crash if you somehow tried to set a sync point beyond one of the lever's max positions. The current download versions, 4.537 and 3.934, have this fixed, so please do update your copy now. No need to do any re-calibration or re-syncing. Regards Pete

Is there a new version? Have they provided any way to assign transponder mode and ident to buttons or keypresses yet? That's what I'm waiting for, and for which I asked the developers a year ago. Sorry, but I don't know anything about "getting it to run inside FSX" -- it doesn't use anything of mine. I assume it uses SimConnect. Do you have other programs working okay with FSX + SimConnect? Maybe you need to ask over in an SB Forum? Regards Pete

There are only three possibilities I can think of: 1. One or both of the Keys you are using for FSUIPC and WideFS is counterfeit, or 2. The signature on the FSUIPC DLL does not check, possibly a corrupt file, or 3. The system date on the FS PC is before the date of your purchase of one or both keys, making them look invalid. Possibility 3 is the most common and the easiest for you to fix. To check 2 right click on the DLL, select Properties, and find and check the signature to be valid. cuuent versions of FSUIPC are signed by simflight. Regards Pete

They don't change of their own accord -- only if you unplug and replug things in, or reinstall Windows. If you didn't know what you were doing you could have used the "AutoAssignLetters" facility. Anyway, yes, your edit looks okay. Why didn't you just try it and see? You can always make a backup copy of your INI file, in case you want to change back. Regards Pete

Okay, fixed in 4.536 now available in the Updates Announcement. I had a complete chunk of code missing in the FSUIPC4 version! Thanks & Regards Pete

The difference is only the version number in the Linkage structure. There's a value 0x0800 in the, er, 6th (I think) DWORD in that structure, which needs to be 0x0900 for FS9. You can change it in your DLLmain function as that is called before FS gets a chance to do its linking. Sorry, I've no idea. I don't use AppendMenu -- I use InsertMenuItem. Note also that FS seems to re-build its menu each time it is displayed if the option to hide it is chosen. So you have to add your items every time it does this. To do this I intercept the "WM_NCPAINT" message, get that processed by the default msg proc, then check and add my item(s) again. Regards Pete

Sorry, I'm not a Squawkbox user. You need to ask their Support for help. Sounds like you are not installing it correctly. Or are you trying to use Squawkbox 3 with FSX? If so then that is the wrong version -- I'm sure you need Squawkbox 4 with FSX -- and SB4 doesn't use FSUIPC in any case. Regards Pete

Yes, of course -- in my earlier reply I pointed you to the fuel tank offsets which contain their capacities and current levels. You do seem to be skipping replies made to you for some reason. :-( Please do read more carefully. I'll repeat the information again just this once: "The fuel tank capacities are provided by one offset location for each tank, and the level of the fuel in each is provided in another offset location for each. The offsets are listed quite clearly in the documentation -- check offsets 0B74 to 0BA8 for the more commonly used tanks and 1244 to 1260 for the extras some aircraft have (2nd and 3rd centre tanks, and 1 or 2 external tanks)." Another way to find this stuff is to use the FSUIPC for Programmers documentation, which is included in the SDK, and simply search it for appropriate words, like "fuel" in this case. It really doesn't take so long -- certainly faster than asking here all the time! ;-) Regards Pete

Weird. I can't think of anything you could do with it other than run it! Anyway, glad you resolved it. Regards Pete