Pete Dowson

Good. Thanks for the feedback. 20 looks hot favourite at present. Regards Pete

How are you assigning them, in FS or in FSUIPC? From reports already in from other Saitek users (see some other recent threads here), the Saitek devices or drivers seem to occasionally be a little slow in responding, and fail the new safety meassure in FSUIPC -- the JoystickTimeout. A glance at the FSUIPC log file would show if this is happening as it tells you which joysticks fail the timeout. If this is the case try increasing the JoystickTimeout value, in the FSUIPC INI file, from 15. Try 20 to start. Let me know please. I'm trying to find the best value, the lowest one which always works. Change it before loading FS. If this isn't the reason for the problem, we'll need to investigate further. In that case, if it isn't the timeout problem, it may be related to the assignment. Did you assign in FSUIPC or in FS? If in FS make sure the sensitivity slider is full right and the null zone slider full left. Remove the DLL from the Modules folder, and put it back. But how can that achieve anything? The software doesn't change just because you take it out of a folder and put it back in. If you mean remove all of your settings, so you have to start all over again from scratch, then you simply delete the FSUIPC.INI file. That contains all of the settings from the FSUIPC options menus. Regards Pete

No, I'm sorry, none of that really makes much sense. Can you tell me what the registry key is for the correct path to GFConfig.exe (& therefore GFDev.dll), please. I'll double check my code to make sure I'm using it correctly. Maybe it has changed with more recent GF releases. The Saitek device is absolutely totally unrelated to anything made by GoFlight. The GFDev.DLL does not have anything to do with any Saitek devices. The code in FSUIPC for GoFlight is totally separate and not related to any non-GoFlgiht devices, buttons or joysticks. So you probably have two separate problems and you are confusing the two. So, slow down a bit and deal with one at a time. First, if you sometimes get the Saitek device not recognised, have you checked the FSUIPC log file afterwards? Does it show a message saying that a Joystick has exceeded its timeout of 15 mSecs? If so, you are another one with Saitek devices who is experiencing this. If you read other threads here (particularly the one entitled "FSUIPC 3.96 and Joystick Problem") you will see that the new safety timeout incorporated into FSUIPC versions 3.96 and 4.57 seems a little too tight for the Saitek drivers or devices which appear to be somewhat tardy in their responses sometimes. So, for that problem please try increasing the JoystickTimeout value in the FSUIPC INI file. Try 20 first, but if that doesn't give you 100% success with the Saitek, increase it a bit more. I am trying to ascertain the lowest value which always works. You'll need to change it before running FS. None of this is related to GoFlight equipment, though, which is not polled like normal joysticks but relies on notifications arriving from GFDev.DLL. Get the Saitek working first, whatever. Regards Pete

But 100 is a tenth of a second! The polling rate is at least 20 times per second. if joysticks took 100 mSecs to respond, nothing would ever happen! Could you not find a lower value which works 100% please? I really do need that sort of feedback so I can set the default properly. 20, 25, 30? Oh, sorry. no. I cannot help at all with hardware connection problems. I don't even have any of the hardware in question. If you eventually sort that out THEN still get problems connecting to FSUIPC, please do the logging as I suggested and i'll take a look. Regards Pete

Thank you very much for posting this. Good detective work on your partwho would have possibly thought such an odd reason? Anyway, buy yourself a well-deserved beer and pat yourself on the back! As it looks like it is an FSC installer problem have you also told them so that they can correct it in their next update? Regards Pete

I've looked at my results for FSX and the file "Runways.csv" definitely contains MN76. Here are the entries: Which csv file did you look at? But missing from where? Regards Pete

Thanks! That was something I didn't know! Pete

What other FSUIPC-using add-ons? FSNav doesn't count as one, it doesn't use FSUIPC at all. Go into FSUIPC's logging page and enable IPC read and write logging. Run the cpFlight driver. See it not connect. Close it. close FS, show me the FSUIPC log file from the Modules folder. If it's too big to paste into a message here email it as an attachment to petedowson@btconnect.com. BTW you are in the wrong thread! This one is about joystick timeouts! Regards Pete

That should work, then. no need to mess in the Registry if you've done that. Regards Pete

GF.Dll? Do you mean GFDev.dll? You need GFdev.dll to be accessible to FSUIPC. If it isn't found then FSUIPC will assume there are no GF modules connected. If it is actually there, in the same folder as GFConfig.exe, and FSUIPC still doesn't find it, the most likely problem is that the Registry entry for the GFConfig install path is missing or incorrect. Maybe you installed the GF software manually, or moved it later? Or possibly have made a Windows reinstall or rollback since installing? All you need to do is make GFDev.DLL accessible. For FSX you could put a copy in the FSX Modules folder, but you must not do that for FS9 (it will crash). For both, you could simply place a copy in the main windows folder -- Windows looks there also. Note that there's a very recently updated copy of GFDev.dll available in the Updates and other Goodies Announcement above. Regards Pete

Is this with FSX? If so, maybe they sleect views defined in the CAMERAS.CFG file? (in the same folder as the FSX.CFG file). And maybe the number relates to the "HotKeySelect" parameter in that CFG file? Regards Pete

No, not unless it is injected into FSUIPC's TCAS tables by a utility program, so that it looks like AI Traffic -- and that data doesn't include the squawk code in any case. I'm sorry, but there's never been any multiplayer interface facilities in FSUIPC at all. Regards Pete

Yes, sorry about that, but it will certainly be due to that JoystickTimeout. This new feature was intended to remove a much more serious problem for some, that of FSUIPC options hanging because of joystick drivers taking longer than the polling interval to respond. After a lot of testing here and on other users systems it looked like 15 mSecs was the best value, but evidently it is too tight, sometimes. The fact that yours started selectively indicates that a little more leeway would do it, so I'm hoping something between 20 and 25 will be okay. I will also change it so that the timeout only applies in the Axis, Joysticks (Calibration) and Button assignments options, not in normal use within the simulator. However, I won't upload an update until I know the best timeout value to set, one which will work 100% on good joysticks. Regards Pete

Seems as if the Saitek drivers often take more than 15 mSecs to respond. Didn't you read any of the earlier messages in this thread at all, explaining this new Joystick timeout feature and how to adjust it? Please, before loading FS, edit the FSUIPC.INI file (in the FS Modules folder), changing the JoystickTimeout parameter. It will currently be 15. Try 20, 25, 30until you have 100% success. I need to determine a reasonable timeout. Up till now, and now with Saitek particularly, there's been no problems with any devices. And on those folks' systems which hang in the Assignment options because of long-delaying drivers, 25 mSecs timeout wasn't tight enough and 15 worked very well. So, please, do determine what value works for you 100% and let me know. I will change the default, but I don't want to make it too large. Please do not go back to an earlier version of FSUIPC. There's no point in doing that, it helps no one. Regards Pete

There is one possibility I can think of. If you are using Vista or Windows 7 and are running FS and the CPFlight driver at different privilege levels then they cannot communicate -- Windows prevents it. If you are running either of them "as administrator" then the other needs also to be, or vice versa neither of them should be. Another possibility, which doesn't look quite so likely, is that the CPFlight driver needs write access to the FS folders. If FS has been installed in its default place (Program Files), then there would be problems with write access UNLESS the driver was "run as admin", because Vista and Win7 otherwise prevent such access to Program Files. Regards Pete

Probably. You might eant to check that it is up to date though. Current version is 4.41, available from the Updates Announcement here in the Forum, or from http://www.schiratti.com/dowson . Regards Pete

Ah, you mean the Flight Number, for FS's inbuilt ATC? That comes from the Aircraft.CFG file. Which version of Flight Sim are you using? I know you can't change it in FS9 or before, but I you can (according to Microsoft SimConnect documentation) change it in FSX and ESP. However, as it says in the FSUIPC Offsets Status documentation, I don't know if FSX/ESP then actually uses it in their ATC messaging. No one's tried it that I know of. I don't use FS's ATC, only Radar Contact, and you can change your Flight Number / Callsign there quite easily. If you mean FS versions other than FSX or ESP, I don't know any way to change it by program. It isn't really something anyone has delved into so deeply. Sorry. Regards Pete

Is this default scenery? FSX or FS9? Are there any later entries, deleting it? Possibly its runways aren't of the standard stipulated for Radar Contact so don't feature in the RC CSV files? Is that what you want it for, Radar Contact? Short grass runways aren't used much with IFR flights. They may be eliminated because of that. I don't remember asll the criteria Radar Contact wanted at present. Perhaps if you explained your problem? Regards Pete

In case it is still just rather slow at responding, you could try extending the JoystickTimeout parameter even further: like 100 for instance. If it can't respond within a tenth of a second something is definitely broken somewhere. Ugh. That doesn't sound good at all, I agree. Okay. Thanks. Pete

Why is that? You only ever need to go into FSUIPC's options to change them. Surely once you have FSUIPC set up the way you need it, you never have to use the options again, so you can fly in whatever mode you wish? Sorry, what is that supposed to mean? FSX is a different program, with different graphics, and different options. FSX has its own share of problems and they aren't all the same as those in FS9 or any other version of FS. The black screen problems which sometimes occur in FS9 can also occur in FSX, just differently. None of them are at all related to FSUIPC. The most common one in FSX is a completely black screen when swapping between full and windowed mode, or restoring from minimized. I know for sure that last one afflicts a lot of users. FSUIPC isn't drawing the dialogue when you select the option, it is done by Windows using the normal GDI graphics facilities. I suspect the full screen problem is due to some conflict between the video driver supplied library files (DLLs) and the main application graphics support in Windows. It is entirely possible that some such problems are derived from messy video driver updates, where previous drivers haven't been cleared out thoroughly before introducing new ones. I'd recommend not only uninstalling previous versions before installing new ones, by also re-booting in safe mode (without video drivers other than basic VGA support) and using one of the driver cleaners to clean the remains of old drivers before re-booting and installing the new ones. I don't think you need to do this every time, for minor updates, but it would be the first thing I did if i had troublesome conflicts such as those you are seeing. Regards Pete

I'm sorry, but there was nothing rude intended at all. I was only genuinely trying to explain why you have probably never seen the question asked or answered here before, not in the 10+ years of FSUIPC. Why do you think I'm being rude when I'm merely trying to explain things? Odd that no one has asked it in the place they'd be sure of an answer, even if it is one they apparently don't like, as you appear to. Okay. Perhaps that's better for me too if you react so when answered straight and level. I don't understand folks who just don't like the truth. Pete

Well I don't know why anyone would say such nonsense. You can have an FSUIPC installed in all and every copy of FS you might have installed. I have FS2000, FS2002, FS9, FSX and ESP installed on my test system, with FSUIPC3 installed in FS9 and earlier and FSUIPC4 installed in FSX and ESP. Since it is merely a Module placed in the folders within FS's own folder system, and since it only runs when FS is running, why would there ever be any problem? I've never seen it asked, and I cannot imagine why it would be. It's a bit like the question "can I have FS9 and FSX or do I have to uninstall one first" -- it isn't asked presumably because the answer is pretty obvious. What may not be so obvious is that you can't run two copies or two versions of FS on the same PC at the same time. And, for WideFS users, the client installations, where you run your WideClient, can be completely unchanged no matter which version of FS and WideServer is running on the FS PC. The Server changes (the FSX/ESP one is built into FSUIPC4 rather than being a separate DL), but the client does not. Oh, and of course the Keys for FSUIPC4 and WideFS7 are not the same as the FSUIPC3 and WideFS6 keys and need to be purchased separately. Regards Pete

I thought you must already have purchaswed a Key, as you said "I'm trying to register"! You don't need anothere for 4.57! From my experience buying other things from SimMarket (I've never bought FSUIPC for some reason), they do neither. Once your purchase is confirmed you retrieve your Key on-line from the details placed in your account. It's a similar system as many of the on-line shops -- Aerosoft, for instance. Regards Pete

I've answered this at length just a little earlier in this thread, which isn't actually that old (although of course the FSX problem is over three years old). Please do go back and read through it. I don't think I can add anything else at all. I said it all the other day. Maybe that makes it worse? Sorry, but I don't know. I use REX for graphics, but I've always used ActiveSky for the weather -- ASV6.5 then ASX and now ASA, along with FSUIPC4's wind smoothing option. I never have an overstressed aircraft, but there are still occasional severe windshifts, but mostly at low altitudes with low wind speeds. Regards Pete

Please use version 4.57 now available from both the Updates Announcement above and from the usual Schiratti site. Registration of FSUIPC4 and WideFS7 has NEVER been done in the Add-Ons menu, and you don't need to run FSX as Admin. If you look inside the ZIP you downloaded for 4.53 (or for 4.57 now) you will find a document about Installing and Registering. It is provided for a purpose, to actually show you how to do things. Please take a look at it. Registration of FSUIPC4 and WideFS7 has always been done via the Installer, NEVER in FS itself. (FSUIPC3 and WideFS6 registration is now the same, but that is much more recent). Pete