Pete Dowson

Odd. But Do I understand that the parameter does make your screenshots clean in instant replay mode? Regards, Pete

There are no facilities in FSUIPC for adding or removing messages. It has never been one of its functions. I really wouldn't know how to do it programmatically. I think there are only two ways to get rid of the red superimposed messages, and both affect the whole session. One is to use an edited version of the messages DLL with them all removed. However, I fear that in the case of messages containing changing numbers, as here, this won't help -- you'll still get the changing numbers. The other, I think is actually a parameter you can add to the FS9.CFG file which is said to hide all messages, so presumably does work on those too. However, although I did write it down a couple of years ago (when FS2004 came out) I can't find it at present. Sorry. Possibly if you ask the question on the FS2004 Forum someone will remember. I did look through their FAQ but it isn't listed there. Regards, Pete

Good! Wish I was always right! :-) Pete

No, not without writing a driver to interface to WideFS. I wouldn't really advise that in any case unless you really want some latency in the control (caused by the delay in transmitting across a network). When flying (or driving or anything like that really) you are reacting to visual feedback far faster than you would think, and even an extra 20 mSecs (about the best you could hope for on a Network on average) would tend to lead to you overcontrolling. It would be akin to trying to control an aircraft with a frame rate of less than 10 fps. Better just to get an extension lead if you want the yoke further away. ;-) Regards Pete

If you mean an FS panel, then you'll need to find a gauge for one -- all the default gauges only appear to have ADF1, but maybe there's a freeware one out there someplace. Then, as well as adding the gauge to your panel (a matter of adding it to the PANEL.CFG file) you would need to add it in the [Radios] section of your Aircraft.CFG file. If you take a look at that section you'll see how to do it, it's only one line. This is not really my subject at all, but that is how I understand it. You may get some more detailed suggestions in the FS2004 Forum or an aircraft/panel Forum if there is one.

Okay, I've now had a look, and as far as I can see FS does not support standby frequencies for the ADFs. There are none that I can find, and therefore there are no facilities to swap them over. In my implementation of ADF radios on PFC radio stacks I did the standby frequency displays from memory internal to the driver (PFC.DLL) then "swapping" was just a matter of reading the only current frequency known to FS and swapping that for the one I was storing for the standby. I think you will have to do the same for your cockpit. If you are not actually writing drivers for this, then you could probably do it in pmSystems. Regards, Pete

Sounds like the sensitivities are set to zero. FS2004 has a nasty habit of defaulting new axes to zero sensitivity. Go to Options-Controls-Sensitivites and check. Ideally, if you want to do fine calibrations in FSUIPC, you want maximum sensitivity and minimum null or dead zone in FS. Regards, Pete

Well, I think can add those as an extra bit. Though I cannot see an FS control for this -- the others are implemented simply by driving the FS controls. Odd that there are none specific for the ADFs. Possibly the anonymous "Frequency swap" control would do it, but it may need directing to the ADF in the first place. If it is easy I will see if I can fit it in this week, but otherwise it won't be for a few weeks as I am disappearing on holiday from this weekend till October 12th. I will put it on my list either way. Check the Beta versions list at the top of the Forum at the end of the week. Meanwhile, you could experiment with FS controls. If you find out what works you could then send them via offset 3110. [LATER] Please see my next message here! Regards Pete

You shouldn't need to do that if you start at least one engine and its generator. The battery life option just "cheats" by making the battery last longer, up to forever. If the battery had failed you wouldn't see anything, on the radios or in any of the glass cockpit display screens. It sounds like you've just not enabled the mode you want. Doesn't the PSS A320 come with any documentation? They are usually pretty good with their manuals. Regards, Pete

Sorry, there is no way I can support such an old version of WideFS (three years I think). The current version is 6.50. I don't think you can run WideFS 5 on any FSUIPC 3.xxx version in any case. Also, if it is WideServer which says it can't run, it is the WideServer.LOG file which is relevant, not the client one. Regards, Pete

Not without it being written that way, no. What is wrong with it as a separate program? I often wish FSNav was a separate program, as then I'd run it on a separate PC. As it is I don't use it as my FS PC is totally occupied in providing the scenery view only. >> Thus, the question is: can any application be made to run as a module that would run in FS2004 in full screen mode without the user having to task switch? << No, not without the program sources and a deal of programming skills plus suitable language tools. Sorry. Regards, Pete

Always the latest. I'm using 1.21, not yet released. Where did you see 1.20 by the way? I presume it was attached to a reply to someone who asked for something? In the "Supported Releases" list above it does say 1.10, but all those numbers there are just minimums. I don't revert to older versions. Forever onwards! ;-) One of my problems is that I can develop faster than I can write documentation (or maybe it's an aversion! :-) ) Regards, Pete

Glad you found the answer. Perhaps the author will ask Mr. Schiratti to put a link up on his "Peter Dowson" page (there is a long list of FSUIPC-using programs on the right-hand side). It is possible, but I don't do such things unless they are offensive or duplicated. In any case it may help the next person who is looking ;-) Regards, Pete

Is there a Modules menu? It is usually FSUIPC which creates it. If FSUIPC isn't there, what is? There's really no way I know that FSUIPC, properly installed in the FS Modules folder, and properly still named "FSUIPC.DLL", will not appear in the Modules menu. Please double check. You have probably put it in the wrong place. Regards, Pete

Most of the variables listed in the second table of the Programmer's Guide can be made available if needed. It's just that the can't be mapped directly, so extra code is needed to obtain them at regular intervals and place them into mappable memory. They were all mappable in FS2000, which is how they ended up being listed. I only tend to add such extra code when requested with good reasons, because it all adds to the performance limiting path through my code. Obviously if you are using the Panels interface directly there is no advantage in asking FSUIPC for them -- I would probably have to do the same as you (though I tend to bypass the PANELS.DLL call indirection and ask the Sim engine directly). Regards, Pete

1. There's no "freeware" and "payware" FSUIPC, only the one FSUIPC. If it is user-registered you can access the extra facilities, if it isn't, you can't, that's all. 2. The installation is as described in the User documentation, which of course is part of the purpose of such documentation. And yes, it is just a matter of copying the DLL. Since this is so simple, and since it is thus made so clear that nothing else, hidden, is going on, I prefer such a method. Self-installers always leave me wondering what's gone where, and especially what horrid entries they've made into the Registry. Pete

Oh, right. Good. No, because I don't know. For most things you get best results by trying to match the FS frame rate, so setting FS's frame rate limiter to, say, 25, and writing every 40 mSecs should be okay. But having said that, some things in FS do seem to be updated at a faster rate. FSUIPC doesn't get to know about these because it, too, is triggered by the frame rate (with a standby 55 mSec timer for paused and minimised periods). Experiment some more. If you find FS is interfering too much between your writes then I can look at doing the same as I did for the vertical wind -- take the last value you wrote and repeatedly write it for you till you write another, or until a timeout expires (which could be 10-14 seconds, allowing your program to also run on WideFS from a client). Could you tell me the exact application of this? What is it you are doing with it? Regards, Pete

Setting the speed to zero isn't possible, it is dynamically caliulated using the velocities and accelerations you'll find in the higher offsets. You can write to those with some, temporary effect, but you have to keep writing. Well, that could be made to work using the already FSUIPC-implemented "flight freeze" facility, which holds the latitude and longitude but not the altitude. That was reqested for use in flight training schools -- the aircraft continues to fly and has speed, but it's position over the world doesn't change. All you'd then need to do is maintain altitude. The flight freeze facility was added in version 3.44, with a bug fix in 3.45. Check the FSUIPC History document -- it's the second item under 3.44. It is usable by programming buttons and keys as well as through FSUIPC offsets. Regards Pete

You can download it and use it with freeware applications that have an access key, and also with accredited payware programs. Without paying you don't get any of the user facilities, that's all. There are announcements at the top of this Forum explaining everything. Also, if you download the ZIP and read the user guide, everything is explained there too. Pete

It is enough to indicate that there is something wrong with your Keys, either the FSUIPC one or the WideFS one, or both. Can you tell me where you purchased them, please? There are some illegal key generators around and they can produce exactly the results you are getting. I can see an Ingmar Bail listed as purchasing an FSUIPC key back in April 2004, but I have no record of any WideFS purchase at all. However, my records aren't complete and are only from one reseller. Please ZIP up your FSUIPC.KEY file from the FS Modules folder (do not send it without Zipping please) and send it to me at petedowson@btconnect.com, and I will confirm this or otherwise investigate the problem. Regards, Pete

Yes, it is the spaces in the names which confused my programming. Thanks for confirming. No, no need. But I always find it more convenient for several things to keep away from such folder names. Just something to think about for the future. ;-) Regards, Pete

I really doubt whether that is possible without actually patching code someplace. Even if it were possible, to find the correct place to patch in a new value so that it gets used consistently would involve another nightmare of tracing through hideous C++ compiles code at machine level, trying to recognise things as they crop up. Even if I understood this area it would be very difficult, and would be many many hours of tortuous hacking. The best you could possibly get easily would be if FS responded at all to you writing to offset 28C0 (FSUIPC does allow this). If you can induce any effects whatsoever writing there (and you'd probably need to do it as frequently as possible), then I could try to provide a way for FSUIPC to sustain the writing at closer quarters (i.e. faster and in time with FS's recalculations) to try to override FS's own computed values. I have done this for some other areas, notably the vertical wind component (used to simulate lift for gliders, for example), and it can work, but getting the timing right is important to stop fluctuations. Regards, Pete

Try http://www.flightsimmer.com/. I think they get some capable technical folks there. If they don't know I expect they could tell you where else. Regards, Pete

That's more or less what I do in PFC.DLL for the PFC jet cockpit, which has a tiller axis input too. I actually go further, gradually changing the sensitivities of the two inputs -- what FS sees is a combination of the two, all tiller at 0 kts, all rudder at about 60, half and half at 30. You can do something very much like it now, using the multiple control input facilites. You won't get the automatic changeover between the two inputs which I implemented for PFC -- but you can do that yourself of course, just take your hand off the one and use the other. You would calibrate the tiller input (in Windows' Game Controllers and/or FS Assignments) to give maximum effectiveness over a smaller range, and the rudder using its normal full range, thus emulating the greater turning power of the nosewheel. Just check the section in the Advanced User's guide on Multiple Joysticks. You can actually have up to four different inputs for all three flight controls, as well as the proportional brakes and main (single) throttle. FSUIPC takes the one with the highest deflection, so you just park or leave the unused ones alone (making sure they have an adequate null zone so they don't interfere if they jitter). These facilities have been available in FSUIPC for a few years now I think. Regards, Pete

Well, I never! I didn't even know FS did that. I certainly have never come across anything that I would recognise as a trigger value for this. If you know where this is or how it is set I can certainly add a setting for it. Perhaps you could ask around in an aircraft designers forum someplace? Regards, Pete