Pete Dowson

Sorry, what does this mean? Pete

If you reinstalled Windows or rolled back the Registry you will need to re-register. Use the same details and enter them again -- cut and paste from the KEY file if you like. It does actually explain this in the User Registration section of the FSUIPC User Guide, thus: Regards Pete

No, the logs show everything as if it is perfect, no problems at all. The only possible reason I can think of for the gradually increasing latency is a pile-up of TCP/IP packets in memory, getting worse as memory fills and the swap files used. Is that an old Pentium 4, really? Not a Core 2? I must say straightaway that I do think your hardware just isn't up to FSX needs. I'm really surprised you can fly. What sort of frame rates do you see? My test machine is an old Pentium4 3.0 GHz, the slowest with hyperthreading, and it has 1536 MB memory, and although I use it for testing and debugging I could never actually fly with it! Anyway, that is no excuse, but it may well be part of the story. For now I can only suggest the workaround I mentioned. Meanwhile I am keeping up pressure on Microsoft to try to get the use of TCP/IP bypassed for internal comms, with FSUIPC and other DLLs. Regards Pete

Do you calibrate your joystick axes in FSUIPC? If so, there are work=arounds you could try: 1. Set "NoAxisIntercepts=Yes" in FSUIPC4.INI. 2. Either use only FS assignments and calibration or de-assign the axes in FSX and assign them instead in FSUIPC, using the "direct to FSUIPC" option for each. Then calibrate in FSUIPC. Okay. I'll take a look. We never managed to nail this one down enough for Microsoft to prove anything. It always seemed to be due to security hooks. Regards Pete

I agree. Can you report it as a bug to tell_fs@microsoft.com, please? I wouldn't have thought that it was supposed to be that way. I'll mention it to my contacts too, but a real user bug report is always good. Pete

Neither have arrived yet. Pete They both just arrived, together. The FSUIPC key is valid and expires on 23rd July. I'm afraid that the WideFS key in the KEY file is not and never was a WideFS key at all. It is an illegally generated FSUIPC key, made by a pirate generator by the look of it. Using it will stop both WideFS and FSUIPC working correctly. Regards Pete

So FSX won't accept any keyboard commands then? Why would you click on the overhead in that case? You'd need to use the FS controls instead, via keyboard or button assignment. Regards Pete

No, it shouldn't be. Actually i only have the scenery view on the main PC. RC runs on the Network, but it still gets its key strokes through FS. Hmm. Strange. It sounds like the undocked Windows aren't actually owned by FS. If that is the case you'd certainly not want to click on any of them. Why are you losing focus from the main Window in any case? Well, ShowText has font and colour options, but making things part of a panel is where the problem lies. It is very difficult to get it working correctly with both Windowed and full screen modes, and the variety of special panels appearing. It really was too much of a pain to maintain. Regards Pete

Good. Thanks. Pete

The FSUIPC display window is just that, a display window. It does not receive keystrokes at all. No, that is not true if all the Windows and panels are part of FS. It is the PROCESS which receives the keystrokes -- in this case FS. Radar Contact uses a facility in FSUIPC to capture keys as they arrive to FS. If FS loses the keyboard focus, it also loses the sound. Are you losing FS sound too? If not, then you don't lose keystrokes either. There's no difference in this between FS9 and FSX. You have something else going on there. Not when it was always so problematic in FS9 and before and almost impossible to implement properly for FSX in full screen modes. And not when the built-in FS window facility now used is so good. Why would you prefer AdvDisp? If you want a separate program altogether for the display you can use ShowText. That's what is used on a Networked PC (it is freeware included in the WideFS ZIP). Regards Pete

Neither have arrived yet. Pete

I cannot support old versions I'm afraid. 4.12 seems okay here. Can you check and get back to me if you still think there's a problem? I'd need to report it to Microsoft if so. If there is it is going to be a SimConnect/FSX problem, as FSUIPC4 uses SimConnect 100% in this area. There are no intercepts in FSX code as there were in FS9 for FSUIPC3. There is nothing in FSUIPC4 to make any of FSX's menu options go wrong. Regards Pete

Yes, or more simply 33 degrees and 56.33/60. ;-) Pete

I hope you Zipped it, or it won't get through. Looking again at the Log, you have two things wrong: You have a bad FSUIPC key AND your WideFS is not licensed at all, or is expired. Not connected by WideFS, because there was no valid Key. See the WideServer Log. No, I don't do temporary licenses. Sorry. And how did you get one from PM if you are not even using PM? Regards Pete

No. there are no hours! And the format is user selectable, I think -- probably via unpublished options in the CFG file. But you can always tell from the way it is presented. You actually showed them in the Degrees and Minutes format: See that little sign, ' ? That means "minutes". There's a seconds sign, ". If the format is degrees/minutes/seconds it looks like this: N33* 56' 33" When only minutes, no seconds, are given you get the decimal point indicating that the following digits are decimal fractions. And of course you can also have just degrees with a longer fractional part for similar accuracy. Pete

I'll have to work out some extra logging to see what is happening. I'll get back to you -- it'll be this week, just not sure when as present. Pete

No it isn't. It's 33.938833 and 118.404833. I think you are mixing up minutes (56.33') with minutes and seconds (56' 33"). It isn't, it is identical. They come from the same place in FS. You need to understand the units. Regards Pete

It is a bad key -- or it has expired a little earlier than you said. If you'd like to ZIP up your FSUIPC.KEY file and send it to petedowson@btconnect.com I can check why. You won't get that working with a bad key, so that needs sorting first. Regards Pete

Thanks for the files. As far as I can see, the Registry is exactly the way I expect it to be, so the mystery deepens. I'll have to think about this. I may add some more logging and ask you to run some tests for me. Okay? Regards Pete

I've already added the SteeringTillerControl=n parameter and will test it tomorrow. No. The only thing I can think of is that the way it is added to the Registry is different. For DirectInput devices I have to get an ID (a "GUID", and I search certain parts of the Registry for these. Maybe my method isn't general enough. Perhaps, if you don't mind using RegEdit, you could export me the registry entries for your joysticks. Run Regedit from the Run option (Start -- Run). This is the area I look in: WinXP: HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput Vista: Same but in HKCU instead of HKLM. If you could export that section (to a REG file) then ZIP it up and send it to me at petedowson@btconnect.com, maybe I'll find out what is wrong. In case you are interested, within that section I look deeper, to VID_xxxx&PID_yyyy\Calibration (where xxxx is the Mid and yyyy is the Pid of the device (in hex), from the normal Joy interface). Inside there I check that the "Joystick Id" parameter matches the "joy" interface ID, and if so read the "GUID" value, which, at last, enables me to use the device. Maybe you could also run the attached JoyView program, please. Find the right device (out of the 16 listed), and tell me which it is (1-16), and the Mid and Pid (in the joyGetDevCaps section). Regards Pete joyview.zip

If you had a Simconnect problem before and just tried to reinstall or rapir it without deleting that specific folder then Simconnect would not have been repaired. It seems that the installer checks for the presence of the folder and if it is there wrongly assumes all is well. You don't need to un-install and re-install anything. Just follw the instructions in the FSX Help announcement above to repair the base SimConnect installation. Something "not working" shouldn't mean you have to reinstall FSX. Just un-install whatever it is you no longer want. Regards Pete

What does the Install log show? It sounds like you have a BAD install of the base FSX, after which you installed the SP1 update. You need to repair/reinstall the essential base version of SimConnect, which you can do by following the instructions in the FSX Help announcement above. I'm afraid there is no way I can provide code which repairs SimConnect if that is installed incorrectly or gets corrupted. SimConnect is by Microsoft. I would love to include the SimConnect.MSI in my installer so that I could ensure a good installation, but Microsoft will not allow this (and yes, I have asked). You have to use the Microsoft DVD to repair, there's no choice. Your "clean" installation couldn't be that clean if it has the SP1 Simconnect installed -- you must surely have installed SP1 too? And was your so-called "clean" install actually a re-install? If so, even if you un-installed first, this will not affect a bad SimConnect installation because the Windows Side-by-Side system for libraries like SimConnect won't un-install that easily, and, unfortunately, won't repair either unless the folder is actually missing -- please see the FSX Help for how to deal with it. I have been complaining to Microsoft about the FSX repair simply not being thorough enough, to no end thus far. I just hope they can do something about it in a future update. Regards Pete

I think that pretty much proves it is a driver problem. Stick to maximised Windowed mode until new drivers are available. If you run the screen at a high resolution, the title bar isn't really a problem in any case. Regards Pete

Was this in another thread? Since I had never heard of this card I most certainly would note simply state such a thing as I wouldn't know. didn't you say it worked with FSUIPC3 but not FSUIPC4? The only difference between FSUIPC3 and 4 as far as Axis Assignments goes is that FSUIPC4 uses DirectInput, just like FS does, whereas FSUIPC3 uses the old Windows "joy" interface. For buttons, rather than axes, they both use the old joy interface. Well, that implies that the card looks like a standard DirectInput joystick to Windows -- it actually says "THE USBAXES CARD CONNECTS TO THE USB PORT AND IT'S AUTOMATICALLY DETECTED BY THE OPERATIVE SYSTEM AS A 5 AXLES AND 24 KEYS JOYSTICK." So it should work fine. I'd like to know why you cannot use FSUIPC4's Axis Assignments. Something is wrong somewhere. It recognises all standard DirectInput devices. Mind you, it only recognises the first 16 DirectInput devices. Might you have more than 16 already connected? Not at present. There is a built-in nose wheel steering facility in FSX, but it doesn't appear to be exported to the Control Assignments dialogue at present. For the other additional axes supported by FSUIPC, there are parameters in the INI file for assigning FS control numbers, so you can use an axis which is otherwise used for something else (that you don't need) in FSX. If you look in the FSUIPC4.INI file you will see them, looking like this: FlapsSetControl=0 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 I could, perhaps add a "SteeringTillerControl" here as well. I'll have a look, see how easy it is to fit in now. Regards Pete

Must be. Good point, I never thought of that. Maybe, for such non-Serial Serial ports it's actually the setting of the CommState which needs that part of the name. as well. Maybe I am opening COM19 correctly with the CreateFile, but the settings are then all wrong. I'll tell you whatI'll try including the \\.\ in the name for the setting of the COMM state for ordinary ports. If that works, then you can try COM19 without the \\.\. Give me a few days. I'm in the middle of something else at present. Regards Pete