Pete Dowson

A real NG yoke provides MCP dial operations on rocker switches? Really. That's news to me. In the 737NG manuals the yoke switches are: stab trim, A/P disengage, PTT (on on the left for pilot, right for co-pilot), and something called a "memory device" on the right for the pilot which I can find no other reference for. It works fine here, repeating, provided of course that you have the "repeat" checkbox set in FSUIPC (repeat whilst held for KeyPress). The rocker switches on both my PFC yokes (one Jetliner, one Cirrus II) are non momentary. A different code is received by the driver when they are released. But the way they work does not allow more than one pressed to be recognised at a time. I think this is because they use the old CH way of encoding up to 14 buttons on 4 wires. Check you are using the latest version of FSUIPC. You should always mention versions. Regards, Pete

I think all the Aerosoft stuff is supported directly in PM. The only software normally needed of my range is FSUIPC and, of course, WideFS for a network. Most PM users run it on a network, it is really designed to be used that way. Regards, Pete

I don't know, sorry. I really don't know much about the actual simulation modelling in FS, or the graphics methods. There are experts around, but maybe not many among those who visit this forum. You could try the FS2004 Forum, or possibly there is an aircraft designers forum somewhere? Regards, Pete

Yes -- it seems you do realise that the offset is allocated and maintained by an application. In that case, what is the problem. It is readable and writable just like any other offset in FSUIPC. Try using FSInterrogate, or program a button or keystroke in FSUIPC using the Offset bit manipulation controls. Regards, Pete

What does that mean? Where in the DLL are you trying to look? The offset mapping is only valid when you run FS with FSUIPC installed. There's no point in looking at the DLL module itself. If you mean you cannot read or write it through the FSUIPC interface, but of course you can, but why do you want to? If on the other hand you mean that it is not specifically listed in the Programmer's Guide, in the FSUIPC SDK, then that is because it is in part of the offset map which is allocated for use by specific application programs. It is no business of mine what such allocations are used for, nor is it my job to publish them even if I knew. Most are private between parts of the individual applications in any case. Please try to be a little more specific next time you ask a question, eh? It is difficult to know what you are asking in this case. Regards, Pete

You might want to contact Enrico over at http://www.schiratti.com to get your program and link added to the list of programs on the right-side of the "Pete Dowson" page over there. Regards, Pete

Where are you reading the wind details? Shift+Z tells you the ambient wind at the aircraft. In Fs2002 the direction shown is degrees True, not Magnetic. The winds aloft aren't in bands of fixed direction/speed, but vary between defined later "centres". On top of this if your have wind transitions and smoothing enabled those add other factors. As you might now realise, it is really impossible for me to comment without a great deal more information. If the winds are set correctly in FS's own weather dialogues, then the other factors should follow, but you need to interpolate between layers even then. Pete

Sorry, I've never used NetPipes. There wasn't any such thing around when the IPC interface was first invented. I'm sorry, I don't exactly know what you mean. If you mean would I deliberately make FSUIPC tell lies, give you false information, then, no of course not. If you mean is it bug free, then I'd have to answer of course not, no non-trivial software is ever bug free. But it is supported with regular updates and I fix bugs fast once reported and reproduced. Regards, Pete

The button is being seen and acted upon in FS as well. You need to de-assign it in FS Options-Controls-Assignments. Regards, Pete

Just finishing now. Usually get to bed between 01:30 and 02:00, sometimes a bit later. But I don't get up too early! :wink: Regards, Pete

Sorry, I don't actually offer anything. Sales are entirely handled by the retailers, and the discount for buying them together is just that -- it actually less work for them, of course. It doesn't apply for separate purchases. However, if and when you do purchase WideFS you do need to do so in the same name and email as for FSUIPC. If your email address has changed since then you will need to make a point of telling them that when ordering. Regards, Pete

That does sound more like it, yes. Glad you resolved it. But you may also want to try the pre-release versions of FSUIPC and WideFS I supplied earlier in the PM support group. Regards, Pete

Sorry, not I. Try one of the other forums. There are some good experts around I think, but for me it is just trial and error. And I don't really remember my FS2002 settings, it's been a long time since I used it. Regards, Pete

Hmmmnot certain why the weather downloads would do that, but it sounds like some sort of incorrect mip-mapping level is getting selected. That does happen if you slew very fast, for instance, and is just where the graphics system isn't keeping up with the movement expected, but I don't know any reason for it to happen when flying at normal speeds. Regards, Pete

Not sure what you mean by "resolution dropped" -- resolution of what? But if you are using downloaded weather in FS2002, FSUIPC cannot help -- it really has nothing whatsoever to do with it. In FS2002 and earlier I only ever found out how to sort out global weather. Mostly the dowlnoaded real weather in FS2002 and before was not good in any areas not close to a weather station. It reverts to global weather or noe at all rather than interpolating between distant stations. I think most folks who cared at all about good weather coverage in FS2002 used a third party program, which controls FS weather via FSUIPC's global weather manipulation. ActiveSky or FSMeteo -- both are many times better than FS's own downloads in FS2002. But the "latest" ActiveSky is ActiveSky2004.5 -- isn't that for FS2004 only? Or not? I don't really know of the situation for FS2002. Regards, Pete

I think that's all to do with how it is programmed/declared in the EPL. I was totally confued by all of that too and had to ask Ralph Robinson for help. All that was years ago. It was all quite easy when I used the ISA EPIC andf my VXD, but I just got completely lost with the changes to the system later. Sorryyou do need help from someone who knows EPIC USB EPL methods. I am totally out of touch now, not being an EPIC use at all for a long time. Regards, Pete

That's the problem thenthere's something set up wrong somewhere. Such retries only occur when Windows refuses to accept another frame from my modules. Are these errors occurring in the client, or the server logs, or both? Only 8?!!! That's far too low. What sort of processors are you running this on? What is the FS frame rate limiter set to? Your average frame rate recorded at the end of the Wideclient logs should be close to your average FS frame rate. What is the average recorded at the end of the WideServer Log file? How may Client PCs are there (you mentioned a 5-port hub), and do they all have similar problems and similarly low frame rates? If you only have the two PCs, then it would be more efficient to link them directly, via a cross-over cable, rather than through a hub. The current "bare vanilla" CD is up to SP2. Service Pack 1 was included on CDs a long time back. Did you buy it when it was first released? I would most certainly recommend at least going to SP1 level if you are not there at present. There were all sorts of things wrong with it initially! I'm not sure where Internet access comes into it. Is the Server regularly accessing the Internet whilst you are flying? I would have thought it best for FS performance to keep all that off the FS PC. I'll be releasing my latest Beta versions of FSUIPC and WideFS to the PM support group either later today or tomorrow. You may want to keep an eye out for them there and re-test when you get them. Regards, Pete

The "latest" being the ones listed above as Supported? Version numbers are always more exact. Some folks say "latest" but actually mean the last ones they saw or downloaded, maybe months before. I have read a couple of similar stories on the PM support site. They mostly sound like some sort of graphics processing hiccough from what I've read. Ah, so you do really have "the latest". Yes, as per documentation, it is not used on the Server any more, as it automatically supports both IPX/SPX and TCP/IP clients. Seems that Katy is a little out of date -- I think this may be due to the fact that she has been moving house and probably hasn't had time to keep up to date. Please, whenever you update any of my programs, peruse the History section. For WideFS, this is right at the end of the WideFS.doc after the heading History of Recent Changes You will find, in the section "Version 6.41 includes ...", this paragraph: These changes are also listed in the "RECENT RELEASE CHANGES" announcement near the top of this Forum, which you could read instead if you wish. I think that Timeout=0 has always been recommended for PM use. It is actually a better value for most aspplications now that most folks are using Windows 2000 or XP, which multitask better than Win98/Me. In the next version of WideFS (due next week), also pre-released as 6.414 on the PM support forum, the Timeout parameter is actually deleted and instead an "ApplicationDelay" is added, which does default to 0. If there are no errors showing in the WideServer and WideClient LOG files, then there is nothing wrong in the WideFS operation. It sounds like either something slow in the Client -- though I would expect something like video processing delays to cause jerks rather than consistent slow downs -- or some sort of extensive buffering going on between Server and Client, in which case the switch might be suspect. Does it operate any buffering? Seems unlikely. Otherwise, I assume some setting in the Client's network settings? Have you tried using IPX/SPX? Regards, Pete

I'm not sure why it would want FS2002 to be on it, but possibly that's so it can install some DLLs or other parts into the FS installation. Probably you would need to install it on the FS PC then copy the SB folder onto the client PC to be run from there. I am sure there must be some good help on this at wherever SB is supported. I don't actually fly on-line myself, but I do know that many folks run SB on a client PC. Regards, Pete

What does the FSUIPC LOG (in the FS modules folder) show? Are you using a user-registered copy of FSUIPC? Possibly you are not getting a proper connection because the example program is not getting access. Please try using FSInterrogate and examining its results. Look up the offset and size and units of those in the Programmer's Guide, and read them following the methods shown and documented. But don't expect to be able to read much at all with an unregistered copy of FSUIPC. Until an unregistered FSUIPC sees a correct Access key it will only supply its version number and the FS version number. Regards, Pete

But you said earlier: The "client computer with WideFS" should mean a PC with WideClient ruunning! What does it mean to you? It is WideClient which looks like FS to the application, like Squawkbox. Run WideClient, see it connect to FS, run Squawkbox. Pete

No, sorry. I'd like to be able to intercept and interact with FS ATC, but have not found a way. I am hoping things will be better in the next version of FS. Would an on-line flyer use FS's ATC? Seems strange. And I'm not really sure what to make of "window state". Why would someone fly with FS minimised? and if it was detectable and he wanted to avoid that, why not swap programs with ALT+TAB or similar? Regards, Pete

Ghastly silence? :shock: Is this compared to the aircraft engine sounds just before you closed, or do you mean all your fans stop turning, your hard drives stop spinning, etc? If the CD is firing up it sounds like it may be related to the CD protection mechanism in FS. It's pretty nasty in my opinion, and I know it doesn't work properly on all machines/CD drives. Possibly some other process in your PC is interacting badly with it? Especially with XP SP2, which adds quite a lot of new security stuff into your system. Maybe you had an anti-virus add-on and WinXP is adding its own actions to this. Sorry, I'm really running out of possibilities here -- but from what you say now I'd guess it is more likely to be related to something outside FS than any add-in DLL and so on. Hmmm, I can't really say I know of any sound a modem makes before dialling, but maybe the phone lines do something like that where you live. Aha! I think that proves itThat strange ".tmp" process is actually part of the protection mechanism which is implanted into FS2004 to (a) check the CDRom, and (b) prevent debuggers getting inside FS's code. The latter action is why it is running all the time. It certainly seems something else in your PC is interacting badly with the FS protection. Maybe if you used the "no CD" hack, replacing the FS9.EXE file, you'd have no problems, thought really I should not suggest such a thing as it is strictly speaking a violation of Microsoft's copyright. I actually have to use it because I need to debug modules inside FS -- without it there'd be no FSUIPC or WideFS for FS2004. Regards, Pete

No. But I think you can just play waves from your program and they'll mix with FS sounds if it has focus. At least, there are several programs which achieve this with no special facilities. Regards, Pete

All I know is that you write strings with the variant "FSUIPC_WriteS". The 2-byte value at 32FA will be written from a normal FSUIPC_Write, that is just the reverse of the Reads you've already sorted out. I think the complication with strings in VB is something to do with the fact that they are passed by value not by pointer and the declaration of the Write procedure had to be changed to deal with this. Another possible complication is that your program is using Unicode or Wide Characters (16-bit character codes) instead of the standard 8-bit (single byte) ASCII which is used by FS and most standard Windows APIs. I hope someone knowing VB will jump in and help, but it might be a good idea if you showed an extract of your code and explain what you see happening at present. Don't forget to use FSUIPC's Write logging (Logging options page, IPC writes) to see what FSUIPC makes of it, as I suggested. Regards, Pete