Pete Dowson

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

No, TrafficLook is just a standard FSUIPC-interfacing program and works fine on a WideFS client - in fact that's how I use it most of the time. I think in some older versions you needed to wait till FS is running before starting it, but version 1.55 should start okay either way. Regards, Pete

It wasn't MY assignment! Please read the thread a little more carefully. I asked Peter for HIS assignments, so I could understand exactly what he has done, so that when I document it I will know it works! This is because I have no way to test it here! Just copying someone else's assignments to your INI files won't necessarily work. Your hardware may be different .. as I see it is! So, you assigned all the Hat buttons as if they were on joystick 1 and expected them to work from joystick 0? If you KNOW what you are doing, try editing the assignments you copied to make them address #0 instead of #1 as they do now. You can see the 1's, can't you? Otherwise, why not simply do as I suggested. Delete those you added and go and do the assignments properly, via the FSUIPC Buttons tab. you know, the one in the FSUIPC Options when you load and run FS and press ALT M F. I did explain this. Please, what is the problem now? Regards Pete

Do you mean Pete or Peter? ;-) I assume you made sure there were no duplicate numbers on the left? You copied them literally, no changes? Is your CH yoke joystick #1? The reason I put the names in my copy was so that you could do all those assignments in FSUIPC's buttons tab -- then you'd be sure. Check in your INI file, are the other CH buttons all joystick 1 (1,)? Or look in FSUIPC. When you press a button, what does it show? If FS is doing something then one of those button numbers is being seen as "ON" initially -- if you are looking straight up, then it sounds like 1,32 is on all the time. Without knowing what you have connected I wouldn't know what that was. If you don't know how to edit and interpret the INI file, I wouldn't mess about with it if I were you. Program the buttons in FSUIPC's Tab. All you need to know from the list above is the "R..." is for Press and with the button Repeating, whilst the "U ..." is for Release ("Up). So you do two assignments for each of the hat positions which look like buttons 32-39. Pete

Okay, I'll annotate those, so: 41=R1,32,C65734,0 ; PAN_UP 42=U1,32,C66415,0 ; PAN_RESET_COCKPIT 45=R1,33,C65856,0 ; PAN_RIGHT_UP 46=U1,33,C66415,0 ; PAN_RESET_COCKPIT 43=R1,34,C65672,0 ; PAN_RIGHT 44=U1,34,C66415,0 ; PAN_RESET_COCKPIT 47=R1,35,C65857,0 ; PAN_RIGHT_DOWN 48=U1,35,C66415,0 ; PAN_RESET_COCKPIT 49=R1,36,C65735,0 ; PAN_DOWN 50=U1,36,C66415,0 ; PAN_RESET_COCKPIT 51=R1,37,C65855,0 ; PAN_LEFT_DOWN 52=U1,37,C66415,0 ; PAN_RESET_COCKPIT 53=R1,38,C65671,0 ; PAN_LEFT 54=U1,38,C66415,0 ; PAN_RESET_COCKPIT 55=R1,39,C65854,0 ; PAN_LEFT_UP 56=U1,39,C66415,0 ; PAN_RESET_COCKPIT Interesting that you found "PAN RESET COCKPIT" was the one to use. I see there's a "PAN_RESET" too (65875) which, from its numbering appears to be more associated with the other controls you've used. Did you try both? Any difference? Thanks Peter. It looks complete -- 8 buttons down and up -- can't be any more ;-) Best regards Pete

Please check the Interim Versions announcement above and download the latest FSUIPC (3.709) from there. It is a bug with saving some types of aircraft-specific changes, fixed in 3.707 as you will see. Regards Pete

Ah, yes, by assigning to each of the 8 buttons a POV_VIEW with the appropriate direction parameter! I had forgotten that! Thank you ever so much! The thread is http://forums.simflight.com/viewtopic.pht=#338853. Peter, I may add this example to my documentation. I don't suppose you could extract the appropriate lines from your FSUIPC.INI file for me, could you? I don't really have a proper hat device to do my own and test it to be sure, so a known working example would be great. Thanks! Regards, Pete

In transition? The traffic should only be relaoded when you are on the ground. weather at a destination should have been set enough in advance for the traffic to be okay. You need to check those options badly. Do you have any documentation for ASV6? No idea what would do that -- except of course the very same sudden wind change ("shear" its called) which is presumably also why the traffic is being reloaded. You should be able to switch off the latter, but the former probably means you have no wind smoothing enabled. Al this sounds like a badly configured ASV6 setup. I use ASV6 all the time, and even on its default settings it is not doing any of that sort of stuff. Have you been changing things I notice you did mention VatSim? Are you using two weather sources -- ASV6 and Squawkbox or something? I'm not sure they'l get along, you need to switch the weather off in one of them. Pete

This sounds like a facility in ASV6 to force FS to reload the traffic when the wind is changed, so that they use the correct runways. I am not *sure* about this, though -- you'll need to check your ASV6 options and/or documentation. I don't think it should do this whilst you are flying, but it may do whilst setting new weather whilst you are on the ground. The only other thing which causes traffic to be reloaded is a change of more than a couple of minutes or so in the time. In fact some programs actually change the time in order to force this to happen. You can also do it manually (as I do after new weather has been set) by assigning a button or key to FSUIPC's "traffic toggle" control. Nothing in FSUIPC -- take a look at ASV6. If you don't let it force a traffic reload you may have difficulties taking off against AI traffic taking off or landing in the wrong direction realtive to the wind. Pete