Pete Dowson

How is your name here (J White?) related to the name of your registration (Kong Sun Choi)? Licenses are not transferable. Anyway, it is now clear what is going on. The log tells me that you have an incorrect, probably pirated, Key for either FSUIPC or WideFS, or both. I think WideFS, hence the problem. According to records you, if you are Mr. Kong, only purchased an FSUIPC Key, no WideFS key. And there's no record of any FSUIPC4 or WideFS7 purchases in that name, which is even more suspicious. Have you changed your name, or registered using a different one? If you think your keys are legitimate, please ZIP the FSUIPC.KEY file from the Modules folder and send it to me at petedowson@btconnect.com for further checking along with your receipts from SimMarket. Otherwise I'd strongly advise you to purchase legal key(s) immediately. If I don't hear from you by this time tomorrow I will report this to SimMarket. Regards Pete

That's really weird. The logs show it is all communicating okay. One more thing, the last straw as it were. Make sure FS2004 is closed and show me the complete FSUIPC.LOG file please. Regards Pete

Your program is running okay on both FSX and FS2004 when on the same PC as FS? Which example, the C# one? Can you try one of the utilities I provide, like FSInterrogate, TrafficLook or WeatherSet please? Also, the two log fragments you showed originally are not enough. Both WideServer and WideClient show performance details when they terminate. Can you run FS2004 and WideClient and, when you are sure they are "connected" or appear to be, and your program (or any other) still fails, close WideClient and FS and show me both the logs. Please also confirm you are running the same WideClient, from the same folder on the client PC, for both FSX and FS2004, so I know it is indeed being set up the same. Finally, you should also try the current version of WideClient, 6.78. It was released last week but unfortunately Mr. Schiratti is unavailable at present, so the main download site isn't getting updated. You can get updates for many of my programs from the Announcements above, however. Regards Pete

Best really to develop and test locally, on the FS PC. All WideFS is doing it extending that interface to another PC, but debugging and so on is usually much easier on the same PC as FS. This is unlikely to be anything to do with WideFS. What does it do on the FS PC? It sounds like you have something wrong in the program. Show me the FSUIPC_Open statement you are using. You may have it set to only connect to FSX, so it refuses to connect to FS2004, which of course is a different version. Regards Pete

FSUIPC does NOT, repeat NOT, touch any hardware. It doesn't read your switches. It reads joystick buttons and keyboard presses from Windows, just like FS itself. If you can assign things in FS, you can assign things in FSUIPC. Just more in the latter case. So you first need to understand what you are connecting and what drivers and so on you need for that. I cannot help you there, you need to use the documentation for the device(s) or the support from their makers or suppliers. That's for programmers. Are you going to do any programming? If not, forget it. What on Earth are you reading? If you want to do programming, first learn a programming language, practice on something simpler, then download the FSUIPC SDK and try the examples. But you certainly need no programming simply to assign buttons and keys -- can you look at FS itself and understand how to assign things there? If so you can do it in FSUIPC. Have you even looked at the simple user guide to fSUIPC, with pictures? Tried anything? What's written in gobbledegook? Where on Earth have you been looking? Just refer to the user documentation you have for your devices and your aircraft and then FS, or if needed, FSUIPC. By all means ask specific questions if you get stuck, but please do not expect anyone to do everything for you. after all, you know what you want to do. If you can learn to fly a complex aircraft and understand what all the buttons switches and dials are for, then doing such simple things like assigning buttons or keys should be a doddle for you! Pete

I think you still misunderstand! The FSI documentation only tells you how to use FSInterrogate. You want the complete table of offsets and their explanations supplied as the major part of the FSUIPC SDK! Doesn't the VB.Net Shell ZIP file in the FSUIPC SDK include an example? Have you looked? I'm pretty sure most VB.NET users manage with that or the Paul Henty library method. Pete

You can do that, just by having more than one assignment to the same keypress/release, but you have to do it by editing the parameters for it directly in the FSUIPC INI file -- the Options dialogue only allows setting of one action for keypress and another for key release, no more. The format of the parameters in the [Keys] section of the INI is fully described in the Advanced Users' guide. You should use the "Sound off" and "Sound on" controls for the sound switching, as you cannot program a key press to send a different key. All of the FS controls are listed in the List of FSxxxx Controls document available from the Schiratti download site (the one containing all my stuff), unless you are using FSX where you will find it already in the FSX Modules folder. (In this case I can save you the trouble -- sound off is 66063, sound on is 66062). You can edit the INI file whilst FS is running, then test your changes by going to the Keys tab in FSUIPC options and pressing the Reload key. Note that once you do this you cannot change the space bar assignment in FSUIPC's options, as it protects your multiple assignment this way. Regards Pete

Ah, thanks Thomas. I didn't know that! Pete

This appears to be just a declaration, not a program? What is the "256" part for? (Sorry, I don't know VB). Use FSInterrogate to see how things work. The correct reference to what the values are is the documentation, not really the brief labels in FSInterrogate's parameter files! Maybe if you showed a bit more of the program, like where you initialise the interface and where you read the values it might help? Regards Pete

It's a pretty bad bug in FSX, actually carried over from FS9. In FS9 I managed to fix it in FSUIPC pretty well with the wind smoothing. In FSX the FSUIPC4 wind smoothing does do a reasonably good job, but it still isn't completely foolproof. However, after lots of experiments and improvements over an extended period in I did mange to overcome it to pretty much most folks' satisfaction, and even added my own more realistic turbulence emulation (the smoothing in FS9 cut all turbulence out by the way it worked). Have you tried enabling the FSUIPC4 wind smoothing at all? Of course you'd need a registered copy. Regards Pete

No idea. Everyone has different needs. Throttle1=-12288,-11641,-10132,16171/8 Min -12288 (below that is max reverse only Idle zone -11641 to -10132 Max 16171 (above that is all max thrust) Can't remember what the option values (/n) are -- it'll probably be filter (F) or Rev, whatever you see ticked. I don't tend to edit these in the raw form and don't expect others to. doesn't look very large, but the numbers depend so much on the individual device, and how it is calibrated or mapped in the windows drivers for it, that it is impossible to tell. That would only happen if both of the axes are identical in every way and are both treated and calibrated identically in the windows drivers. It can happen -- with digital devices usually (or perhaps those using optical readers rather than pots), but it's not all that likely likely. Anyway, the separate throttle levers in a real aircraft are never identically positioned for the same thrust 9unless digital as in the Airbus). There's normally always going to be a default set of parameters. Else how does FSUIPC know what to do for an aircraft you've not set specific stuff for? It contains no actual set calibrations in any case, only the default options. Generally there's no point anyway in having aircraft-specific calibrations unless you either have different controls for each aircraft (and so different assignments as well), or simply want them to behave differently for each (e.g. no reverse zone for a Cessna, but one for a 737). [buttons.Level D Simulations B767-300ER] [buttons.American Airlines B767-300ER TCP LDS] If you changed the parameter "ShortAircraftNameOk=..." to "substring", you could have the one section for all B767's by changing the heading in one to [buttons.B767] and deleting the other section altogether. See the Appendix about all this in the recent advanced user's guide. Regards Pete

Yes. As long as the Port specified in your SimConnect.CFG/XML files for us by GMAP isn't one of those used by WideFS (9002 and 8002 by default). Pete

You seem to have omitted to paste them in! But you said it was the Saitek pedals causing ityou said "I know it's the Saitek pedals because if I unplug them from the USB port the rolling immediately stops.". In the log, in the same line as you found "PAN VIEW", there would also have been the FS control number, probably 66416. You need to find the line in your [buttons] or [Axes] section(s) (more than one each if you are using Aircraft-specific assignments) which contains that control number. Then delete that line (or better, to test, just comment it out by putting a ; at the start of the line. You can do this whilst FS is running, then go to FSUIPC's Axes or Buttons tabs and pressing the Reload button there, so it reloads the INI file settings for that group. Regards Pete

In FSUIPC's "Logging" page, enable Event and Axis logging, then look at the FSUIPC.LOG file to see what FS control is repeating all he time. Sounds like you have something assigned to one of the PAN controls. Pete

Why not assign the buttons the same way as you did in Fs2004 then? Sorry, I don't understand your difficulty. You are in control, you can use the buttons how you wish. The controls in FSX are the same as in FS9 as far as the Gear is concerned. What is the problem? Just assign the two buttons to Gear Down and Gear Up as you wish to do! Pete

Yes. No, you need to purchase and register WideFS7. You install FSUIPC4 in FSX and Wideclient.exe on the Client PC. You can register WideFS7 in the FSUIPC4 installer. Pete

FSX contains the exact same Gear controls as FS9, no difference at all. There's a Gear Toggle (same as the 'G' key by default) as well as Gear up and Gear down. I'm not sure why you have the assignments different in each, but you can certainly change them to be as you like. Regards Pete

AutoSave itself creates nothing, it simply calls the same routine in FS that you would do if you pressed the ; key (default assignment) and entered a name. It just does both these things for you, automatically, at intervals. The extra thing AutoSave does is automatically delete files cyclically according to the number you specify. It actually does this not only for the .FLT, .WX and .FSSAVE files, but for others, saved in the same folder, with filetypes PSS, FMC, ABL, RCD, SPB and (in FSX's case, with the latest FSUIPC 4.333) IPCBIN. These more or less cover what was being saved by both FS and many add-on programs -- including the PSS aircraft and, I think, the original PIC ones (preceding the current Level D range). I'm not sure if it still does -- I don't really use any add-on aircraft myself. "RCD" are Radar Contact data files. I don't mind extending this as needed, but only for files in the same folder. Unfortunately, PMDGs saved files go into their own area. I can't really start extending AutoSave's operations into other parts of the disk system, though its filetype, ".FLT.SAV" would certainly be easy enough to add to my list for the normal FLTs folder. On the other hand, maybe an INI file option (only) could be added where you, the user, can provide an additional folder path to be handled, and the fie-type to be deleted. I'll think about that. Shouldn't be too much work ... Regards Pete

How do they get fragmented? You wouldn't have thought they were big enough. The PMDG software is detecting the saving of flights and automatically saving its own data. If you don't want that to happen I suggest you either look to see if there's a way of turning it off in the PMDG options, or else you'll need to stop using AutoSave. Simply go to FSUIPC's AutoSave tab and disable it -- you must have enabled it there in the first place, as it is off by default. Alternatively, if you find the Autosave with PMDG data useful, you'll need to remember to go delete them now and then. Incidentally, 1444 saves in one flight seems a bit over the top. Why don't you think about reducing the frequency a bit. say to once every 2 or 3 minutes? Then you'd need to go on a 2 day flight to accumulate that many! ;-) Regards Pete

Yes, that was a minor error, fixed immediately by 3.821. In fact 3.817 was identical to 3.82, it was the "release candidate". Hopefully 3.849, though, not 8.849? ;-) Regards Pete

What is FSUIPC.DLL doing there? That is only for FS9 and before. Did you put it there? Only FSUIPC4 works with FSX. And there should be several more files in any case. Please see the Installer log again. It should also have placed all the documentation there too -- the History, the User Guide, the Advanced User guide and the List of FSX controls. If there is no FSUIPC4.LOG file nor an FSUIPC4.INI file, then FSUIPC4 is not being run. It is as simply as that. And it seems it is not being run because you installed it for someone else, this Ten Katen, instead of for yourself. You can have as many hard disks as you like for one user. The number of users and the number of hard disks are not related, they are nothing to do with each other. I must repeat what I said before. You must install FSUIPC4 using the installer when you are logged on as the person who is going to run FSX. It is absolutely no use installing it for a person who isn't going to run FSX. You are wasting my time as well as your own. Regards Pete

Sorry, what, exactly, is the same as what "last one"? You've not sent me any FSUIPC4 log file yet, only the Install log, which obviously never changes unless you re-run the Installer. The FSUIPC4 log file is NOT the installler log file! The FSUIPC4 log file is only produced when FSUIPC4 is run. If there isn't one then FSUIPC4 isn't being run. The previous install log you showed contained this: Found FSX.CFG in "E:\Users\Ten Katen\AppData\Roaming\Microsoft\FSX\FSX.CFG"! Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. ... FSUIPC4 section of DLL.XML written okay which does indicate that you have, at least once, run FSX as user "Ten Katen". If you had not there would not be an FSX.CFG file for that user. Since you have now installed FSUIPC4 when running as that user, you need to always run FSX as Ten Katen. If you want to also use it as another user, you will have to run FSx then install FSUIPC4 for that user too. FSX will install for the currently logged on user. If you want to install for a different user you must log on as a different user. You must run FSX when logged on as the user for which it is installed. Otherwise all of the installation you might ever do is completely to no avail. None of that makes any sense to me, I'm afraid. You aren't running FSX on Vista then, if you are running vista under an administrator account and you aren't running FSX on that account ...????? It sounds like you should start again. FSX should be installed AND run by the user who wants to use it, not by anyone else. Regards Pete

3.80 is very much out of date and isn't supported. Current is 3.82, and there's a 3.849 available in the Announcements above. Pete

The default single generic throttle does that, as do the individual throttles in FS itself. I assume you must mean in FSUIPC? You do not mention FSUIPC anywhere. The reverse option applies to the 4 individual throttles. I assume you are using those? Yes, of course. Simply make the reverse zone zero size. Calibrate the Reverse (minimum) and one value of the Idle zone to be the same, or as near as possible the same, then make the idle zone big enough to always reach by making sure the upper idle value leaves a reasonable area on the axis. You always need a proper idle zone in any case, to be sure you can actually always get to idle. The letter assignment is based on the Windows joystick driver. it doesn't matter what it is. Pete

None of the default aircraft have an APU before FSX, and in FSX the APU doesn't really seem to function much. If you are only talking about add-on aircraft then each will be implementing such additional systems differently and you will need to refer to their documentation to determine how to operate it. Once you know how to operate your add-on aircraft, then you can seek ways of possibly assigning joystick buttons or switches, whether using FSUIPC or not. Regards Pete