Pete Dowson

There are basically two ways -- the easy sledgehammer way (which actually my own TrafficLook uses) and the "correct way". The correct way is by reading the table size data and calculating which bits to read and which not. Then reading them, but only when flagged as changed. This is difficult and loong-winded to program, but very efficient at run time because you are causing minimum work. However, the brute-force method seems to work pretty well (try TrafficLook and see). This is simple declaring arrays of enough TCAS_DATA structures for all the aircraft, and reading them all, in one read per table. If you are only interested in the "bState" you are only interested in the two main tables, the traffic entries only, from E080 for ground and F080 for airborne traffic. So, your "pseudo code" (C to me, sorry) would be (omitting error checks for now: TCAS_DATA ground[96]; TCAS_DATA airborne[96]; DWORD dwResult; FSUIPC_Read (0xE080, 96 * sizeof(TCAS_DATA), (BYTE *) ground, &result); FSUIPC_Read (0xF080, 96 * sizeof(TCAS_DATA), (BYTE *) airborne, &result); FSUIPC_Process ... Now you have all the data in nice local tables in your memory and can access them as and how you like. This is exactly what TrafficLook does. Regards, Pete

Ah! rightsorry, I didn't see the "Traffic" part, which I now see was in your subject line but not in the message. It's just a number. I assume you are managing to find the TCAS entry you want? Please, what is then the problem? It sounds like you've done most of it if you've got that far. Regards, Pete

Okay, then now you are definitely into Project Magenta support areas. All FSUIPC does it toggle the bits in the offsets PM is using, It is then up to the PM software to see this and obey. I don't know what builds you are using from PM, but if you are not using the PM MCP then these controls need very recent builds. Even then I think some things might be broken. Please check with PM support. Sorry, I don't know, and I cannot really offer PM support. It works here with the builds I have (GC414, CDU351, MCP382). Can you check with PM support, please? All FSUIPC needs to do is waggle the bits, it is very simple. The rest is up to PM. Regards, Pete

What is the "bState" value? I'm not able to help with C# I'm afraid, so I hope someone else will jump in -- I assume the C# part of the SDK isn't sufficient? However, I don't even understand the value you want. :? Regards, Pete

There is no way I know to get locations of any actual buildings, roads, tectures, etc etc in FS's BGLs at run time. The "tower location" you can read in FSUIPC is a moveable thing -- you can set it in the Map dialogue. It you want it to coicide with the actual tower building, you can move it there and save the Flight. Regards, Pete

None at all, sorry. I've found no way at all to influence FS's local weather other than the visibility. this is actually mentioned in the documentation, and has been discussed a lot. I dearly wish I could intervene as I was able to in FS2002 and FS2000, but I've found no way at all. Check out FSMeteo and ActiveSky. I suspect that they provide wind limiting options, but in any case you can then apply some filtering in FSUIPC. Regards, Pete

If you are using a P4 3 GHz or better with hyperthreading enabled, just assign FS to one virtual CPU and everything else to another. If you are using an Athlon 64 FX53 or better you are probably going to be okay anyway. Anything else you are really going to be better off moving as much as you can off the FS PC. Just bear in mind that there is always an unavoidable latency when driving things over a LAN. This may only be 10-30 milliseconds much of the time, but there will be occasions when it is longer. I would never advise having the main FS flight controls on anything other than the main FS PC. The latency might not matter quite so much with heavy airliners but it certainly would make flying, for example, aerobatic aircraft, fighters and especially helicopters more difficult. So, consider if you can split things and if so how you'd split it. Regards, Pete

Well you can determine that by trying whatever it is you are thinking or running on a Client PC on the FS PC first, instead. If you like whatever it is you are running (assuming it is a separate program using the FSUIPC interface), and you'd prefer to have it running on a separate PC, then WideFS is justified. If you don't mind running it on the same screen as FS, or if you have two monitors and can run it with its Windows on the second monitor, then you don't need or want WideFS. Installing and setting up WideFS is not something I'd encourage unless you need it, and certainly I'm not really willing and able to support experiments "just to see", so I'm afraid there are no trial offers. Sorry. If you tell me what you are considering it for I might be able to advise on how useful it may be. Regards, Pete

Please find the Caps Lock key on your keyboard, and turn it off. All CAPS is harder to read and comes across as shouting. When you load WideClient is will display "Waiting for a Connection" until you load and run FS on the server, with WideServer installed. This is perfectly normal. Just proceed and run FS on the server. Regards, Pete

You are mixing up two completely different things. The "49" value for the PM interface is a parameter used for the direct PM interface. There's no Keysends, no alteration of WideClient.INI, no Keypresses at all involved with that. You say you've read the documentation, so please PLEASE tell me how you mix KeySends (which are for activating KeyPresses on Client PCs using WideFS) with explicit PM controls supported by FSUIPC directly and not involving WideFS whatsoever? Where are you linking these things together? Either use KeyPresses (and therefore WideFS's KeySend), or use the direct controls provided. It's probably better to use the controls -- the keypresses are intended for programs which, unlike PM, are not operated through PM offsets. That's more a question for PM support I'm afraid. But I would recommend you scrap all that anyway and use the PM controls as provided. Just delete the stuff you added to WideClient. Go to FSUIPC's Buttons page, press your button, find the PM control in the drop down list. If you look more carefully you will see you don't even need the "49" you found, you simply need one of these: Pm Nd Range Dec Pm Nd Range Inc Pm Nd2 Range Dec Pm Nd2 Range Inc You don't need any parameter with those, they are simple direct controls. I think it is just a matter that you ploughed into the Advanced User;s documentation and misunderstood it all. That is for Advanced users. Beginners should really stick to the easier stuff :wink: Next time you want a control, look through the list first to see if it there. I know it is long but it will be quicker! If you use KeySend, then, yes. The parameter in FSUIPC provides the KeySend number. With up to 255 different KeySends possible, there has to be some way to link them, do you see? Oddly enough, it is for providing parameters -- for those controls which use then, like the KeySend facilities, some of the PM facilities, and of course for those FS controls which need a value (mostly those ending with "Set"). Parameters are extra qualifying data, that's all. Your "72" is a Key stroke code and used wherever you want to define the key press 'H'. Your "49" was obviously (if you go look again) listed as a parameter for the PM GC Controls (By Param) facility, which you would only need to use if there was a function there you needed which wasn't listed separately as a PM control in any case. You may have read the documents but you seem to have linked several parts which are not linked either by narrative or reference. I really don't understand why or how you have done this, but you seem to have rather gone out of your way to make it seem as complicated as possible when, in fact, there was a listed control directly applicable to your needs which you didn't find. :( :( :? :cry: Pete

FSUIPC cannot smooth winds in local weather, and AS2004 uses local weather. In fact the only smoothing option in FSUIPC which works usefully in FS2004 is the one for visibility. Global weather control is problematic in FS2004 (see some of the notes about it above and in the docs, not to mention all the threads! :wink: ). Regards Pete

Okay, thanks. Actually I just checked, and it looks to be some default scaling value which is really messed up, way out of range. I expect it to be easy to fix, and would do it straight-away if it were not for the inconvenience of having too much other code half-baked as yet. For now you could try using the control with the reverse range included (PropPitchR12) and just calibrate the reverse zone to be negligible or non-existent. Regards, Pete

No, not axes at present. Only buttons and switches. For flight control axes it isn't a good idea because of the latency (delays involved), but I suppose it could be useful for other axis assignments, like flap setting perhaps. But it isn't a facility high on my list. Sorry. You could check out FS Communicator http://www.flightsimulator.at/frm_fscom.htm. I think it might be able to do this and more. Regards, Pete

No, not at present. Only buttons and switches. For flight control axes it isn't a good idea because of the latency (delays involved), but I suppose it could be useful for other axis assignments, like flap setting perhaps. But it isn't a facility high on my list. Sorry. Regards, Pete

If you bought it from SimMarket, go to http://www.simmarket.com and open your account. If you got it anywhere else you need to contact the supplier. Next time you register you should consider keeping a copy off the PC, maybe printout the FSUIPC.KEY file or keep a copy on a diskette or something. Regards, Pete

Er .. I have no "Prop RPM 1-2" controls listed. Do you mean "PropPitch12" or "PropPitchR12"? I can check it out here if you let me know. The version and registered state of FSUIPC is nothing to do with PFC.DLL. It's a shame you didn't report it earlier, as I am in the middle of massive changes to PFC.DLL and cannot possibly release an update for several weeks. If I can reproduce the problem I will do, but the next release is likely to be in July or later now. Sorry. Please confirm which control it is you are attempting to assign. Regards, Pete

If it is freeware it may already have a Key for FSUIPC -- check the Freeware Keys sticky thread above. If you never want any such problem in future you can of course purchase a registration for FSUIPC yourself. Full details of what you get are found in the User Guide documentation within the FSUIPC.ZIP. If you are not interested in any of the facilities offered, but just want to run freeware, then the keys wil be in the list for those I've been asked about and know. For others it depends whether they are "alive" (still maintained by their authors) or not. If they are, it is more polite to ask the author first. I have supplied very many freeware authors with keys for their programs, and many of them make this process automatic -- invisible to the user. That is the best way. Regards, Pete

I don't fly online myself, and I don't know fsbrealy, fsbhost or servinfo, but I am pretty sure that you need Squawkbox, and that needs to talk to FSUIPC. The program is freeware and has a Freeware Key listed in the Sticky thread by that name. Get the key then run FS, go to FSUIPC options and press the "Register an application" button, bottom right on the first page, then enter the program name and Key where it says. I'm afraid for all the other magic you need to work to get on-line you'll probably need to ask elsewhere, maybe at the VatSim site itself. Good luck, Regards, Pete

Just put it in the Modules folder, as per instructions. What are you wanting to use it for anyway? As I said, I don't think it will do much in CFS, but more in CFS2. I don't have either so I cannot really tell you now what works and what doesn't, but whatever does work will follow the documentation. Regards, Pete

The bigger problem in FS2004 is getting the kind of direct control you want. As explained elsewhere, FS2004's weather engine is simply not directly controllable. It's a complete new beast and seems to be an attempt to simulate a true atmosphere. If you start off with zero weather -- eg use the Clear All Weather facility in the FSUIPC weather interface, or the hot key, then setting global weather should give you your wind almost immediately. There will be a hesitation, a stutter. In FS2004 I have found no way just to change one weather element. When you change the wind, FSUIPC has to supply a complete set of weather -- pressure, clouds, visibility and temperature, as well as the wind. Then FS2004 uses this "global" data to populate all the nearby weather stations which have no local weather of their own. Immediately after "clearing all weather" this will be all of them. A matrix of possibly over a 100 stations may be so populated -- it is this process which I think causes stutters. A complex data structure is generated internally, one which I've not fathomed at all I'm afraid. There is no such thing as weather set at any arbitrary position, weather is only "set" at weather stations. I can read the weather an any position -- what you get then is an interpolation based on the surrounding weather stations. The next problem is that, once the stations have their weather set, they "develop" locally. After an indeterminate time you cannot influence them any more with global settings because they now have their own local weather. The only way to change them is either to set specific station local weather, using their ICAO ID codes, or starting again -- clearing all weather and setting global again. The problem with this way is that it is noticeable and ugly. I hope I haven't put you off. You should experiment with what is available and see for yourself what you can do. Originally I thought these difficulties would make most weather control programs almost impossible to get right, but folks like the authors of FSMeteo and ActiveSky have worked wonders. None of it is perfect -- there are certainly bugs in the FS2004 weather engine (especially in the wind interpolation algorithm) which mess things up and these seem to become more evident when ambitious weather settings are attempted. But start simple and see what you can achieve. Regards, Pete

Depends where you bought it. If from SimMarket, go to http://www.simmarket.com and open your account with your user name and password. Then you can retrieve your key directly. Please, after re-registering in FSUIPC, save a copy of your FSUIPC.KEY file. Only version 3 is so far registrable -- versions 1 and 2, long defunct, had no registrations. so your key must have been for version 3. Only the latest version of FSUIPC (currently 3.22) is supported in any case, and you should always upgrade when a new version comes out unless there is some particular problem stopping this. Regards, Pete

It has some functionality with CFS and CFS2, though none at all with CFS3 -- the first two were very similar in structure and design to FS, but CFS3 was a completely different monolithic design with no way in for additional modules in any case. What you may or may not be able to do with FSUIPC in CFS is debatable. Not a lot I fear. CFS was not much further developed really than FS98 so the level of support would be similar to FS98 but less because of all the bits of FS missed out. CFS2 is much better supported and is sort of a mid-way thing between FS2000 and FS2002, minus loads of stuff omitted as irrelevant to combat simulation. In the end I should try it and see if it does what you want. But I cannot support it, so please take is as it comes. No way, there's nothing else remotely similar which any of my FS modules will work with. Sorry. Regards, Pete

Okay. Watch the announcements at the top of the Forum for new facilities in FSUIPC. When I get time I will try to add the response curves option for the main joystick controls. The actual facility isn't hard, it's finding a tidy implementation for the user interface that takes all the time! I can't promise it for any particular release, but I'll have a look soon. Regards, Pete

It sounds like the author has put loads of checks into the program, possibly deliberately to encourage the commercial version to be sold. Only by (illegally) hacking into the program and changing the checks it is making. Already, using the "MakeItVersionFS2002" fiddle (which was only added for a very specific problem with a very specific panel), is near the knuckle if the author didn't want it to be used with FS2004. Unless the author wants to create a revised freeware version (which of course you can ask about) I think that's your only option -- sounds like he intended it that way. Sorry. Regards, Pete

Sorry, I cannot realy offer PM support. I am not part of the PM team, just a user (when I get the chance to fly). I can say that I've not experienced any of these problems, but then I have no other cockpit (panel) loaded. Do you happen to be using a complex add-on panel as well as PM? This could be a factor. The other thing is that the data in the PM's aircraft Text file needs to reasonably accurately apply to the model of aircraft you are flying. No, it won't be anything to do with "offsets", and in any case they contain the data values being passed back and forth between the various PM components and FS. They are for programs to sort out, not people. Please refer your problems to the PM support email. I'm sure someone will help you. Regards, Pete