Pete Dowson

I don't think Teamspeak has a direct control for PTT, so you'll just have to program your button to send F12. Please refer to the section in the User Guide on programming Buttons. It's easy enough through the Buttons tab in FSUIPC options. Pete

Those are gauge variable names, nothing to do with FSUIPC offsets. Yes, all the fuel management programs around, including the freeware fuel dumping gauge and pmSystems APU and fuel-switching mechanisms, operate by changing the levels in the relevant offsets -- see the ranges 0B74-0BA8 and 1244-1260. All in all there are up to 11 separate tanks you can alter. This has been the case since FS98 days, in FS2000, FS2002 and FS2004 (except for the extra tanks at 1244-1260 which were added at some stage). Why don't you use FSInterrogate to find all this stuff out? That's what it is for. You can read values, see how they are computed, and write back values to see what happens. This is why it is provided in the SDK! Pete

Yes, it does actually say in the documentation (in the Registration part of FSUIPC's user guide) that your identification details need to be the same for both parts. Sorry.. SimMarket should be able to help, but otherwise I can arrange for an updated FSUIPC key for you. You will have to find the emails from SimMarket for both the WideFS and FSUIPC registrations and send them to me at petedowson@btconnect.com. Regards, Pete

Thanks. Obviously FSUIPC cannot guess whether the inputs it is seeing are reversed or not. You always need to set the Maximum higher than the Minimum. Then it will smoothly spread the needed range between. If the pedals work in reverse, that is give max braking with feet off and zero braking with the toes pushed firmly down, then they are reversed and need the "REV" option checked, BEFORE calibrating. However, the gentlemen here seem to be saying their input values were normally zero with feet off, going negative when pressure in "brake-off" direction (not sure how they accomplish that, mind). This does seem to imply that they are not reversed. Maybe they aren't explaining themselves well enough. Even so, it certainly seems to be a gross misunderstanding as to what FSUIPC does. All of the test joysticks I have here give ranges from values like -16k to +16k, so if I calibrate one of those for brakes I have the minimum brake input set at something like -16000 or less, and the max at +16000 or more. If I reverse them, it still seems right if I turn the joysticks around so the back faces methat really should be flexible enough! ;-) Regards, Pete

The -7040 to +7040 are the INPUT values. You must calibrate to set the minimum and maximum positions, then FSUIPC spreads whatever you give as the input range to the range FS needs: -16384 to +16384. Indeed. Please follow the very simple numbered steps in the documentation. That is what it is provided for. :-( Pete

You also don't understand FSUIPC's facilities at all? What is wrong with the documentation -- where are you misunderstanding the calibration? Pete

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