Pete Dowson

Before going into your comments further, can I just ask this? The two buttons you are having problems with -- you did make sure that they are not allocated in FS's own Controls-Assignments, didn't you? Programming them in FSUIPC cannot override any FS assignments, and FS has a way of assigning most buttons it finds on connected joysticks automatically. You'll have to program the button to make the keystroke, then, as I suggested! Of course it is possible! In FSUIPC, go to the Buttons options page, clear your current programming for that button and instead use the left-hand side, where you can make the button produce the Keystroke. Is is actually EASIER to do than programming the controls! This is what I suggested in my last message. Please, please, sometime take the trouble to peruse the FSUIPC User Guide. It does cover all this stuff in more details than I can go into here. That is why it was written, to help you do precisely what you want to do! Regards, Pete

I don't know because I cannot see what you are doing from here. Check the [Programs] section in the FSUIPC.KEY file. That is where FSUIPC will store the Key for each gauge or program or DLL you manually register. Gauges and DLLs need the complete name entering (F16.gau in this case), but EXE files just have the name (drop the .EXE part). The Key must be exact. Cut and paste is safer than typing -- if you do type take care to get the 1's and I's and 0's and O's and 2's and Z's correct. They are easily mixed up. Show me the FSUIPC Log file as well if you are still unsure. Regards, Pete

In that case it sounds like this is one of those panels which constantly sends controls to FS to keep it synchronised with their panel, but fails to recognise changes made by other methods. I think it rather unlikely that you'll get that fixed. The only way may be to give up trying to program the buttons for FS Controls, and instead program the key strokes on the buttons instead (i.e. the left-hand side of the FSUIPC Buttons page). You already said that the keyboard controls worked, right? Regards, Pete

You cannot without re-registering and a new Key code, but it doesn't matter. FSUIPC doesn't use it as an email address, it is just part of your unique identification. Just keep a copy of your FSUIPC.KEY file safe in case you need to enter all the details again one day. Regards, Pete

Sorry, I don't make any radar programs nor gauges. You need to identify the gauges or programs you want to make work and either register them if they are listed in the Freeware Key list (see near top of this forum), or if there is no key listed or the gauges or panels are commercial, get in touch with the author about it. If you need to find the names of the offending gauges or programs, look in the FSUIPC Log file. Regards, Pete

Ah, interesting. That explains the access it tries: Illegal read attempt: offset 7B90, You know, for testing, you can simply temporarily remove or rename your FSUIPC.KEY file, don't you? This won't destroy your registration, it simply won't be effective until you restore the KEY file on a subsequent FS load. Anyway, I think the problem is most likely that Lee is not appending the terminating zero when he sends the Key and gauge name to FSUIPC. This will create inconsistent problems, because whether it works or not then depends upon what used those FSUIPC offsets beforehand. I have been reluctant to give in here and add extra code to FSUIPC to deal with the missing terminator (i.e. add one myself), because it is clear in the specification and programmers should really learn to be careful to follow specifications. However, this particular problem seems to be getting more common and is a nuisance in the extra workload it creates, so I will deal with it in FSUIPC 3.30. Meanwhile I am still awaiting a Log file from Dietmar with IPC write logging enabled so that I can verify that this is indeed a correct diagnosis. Best regards, Pete

Is that with everything full up in FS? If so, and it's with the panel as well, that's maybe all you can expect. What total screen resolution are you using? Well, I'd get rid of the panel. If you can get that on a separate video card, or, better, not use FS panels at all and use FreeFD or Project Magenta or whatever on a separate PC, that helps. Without the panel you can use a lower resolution and it still looks good. I am using 2400 x 600 (i.e. 3x 800x600) although my three LCD monitors would allow me to go to 3840 x 1024. For scenery only I don't really miss the extra resolution -- in fact I think the lower resolution is better for scenery, looks more realistic. Certainly the Parhelia is not a fast card. I use a Pentium 4 3.2GHz and the Parhelia gives me around 20-30 fps most of the time. It drops a bit at night (why a few lights take more power to render than loads of textures I don't know), and also when there a lots of clouds. Providing it never drops below 10 I'm reasonably happy with it. Apart from that, and maybe going for an Athlon 64 FX 53 (faster processing always helps), all I can suggest is that you play with some of the FS adjustments till your happy. At present there's nothing that will do what the Parhelia does, and unfortunately Matrox don't seem to be thinking of bringing out a faster version. Regards, Pete

FSUIPC Visibility options, limits. There are several according to clouds etc. To limit it all the way up you also need to use the graduated visibility and set the top target visibility to whatever you want. Is this not clear from the documentation (FSUIPC User Guide)? There's quite a bit on visibility options, and the limits, smoothing and graduation all work no matter where you get the weather from. Regards, Pete

Okay, you sent me the details in a private message. I am posting the reply here because I am sure others will be interested. And then, when you press the button you get flashing lights? They keep flashing all the time or only when the button is held down? In the latter case it sounds like the button is repeating -- maybe either you have FSUIPC repeating it, or the Joystick driver is. In the former case, if after you press it and release it it then continues to flash all on its own forever after, then EITHER something else is interfering with the lights (try the default FS 737 to see if it is something in the specific aircraft), or the button itself is staying "on" and you have some repeat action operating as before. What happens if you instead program the Press for "Landing Lights On" and the Release for "Landing Lights Off"? In all cases ensure there is no repeat enabled. And please test these things with default aircraft -- it is impossible for me to know whether there's something in the add-on aircraft code which is interacting. Regards, Pete

But I have not been able to even start to help you, because you have not once answered any of my questions! I still don't know what FS control you tried, what sort of switch you are using, what you are trying to do in the FSUIPC Buttons page! How can you expect me to help if everything I ask you is completely ignored in this way? :cry: :cry: :cry: Pete

Yes. Its the great TCAS gauge by Lee Hetherington. Is there a key for this one? It works perfectly with AI traffic but not with SB/Vatsim and AI Bridge 2.0 or 1.0. As I said earlier, ILH_TCAS.gau was given a Key back in July 2003. It is probably built in. I am awaiting the results of your re-run of the registration error with more logging enabled so I can diagnose it for you. Please review this part of my last message: As for showing multiplayer traffic, that is 100% a function of AIBridge. Maybe you need a later version -- I don't think the one on the Schiratti page is the right version. You need to go to Jose's own page. There's another recent thread here somewhere which discusses that and provides the link. Regards, Pete

I didn't mention navigation. But surely relying on something like FS's dubious scenery and terrain for such awareness could easily mislead you into thinking you were safe when not (or vice versa, of course). It still sounds pretty fraught to me! :wink: Regards, Pete

Sorry, I don't understand. Where do you get that from? The fix for FS control acceleration from certain panels is a Technical Page option which has been in FSUIPC for a long long time. Actually I think I misunderstood your original question. You said; "The exact thing I want to do is to eliminate that exponencial response from my joystick - less sensitive in the center sections and very sensitive in the outer portions - making the control response of my joystick linear." This is in actual fact the EXACT opposite of what most folks want and the opposite of the response curve facilities I have added in 3.30. The standard response provided by normal joystick calibration is linear. The facilities I am adding provide a nice flatter, less sensitive, response near the centre, sloping (parabolic fashion, not exponentially) steeply at the extremes. This gives much more precise control in the normal flight ranges without losing the ability to reach the extremes when necessary. It sounds like your joysticks give you the sort of response folks have been asking me for, already. If you are talking instead about the time-based response system built into FS since FS2002 (or was it FS2000? I don't remember), just add "stick_sensitivity_mode=0" to the [Controls] section of your FS9.CFG file. Regards, Pete

Sorry, that's pretty meaningless to me. What is the IVSI bit? Is that relevant? Is this "TCAS II" the ILH_TCAS.gau? If this is a legitimate gauge and it is supplying the Key, then the most likely reason for the problem is that the programmer hasn't added a terminating zero, despite this being clearly part of the specification. If you enable FSUIPC IPC write logging just before loading the aircraft concerned, then the data logged will show me what is going on. If this is the case there are three possible courses of action: 1. Write to the gauge author, pointing out the problem and getting it corrected, or 2. Paying for and registering FSUIPC as a User so you don''t get any of these problems again :wink: , or 3. Hoping that I can work out a way of detecting this failure to abide by the specs, and thus working around it. If I do this is won't be until the next version of FSUIPC (3.30), maybe next week. Let me know. Regards, Pete

The ILH_TCAS gauge was issued with an access Key back in July last year. Is it an older version? Check the date on it, and see if there's a newer one. It is odd in any case. The offset mentioned, 7B90, is not normally used by Gauges -- I think that one is reserved for Squawkox 3. Please always mention the version of FSUIPC you are using too -- if it is not 3.22, the current one, please retry with that. Regards, Pete

Strange. I didn't think FS was supposed to load extra modules except from the Modules folder! I will have to watch out for thatthanks for letting me know! Pete

Sorry, what does that mean? This proves conclusively that the WideServer.DLL in your FS Modules folder is version 5, not 6, as there is no way version 6 will run at all with FSUIPC 2.93. I am very sorry, but really, it is not possible. There is no way a version 6 WideServer will run with a Version 2 FSUIPC, they are completely and utterly incompatible. Everything you say is convincing proof that you have a version 5 (or earlier) WideServer installed. In your last message you showed me the FSUIPC LOG, but it is the WideServer LOG which shows the WideServer version. Why don't you check that? Possibly you have renamed an older version of WideServer but still left it in the FS modules folder? To check versions of any of my modules, right-click on them in Explorer and select Properties - Version. Regards, Pete

There is no such message in version 6 of WideFS. I think you must have a version 5 WideServer installed in your FS modules folder. The version 6 WideFS would say "This version of WideServer requires FSUIPC version 3.00 or later!" if the wrong FSUIPC was installed. Please show me the FSUIPC and WideServer LOG files if you need further help. Version 5 of WideFS cannot be used with FSUIPC version 3. Regards, Pete

Ah, so you want FS to show you the world around you? And you will BELIEVE it whilst flying? That sounds extraordinarily dangerous -- I bet that could get your license removed! :wink: Actually FliteMap displays whatever you ask it to, not in 3D of course, but it does provide topographical information if you want. So of course do many other map programs. I still think that this could be highly dangerous. But still, if you want to go ahead, yes, with FS2004 and FSUIPC you can control the position of the aircraft in all 6 degrees of freedom (LLAPBH -- Latitude, Longitude, Altitude, Pith, Bank, Heading). You need the FSUIPC SDK (from http://www.schratti.com/dowson), and of course some information to allow you to interpret the output from your GPS or whatever. There may already be some implementations of this sort of thing -- not for real time cockpit use as far as I know, but more for recreating real flights on the PC afterwards. Try a search in this Forum and elsewhere. Regards, Pete

You can't get any data to have errors in unless WideFS is registered okay, so this is getting weirdly away from your original report. If WideFS is registered, the button beneath that text is disabled and the text on it reads "WideFS is registered". Isn't that clear enough? Sorry, but I don't think I've had any other misunderstandings like that. Your report said this: and it is surely this that we were out to resolve? Can I see what this modal dialogue looks like, please? And at least I need the WideServer LOG file showing this part, because that is where the relevant error message will be. You've not shown me that yet. Looking at the Client log you did send, it seems that the connection is timing out all the time, every 10-12 seconds. I can't tell why without the Server log, and even then it may be difficult, but it certainly looks like either your have a network problem, or the FS PC is unable to give WideServer enough time to process messages. Have you been making any changes to the WideServer or WideClient INI files? If so I'd recommend to retest with the defaults (plus of course the ServerName addition at the WideClient end). Regards, Pete

No. By "another com" do you mean a PC? Running Wideclient? Is WideClient connecting okay? When you run an FSUIPC application on WideFS, it is WideFS those aplications talk to -- if you aren't getting WideClient connecting to WideServer, none of the applications will ever see FSUIPC. Well you are missing any information which would allow me to help at all. Check the WideClient and WideServer logs. When you reloaded everything, did you configure it according to the documentation? I really cannot help unless you tell me more. Pete Thanks.Camtech

Okay. So we need to identify what changed at that time. Can you recall what you might have installed or changed? From the logs I see that the aircraft you are using is accessing FSUIPC in an incorrect (illegal) way. I'm wondering if that was something you installed about that time? BTW, I just noticed that you said: ... but HOW do you see from the dialogue that WideFS is not registered? There's no such message for that in the dialogue -- the button is enabled if it is not registered, it is disabled if it is registered -- so it sounds like the dialogue shows it correctly registered, as do the FSUIPC and WideServer Log files you sent. Unfortunately, however, you seem to have loaded FS and closed it 22 seconds later, so although WideServer is running okay and awaiting clients, it never gets any before you terminate things. And I see you are using FSUIPC 3.21. Please recheck with the current one, 3.22, as released about five weeks ago. Thanks, Pete

A moving map? Surely you want a moving map program as a moving map!? There are good moving maps around which take output from GPS's. But FS isn't one, nor do I make any. I use FliteMap, but there are cheaper ones. Even Microsoft's AutoRoute programs will work. Erto do what, exactly? I'm evidently not understanding. Regards, Pete

For six months? Did you not think it worth reporting till now? My eyesight problems make it much more difficult for me to deal with such things now, whereas maybe I could have attended to it any time in the last six months! For "many months"? With FS2004? Then 6 months not? I need WideServer and FSUIPC Logs, and your FSUIPC.KEY file. Please don't post them here. ZIP them and email them to me at petedowson@btconnect.com. I will deal with them when I can, but I'm afraid it may not be so quickly at present. Regards, Pete

That's a rather inappropriate start, isn't it? :o All BGLTXTS did was scan the file, completely ignorant of its structure or anything, looking for strings which matched the 8.3 layout of old DOS-type filenames. It became useless long ago when the BGL statements calling up textures could use long filenames and paths and all sorts, apart from also referring to many standard textures by reference numbers instead. Sorry, I really don't know much about any BGL utilities these days. Regards, Pete