Pete Dowson

Er .. are you saying that these indications were in the FS panel DME display? Sorry, I thought as you were mentioning FSUIPC in this context you were talking about a Project Magenta DME display, or some other FSUIPC-fed one. I'm afraid FSUIPC has nothing whatsoever to do with any of the displays in any of the standard FS panels, and only a few of the displays in some of the add-on aircraft --- mostly just the TCAS targets for AI aircraft. Please confirm. Regards, Pete

I've deleted your private details from your message. Never show such info in public, please. I know you hid part of the Key, but the other details are private to you too. As described in the FSUIPC user guide, both registrations need to be under the same name and email. It also says that if you state this need when you order then SimMarket should be able to oblige, but if you face difficulties (they are automating things so this is a possibility) you can always send me details of your original FSUIPC purchase (privately, not here -- send to petedowson@btconnect.com) AND your new WideFS purchase, and I will change one or the other so that they match. Regards, Pete

Sorry, it means little to me. most crashes in WEATHER.DLL are a result of corrupted WX files in my experience, but they are few and far between these days on FS2004 after the 9.1 update. One thing that would concern me, though, and may well be a contributory factor: This appears to indicate that you have an original issue 9.0 version FS9.EXE being used with the WEATHER.DLL from the 9.1 update -- you can see this clearly from the version numbers, and of course the dates (30612 = 12 June 2003 compared to 40901 = 1st Sept 2004). I'm wondering how many other mixes between the two versions you have. I wouldn't trust any of it with such a mixture. Possibly this happened because you used a No-CD hack for the FS9.EXE which therefore wouldn't be updated by the FS9.1 update? I think you might wish to consider uninstalling it completely, then installing the original from the CD's, after which applying the complete FS9.1 update. Alternatively, if you check ALL the FS9 DLLs in the Modules folder, and they are all dated 1st Sept 2004 or later, maybe replacing the FS9.0 EXE with the no-CD version of the 9.1 EXE might work. I'm not sure where you'd get it though. Obviously it isn't an officially sanctioned file! Regards, Pete

I never thought you did. The way of getting MP targets into the TCAS tables in FSUIPC has been available now ever since soon after the TCAS tables were added, for FS2002 I think (?). The documentation in the FSUIPC SDK explains how it is done. Programs like AIBridge and Squawkbox has been doing it for a long time, and they work with MP traffic showing in PM's TCAS. I don't see why it cannot be fixed by the VoxATC author if he wants to do so. Why don't you report the problem on the VoxATC support site, if there is one? Maybe he is simply not aware of what he needs to do. Regards, Pete

It doesn't change on the paper clip, but on the word below the paper clip "download". That's the 'button'. Pete

It isn't a button in the usual sense, there's a paperclip symbol with the word "download" below it. When you move your mouse over the word the pointer changes to a hand and the "download" word gets highlighted. THEN you press your mouse button. If you don't see any of this, maybe you have some security options set to hide them in your browser? Regards, Pete

Sorry, where? None intended I assure you -- sorry if you mistake my English. I am glad you brought up the problem and found the cause. As i said, I think I will change the default value for the RestartTime as a consequence. So it has been useful, thanks. 99M is provided when there's no reception as well as when too far away. I really don't understand where you are coming from with this attitude, but if you don't like the way I phrase things I am sorry. Have a good life and enjoy flying. Bye. Pete

Ah! you found the documentation! Good. ;-) Hmm. Never seen any stutters caused by that. Sounds like the drivers for your Network have a lot more to do than most -- I wonder what happened in the SP2 update. Also, if that was the cause, the stutters should have disappeared as soon as you have an active client -- the restarts only apply whilst nothing is connecting. Well, only if it won't connect. If everything behaves itself you should have no problems. A lot of those "sledgehammer recovery" techniques date from times with Win98 and WinMe or mixed protocol networks, where clogging up seemed to be more common. Maybe I'll assume systems are better behaved now -- in FSX I think I'll set the default for that to 0. Regards, Pete

Yes, as described in the documentation. it's the Broadcast port. Until WideServer sees clients it won't have any Client names -- it isn't clairvoyant! ;-) Pete

That in itself itr quite a change. However, all my systems are now on SP2 and I get no stutters. Yes. Did you see the documentation at all? It is called "WideFS.DOC". There's a PDF version too. It is all explained in there -- you will find documentation in the WideFS ZIP. Maybe, but unlikely if it happens with no Clients running, because then WideServer is doing little. But check the Log yourself and show me if there's anything suspicious. Pete

And what about the creation of the Modules folder in FSX, which doesn't exist initially, and the creation or editing of the DLL.XML file in the same folder as each and every instance of the FSX.CFG file? There is much more to installing modules in FSX than there ever was in previous versions of FS. I do not want to have to support your installers because you don't get it right. You show me your module installer working, and then I'll consider supplying just the DLL (not that you cannot get it for yourself, of course, after running my installer). If you want to know how to do this, simply look at the SimConnect documentation in the FSX SDK, supplied with the Deluxe Edition. Pete

Yes, but that's not the same as CREATING multiplayer traffic. As far as I know you can't have MP traffic and AI traffic both active at the same time -- in Multiplayer mode the AI traffic facilities are switched off. In Radar Contact the ATC is coordinated between AI traffic as well as the user quite well, using facilities provided in FSUIPC. But of course Radar Contact is designed to work with AI, not with Multiplayer at all -- really there's no need as MP traffic is generated for on-line ATC, via Squawkbox and Ivap. What problem? So far you have not described any problem. You merely asked about facilities to do with CREATING traffic, and as I said I know nothing about creating traffic. Certainly I can't see there's anything to discuss between VoxATC's author and PM's author. There is no interaction between them, nor is any needed. Maybe you'd like to start over, and explain EXACTLY what it is that is troubling you, as it is now a complete muddle? You confused FSX and FS2004, and then Multiplayer with AI traffic. Would you like to try again? ... and you do mean Multiplayer, do you? Not AI?? There's a world of difference and they don't mix? If that is all you mean then it sounds like an error on VoxATC's part, not writing the MP data to FSUIPC so that it can be picked up. It is nothing to do with PM -- it would also not be seen by other TCAS gauges and programs. The VoxATC author only needs to refer to the information in the FSUIPC SDK. Regards Pete

Why? You can include the installer and execute it. As well as being sure the DL.XML is correct, my code checks for a later version of FSUIPC4 and won't overwrite one -- something which has been a real pain in my side when I allow others to install. Maybe you take care of such things too, but it is by no means a general practice. Please, tell me why your installer cannot run the FSUIPC4 installer? Pete

There's nothing in any of my software with such a period. It sounds like something related to your network -- could the way you have the network configured be doing it? If you don't have specifically alssigned IP addresses, Win98/Me used to give regular stutters. I don't know if there's anything similar in XP, but it may be worth a try. The other thnig XP SP2 seems to do automatically when you upgrade is enable its firewall. maybe you could check that? also try disabling WideServer's broadcasts -- by default they are every second, so it doesn't sound like them. If you set the interval to 0 it won't send any. Regards, Pete

Very clever. It must get pretty busy if it generates enough to populate FS like AI traffic. I wonder why it does this. Isn't AI traffic good enough? Well, Radar Contact performs ATC instead of FS9, but it interacts with AI traffic. True, it doesn't do a lot of control of AI (it stops them interfering with the user, but otherwise its instructions to them follow what their plan would get them to do in any case). But the advantage of this is that you can use Ultimate Traffic, or My Traffic, or FS Traffic 2005, and have a fully populated AI traffic world. Doing it with Multiplayer horrifies me - the PC you'd need for that must be really top notch!? You can't generate AI in FS2004 (well, not via supported interfaces), only multiplayer, as you said. You should be careful not to mix these terms. They are totally different. PM won't talk to any ATC program, nor vice versa. PM provides aircraft instrumentation, it isn't a pilot substitude. ATC interacts with pilots, not instruments. Regards, Pete

Sorry, no. Don't worry, it will all run with super-efficiency from the 'Go'"! ;-) Pete

In FSX? Have you actually managed to get a Multiplayer SDK for FSX? I didn't think one existed. As far as I knew, folks doing Squawkbox and other on-line links are having to use SimConnect facilities instead, to actually generate controlled AI traffic rather than multiplayer. Do you know differently? And VoxATC actually CREATES traffic? How does it do that? It surely never did so in FS2004? The same options are provided in FSUIPC4 for injecting aircraft into the TCAS data offsets which PM reads. FSUIPC4 is compatible in almost every regard to FSUIPC3, at least as far as I have been able to make it and as far as I have received feedback. I really don't know if anyone has yet tested the AI injection facility though -- I've had no feedback on that at all as yet. If there's a but I will fix it, but I cannot test that at present. Regards, Pete

How would anything know where you are going? If you've loaded a PLAN into FS, then maybe the information in offsets 6000 and following provides what you need? Pete

Sorry. No. If the MCP is pausing on the FS PC it sounds like FS is pausing too? Or are you just talking about Client-based PM software? If so, it sounds like it may be video driver or card related on those PCs -- PM PFD uses OpenGL. You are more likely to get knowledgeable assistance with PM problems on the PM support forum/webgroup. Regards, Pete

You are misunderstanding completely I'm afraid. It is perfectly consistent. FSUIPC has no idea whatsoever what YOU or /your aircraft calls your flap positions. All it knows it that for the current aircraft there are N detentes, including the full up and full down positions. These are simply numbered 0 to N-1. Your "0, 1, and 2" are not DEGREES but numbers. They continue 3, 4, 5 etc. Completely consistent and exactly the same for all aircraft, only with a different end number. In FS the value FSUIPC has to set to get to each flap positon is completely independent of the angles too -- the range of values is simply equally divided by the number of positions. Have you an idle notch with a reverse zone, or don't you want any reverse on the throttle levers at all? Movement is irrelevant to FSUIPC -- it is only when you click the buttons that anything is recorded. When you say "back to idle" where is that in relation to the lever movement? If you are using the FSUIPC page for separate throttles, the "Idle" setting is the CENTRE setting, and there are TWO buttons. Both need to be pressed, with a range for idle. But before you do any such thing you should start with the full reverse button, setting that. Why don't you just follow the numbered steps in the documentation, like many before you, instead of inventing your own steps and taking 5 hours to get them wrong? Use throttle sync. That syncs the lever position to give the same input values to FS for each, please check the user documentation. Can't be done -- these are all different for different aircraft, and as far as FS and FSUIPC are concerned they are simply sequential positions, 0, 1, 2, 3, 4, 5,etc. Such a method suits ALL aircraft and is surely easy to understand. If you don't please use a pieve of paper and nymber your flap position names. Pete

Installer. This is only because there is no place in FSX for it to be installed -- the installer makes such a place -- and because installation involves editing of an XML file which may or may not already exist. If this is not done, FSX will not run FSUIPC4 so it won't be any use. I'm afraid there's no way to do it by simply copying over a DLL. Only FSX at present -- hopefully all future versions of FS as well. It is a completely new version. It has been set at 24 Euros (plus VAT in the EU), a small increase from the original price for FSUIPC3 set over three years ago. Regards, Pete

So, have you since tried with the correct version of the Server? I didn't want to see that, it isn't relevant. Er .. this conflicts with your earlier statement? And that conflicts with both?? Okay, this log is from the 6th October. And it is good -- though not a lot of use because it isn't a complete log. Please ALWAYS close FS (and all your Clients) before showing a log, because a lot of vital information is presented at the end. Erthis is a Log from August? Please, I need logs from each end which correspond with each other! Again, this Log doesn't terminate, so is not very useful (apart from dating two months differently to the Server), and it shows a seies of reconnections every 23/24 seconds. something is obviosuly wrong (or was then), but what isn't clear because there's not enough information. Does TrafficLook run okay on its own without all those? Is that all? I thought you said the Server was heavily loaded? Questions you forgot: What versions of Windows on each PC? What frame rates on FS? What is the frame rate limiter set to? Pete

No, there is no pointing to be done. WideClient presents an FSUIPC interface, almost indistinguishable from the same one on the FS PC. That's the whole point of WideFS. It sounds like there is something wrong with your Network. If you'd care to show me the WideServer and WideClient Log files and INI files, maybe I can spot something. Maybe you have so much running on the FS PC that little time is left over for the Network? What PC is it, what Windows version? What are your FS frame rates? Do you use the Frame Rate Limiter, if so what value have you set? And what is "the other program" on the client you say it works with? Is that running at the time you try to use TrafficLook? If so are you sure that's not hogging that PC? Finally, what are the version numbers of TrafficLook, WideClient, WideServer and FSUIPC? Regards, Pete

Because of a bug in the current version. Please check the Interim Versions announcement above and download 3.709 (the bug was fixed in 3.707, the day after it was first reported). Regards, Pete

Okay. Odd that, but I'll document it using P_R_C. Thanks! Pete