Pete Dowson

Okaybut I've made a note on my list to find out what is going on with WideClient anyway. It just won't be soon, as I've been putting off a load of other stuff I need to do, for too long! Regards, Pete

But do both left and right operate, or only one? If both are operating, then, yes, it sounds like some sort of assignment problem -- check in FS joystick assignments that the spoiler axis isn't assigned wrongly. But if only left or right spoiler operates, there really cannot be anything wrong in your controls, because there are no controls which will do that. It would then be simply the way the aircraft visuals and gauges are modelled. Regards, Pete

By "SPUIPC" I assume you must mean FSUIPC? Else you are in the wrong Forum! :wink: Two points here: 1. If you have a user registered FSUIPC then you do not need any keys for any applications whatsoever. The user registration covers them all. 2. Registration of WideFS covers the use of WideFS -- it allows WideServer to run and link to Wideclients on networked PCs. It most certainly has nothing whatsoever to do with "supposedly allowing for the registration of other products"! Where do you get that idea from? To register an application for an unregistered install of FSUIPC, the button to press is labelled "Register an application program" or something very similar. Surely this is more obviously aimed at registering other products than "Register WideFS" -- the latter actually is for registering WideFs. I really don't see how such clearly labelled buttons can be interpreted in the reverse way you seem to have done. It sounds like you entered the details into the wrong place, then, as above. Or you entered them incorrectly. Why not ask about that instead of rushing off and buying FSUIPC instead? You certainly don't have to pay for FSUIPC just to run legitimate accredited freeware -- or accredited payware, for that matter. There are some much older Gauges which may not work, however. These are only those written to interface to FSUIPC in the wrong way (using the external interface). I don't know of any specifically, but I suppose it is possible that some of Eric's older ones are of that type. If the only problem was that the gauge isn't getting access to FSUIPC, then there will be a message indicating this. Check the FSUIPC LOG. But it wouldn't cause FS2004 to freeze. Maybe there is a message window, and it is behind FS -- do an ALT TAB to see if there is an error message awaiting your attention. Anyway, if you have a legitimately user-registered FSUIPC, then there are no access checks made at all, for any program or gauge or DLL. So, if this is the case, you certainly have something else going on with that A318, not an FSUIPC access error. Regards, Pete

Sorry, I've not really had time to follow the link. I tend to be stuck answering emails and messages here too much. Perhaps if you'd actually state exactly what you want to try to do I can tell you, but I really cannot examine someone else's documentation and translate it for you -- if you really want that I think the author of those facilities (IVAP) would be the best place to go. Regards, Pete

I don't use it, but the GPS is just another FS panel window isn't it? Up to 9 panel windows are operated by keypresses Shift+ 1-9 (the numerics on the main KB, not the key pad). The numbers vary from panel to panel, according to how they are defined in the PANEL.CFG file. What list are you looking through -- the list of FS2004 controls, you mean? That's for advanced users and programmers. To program Keys or Buttons, use the options in FS -- find the Modules menu, then FSUIPC in that. Click it. The FSUIPC options dialogue will display. Finmd the Keys or Buttons tabs, click whichever. You'll be able to press you key or button, drop down a full list of FS + added FSUIPC controls, and assign them as you like. Please browse through the appropriate sections of the User guide -- do not bother with the other documents yet. Find out first how to open up the FSUIPC options and use them from inside FS. You seem to be confusing yourself by looking at the last things first. But "GPS poweron", I should think, is just the FS control to power on/off the GPS, not display it or hide it. I don't think the power button is actually supported in any case. Maybe MS ran out of time, or added the control ready for future changes. Regards, Pete

Sorry, none whatsoever. And I'm afraid it will be a while before I can get time to look at it. Really you are trying to make WideClient do something it was never intended to do. (I only added the ClassInstance option reluctantly). Most of the time when WideClient is running it is getting run because client programs are connected and using it. I take it you have no client programs for it. To make it run as a fully operational program on its own is really a different design job. Have you checked WidevieW options to see if it'll do what you want? It would seem much more appropriate. I know that Luciano has recently released a program to do things with mouse movements and clicks over the LAN. Have a look, and perhpas make suggestions to him. It would obviously be better for WidevieW to pass messages amongst its instances than trying to run a parallel, possibly conflicting, system. Regards, Pete

That shouldn't be a problem. Why impossible to pilot? I think you may just be blaming some other little error on the wrong thing? I think a small amount of spoiler is used for turns on many jets. I'm not sure of the details. But, whatever, it isn't a function of FSUIPC or PFC.DLL or any of your controls, because, put plainly and simply, there are NO FS controls availble for operating the left and right spoilers separately. Since it isn't anything to do with any axis or controls, other than links to the ailerons in the aircraft modelling, I am not surprised you can't change it. I think you need to look elsewhere for your piloting problems! :wink: Regards, Pete

You don't need to mess about in the INI file. Go to Keys or Buttons pages and program them using any one of the several Offset controls in the drop down list. When you select an Offset control you will be able to enter the hexadecimal offset (x....) and the value or mask or increment and limit to be used. There's some discussion of this is the FSUIPC User documentation, and definitions of the resulting INI parameters in the Advanced guide. Regards Pete

Hmmm. I don't see the point. What would be the use of a separate control for 2, losing the separate ones for 1 and 3? For differential thrust (assisting ground steering, and engine problems) you need separate control over 1 and 3, surely. This is why it is implemented that way. Next you'll be asking for 1+4 and 2+3 on a 4-engined aircraft! Uh? Regards, Pete

It is on my list. It's rather more complicated of course, and if not done carefully could give strange results. I think what I might do, rather than try to match all 3 or 4 engines, is match engines as follows: For 3 engines: only 1 and 3. Let 2 do what it wants. For 4 engines: 1 and 4, and 2 and 3, but separately. This would keep things balanced without the chance of it going haywire because one out of 3 or 4 is doing its own thing. I've been too busy with FSUIPC and WideFS to do much on the PFC driver in the last few months, but I place to look at it again in January. Regards, Pete

Not in that area there isn't. I can't think what FS could be making of the input it is getting if they all overlay each other. It's as if each was interspersed by a cursor back? One thing you could try -- programming the keys in FSUIPC on the client to execute the FS controls you want. FSUIPC definitely processes WM_KEYDOWN and WM_KEYUP messages and doesn't worry about scan codes, for instance. Regards, Pete

What do you mean? How do you "get ICAO codes from "modules"". I don't understand, sorry. Pete

I think FS needs keys to be provided through the SendInput method. You can set that option in WideFS 6.44, being released as I speak. Oh, you are using SendInput already? Sorry. No idea, sorry. I can think of no reason why. No idea what that could be -- they look identical now when spied upon (use MS Spy++). Regards, Pete

Sorry, I really don't know. I do remember it was possible to run it on a WideFS client -- I think there was a separate download for the install there, and you still had to have something on the FS PC to link with it. But I don't have any details whatsoever I'm afraid. If there's no longer any support site for it I'm afraid you'll just have to post your questions on some generic FS forums and see if anyone can answer. Also, of course, try a search with Google or something -- you never know, it may come up with the answer from someplace. Regards, Pete

Not according to the FSUIPC log you sent -- the session started at a bit before 18:43:47 (your PC time) finished tidily (FSUIPC received a close down call from FS) at 18:43:56. If FS crashed the Log would not have been finished so tidily. Maybe this is a log from a previous load, and your test which crashed immediately didn't even get as far as loading FSUIPC? Regards, Pete

How on Earth does FSUIPC know you've moved your head? I would have thought that was something already done by the software with your TrackIR? If it is producing keystrokes instead of mouse operations you could use Luciano's Key2Mouse program. FSUIPC can deal with keys and buttons, but at present there's no knowledge in it at all of mice. That's a whole different program really. Key2Mouse can be found at http://www.wideview.it/key2mouse.htm. Regards, Pete

Thanks for the files. The key is fine. The FSUIPC log shows no problems, but you only ran FS for 10 secondsdid you get a problem whilst it was effectively almost still loading? The only FSUIPC user logged was the PMDGoptions.dll, nothing else. Have you got enough memory to do that and still run FS? Don't reduce it below 256 Mb. If not, get another stick and try exchanges instead. Regards, Pete

In that case they certainly sound likely to be due to the spasmodic activity in the other processes, and especially the Internet access. Regards, Pete

All application keys are entered by pressing the button in FSUIPC's first option page (ALT M F in FS, or Modules menu, select FSUIPC). The button is labelled "Register an application program" (not too obscure, surely?). Please see the User Guide -- the section to look at is quite near the beginning and is entitled Program registration. There are even some pictures. Regards, Pete

It depends what is causing the stutters, but it sounds likely that it is the internet accesses from SB and AS2004 which may be the biggest culprit. Are the stutters regular or spasmodic? If you were using a Pentium 4 3.2 Gb with hyperthreading, I would have said that you'd probably not notice much of a difference, because FS seems to only use one of the two "virtual processors", showing 50% processor utilisation. This should, theoretically, leave the rest for those other background activities. The Athlon had a bigger cache I think, but it isn't quite as good for multiple processes. However, there are other possibilities. Disk access may be a cause of stutters too, and with more processes accessing different parts of the hard disk, sensible arrangement of data on disk, defragmentation, and possibly even more real memory (for caching) could help. So, in the end, sorry, but I could not categorically answer yes or no to your question. In general, though, I would say keep as much off the FS PC as possible, and that is most especially true for Athlons. Actually I think the mixed systems the WideFS document talks about is with Windows 98 or Me and Windows 2K/XP. Windows 2000 is very much just an earlier version of Windows XP so as far as WideFS is concerned they are both the same. You would have no trouble with either TCP/IP (the easiest to set up), or IPX/SPX (more complicated because (a) it is an optional install, and (b) the Clients need the "server node" identifying exactly by a series of numbers giving the Network Number (usually zero) and the MAC address of the Server's interface card. There's a sticky thread near the top of this Forum about that. Regards, Pete

Send logs and KEY file, zipped of course, to petedowson@btconnect.com. A corrupted key would simply give you an unregistered FSUIPC, it is highly unlikely (almost to the point of impossibility) that it would result in a valid key which matched your name and email yet proved to further checks to be counterfeit. But you can check that yourself anyway -- just remove the KEY file temporarily so it runs unregistered. The PMDG aircraft are self-accrediting in an case. The fact that the errors seems to occur only when running add-ons which use FSUIPC could possibly mean that one or the other is actually causing the crash -- FSUIPC effectively provides an open window to applications for reading (not harmful) and writing (potentially harmful) almost anything anywhere in FS. It is quite easy to force FS to crash by writing the wrong thing in the wrong place at the wrong time. And consider that the more complex add-on aircraft do tend to use FSUIPC (not all, but many), so FS and your system generally is being tested more when using them, so things like heating and memory problems are not really ruled out yet. [To test memory I usually just remove one stick at a time -- it reduces the amount you have but at least proves whether the one removed is intermittently failing. This is not as uncommon an occurrence as you may think. I've had three memory sticks fail in the last two years]. Please be aware that add-ons like PMDG also install their own DLL into the FS modules folder. That is active all the time, whether or not you are actually using the relevant aircraft. I don't know the ATR, but maybe that does something similar. You can, I think, actually fly the PMDG aircraft with the PMDGoptions.DLL removed, so you could try temporarily removing that from the Modules folder, just as a test. When you say "these were only happening with add-ons that use fsuipc", apart from PMDG what else is there you are using which needs FSUIPC? Does the ATR? Sorry, but I am not familiar with many add-ons these days -- there are just too many to keep up with. Another thing which I know can crash FS, and nothing really to do with add-ons, is bad weather files (.WX files). These get saved with your Flights. If you are re-using flights you saved long ago, espcially ones with full downloaded or externally set weather, then try creating new ones instead. Finally, try flying with FS set to mid Summer, just as a test. It is possible that the 9.1 update didn't fix all the texture seasonal change crashes. Regards, Pete

If you have the current version of FSUIPC (or any quite recent version), then the default option settings will not cause that. The option which will do it (apart from running an external weather program of course) is "allow changes to FS own weather". That isn't checked by default, but if it is checked then FSUIPC will be making minor calls to the weather engine, and this will cause the theme to reset. Regards Pete

Are you actually using offsets or the added PM controls FSUIPC provides? I don't really know what, out of all the stuff in PM's offsets list, is actually implemented on the different aircraft modules he produces. My experience is only with the Boeing set. But, originally at least, many only operated if the MCP was running. I think Enrico changed that, but I'm not sure it is all working correctly. If you have questions on PM controls the PM newsgroup/forum is best. Regards, Pete

The directions to get here are, in fact, incorporated into all my documents, including the FSUIPC user guide, and on screen in the first page of FSUIPC options, and also via a link on the main download page at http://www.schiratti.com/dowson. :wink: Sorry, but FSUIPC doesn't touch any graphics at all, and most certainly cannot affect any changed bitmaps you have installed. FSUIPC cannot deal with textures of any sort whatsoever. It is merely an interface for other programs to control things in FS, and to read data from FS. It isn't part of its function to provide extra or different graphics -- I wouldn't even know how if I wanted to. All of the user-controlled weather facilities in FSUIPC are user options, available only to registered users (i.e. those with a valid FSUIPC key). For non-registered copies all such options set defaults. By default the random thunderstorm generator is off, in fact. The only option defaulted on in FS2002 is the one to add a high light cirrus layer occasionally. Please refer to the Clouds section of the FSUIPC user guide. You will find everything you need there. You will see (from the picture on the left in that section, which is the one for FS2002) that no other options are enabled by default, none at all. Replacement cloud packages consist of replacement textures. Once you've replaced the cloud textures manually, they are replaced. No program, and espcially not FSUIPC, will "bring back the original ones" automatically -- they don't even know if you kept them or where you put them. Programs which SET cloud layers through FSUIPC will set them regardless of what set of cloud textures you have installed. These are "weather" programs, like FSMeteo and ActiveSky. Regards, Pete

You have to get just the right input frequency. That's called resonance, and the same principle is used to tune frequencies in radios. The bath is replaced by a capacitance and an inductance which act in a kind of push-me-pull-you fashion which grows in amplitude for the specific tuned frequency, and acts opposing others. So, are you talking about the amount of bending the propellers are doing at their tips, or something? i.e. akin to the engine vibration measures in jets (the latter are of course checked in case they go out of balance -- bird srtrikes or other damage can take out enough vanes for this, I understand). Ah, if FS doesn't simulate this and give you a value, then obviously that's why it doesn't appear and why I cannot map an offset for it. There are many many parts of an aircraft not simulated in FS, even many subsystems either not simulated at all or only given token support. If you are really interested in completing these things then you may want to take a look at the Project Magenta pmSystems project. Although aimed at present at jet airliner systems, the idea and implementation are general enough, I believe, for much wider application. Regards, Pete