Pete Dowson

That message from WideServer normally means WideFS is not registered. Check the WideServer.LOG file and the About/Register option in FSUIPC. Pete

Show me the FSUIPC Log please. Which FS2004 are you using -- it may need the FS9.1 upgrade. Pete

I'll look, but I haven't used Esound for many many years and probably will struggle to help. There's so much commented out there that I've edited it to read it: [Devices] 1=Primary Sound Driver 2=SB Audigy 2 ZS Audio [DF00] [Polling] Epic=10 Var=5 [Sounds] Path=ESounds 2=ESounds\nappminimums 4=ESounds\nminimums 12=ESounds\nv1 13=ESounds\nrotate [Triggers] 2=ALTITUDE_ABOVE_GROUND<=410, 9,1 4=ALTITUDE_ABOVE_GROUND<=210, 7,1 12=AIRSPEED>= 138, 11,1 13=AIRSPEED>= 148, 12,1 Now there are several things I think need checking: 1. Where is the Esounds path? If the path is set to Esounds, why is the "Esounds/" part also in most of the pathnames? 2. There's also only one sound actually referred to -- 12. Sound numbers 7, 9 and 11 were commented out, so those trigger lines are no use. You must relate triggers to the sounds else how does it know? 3. Where is the [settings] section and line defining the device, sound position and volume level for setting 1 which is all you are using? If you want to omit [settings] and just default it you need to either leave off the ",1" or use ",0". [Now I know this is explained in the doc]. Regards, Pete

What version of my PFC.DLL? If not the latest interim, please try that (above). Sounds very much like Windows power management. Go into the properties for the USB port and switch it off. Also, try putting your two USB devices on separate USB hubs -- the motherboard USB ports are in pairs. Try moving one of the devices to a different pair. Doesn't it say? 3000 milliseconds in 3 seconds. Regards Pete

How did it tell you? Was it in a line at the top of the outside view in FS? I don't know the FSRealTime option for that. If it is in the message window, maybe you've got the options set incorrectly? Check those on the "About/Register" page in FSUIPC -- check the early pages in the documentation too. Let me know. The new options work with all the programs I tried them with, but I don't know the FSRealTime one. Regards, Pete

On the rotaries I have each "click" sends eith a button down or button up, so I program both. If yours sends a complete pulse (down and up) for each click, then simply don't assign a control to the release. Pete

Yes, it should do. Pete

No idea, but I would presume that after a snowfall the ground is supposed to stay white. Maybe you could raise the temperature to try to melt it? I really don't know anything about the graphics in FS. Sorry. Regards, Pete

Yes. Where did you get the key from, and when did you buy it? Have you read the announcement at the top about needing FSUIPC 3.53 or later? Regards, Pete

Yes. Where did you get the key from, and when did you buy it? Have you read the announcement at the top about needing FSUIPC 3.53 or later? Regards, Pete

I would need more information to help. There is no A/T Arm facility built into FSUIPC. What are you using? Does whatever it is work with a default aircraft? Pete

The graduated visibility option in FSUIPC graduates the visibility from the top of the normal FS layer to a specified higher altiude, with an upper maximum there -- so it varies as you might wish. There's no upper altitude limit to the visibility restriction as in default FS -- though even in the latter you can set the upper level very high. Unfortunately though this produces the same visibility value all the way up. Regards, Pete

No idea, but FSUIPC casn only deal with axes which are dealt with using the original windows joystick interface - XYZRUV. There are only six. FS now uses DirectInput and I believe that can support more. Regards, Pete

Oh, that. No idea really. It isn't anything to do with FSUIPC, it relates to how the problem of passing pointers to data in managed (i.e. interpreted) languages which MS seems keen on these days. was solved. Maybe someone who understands how the managed languages work can explain -- I never get that far away from the machine. Regards, Pete

Sounds like the axis is using a Log pot, not a Linear one. Regards, Pete

Because WX and FLT files are saved by FS, not by an external program. The problem with the external program arises because it gets notified of the second save and gets its name before managing to react fully to the first one. Really, if you are keen on saving files manually it may be better to simply uninstall AutoSave. Use one or the other, not both. Regards, Pete

Actually the current version, the one supported, is 3.60, though there's also now3 a 3.601 available above with a small fix. Not really. FSUIPC doesn't use any keypresses at all unless you program them, either in the Hot Key or Keys sections. Maybe something else is trapping that key? The sort of crash you are seeing is generally related to video drivers and their settings. If you are using full screen, try Windowed mode, or vice versa, to see if it make a difference. ALT + ENTER toggles these modes. You may also find that changing the "render to texture" FS hardware display option may help, or small adjustments to the anti-aliassing and other settings in your video driver. Finally, you don't say, but if you have not updated your FS installation to FS9.1 do that -- there were many crashes of this type in the early version. Regards, Pete

Take a look at the documentation you already have for FSUIPC. You don't pay for a particular 3.xxx version, but all 3.xxx versions. In fact you are expected to upgrade otherwise you don't get support -- as it says above, in the assorted announcments, I only support the latest versions. The same applies to unregistered users too, by the way. I don't expect anyone to stick with old versions. Regards, Pete

No, as it clearly tells you in the first few paragraphs of the WideFS documentation (see Important Notes). Exactly. Not only that, but it doesn't even use FSUIPC to interface to FS, so how would it use WideFS which is merely an extension of FSUIPC onto other PCs? Regards, Pete

Actually the latest build is 86, as I am using here. No idea, sorry. You'll need to ask someone who knows about these things. Try the Project Magenta support forum, pmSystems section. I think for use with PMsystems all your switches should operate pmSystems offsets, not FS directly. However, I really cannot support pmSystems. Whenever I have a problem like that I ask in the PM support area. There are some clever folks there who understand all that stuff. Regards, Pete

Well, round it up to a multiple of 16 at least ;-) When I said to be economical I didn't mean you had to be really stingy! ;-) Regards Pete

You are making an error with one or more parts of the entries then. Your name, email and Key must ALL be the same as originally notified to you for registration. If you still have difficulties email me all those details to petedowson@btconnect.com. However, all such problems in the past have been folks trying to use different details each time. The only exception was with FSUIPC versions earlier than 3.53 where registrations purchased in 2006 wouldn't work. Incidentally, the current supported version of FSUIPC is 3.60. I am on holiday from later today until May 14th so if you are not quick enough you'll need to resolve it with SimMarket. Regards, Pete

Did you look into the FSUIPC SDK? Check the table in the programmer's documentation. No. All that area is allocated and used by one application or another. Why use FSInterrogate for that when it is all documented? What you'll find that way depends on what applications you are using, and you cannot possibly use all that exist at the same time! ;-) If you want offsets not used by any other application you need to work out how much you need (please be economical -- do not, for instance, use a 32-bit DWORD as a single 'switch' when it can accommodate 32), then apply for an allocation. That is the only way I can ensure no clashes. Write to me at petedowson@btconnect.com. If your email doesn't arrive within the next 12 hours it will await my return from holiday on the 14th May. Regards, Pete

Didn't you check the FSUIPC user documentation. Here, I'll quote the relevant part from the table documenting all the axis calibrations: On a turbo the 8192 level is used by FS as the idle level, not 50% rich. If you are not using a turbo aircraft with separate cut-off and idle positions, simply calibrate the minimum at your detente, and make sure the two centre values are identical and approximate to the correct position on the lever. It sounds like you are calibrating for a turbo. Regards, Pete

No effect? Surely that cannot be? With maximum null zone in FS you normally loase the use of quite a bit of the axis movement. Maybe just not enough to reach halfway, though, which you may need? No idea, sorry. What "joystick programming software" do you mean? Yes, that arises through not having a large enough null zone for either. But, having got that far, I think you could now go to FSUIPC's calibration, calibrate left brakes with the "MIN" point set with the dial more than half way left, then the Right brakes with the "MIN" point set with the dial more than half way right, giving you a null zone in the middle. Experiment. Now you've nearly got there I'm sure it will be possible. Regards, Pete