Pete Dowson

If there's nothing in the title bar from WideServer then it isn't running. It always posts an additive there once it is started -- but don't forget it only starts once FS is "ready to fly". Pete

Which part don't you understand? Are you seeing "(1 of ..." something in the window? If not whay are you asking? Sorry, I don't understand. What are you logging which causes continuous variable logging? What mouse click inputs are you wanting to read? The console log is anyway only a copy of the log file. Have you bothered to check whether normal FS controls (events) are being used, as I suggested? Is the aircraft only mouse controlled -- don't the authors provide any other way? Regards Pete

What values are you reading and where? The values provided by the axis are NOT the values sent to the Sim to position the flaps. That's the whole point of the calibration. FSUIPC maps a range of input values to the true values needed in FS for each notch. It doesn't matter what the input values from the joystick are provided FSUIPC can see that the lever is in the correct position for the notch. To achieve the intermediate positions you click the centre button twice, in two different lever positions, to establish the individual range for the notch shown just above (numbered #1 to #7 for the PMDG 737). That range should encompass the detente or marked position on your hardware flaps lever. (If you are not using such a lever you should not both with notched calibration -- there is no point!). The end positions are achieved by placing the lever below or above the position calibrated on the left (#0) and right (#8) buttons. Therefore those buttons should be pressed far enough away from the end points (the ones you already established) to guarantee you get get below or above them. It sounds like you are simply not providing a Flaps #0 range which your lever can be placed into! Do not calibrate position #1 before you do position #0! If you still don't understand, show me the flaps calibration lines from the INI file and I will point out the mistake to you. Regards Pete

Why did you purchase it then? You can have it installed without purchase for use by other add-ons which use it. It is a bag of many tools. if you have no need for a tool, you don't use it. it is that simple. But peruse the User guide, see if anything is suggested there which interests you (something perhaps better done before parting with money?). Regards Pete

Didn't you TEST it first, as suggested in the text which appears? When you repeatedly click with the mouse, does the same thing happen as when you press "TAB" to test it? Did you read this part of the FSUIPC user guide? When you click the same place with the mouse, do you get the same results? Maybe the routine being called toggles between "ON" and "ARM". You'd need to find the correct command for "OFF" in that case. Possibly it needs some other mouse action. See the boxed section in the Guide entitled Variations for Mouse activated switches which might be made to work by editing the Macro file Sorry, I don't understand this question fully enough to answer sensibly. Same sort of thing. You need to TEST, and possibly edit the file with mouse action values. Without the aircraft you are using I cannot really tell. It is entirely possible that the way it is programmed is not susceptible to FSUIPC's mouse macro facilities. Do the makers supply any other way of operating these switches -- keyboard or joystick assignments? Surely they are not mouse operated only? You should also enable FSUIPC's Event logging and see if the actions you want are merely generating normal FS events. If so you could assign directly to them instead. Regards Pete

Sorry, what does "FSUIPC is fully blank" mean? Do you mean left to default settings? A registered install of FSUIPC is a tool for you to use as you wish, for anything it can do for you. Regards Pete

Must be SimConnect's activity, sending data to FSUIPC on each frame. I've never ever seen any frame rate counter stay rock solid on a chosen target in any case, unless you stop all AI Traffic and other heavy-processor usage items. No. Apart from FSUIPC possibly being used by other programs, and scanning joysticks when you have assignments, it does nothing but sit there receiving data from SimConnect whenever it changes (but not more often than the internal framerate) so it can supply that data to requesting programs. This is different from FSUIPC3 which had to actively go get the data. with SimConnect you simply register the interest and wait for the data to arrive. Try setting the frame rate limit higher so there's some leeway. The VSync will still work. Additionally there are external frame rate limiters which do a far better job than FSX's so it is worth investigating those instead and leaving FSX's as unlimited. I think this link might still work: http://rapidshare.com/files/160642187/Fer_0.2.rar Regards Pete

This appears to indicate that you are providing the IP address (is it correct? The Servers never sees any attempts at all). That shows the server name to be "ROGERP". You supplied what you called: but if it is really called that, it isn't the WideClient.INI file being used, as you can see by the name. If you really meant WideClient.INI then: this is okay, but should really result in the connection reading: Trying TCP/IP host "RogerP" port 8002 ... not the IP address, so something in the data you supply simply does not match correctly. BTW why are you specifying the server details? Doesn't the broadcast work? It ceretainly should do if your PCs are in the same workgroup. The other thing to check is your firewall, especially the one on the Server as that never sees anything from the client. It's rather odd, though, that nothing is reported back to the Client if Widows cannot connect. Sorry, you need to explain that a little clearer: "may or may not "? And why "stop FSX AND the PC then restart the PC."? What good is that? Regards Pete

In FSUIPC Options please enable Button Logging (Logging tab, left-hand side). Then repeat the test so I can see what it is doing. "Shift + F" or "Shift + F1"? You missed the start of the log, which might help. Are you not using SerialFP2 as well? I see no initialisation of the device. If you don't run the VRi driver you should only provide the one port, the device port -- you've provided both, thus: These entries: seem to indicate the device was already initialised somehow. Was that from an earlier run with SerialFP2? "FUN16" is the unassigned key under the word "FUNC" (top right below the scren), and "KEYCLR" is the bottom right, which should be labelled "CLR". You didn't press the LSK1 key, which would send the message "LSKL1". Regards Pete

Why could you not do it with FSUIPC? What does "pulling" and "pushing" the "altitude knob" do? In fact what IS the "altitude knob"? What function are you actually trying to operate in FS? Pete

Why "repurchased"? You only need to buy it once. If it says the key is invalid then it either doesn't match the FSUIPC version (i.e. it is an FSUIPC3 or WideFS key), or you are making any error somewhere. Since you used a false name here (why do folks do this?) I cannot check for you. If you tell me your registered name I may have the details (I don't necessarily get them all). Don't post the key here though. Andy's suggestion about the system date would not invalidate the key, it would only prevent FSUIPC working correctly when registered as it would assume the key was pirated. Regards Pete

The only two ways possible is by losing or deleting entries in the FSUIPC INI file, or having thr joystick ID change on you, as by reinstalling Windows or plugging the joystick into a different port. You are using axes (levers) for flaps? I'm afraid you are going to have to explain exactly what you are doing so I can understand it before I can help. There are so many ways of doing these things. Differences like that show that you are not leaving enough of a "dead zone" at the extremes, to allow for small variations in the values supplied by the analogue axis. If you are using the Detente facilities in the joystick calibration tab then, before entering that mode, you should first calibrate the axis itself, setting the minimum and maximum points to that they are always consistently moving the flaps to up and full down every time. To do this consistently you will normally need to set min and max with the lever AWAY from the real end stops -- allow a little more also for temperature and humidity variations. If you follow the calibration steps in the documentation you will achieve this. THEN go and set the internal detentes, leaving the min and max correctly set. Regards Pete

Both panels seem pretty versatile whether you need to program for those aircraft specifically or not -- but I cannot advise on that point. You might find more specific advice on VRInsight's forum. http://vrinsight.com/phpBB3_en/viewforum.php?f=2 Regards Pete

You certainly have a corrupted SimConnect installation, though since the SP1 and SP2 versions seem okay it may not affect FSUIPC. However, it could adversely affect other programs which may need the original SimConnect version. As far as the signature problem is concerned, have you disabled any Windows services at all? Windows signature checking does need services such as ythe crytographic ones, which may look superfluous to you otherwise. The error in the earlier log (Error ref 80092026) when Googled turns out to be: Try right-clicking on the FSUIPC4.DLL in FSX's Modules folder. Select Properties - Digital Signatures, select the signature and look at the details. They'll probably say "the cryptograhic operation failed because of a security setting". If so you can probably fix it with a small registry change. See this: http://stealthpuppy.com/windows/windowsion-failed Regards Pete

What's a "LAN status" and how do you reset it? Pete

What is "error 13"? Do you mean an error reported back from the FSUIPC_Open call? If so this is "FSUIPC_ERR_DATA", which means it connected but was unable to interpret the data received. I'm afraid I don't know Delphi at all, but I assume you do? If so then simply use the source provided for the interface and debug through to see what is going wrong. All the files related to the interface are included in the SDK. There's nothing hidden. I think the main Delphi source file is "FPCuser.pas". I assume Delphi comes with debugging facilities? Regards Pete

Good catch. It is an error in FSUIPC4. It does work in a Registered install, but it should also do so unregistered, as it does in FSUIPC3. I will fix it in the next main User Release, but that won't be for a few weeks. Meanwhile, the option does work if you use "READY" as well as CLOSE, the only difference then being that your program won't launch until FSX is ready to fly. Regards Pete

Have you read the previous help in this thread? If you have a different problem please start a new thread. In either case please show the WideServer.Log, WideClient.LOG and FSUIPC4.Log files. Also, I don't know the program "GA Panel" so please explain what this is and confirm it uses FSUIPC. Regards Pete

Not sure why clock sync was checked -- it isn't by default. Is this related to your report that "since registering FSX has developed an annoying habit of reloading the the textures at different intervals"? If so then it sounds like something else is doing it, maybe through FSUIPC. Have you checked the FSUIPC4.LOG file (in the FSX Modules folder)? Maybe you have some registration problem? An illegal registration or an incorrect system date (making the registration look illegal) could cause FSUIPC application programs to fail in ways which could case problems. Otherwise, merely registering FSUIPC without actually using any of the facilities thus enabled, would do nothing at all different from having it unregistered. I'm afraid I am on holiday from tomorrow morning until Monday 5th July, so it may be too late now for me to check your log for you until then. Regards Pete

Yes, but that's defined in the Aircraft.CFG file. Well, it is, but only by editing the CFG file and reloading the aircraft. And how exactly do you propose that is implemented? There is no facility other than in the CFG file to change that. Have you hacked into FSX code and found a way? The three commands I listed for you are the only mention of any controls for FBW in SimConnect. The full description in the SDK is: FLY_BY_WIRE_ELAC_TOGGLE: Turn on or off the fly by wire Elevators and Ailerons computer. FLY_BY_WIRE_FAC_TOGGLE: Turn on or off the fly by wire Flight Augmentation computer. FLY_BY_WIRE_SEC_TOGGLE Turn on or off the fly by wire Spoilers and Elevators computer. Are these descriptions incorrect? If not, I would have thought that if they were all toggled off the FSX FBW wouldn't be doing much at all! Also, there is a separate FBW package listed in Project Magenta downloads. Doesn't that work? Regards Pete

That's very generous of you. Thank you! Well out of date and not supported. Your FSUIPC3 key is valid forever for all versions of FSUIPC3. In fact I need you to keep up to date or I cannot support you -- I only keep latest copies of the software. There's also an even more up to date version (3.989) available in the Updates announcement above, but install 3.98 first. Regards Pete

Is that the FS9 version, or do you have a Beta of the upcoming FSX version? What is this "latest version" you installed? I always need version numbers please! Folks have said "latest version" and been using a year old version! And what version number did you update from? Not at all? Using mouse, keyboard or programmed buttons? Programmed in FSX or in FSUIPC4 or where? FSUIPC isn't aware of whether you are in full screen or windowed mode, and doesn't care. You can simply paste it into your message. If you select it after pasting and select the "code" button at the top of the editing area it will enclose it like a scrollable file. That's the best way. In any case, enable "event logging" (in the Logging tab), first, then reproduce the problem, and then close down FSX before getting the log. If you keep the session only as long as needed the Log should not be too long. If it does grow really large we'll have to resort to emails. Your English is fine. Don't worry about that. I'm not sure I'll be able to do a lot about this. It sounds very much like a PMDG 737 problem. If it is the FS9 version you are using in FSX then I'm surprised much of it works at all. Do they support it for FSX use? Do their Gauges and DLL's run in FSX? I thought they needed a DLL called "PMDGoptions.DLL" installed, and I don't think that can work in FSX. If you are testing the Beta FSX version then you relaly need to deal direct with the PMDG Beta group leader. Anyway, I'm on holiday from tomorrow afternoon till July 5th, so I'm afraid a fuller investigation may have to wait. Regards Pete

Certainly sounds like you are using an old version. You should be on 4.60a at least, and 4.617 is available in the Updates announcement in this Forum. Regards Pete

Have to check that, does this replace functions of GFDisplay, i.e. displaying values on GF's displays? Yes, with a rather less arcane system -- proper program statements rather than complex parameters. But it is only implemented in FSUIPC and so only runs on the FS PC. If your freezes are due to poor CPU usage on the FS PC then obviously it wouldn't help. I suspect Wilco might have an SDK available. I've not really heard. Certainly Nico Kaan might be involved with that as he is with Level D interfacing. But I'm not aware of anyone using the PMDG 747 in an all-hardware cockpit with all indicators and readouts correct. Certainly the control of the switches and so on can be handled -- mouse macros seem to work well with PMDG stuff, and if not that the L:vars. Maybe you can get hold of display values through L:vars too, but that would certainly need Lua plug-in programming. Ask around in one of the cockpit building forums, and especially MyCockpit (http://www.mycockpit.org/forums/ ). Sounds like you need to do some twiddling with priorities and assignments. I'm surprised you have any such problems with FS9 -- FSX is the one which clobbers performance unless you tune everything correctly. Are you using an old underpowered PC? No, it is on the same PC too. If FS9 is taking 100% of the resources then nothing will stop the "freezing". Regards Pete

My main idea is to follow the instructions given in the Error report. Have you not bothered? It seems explicit enough. Perhaps you missed it? Look, it says: The "I" here used to be myself, "Peter L Dowson", but since my Certificate expired the publisher is simFlight. So please do what it says: load Internet Explorer, go to Internet Options - Content - Publishers and if simFlight is listed as "untrusted" remove it from that list. If it is there it is because you have, at one time or another, told Windows to refuse permission for a simFlight signed program. If this is not the problem then I would certainly need to see the FSUIPC4 Install log, which you'll find in the FSX Modules folder. This is why such a log is produced, to provide information in the case of a problem. Regards Pete