Pete Dowson

3.202 is well out of date and is not supported. please be sure to update. Current is 3.22 and version 3.30 is imminent. Sorry, what is "Strg"? What control are you using? These are the useful ones: LANDING LIGHTS OFF LANDING LIGHTS ON LANDING LIGHTS TOGGLE If you have a push button, program it as TOGGLE, but only when pressed, not released. If you have a toggle switch, program it for ON when "pressed" and OFF when "released". That's all. Please be sure to always use the latest FSUIPC. I cannot support old versions. Regards, Pete

WideFS cannot possibly split off bits of the program "FS" to different PCs. WideFS links EXTERNAL PROGRAMS which interface to FSIOPC, running on different PCs, to FSUIPC running on the FS PC. You cannot have one copy of FS running on one PC and bits of it running elsewhere. All of its gauges and graphics need the rest of it too. This is explained very clearly in the documentation, which is always best to read BEFORE paying for its use. Just glance briefly at the WideFS.DOC. Quite near the beginning you will see this:

Sorry, no. I have never heard of such a message, and it is not one from FS as far as I know. Do you have some add-on like Active Camera loaded? Else it may be a function of the cockpit you are using. Try posting to the FS2004 Forum. Regards, Pete

You have misunderstood, sorry. Those facilities are for manipulating values entered directly into FSUIPC's flight controls offsets by an external driver program, such as that for the Aerosoft GA28R cockpit. Exactly what you want is provided in the NEXT version of FSUIPC, 3.30, which is nearly ready but which is unfortunately delayed by my sight problems which limit my PC working to 30 minute bursts a few times a day. I hope to get 3.30 sorted out for release soon, but please don't hold your breath! :wink: Regards, Pete

As far as I know, no -- there are threads elsewhere in this forum about this very subject. So far no one has found a satisfactory way for me to provide such support, and the methods which work fine with Roger Wilco and AVC don't appear to be any good with Team Speak. Regards, Pete

Sorry, this is not something I know anything about nor which is anything to do with any of my software. Are you sure you are posting to the right forum? Please try the FS2004 forum. Regards, Pete

Okay. Here it is in context: Isn't that clear? If not, what is it you don't understand? Regards, Pete

I thought it was always running, if installed, and F9 just displayed its window. No. FSNav is already running. You surely would not want only to see its window and not FS when loading FS? Just press F9 when you want to se its window, F9 to hid it. No. Like FSNav, Active Camera is an entirely separate FS module which is in no way related to FSUIPC. Regards, Pete

It means that in clouds you see however far you'd expect to see in a cloud of that density. The point is that at the level FSUIPC is "fiddling" the visibility it could easily make the visibility ignore the clouds, which would be horrible and unrealistic. No, of course not. That's the whole point of using words like "internal" and "external"! Sorry, I don't understand this out of context. FS provides the visible facilities you describe here, not FSUIPC. Pete

What other programs are you running? For example, what are the WideClient's supporting? What other add-in modules? You need to performa a process of elimination. First run with no other accessory programs at all, no WideClients, nothing. Then, if that is okay, start adding things back. Regards, Pete

Yes, it has been there a long time but was spotted only a few weeks ago. I've corrected it here but there's been no other reason to make a new release yet. Thanks anyway! Regards, Pete

Is it supposed to? I thought the FS2002 series were 5.xx. Version 6 of FSMeteo uses the new weather facilities unique to FS2004 normally -- maybe you need to set this in its INI or options? It can only operate via Global weather setting in FS2002. I'm sorry I can't help any further here. I expect your Log files will be useful to Marc, the FSMeteo author, though. The FSUIPC log shows nothing wrong. Regards, Pete

That's because Microsoft forgot to provide such a control. It is an FSUIPC addition. Buttons are easier. Key presses can be sent over, but WideClient MUST have the keyboard focus for it to see them. You have to tell WideClient to do this as described in this section of WideFS.doc: Once you have the keypresses going to the FS PC, you can program them in FSUIPC's Keys page as usual. Bear in mind that FSUIPC does not know where the keypresses came from, so the same ones will operate the same way on the FS PC too. Regards, Pete

Sorry, I just noticed a "Question 3" hidden in there: If the visibility soecified for the FS visibility layer is changed, or the upper altitude of the visibility layer changes, then your limits are re-imposed if neceassary and then everything is ra-calculated to give a new target visibility for your current altitude. If you haven't got the FSUIPC smoothing enabled, it will change as quickly as FS tries to change it. With smoothing enabled it changes at the rate you have specified. Regards, Pete

"Surface visibility" is actually short for "surface layer visibility", which simply means the layer from zero to whatever is set for the upper altitude of that layer. I think originally FS was meant to support multiple visibility layers, but it has never worked with more than one, so "surface" means "the extent of the FS visibility layer". It keeps the surface visibility, whatever value that may have (30 miles or less, because it is a clear day and your limit for that is 3000) up to the top of the visibility layer, whatever that may be (FS dialogues or downloads set it, FSMeteo and other external programs set it -- though FSUIPC offers an optional override for that), and THEN it gradually and smoothly changes the value from that altitude to 25000 feet, by which time it will be 40 miles, your upper limit. The reason the changeover from a fixed (surface) visibility to the graduated one is at the top of the visibility layer is that you specified 0 as the lower altitude -- this is a special facility to operate in this way, and it is recommended as you then get the best results. Regards, Pete

Didn't you try going to the Keys or Buttons options and looking through the drop-down list? It comes uner "A" for Autobrake, so it is near the beginning (they are in alphabetic order). Also, searching through the FSUIPC User Guide would find this: mentioned in both the Keys and Buttons sections. Regards, Pete

Sorry, I don't understand the question. Is this just some graphics view you need? You may get better luck in the FS2004 forum I think. Regards, Pete

I've had one other report of that, but I've not been able to reproduce it here. For the other chap it didn't occur with my latest interim version (which should have become 3.30 by now but I can't see well enough to work on it yet). I'll email you the interim version to try. Regards, Pete

If they were available I would have provided FS controls for them long ago. PMDG play their cards close to their chest. They are proposing to release an SDK some time soon, but it may not be free. I am really not sure yet how this will pan out, but I am meeting one of the PMDG folks on Saturday. Maybe I will learn something useful then. Regards, Pete

FSUIPC doesn't connect to VATSIM. The full documentation for interfacing to FSUIPC in contained in the FSUIPC SDK on http://www.schiratti.com/dowson, but it sounds like that isn't what you want at all. It is Squawkbox which talks to ProController (I think that's what it is called) at the ATC end. But what protocol they use and so on, I have no idea. You'll have to ask the Squawkbox developers I think. Regards, Pete

Sorry, I don't really understand much of that. In JET models the mixture merely operates the fuel cut-off lever -- it is either "fuel on" (full rich) or "fuel off" (full lean"). In PROP models it operates the fuel mixture, as you'd expect. I don't know what this "idle release" control is I'm afraid. What is it supposed to do? Perhaps it isn't actually simulated in FS? Regards, Pete

I think this is a good idea for a separate application program. I will look at providing access in the FSUIPC interface to the values FSUIPC is using for the visibility control. Regards, Pete

There are two different things here. 1. Multiple views of outside scenery. 2. Decent instrumentation on its own screen, plus possibly ancillaries such as moving maps and so on. If you are a GA flyer then views of the scenery are probably quite important, but I think for airliner flying decent instrumentation is the priority. After all, at 35,000 feet there's not a lot to look at outside really. For multiple outside views there are two choices: 1.1 Multiple FS installations linked by WidevieW (by Luciano Napolitano). 1.2 Multiple monitors on one PC, via a dual head card or a triple head card, or possibly an AGP card and a seperate PCI card. The disadvantages of the WidevieW approach are that you need good fast PCs for each view, and each PC needs a full FS installation. Even then you will never quite get them exactly matching, especially in terms of AI Traffic and cloud positions and things like that. But there are a number of satisfied users and it can be a good solution. The multiple monitors solution should be better, but it looks like you need to avoid ATI video cards. nVidia provide good dual head operation, but the problem with two monitors tends to be that your centre of vision is on the "join". The only three monitor solution which works at present is with the Matrox Parhelia -- this is what I use. With all the instrumentation moved to other PCs and only the outside view on the three, this is very satisfactory -- but you do need a FAST PC (mine is a P4 3.2GHz). The Parhelia is nowhere near as fast as the faster cards available these days. I know of one person using a 7 monitor outside view, with a Parhelia centre PC and two PCs with dual heads linked with WidevieW. For external PC instrumentation you use WideFS. Investigate Project Magenta (not cheap, but very good), and other offerings such as FreeFD. See the FSUIPC user list on the right of the http://www.schiratti.com/dowson page. Hope this helpa. Regards, Pete

WideClient contains no sound code whatsoever. It isn't WideFS which is controlling the sound. It sounds like FDC needs the Focus to produce the sound -- why it regains focus when you give it to WideClient I couldn't say, but it sounds like FDC is making itself a "child" of WideFS (i.e. a "child" of the FS window). This is the same sort of thing that FS itself does -- its sounds stop when you transfer focus to other programs. This certainly isn't a necessary behaviour of programs making sounds, it is down to the way they are programmed. If there were an option for WideFS to keep focus, then with it enabled how would you ever be able to access your other programs? A facility to keep the window on top is not relevant, it is the focus which is needed. Sorry, but I think your only recourse is to ask the FDC author for an option for the sounds to be maintained even without focus. Regards, Pete

Ah, glad you managed to resolve it. But I wonder how it got like that in the first place? Regards, Pete