Pete Dowson

I don't understand you. Whether the INPUT values are negative or positive simply doesn't matter. ALL that matters is that the maximum is higher than the minimum. Many joystick inputs actually give ranges from -16380 or so to +16380 or so, yet FSUIPC's calibration will still give zero from wherever you want the "no braking" limit to be! I think you must be misunderstanding something fundamental about how FSUIPC calibration works. Perhaps you should read the documentation again? Please follow the calibration instructions. In the case of brake pedals, press your foot lightly on the pedals just a little so that you would, without calibration, be getting a bit of braking. Set that as the minimum. Set the maximum to something off the real maximum. Then the braking will be proportional between those two points, and anything outside won't be -- the output will remain zero below the slight touch point, no matter HOW negative things get, and maximum beyonf the max point you set. It really is that easy. I don't understand how you could make such a meal out of it. :-( Pete

Correct. Why not read that very fact right at the beginning of the WideFS documentation? Pete

Because either the registrations you have are illegal (pirated) ones, or because you have registered in 2006 and are still using a VERY OLD version of FSUIPC! Please read the announcements above. The current version of FSUIPC is 3.70. Pete

It doesn't matter where you put them. Your choice. If you have two HDs I usually fnd it best to keep Windows and all its system files on one and all my applications on the other -- hopefully this allows dual access with less head movements, but I doubt if it is a measurable difference. Regards Pete

That's how SimMarket send them. but if you have backed up your files then all the details you need will be in the FSUIPC.KEY file, in the old FS Modules folder. It's only a simple text file -- open it with notepad. If you can't find it check that Sticky above about what to do if you lose your key. Regards, Pete

You'll need to re-enter your registration details too. And don't use an "old DLL", get a new one. Maybe even 3.705 from the Interim Version announcement above. Regards, Pete

It is pretty well instantaneous herehave you used FSUIPC's extensive logging features to log the reads and writes (Monitor the offsets involved to the log as well) so you can see the timing relationships. I really don't know how you've programmed you EXE -- if you scan the values you are reading every 2 seconds then you'd expect an average delay of 1 second. If you scan every millisecond then, apart from bringing FS to its knees you'd see it change faster, but put much more load on the system. It also depends on FS frame rates. If FS is running at 30 fps, say, then most requests should be easily met in 33 mSecs (1/30th second), assuming your program is matching the frame rate and doing so without impinging upon performance. Programs like Project Magenta's MCP perform many interactions with FS every second -- that part of the PM suite is an advanced autopilot and would not be able to control the aircraft properly unless the response was good. And it does control it, and very well, even over a WideFS network link in some folks' systems. As you see, there are too many imponderables for me to judge timing from what you say. You'd need to research both what your program is doing and what FSUIPC is seeing -- the logging helps with the latter. Regards, Pete

Really? I thought the tug control did nothing. Maybe the parameter is the direction in degrees, so it would be relative then? The pushback control merely starts the pushback straight back, and then pressing the 1 or 2 key selects the direction of turn. I don't know of any other way -- if you are experimenting with the tug control, please do let me know what you find out. I thought the tug controls were unused in FS. Regards, Pete

Er, why "state" as 0 and 1. Oil leak persent will not be a BOOLEAN on/off think, it's the amount of oil leaked as a percent or proportion of the total capacity. Writing 0.0 will presdumably give you 100% full, and writing 1.0 may either give you 99% full (100% - 1% leaked), or totally empty, depending on whether MS really mean "per cent" when they say so, or, as is often the case, mean "fraction" 9so 0.5 is a half, etc). I should think the oil pressure would drop to zero if you leaked 100% of the oil. But it certainly says it is the oil leak percent. Why can you do things from your application but not from EPIC? Surely if you cut off the fuel the engine shuts down? That's what you are doing writing to 0928 -- it's the same as using the mixture control and pulling it back to full lean. How can it not? Pete

Answered earlier in this thread. Try http://www.schiratti.com/dowson as noted in many places including just above! I have no server, by the way. Pete

If Windows sees them all, so will FSUIPC. There shouldn't be any problem, though the interface in Windows I use does limit the total number of Joystick devices to 16 (not the 128 for USB devices read via DirectInput). Just be warned that, in FSUIPC 3.70, if you are using Aircraft-Specific joystick calibrations there is a bug in that version which messes up the loading of those from the INI file unless you set "ShortAircraftNameOk=Yes" or "ShortAircraftNameOk=Substring" in the FSUIPC.INI file -- by default it is set to "No". I have fixed this and will upload an interim update to the Announcements above shortly, maybe even later today. If they all contain the word "Cheyenne" then simply edit the INI file title (the bit in [] brackets) to read "Cheyenne" and set ShortAircraftNameOk=Substring. Then it'll match anything with Cheyenne in the name. Regards Pete

Work with which Flight sim? Why do you think it won't work with the current version of FSUIPC? It should do, but you'll probably have to buy a user registration. Pete

You can pay for WideFS separately and register and use it without paying for FSUIPC. The registration of FSUIPC gives you access to all the facilities documented in its user guide, but nothing extra for WideFS -- which is why I advised you to look at it first. However, if you ever do want to take advantage of the FSUIPC facilities, like button, key, and axis programming, accurate joystick calibration, and many other assorted facilities, then it is certainly cheaper to buy both FSUIPC and WideFS together. ;-) Regards, Pete

It looks like ActiveSky is trying to access FSUIPC to set the weather before it has actually passed it's Access Code: see these lines The registration check seems to be occurring AFTER the write to C800 (which is part of a request to do something with the weather). I can analyse this further if you would like to enable IPC Write logging (a check box in the Logging page of FSUIPC options -- enable it before running ASV6). But there is something vaguely familiar about this error. Maybe it has happened before and is now fixed? I cannot recall. If you are not completely up to date with ASV6, could you update it first and try again -- I think the latest is SU4 ("Service Update 4"). It may also help to post your question (and this, my reply) on the ActiveSky forum. There will be no Version 4 for FS2004 and before, so it depends if you are planning to update FS to FSX sooner or later, or not at all. FSUIPC4 will only run on FSX and later and will need a new registration. Regards, Pete

You mean you paid first without even LOOKING at them? Both Zips have full documentation. The normal thing to do is find out all about them, decide if you need them, THEN buy them if you want. I do hope you've not wasted money -- you don't need to buy FSUIPC to use PMDG aircraft as they have licensed access. http://www.schiratti.com/dowson Regards Pete

When folks have any problems whatsoever FSUIPC always gets blamed first. No, because FSNavigator is NOT a separate program, it is an FS module, just like FSUIPC. It doesn't even use FSUIPC or anything of mine at all. Pete

No. Why would you even suggest it? Pete

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