Pete Dowson

It works fine. Did you check the FSUIPC documentation at all? In the section actually describing the option it says Regards Pete

Well, unless some of your clients are slow, 20 is probably a bit low. You need to find the highest sustainable speed. Try 20, first, if that's okay move up to 30, if that is jerky or a problem, bring it down to 25 .. you know what I mean, "zero in" on the omptimum. That's okay, it isn't a problem -- I was only explaining the logs for you. I do the same -- in fact I have my own cockpit-based WideClients run in the Windows Startup group (there are no keyboards nor mice on 6 of the PCs in my cockpit in any case). If I were you I'd use the Windows task manager performance monitor to monitor the use of memory. If the numbers for committed memory just keep increasing the whole time you run FS (there may be little decreases now and then), then you probably have a memory leak. As time goes on this will gradually result in more and more periods of stuttering as a type of disk thrashing results. Eventually (and it would take a long time if you have lots of disk space) FS would say there's not enough memory and close down or simply crash. Regards Pete

Most all of the low-offset values are read-only, derived from values elsewhere. You could try writing to, say, 3AA8 (oil leak percent) to change the oil quantity, but i'm not sure that will work either. When the sim engine is running most of these values are *results* not inputs, so your value will simply be overwritten on the next sim frame. I'm hoping to be able to do a lot more in FSX and beyond. ;-) Regards, Pete

No, no errors at allThe server shows a good start up at time approx 19:56, when all three Clients connect. Then FOUR HOURS and 21 minutes later, all three clients disconnect -- it looks like you closed them. The OVERHEAD and FLIGHT logs appear to be from a completely different session, judging by the time -- 10:12. They also simply show that you started them before the FS PC ("laptop") was even available (not booted) -- Windows can't even identify it for the first 3 minutes. Then there are 29 minutes where it knows the PC but there looks to be no FS running at all. Then it connects, WideClient loads up 5 programs on the FLIGHT pc and two on the OVERHEAD. Then you took the file and Zipped it up. You never closed anything down, the log doesn't finish, there are no errors. none at all. The GC log is from a different time, again (?) -- 00:46, but here at least you started it when FS was running, it connected directly, loaded up PFD x 2 and ran without errors till you closed it down tidily a bit over 10 minutes later. Because it is closed tidily (the ONLY one!! -- please ALWAYS close everything before supplying logs), the performance data is shown at the end. And it is a very high performance indeed. It averaged 49 frames/sec for those 10 minutes -- what do you have the FS limiter set to? I think you might want to bring it down a bit as you are in danger of overloading your client PCs, if not your FS PC. NO ERRORS at all on the Network.WHERE ARE YOU MEASURING YOUR FRAME RATES? If those are FS frame rates, you have an FS problem, not a WideFS problem! None as far as I can see. There's nothing here that shows there is a Network problem. Why do you think there is in the first place? You never answered the question about that -- what are these fluctuating frame rates? Where? Why suspect the Network in the first place? Regards, Pete

It's a folder (a place on your hard disk, where files go), called "Modules" and it is inside the folder where your copy of FS is. I don't have a website. Alll my FS files are available from http://www.schiratti.com/dowson, where they've always been, and of course where many of the Announcements at the top of this forum point to. Why not try browsing through those occasionally? How did you even manage to find this Support forum if you can't find my programs? I don't understand! :-( Because you messed about with it by installing older add-on programs which were published before the version of FS you are using was ever known about, let alone available. If you want your FS installation to stay pristine, just never ever add anything to it at all. If you give in and add things again and it goes wrong, please ask for help from the folks who published the add-on that messed it up! Pete

You are using FS2004 updated to 9.1, with a copy of FSUIPC dated much earlier. Thast very old copy of FSUIPC has no knowledge whatsoever of the later version of FS -- it cannot see into the future! However, FSUIPC was updated to work with the updated FS2004 on the same day it was released, long ago! Just download the current, supported, version of FSUIPC and put it into your FS modules folder. Microsoft did actually tell everyone about all this in their FS2004 update READ ME, but of course no one ever bothers to read those, do they? They should have called it "DO NOT READ ME UNDER ANY CIRCUMSTANCES!" :-) Pete

Sorry, my WinRAR free trial expired long ago. Can you please ZIP files, not RAR them? Why WideServer? Are there errors shown? What about the Client(s)? There are two ends to every connection, you know (at least! ). Where are you measuring the frame rates. If those are FS frame rates, then it is most likely FS which is clobbering WideServer, not the other way around. Either way, as it is cumulative it sounds VERY much like a memory leak in FS filling up real memory and causing serious periods of virtual memory swaps. I think this is usually caused by certain types of scenery (land class files I think) being configured or situated incorrectly. I had lots of problems exactly like that after installing a bunch of scenery and only found them after several hours of elimination. I decided to do without the culprit scenery when I found it. Regards, Pete

The information is available, and FSUIPC can log stuff, but it wouldn't be in a form you'd want to have to analyse. You'd really need a program written to interface to FSUIPC to read such things and analyse it at will. There are some programs around which do extract and partially analyse (or at least present well) a number of values. I don't know anything specifically in the area you are interested in, but FlightKeeper does the sort of job I like as an airliner flyer -- I'm not an aircraft designer though. ;-) If you don't fancy doing any programming, have a search. Maybe there is a suitable program already available. There are several which do monitor performance type values but I don't recall their names off-hand, not really using them myself. Regards, Pete

I don't know much about these things, but I think programs need you to have admin rights to be able to change the registry, or do much installing in certain places. I think even having FS in its default place (in "Program Files") can present problems unless you have Admin rights. If you are the only user and haven't restricted your access deliberately, it sounds like something has. Best ask over in the FS2004 forum. Katy Pluta visits there occasionally, and knows a darn sight more about these things than I. Regards, Pete

No. In the US most if not all of those beginning with K do, but a lot of the lottle ones don't. World-Wide it varies. There's a list in the Weather folder. How did I prove that? By saying, as you just repeated again, that "FS stores a "base" elevation in this area as, for example, 600' MSL. With a surface wind layer altitude set to 1000', this will result in a surface wind layer of 1600' MSL. Whether I'm over a mountain, a low point in the valley, or a high point in the valley, the surface wind layer altitude stays at 1600' MSL." Since 0B4C is the ground altitude beneath the aircraft, not this strange "base altitude" you've found, how can both statements "0B4C + 0EEE" give the wind altitude AND "Whether I'm over a mountain, a low point in the valley, or a high point in the valley, the surface wind layer altitude stays at 1600' MSL." actually be true at the same time? They appear to contradict each other. Exactly. You've said it again. And 0B4C is therefore changing all the time. If 0EEE + base (600) always = 1600 .... well, I surely don't need to go further? Oh, you are saying the 0EEE changes all the time tooAh, that's different. Sorry, that changes everything. But in that case .... where does this base altitude of 600 come into it? I'm now even more confused. :-( Anyway, at this stage, three full years after FS2004 and FSUIPC3 were released, I can really do no more than document this for anyone still concerned with FS2004 after FSX comes out. Incidentally, some checks with FS98, FS2000 and FS2002 are necessary really, to see when and what changed where. Thanks! Pete

What does the FSUIPC Log file show please? All the details are in there. Pete

Very good! Thanks for letting me know! Regards Pete

You cannot insult me by asking straight-forward questions ;-), But I am sorry, I am really too busy to take on additional work. I am actually hoping to reduce my workload so I can do some flying one day! If you want a programmer to help you write software for your cockpit, though, I certainly think that you may find others here, in my Support Forum, who might be interested, especially if it means getting their hands on some nice cockpit hardware. I suggest you word out your plans, in as much detail as you can without revealing anything you shouldn't, or committing yourself to anything you can't keep to, and post again. I could make such a post 'sticky' for a while, if you like, to keep it near the top. You should also consider the same in the cockpit builder's Forum, near here, and possibly in Project Magenta's support site. Have you also thought about the possibility of talk to PM's Enrico Schiratti, who currently does support a variety of advanced cockpits with his software? Good luck! Regards, Pete

Erno it wasn't. The first message, just above, contains only this: This seems to assume some earlier messages in the thread, but there are none. Maybe you started a new thread by mistake? Oh, that problem. Right ... Erwhy the "?" on "outside window". The window that shows the outside -- the scenery, the view through the front window? How have you hidden the menu bar if you've never found out about the right-click menu? You can edit the FSUIPC.KEY file (in the FS Modules folder). Just add a line in the [Programs] section (add that line too if it isn't there). The registration line to add is =KEY For example squawkthing=ABCDEFG12345 No spaces, just the name and the key as listed in the Freeware keys list. But please do try to unhide the menu -- I can't understand how you can possibly not know about that FS facility? Regards, Pete

If they are short enough, just, show them here. Otherwise ZIP them, with your INI files too, and send them to me at petedowson@btconnect.com. Pete

What "DrWatson" log? It is the FSUIPC Log that is relevant, and that is in the FS modules folder. It is a plain text file, you can look at it and show bits here. In any case, if your only problem is access permission, please use the freeware key provided -- check the announcements/stickies at the top of the forum. Pete

Described before where? This is the first message in this thread!! This simply means that you have failed to enter the Key to allow Squawkbox to talk to FSUIPC. See the Freeware keys list above, and refer to the FSUIPC user guide for how to enter it. Pete

I might be able to help, but I need to see the Logs. Why are you so reluctant to provide the information to help? There is absolutely no point in reverting to old versions, they really will NOT make any difference if you have a Network problem. And you will never get any further help from me if you don't keep to latest versions. So, please just do yourself a big favour and help me help you. Pete

No. FSUIPC is entirely irrelevant. it has no bearing whatsoever on your Network. In WideFS there have been no changes to the Network protocol actions in a very long time, only the addition of UDP support a few months ago. If you aren't going to show me any logs I cannot help. If you don't want to use supported version I cannot support you. Please re-consider. Pete

As I said, let me see the logs. Something is wrong with your Network. Pete

Sorry, but I only speak English, C and ASM. Perhpas someone else will be able to help? Normally nothing needs changing or entering at all, expecially if both systems are running Win2000 or WinXP. This is with the current version I notice that now, in this message, you have changed your story. Originally you were only saying that the PTT didn't work at all. Now it is far worse! ... This sounds most definitely like a Network problem. This is NOTHING like a "failure of PTT" you originaly reported. What has changed? I cannot with no information. ALL information about what is happening in WideFS is provided in the LOG files. Please show me the WideClient LOG and the WideServer LOG files. PLEASE DO NOT MESS ABOUT WITH THE INI FILES! Pete

Hmm. Everywhere? Did you try looking in the FSUIPC user guide at all? I do't know if you are a Registered user or not, but it is possible either way. This part of the section "Message Window Options" is relevant (it's about the 7th para): Pete

Please update. that is very old. Current version is 3.70. There's no sensitivity adjustments as such in FSUIPC. For that sort of thing go to FS's menus -- Options, Controls. FSUIPC does offer a response adjustment for axes calibrated in its "Joystick Calibrations" section. It is all fully documented -- you can choose between settings with difference amounts of flattened (lessened) centre responses. It is done with a graphic showing you the response curve. There are pictures in the User Guide, even, please take a look. I don't know the aircraft you are using, so I have no idea if these facilities will truly help. Regards, Pete

Ah, so it is in 100ths. FS will be scaling it then, on the input side. Thanks for the info. It is stil really only a bunch of 8 buttons! ;-) Pete

Okay, the logs show that the connection of the Hat to FS in this was generates exactly the same sort of controls you are doing with the assignments to PAN_VIEW with the parameters 0, 45, 90 and so on. I think that if you enabled Repeat whilst held then the results should be indistiguishable. The DLL itself cannot be patched or changed internally with causing failures when it is run. It is protected against hacking, if that's what you mean. With FS2004 and before it cannot be stopped from loading by FS even if it is hacked -- I think that is likely to be changed in FSX though. If you merely mean to stop another installer installing an older version, well, you could try making it read-only in Explorer. but programs can remove that attribute in any case. If you are frequently installing such packages with bad installers like that I would recommend that you simply right-click on the FSUIPC.DL after each installation and check Propeties Version. Obviously dong this 10 times an hour wouldn't be convenient, but i wouldn't think you were installing or re-installing packages so often unless you are in a shop demonstating such processes. It's just a little free-standing utility originally provided by Thrustmaster for checking their joysticks. Anyway I don't think you need to use it now. The logs show everything. The Hat is NOT a continuous axis providing values 0-360, so it doesn't really justify axis treatment. It is merely 8 buttons with a common "off" position. I think the provisions in FS and FSUIPC are fine. I think the log shows it can and does if you program the 8 positions using PAN_VIEW with parameters 0, 45,315 and enable repeat. Yes. You have a little more flexibility with FSUIPC in that you could even program the 'offs' differently, eg to choose to execute "VIEW_FORWARD" to return to a normal view, as you might wish. Regards Pete