Pete Dowson

No idea, sorry. What are they modes of? Pete

This is normally easily done by holding the switch and having it repeating. What would the delay be for? You operate the starter level (fuel cut off) to "start" (i.e. enable the fuel) when you see the N2% rise enough -- e.g. 20% in the 737, and then release the starter. In the real airliner the switch is magnetically held in the start position until the engine starts. I'm not sure if there's a timeout on that. Perhaps if you could be a little more specific about what you want to actually achieve? Regards, Pete

Thank you! It's very nice to get some positive messages in the midst of all these technical difficulties I deal with every day! :D :D :D Regards, Pete

But the positions in the FSUIPC calibration are only so that a correct centre can be achieved. Centre is merely the value 0 (ZERO) fed to FS. Minimum is -16383 and maximum is +16384. FS knows no other specific positions, so there's no way FSUIPC can know what other intermediate values to calibrate to, is there? It is different with Flaps, as FSUIPC can get the number of flap detentes from FS and it knows that these are equally spaced along the range of values. Your aircraft presumably is taking some arbitrary input values on the axis and treating them the way it wants. There's no way I can calibrate to unknown arbitrary values. Your best bet is to calibrate for a good min, centre and max, then mark the position on your lever for achievement of whichever of the two intermediate values isn't actually set by a zero input. Regards, Pete

Not without more information, no. Please tell me the version numbers of FSUIPC, WideServer and WideClient. If these are not the current ones (3.45, 6.45 and 6.45 respectively) please try those first. Then check the WideServer.Log file (in the FS Modules folder) and the WideClient.Log file (in the same folder as WideClient. If they are short enough, show them here, otherwise Zip them up and send them to me at petedowson@btconnect.com. Be sure to close everything down first. I need to see the performance figures too and these are only provided on close down. If you've been changing any of the performance parameters in WideFS INI files, please remove those and let them default again. Regards, Pete

There's something odd going on here -- I saw your new email flash up on my MailWasher program as suspicious (highlighted in Red) and before I could get it it was deleted from my mail server. Seems like someone somewhere does not like your email address! I am sending the original email containing the Key again. Let me know. Regards, Pete

You deleted the first few lines from the log, so I am still none the wiser about which version of FSUIPC you are using! PLEASE always state versions when asking for support! This error: is catastrophic. If FSUIPC hadn't trapped the error then it would have resulted in FS crashing to the desktop, probably with not even an error message. It looks very much as if some part of the FS installation is corrupted. The most usual reason for this particular type of crash is a corrupted weather file (WX). The fact that it seems to occur when trying to change the weather with AS2004 reinforces this surmise. As an experiment, try removing the FS9.CFG file. You'll find this in: Document and Settings\\Application Data\Microsoft\FS9 Keep a safe copy so you can restore it later, if removing it doesn't help. Then run FS again -- it will generate a new default CFG file. Another file there which may be responsible is the wxstationlist.BIN. I think (but I'm not sure) that if this is removed it will get re-created from the one in the FS "weather" folder. Finally, I see you are still having FS load, as default, the original FLTSIM.FLT file from the FS "Flights\Other" folder. This will have a short WX file too, which may possibly be corrupted, so you could try creating a new Flight with its own base weather from the initial menu and saving it as default, then reloading FS so it uses that as its starting point instead of the original. I'm not sure how these "corruptions" arise, but I think it is to do with the occasional updates made in the weather station list by Microsoft/Jeppesen. These updates will be applied when you download MS weather. If you've never used downloaded MS weather then I am very puzzled. Regards, Pete

I don't actually have or use any voice program, so I don't know how to set the key you want to use in those. You'll need to look at their documentation. If it is just that you want to program a button to produce a key press in FSUIPC, this is described in the Buttons section of the FSUIPC user guide, and is easy enough to see what to if you go to the Buttons page in FSUIPC options in any case (Modules menu, select FSUIPC then Buttons). With Roger Wilco or AVC there are, in fact, special controls added for Push To Talk, so rather than assign keystrokes you should use those. Regards, Pete

What version AS2004? If it isn't the very latest, get it. And make sure you are using version 3.45 of FSUIPC. After that I don't want to see ActiveSky messages or logs -- those are for AS support. If you need me to look at FSUIPC it is the FSUIPC Log I'd need to see. Regards, Pete

And was it? Sorry, I don't actually know whether it was or not. This is a question for PM support I'm afraid. Yes, please ask PM support. I am very sorry, but I simply cannot undertake to support their software as well as all my own. It's a full time job as it is! All FSUIPC can do is forward the code to the PM module. What it does and doesn't do with it as a result needs to be sorted out by PM. Regards, Pete

Well, first, please ALWAYS declare the versions you are using. Current FSUIPC is 3.45, WideFS is 6.45. Then, it appears, that this is probably more a question for PM support. All the PM controls in FSUIPC do is operate assorted bits in the offsets declared by Enrico Schiratti in the PM Offsets documentation, available on the PM site. the VS button appears to be bit 31 in offset 5410, which is toggled (i.e. simply changed -- from 1 to 0 or 0 to 1). You should check that first in the FSUIPC Monitor -- see Logging page. Monitor 5410 as a U32 in hex, see if the top bit changes. Again, please check the PM offsets documentation. There is really very little to go wrong in FSUIPC for any of these PM controls. All it does is change bits in declared offsets. You can check those easily yourself. If the bits change, as I believe they do, and PM does not respond, then I really cannot do anything more -- you need PM support to look at it for you. I do know that some of these things have stopped working, started again, and stopped yet again, with different builds Enrico produces. I really cannot re-test them all every time he posts new builds. I think these days he prefers folks to use the "pass through" facilities -- offsets 4F4 (for GC) and 4F2 (for MCP). The relevant FSUIPC controls for these are "PM GC Controls" and "PM MCP Kcodes", which need parameters to pass to PM. There are some listed in the FSUIPC Advanced User's guide, but the main reference really is the PM offsets document from the PM site. Yes, but how is it programmed in FSUIPC? Check that the correct bits are being changed. If they are, as I believe you will find, then it is most certainly a matter for PM support. Please try to eliminate other things when you are trying to diagnose problems. Here, for instance, for test purposes, you could esily simply program a couple of keyboard combinations to the same PM controls in FSUIPC. If they don't work then you know it is PM. Regards, Pete

I sent that last night, well it was today by then -- 00:09Z Monday 31st Jan. Regards, Pete

Okay, this is confirmed as a bug. Apologies. It isn't just the spoiler axis, it is all axes. It will be fixed in the next version, in a few weeks. Meanwhile the work-around is to also check the "filter" setting. It remembers "filter" and "filter+reverse", just not "reverse" alone. Thanks for the report. Regards, Pete

Why do you set ActionKeys=Yes? Radar Contact does NOT use keys directly, it uses the FSUIPC Hot Keys facility, as I said before. Your WideClient INI can simply contain default parameters. And it really is more a question for Radar Contact support. it is certainly nothing to do with WideFS, it is arranged by Radar Contact using facilities in FSUIPC. I know you did, and I pointed out that you are using an out of date unsupported version of WideFS. Please upgrade! The only improvment I can see is in the way you run the programs: RunReady1=c:\Program Files\rcv30\rcv31.exe RunReady2=C:\INSTALLDIR\Modules\ActiveSky2004\AS2004.exe RunReady3=C:\FS2004\SHOWTEXT\showtext.exe You should consider a delay (DelayReady1 and 2) between each, else they could be tripping over each other during initialisation. Regards, Pete

As long as you are on the same PC, your access to FSUIPC means you already have a Window handle owned by the process. Or even without FSUIPC you just need to find the top level window with class name "FS98MAIN" (they are all called that no matter which version!). Once you have the Window handle I think you can find the process name (probably full path name) easily enough. Regards, Pete

It should be saved. The code is the same for all the supported axes. I'll check. (Shame you didn't report it in the previous version -- if it is a bug I could have fixed it by now!) Regards, Pete

Does the panel accept axis inputs to control these levers? If not then I don't see how you can do it. If so, then isn't it merely a matter of proper calibration? That sounds like 4 discrete switch positions to me, not axis inputs which have a continuous range. I assume his panel is designed to be used with switches and buttons? Or only with the mouse? I'm afraid there are more questions than answers here. Until I know how you are allowed to control those levers -- i.e. what the programmer has provided for such control -- there's no way really I can advise. Certainly there's nothing in any of my programs at present which convert specific axis range values into keyboard or button presses. If the documentation supplied with the panel doesn't tell you these things it seems you will need to contact the author. If he hasn't provided any axis controls for those levers, then possibly he would be amenable to changing it? Regards, Pete

Firstr thing is that you are using an out of date unsupported version of WideFS. Current is 6.45. You don't say what the problem is, exactly. Your title says "Problems getting wideclient to recognize keystrokes" but WideClient doesn't need to recognise keystrokes. If fact nothing on the Client PC has anything to do with keystrokes. Radar Contact uses the Hot Key facilities in FSUIPC, no keystroke facilities in WideFS. The keys it expects are pressed on the FS PC whilst FS has the focus. Regards, Pete

No, not at all. Please read what I said. Here, I will repeat some of the more impoertant bits for you: I also said: In other words, I am anxious to resolve the issue. If you won't help, as your odd over-reaction suggests, then I can only surmise that there is something to hide. How else can I help resolve problems except by checking data? Since you have paid for the registration, then surely you will want me to resolve the problem so that you can keep abreast of all the improvements I am adding to the program? So far, in all cases of problems reported like this, all but a couple have not followed up their reports by providing the Key file for checking. And, oddly, like it seems you propose to do, have never come back for more support. Slightly suspicious, maybe? Of the two that did, one definitely had a genuine problem, but it wasn't the key itself, and the other was actually a counterfeit key. I do have a "Lars Kluver" listed as a purchaser from SimMarket, but the email address is different. This was a registration in early August 2003, and I note that the 'u' was accented (umlaut?). The very first versions of the Key generator did have a problem with accented characters, and it is just possible that this is the cause. But I really cannot resolve it without your cooperation, don't you see that? Regards, Pete

That sounds very useful. Thanks. Yes, that's actually been a facility in most recent versions of FS. I documented it in the FSUIPC Advanced user's guide in the section about multiple INI installations. Is that down to the German FS9 or the German operating system? The "Application Data" sub-folder is used by many programs, not just FS9. I think this part of the path is one of those available through the "SHFolder" API -- there's a constant defined for the API to get a system path as follows: You can get the path as above. Except for the /CFG: option, you can get the name from the Process EXE name. I'm afraid I don't really know how to track down the use of the /CFG: option. In all versions before FS2004 the CFG file is in the main FS path. Regards, Pete

You won't get any support from me for that. If you have something that works well with 3.40 and not with anything later, then it sounds like you are using an illegal (i.e. counterfeit) user key, or at least one which has something wrong with it. Try 3.45 again, but after temporarily removing your FSUIPC.KEY file from the FS Modules folder. If that "fixes" it, then the key is suspect. Zip up the FSUIPC.KEY file and send it to petedowson@btconnect.com so that I can investigate. Regards, Pete

In that case, for such simple things, you might find the FS98 interface sufficient -- the direct writable offsets at 0F1C (114 bytes). This interface was all there was in FS98, the extensions in the AWI were to allow for the many more layers possible in FS2000. There's a simple addition for the FS98 interface for rain/snow control and a few other things. Read the Notes in the Progrmmer's guide under the title "Additional information for Application programmers". Anyway, to briefly answer your earlier questions as best I can with my failing memory: Set replaces the whole structure. If you read the actual comments in the header file you will see it does say "set all ...". If you are setting all the weather this is better than adding all the time. AddAt adds a cloud layer at the altitude specified in the command itself (the lower 16 bits). It should do this without disturbing the others, but some small adjustment might be made if this makes any layer too "thin" (and no, sorry, I don't remember how 'thin' they can be). nAfter is merely a counter for the number of layers following the current one in the same command data structure. Since you can only have one such layer in AddAt it is always zero in that. If you were setting 10 layerrs by Set All then the first one would say 9, then next 8, and so on. The last 0. If you have any other existing program which uses this interface you might learn a lot by turning on FSUIPC IPC write logging and seeing exactly what it does. Come to think of it, my own "WeatherSet" program uses the AWI and was intended as just such a demonstration. You can check all sorts of things with that. WeatherSet2 is the demo program for the FS2004 NWI. Regards, Pete

Well, no, not at all. After scanning through the rest I find I really have no idea what it is all about. Never having used Squawkbox or even Multiplayer, I have no idea I'm afraid. Just to carry on a bit: Now ALL of those things that are going wrong, every single one of them, are to do with the relationship between Squawkbox or whatever and FS, via the Multiplayer interface. I really have no idea how that works or even how to set it up, but I do know it isn't at all related to either FSUIPC or WideFS. It will be related to the Network, obviously, but it is a separate conversion between FS's multiplayer interface and whichever part of the rest of the set up which deals with it. That's where I get lost. I have no idea of the relative functions of SBRelay,ServInfo, HostSB, and Squawkbox. Sorry, but I do really think you need to seek help from the folks who do this stuff. It will be some setting either in FS multiplayer or one of the other accessories related to your on-lne flying. All Squawkbox uses WideFS and FSUIPC for is to ascertain the position of your own aircraft, and, possibly (either directly or via AIBridge) to feed the MP aircraft into the FSUIPC TCAS data. Regards, Pete

This is for FS2000 or FS2002 I take it? Er, no. You can set many wind layers all at once. And winds are not necessarily the strength and direct at the upper altitude -- maybe they will be in the centre of the layer, but the altitudes give are the changeover points and normally there's be a lot of smoothing between two adjacent layers. It's a long long time since any one started using AWI. That was designed for FS2000 and extended to FS2002 but it isn't really of much use in FS2004. Can you confirm that you realy do want to program weather for older versions of FS, and then perhaps we'll discuss the interface. I would need to revise it first as I wrote all that stuff five or six years ago and haven't used it or discussed it for years. Regards Pete

There is no way FSUIPC can have any influence on the graphics. That sounds like some limitation has changed on either real memory or video memory. Certainly, different versions of FSUIPC will have slightly different memory occupancy, but not enough to influence anything critical unless something else had made it so already. BTW what version is the "FSUIPC you used before"? Regards, Pete