Pete Dowson

I get that too, sometimes. Only at night. In my case I'm pretty certain its the Matrox Parhelia video drivers I'm using, but they are so much faster than the previous versions that I stick with it and do only day time flights. These CTDs (yes, that's the semi-official acronym! :wink: ) were much more common before the 9.1 update, and most are fixed. But one of the major causes used to be seasonal texture problems, during the changover periods of late Spring and late Autumn. Maybe vertsion 9.1 hasn't fixed them all -- try setting the FS date to mid Summer or later Winter and see if it makes any difference. Otherwise, things to check include overheating in the video card or processor, and maybe updated (or older?) video drivers. No. There's only one error there -- the Service offered by WideServer suddenly disappeared. It will have disappeared because your FS crashed. You are getting cause and effect the wrong way around! :wink: Regards Pete

No, sorry. There's no useful information in those in any case. If you are still using FS2004 original release, try updating with the FS9.1 update. It fixes a lot of possible "crash to desktop" problems. What issue with WideFS and ActiveSky? None has been notified to me. What a strange thing to say. As for "working closely", I've always supported programmers in interfacing to FSUIPC. Damian in not the only application prtogrammer to receive answers to questions and advice from time to time. Please explain yourself a little more clearly if you want proper answers, eh? :wink: Regards, Pete

I really know nothing at all (sorry) about SBRelay or HostSB, but I do know that quite a lot of people do run Squawkbox on a WideFS Client PC. DirectPlay is part of the multiplayer side of things. It isn't handled by WideFS -- that only deals with the FSUIPC interface to FS. It sounds like either you need to install a later version of DirectX on the Client, or possibly Squawkbox has to be run there first. But I don't really know. AVC is not an FSUIPC interfacing program, of course, so it isn't dependent upon any of the rest of that stuff. I hope someone who knows about Squawkbox stuff can jump in and help here, otherwise you would really be much better off asking in one of the on-line flying forums. Isn't there one for the service you want to connect to? This forum is really for technical help with FSUIPC, WideFS and so on, but most of the stuff your talking about has to do with TCP/IP links and multiplayer. I think the FSUIPC interfacing part is relatively trivial. No, don't tweak anything. If the Client is connecting, that's it. The rest is up to the programs you run. Regards, Pete

There may be an FS control in the drop-down list which does such a thing. I don't know, really, sorry. The drop-down list of controls in both Buttons and Keys pages of FSUIPC are mostly listing controls from FS -- the names are actually from the CONTROLS.DLL in FS and vary from version to version of FS. There are additional controls added by FSUIPC, but none for such a function as you describe. I certainly have never had anything in any of my FS add-ons which change things in any FS CFG file. Are you sure you are not thinking of some other add-on. FSAssist or something? Have a scan through the FS controls. Perhaps some of the names there may ring a bell. I included a PDF document listing all the FS2004 controls in the latest FSUIPC ZIP (3.411). Regards, Pete

Good! I'll make a release later in the week. I've got quite a few bits and pieces to put together for release soon. Regards, Pete

Maybe its sort sort of video driver issue. Try in windowed mode as well as full screen, and also see if looking out the side window then back brings the display back. Also, if you use the 2D panel try the VC and vice versa. Regards, Pete

Impossible to fly an aircraft just because of a DME problem? Phew! I'd scrap that aircraft and get one far more flyable if I were you! :) No, the DME value from FSUIPC is available all the time. But panels with normal DME gauges certainly won't be using FSUIPC for that. The DME distance is a standard panel value. It's been available to panel makers for as long as I remember, certainly since before FS4 even, and I know of no panels which depend upon FSUIPC for it, none at all. I think you will need to visit the PSS support forum. Regards, Pete

No, there never was any such option in FSUIPC. Only in FS itself that I recall. It's for 2D panels only I think. Regards, Pete

It isn't possible. FSNav is an FS module, not an external program, and it doesn't even use FSUIPC at all. WideFS provides a Network copy of the external program interface to FSUIPC. It works with any separate program which uses FSUIPC to interface to FS, as stated near the beginning of the WideFS documentation. It cannot possibly work with thnigs which don't even use FSUIPC, nor with anything installed into FS, like aircraft, gauges, panels, scenery, and DLLs like FSNav. Regards, Pete

Can you please try the attached test version (2.131) and let me know. I can't see any measurable difference here, but I've made a change in the code to avoid checking for a panel change within 10 seconds of my previous check. I hope this will get around the problem without any unwanted side effects. Regards, Pete AdvDisp2131test.zip

What, exactly, "talked" in this way? What was the message and when/how/where did it appear? Check the FSUIPC.LOG file (in the FS Modules folder -- show it to me if you don't understand it. You tried to register what, exactly? Did you go to SimMarket and purchase a Key? If not, where did you get the key? I always do, but I'm afraid I need quite a lot more information if you want me to help you at all. To start with, the version number of FSUIPC is important -- either read it in the FSUIPC options, ALT M F in FS, or right-click on the FSUIPC.DLL file in the FS modules folder, select Properties-Version. Regards Pete

I can take a look. Run something that replicates the problem. Close FS, then ZIP up both the FSUIPC.LOG and FSUIPC.KEY files (both from the FS modules folder) and send them to me at petedowson@btconnect.com. Regards, Pete

Thanks for the info and the offer, but really, unless there are already applications which can be used on PCs which can operate using this method, I don't see any point in me spending time on it, at leat not at present. I've too much else to do as it is, and adding Ethernet support to GPSout is not going to be trivial even if it were simple TCP/IP packets. If they are using their own packet protocol then it gets even more complicated. Regards, Pete

Lee, Since this last Forum message of yours we have exchanged several messages by email. The last such email I received from you said I must admit to not seeing anyone else here asking since your good self, but what is more puzzling is that I am still waiting for confirmation from you that version 6.418 of WideClient, sent to you on the 8th December, works okay. You seem to have sent me a message which indicates that you are no longer seeing my emails. This is made worse by the fact that I replied to your last email 31 hours ago, again attaching the Wideclient, and this time as a priority message, and still I have seen no acknowledgement. The messages are not bouncing at all. I can only think you are either ignoring them, or that they are being deleted at your end as spam, for some strange reason. I am hoping to make a release later this coming week or WideFS 6.44 and would like to be able to document how to use this new facility to enable PTT programming for Teamspeak. Do you think you could try the latest Beta for me, please, and let me know? For information, I append my message of the 8th below. Regards, Pete ====================

That's fine, but where's the PC software with such Ethernet reception capability? Regards, Pete

Ah, well, in that case it is still a puzzle, as the loading times for all the default aircraft, for example, are identical here no matter which version. I can only think that the answer lies there somehow. Pete

It certainly is. I note you said I have all the PMDG 737NG aircraft, and my system is a 3.2 GHz Pentium 4, but with WinXP Home SP1. Can you tell me exactly which cockpit you have this problem with? Better still, save a flight amd send me the FLT + WX file for it -- send to petedowson@btconnect.com. Have you got WinXP SP2 installed? I've been thinking about it but have so far resisted. Regards, Pete

No, because there's no point. What is at the receiving end to "feed" the program the NMEA data as if it came over a serial connection? I don't know of any programs accepting stanard NMEA data over Ethernet. Yes, Regards, Pete

It won't be AdvDisplay doing any of that. The only change was to deal with the case where the SAME aircraft was loaded again. There's no other change to any part of the code, whatsoever, and certainly when loading a different aircraft the actions are identical. All it does it find a window part to attach to. There's something else going on in your system. Sorry. But, of course, please yourself which version you use. I just can't support older versions. Regards, Pete

Sorry, I can only support current versions. No one ever actually reported that, and it is too late to fix it in an old version now. Left on both Captain's and 1st officer's yoke? Doesn't sound right. The outside handle in each case is already pretty busy with the trim rockers (two), A/P discon and PTT buttons. I think that there may sometimes be a CWS enable button too, for emergency temporary A/P override allowing elevator and airleron control whilst held. I'm afraid I cannot make anything out in the picture you sent, but thanks anyway. It may be that the particular airline your friend works for has had extras added. There's certainly no mention of any MCP control on the yoke in any of the 737NG references I've got -- a full 15-volume Continental 737NG AOM, and the official Boeing computer based training package, and, of course, Bill Bulfer's excellent 737NG cockpit companion. Regards, Pete

Ah, there you go, then. That's the winds explained. Ah, I was reading the "airport AWOS" as identifying the airport! :wink: Unfortunately, FS2002 uses AMSL for its cloudbases, throughout -- including, most incorrectly, its ATIS reports. You can check this yourself -- in the Advanced Weather dialogues the values are AMSL, with the aircraft shown at its appropriate altidude in the graphic even if it is on the ground. The "Base" value in the dialogue is AMSL. Compare that with your ATIS report. Yes, but where was what reporting the winds at 17000? Is 17000 exactly one of the levels listed in the upper winds list? The winds aren't "fixed" in static layers, but blend into each other as you climb or descend. This is why I suggested using Shift+Z to find the ambient wind actually present at the aircraft. With a good weather program like ActiveSky you will also get the winds changing as you fly between METAR stations, so unless you are directly above the Lat/Lon of the station reporting the wind you are reading, it won't necessarily apply in any case. The wind could be changing to match the METAR reports of the other stations around you. Regards Pete

But evidently no one cares enough to have bothered to do so. If they want help to resolve their problem they know how to contact me. Regards, Pete

There's no change at all needed in keys for the life of Version 3 (FSUIPC) and 6 (WideFS). The only keys which won't work are those blocked for any reason, like non-payment, or illegal actions such as publishing them for others to use. You are probably not entering all the details correctly. it isn't only the Keys which have to be entered exactly right, but also the name and email with which they are associated. All three entries must be exactly as originally notified to you. Regards, Pete

So what's this to do with winds at 17000 feet? You seem to be reeling off loads of disconnected observations none of which helps paint a picture at all, far from it. Where is AWOS? It isn't in my index of airports, nor in my Jeppesen database. If fact I cannot even determine what country it is in -- the AW prefix doesn't seem to be used. What is the magnetic variation there? The METAR reports will be in degrees TRUE, the surface winds in FS2002 are in degrees magnetic usually. If the mag var is around 14 then they would match. The difference in speed between 15 and 16 is probably rounding and can be ignored. The difference in cloudbase wouldn't be the ground level, would it? Perhaps one is AGL and the other AMSL -- I think some of that stuff is confused in FS in any case. I'm not sure how any of this report possibly relates to your last one. If you are using FSUIPC's wind transition facilities (or those are switched on by ActiveSky), then the FS winds are controlled purely by having only one FS layer. This allows FSUIPC to control the smoothing which can otherwise be a problem in FS's own layering. Please take a look at the FSUIPC User Guide some time. A lot of this is explained there. Pete

If no one wants to come and ask questions or report problems here then I don't want to know. I gave up chasing things like that a long time ago. I have enough to do as it is, to waste my time that way. Obviously it's either of little consequence or they all realise they are using stolen or counterfeit Keys and don't want to show their faces. Regards, Pete