Pete Dowson

You are failing to read the User Guide, one of the documents among those "14 icons", which explains clearly how to install in its first few pages. You most certainly couldn't have Registered it yet as it has to be installed first. Instructions for Registering are strangely also to be found in the User Guide. Why not try reading documentation first anyway? It is there for a purpose. ;-) Regards Pete

Well, I would tend to ascribe that to the likely fact that very few folks have enough joystick axes to assign multiple throttles, prop pitch controls and mixture levers. When there's only one the generic mixture lever is used for all engines, and that has no "idle" detente setting. If there only three settings, why are the levers showing continuous smooth changes with associated mixture values? Regards Pete

If FSUIPC is not configured to do anything, it is "turned off". Who exactly is "calling2 for this, and in what exact terms? I've never heard of anything like that before. For example, if you use FSUIPC for weather options, or to program some buttons, how is that possible impinging on ther aircraft? No, but all of your axis assignments, joystick calibrations and even buttons and switches can be made aircraft-specific. Though I fail to understand what could possibly be required here. What are they REALLY talking about? No one else has ever mentioned anything. What exact problems have you got? Without specifics there's no way to help you. Regards Pete

Why are you messing with the INI. Use the Options screen, in FS. Don't! Go to FSUIPC's "buttons and Switches" option, press that button, opt to program it for a control, not a key press. In the drop-down find "Offset Word Set" and assign it, set the offset to x4850 and the parameter to 5002. Confirm, exit, job done. Please do take a look at the FSUIPC User guide, which even has pictures and examples. Regards Pete

Thanks! It is so nice to receive the occasional note from someone without a problem attached! ;-) Regards Pete

No, not at all. That just complicates matters. If you don't need it, don't install it. What appears to be the problem is that you have the SP1 update installed, but the SimConnect for it is wrong. The base version of SimConnect is okay (it is that which is loading FSUIPC), but FSX doesn't want to use it as it believes the SP1 version is there. The version of the DLL in that second folder should match the version number on FSX.EXE. I think you have a mis-installed SP1 update. You need to try uninstalling SP1, checking again, and if things are then okay, re-install SP1. There is a possibility that this process won't actually re-construct the WinSxS stuff, so after doing it if it still doesn't work, i think you'll have to try deleting that second folder, above, and repeating the uninstall/re-install process. Please do send a note to tell_fs@microsoft.com about all this. I want to make sure they fully realise the extent of the problems their installation process creates. No doubt a lot of this is to do with windows rather than FS directly (Windows is responsible for the WinSxS system), but I think the FS team need to attend to it. The SP2 or Acceleration update avoids problems with firewalls for local use of SimConnect, and the installation process should have been improved too. Acceleration doesn't need SP1 (it will install it if it isn't there), but SP2 needs a good FSX + SP1 to start with. Regards Pete

Yes. It's the FS "live" weather processing for wind layers (I think temperature layers have similar but less consequential problems). The same bug occurs in FS9 and FSX, and it doesn't just appliy to weather written through FSUIPC (or SimConnect in FSX), but also to FS's own downloaded weather. Unfortunately, so far, there's no fix in FSX, so the 180 degree and similar windshifts are a really serious problem. The only way in FS9 to fix the matter is to use FSUIPC's wind smoothing, which actively overrides the resulting winds at the aircraft on its way from the WEATHER.DLL to the Simulation Engine (SIM1.DLL). I'm still looking for a way to do the same in FSX. Regards Pete

But the throttle quadrant mixture levers in the FS King Air do slide continuously, not jump, if manipulated by mouse or normal FS controls. If that is the case, I don't understand why I built a jump in at all. Regards Pete

Sorry, but you missed the question. What was the real FS Map (World menu -- Map) showing as the TRACK (not the HEADING?). And what was the HEADING INDICATOR showing? All these things, HSI, Heading Indicator, FSNav get their information from the normal FS gauge variables. None of this comes from or is influenced by FSUIPC. Regards Pete

You seem to have ignored parts of my previous reply. Please give me an example of the messages you are expecting to be suppressed. The only one you've mentioned so far is "tailhook extended" which is one I've never even heard of or seen myself. I really cannot do anything without more details. Possibly the messages you are concerned about were never suppressed by FSUIPC in any case, only by FS CFG file parameters, which you have forgotten to re-enter? No, no way. FSUIPC is completely self-contained in this. It intercepts the messages via a hook into FS's innards. The only way that wouldn't "take" is if the version of the module it is hooking into is one which it doesn't recognise. FSUIPC3.7xx recognises FS9.0 and FS9.1. It may not work with FS9 pre-release Betas. Incidentally, these messages cannot be intercepted in FSX in any case. The facility now only works for external program's messages. Regards Pete

Yes, buthere's the problem. WHAT, if any, turboprops need this jump? The ones supplied with FS don't, evidently. This is why I am at a loss to understand why the jump is there in the first place. You said it was okay for turboprops -- but why? Where have you found this to be so? Jets are okay. There's no mixture control as such -- it operates the idle/cutoff switches and they are either on or off. That's what I was thinking. But I would still like to know why there's a jump in the first place. Maybe it was by request, but if so it was for an aircraft I cannot seem to identify. Regards Pete

Great news! Thanks for letting me know. Pete

Hmm. It sounds exactly like you are mixing up Track and Heading. With a severe cross-wind the heading will not be anything like the track -- the aircraft will appear to be heading one way but still follow the desired course over the ground. double check that -- look at the FS Map, which shows your path over the ground. The ND in most airliners can be set to Track up or Heading up. Set yours to Track up, then you won't be fooled any more! ;-) Regards Pete

Okay, maybe you can, but I don't. This isn't a problem because only Wideclient can use the connection and it is (a) only run where you want to run it, and (b) directable to a specific Server and port. Regards Pete

Then you are not looking in the Modules folder which is being used by the FS you are running, as there is nowhere else for it to read it from. If you are using FS2004 under Vista and have allowed FS to install into Program Files, bear in mind that you don't see the real Modules folder unless you run as an elevated administrator -- because FS2004 is not Vista-aware, Vista actually aliasses the folders so that programs can write to the otherwise protected ones in Program files. I repeat my earlier question. Why are you wanting to do this in any case? The only possible reason I can think of is that you are using a pirated/illegal key and this is causing FSUIPC client programs to fail. Is this the case? Regards Pete

Which "previous version"? Version 3.75 is quite old already. And there's no problem I am aware of which could cause such diverse and strange problems, especially for sophisticated aircraft which do their own things so successfully. I doubt it, as 3.75 is still the main current version. By all means try 3.766, available from the "Other Downloads" Announcement above. But otherwise I think you need to ask around in the PSS and PMDG forums, respectively. It sounds extremely unlikely to be related specifically to FSUIPC. Regards Pete

I don't know what WidevieW does, I'm afraid, as it is not my program. However, Server's listen on PORTS, not IP addresses! You seem to be a bit mixed up. WideServer listens on a specific, configurable, port. Where else are you running WideServer? Only the PC running FS will be listening on the selected port. Regards Pete

What do you actually mean by "the registration does not go away"? If there is no KEY file in the Modules folder then FSUIPC sees no registration. That's it. Nothing else. It is simple. Why are you wanting to do this in any case? If you simply want to throw FSUIPC away, just dleete it from the Modules folder. Pete

Okay. I've checked anyway, using my own primitive joystick (a game pad actually). It seems this has ALWAYS been the case, on all versions of FSUIPC, no matter how assigned, for many years. The problem I have now is that, from the coding, it looks deliberate. i.e. not a bug! But why? You said "this is OK for TurboProps", but why? There aren't many turboprops in FS (default), but they all seem to have smooth mixture values between 8k and 12k. So I'm a bit at a loss to know why it is programmed like this in the first place -- it is lost in the mists of time. Well, you'd think so, wouldn't you? Especially since it has always been like this. Someone may have noticed but certainly you are the first to bother to mention it too me. I am a little worried that, if I "correct" it, I will mess someone else up. If only I could understand or remember the reason for it. Regards Pete

Sorry, that doesn't make sense to me I'm afraid. The "Cl" and "Dt" buttons are one and the same. It's a toggle. If you press "Dt" you switch into detente mode and the button changes to Cl, if you press Cl, then the detentes are cleared (including the detente displays) and the button changes back to "Dt". You cannot set any detentes whilst Dt is showing, you have to press it to enable detentes. When you press Cl, you don't get any #0 or #1 showing! Please explain what you mean. Can't you simply follow the steps given in the user guide? None of the values are "cleared", only the detentes. Values are only ever set by YOU, pressing the "Set" buttons above the value displays. They don't change otherwise. The OUT value will only change in response to calibrations already set. You are calibrating against the INPUT values in order to AFFECT the OUTPUT values. That's the whole purpose of the calibration facilities! With detentes, when set, the OUT values will jump from one flaps position value to the next when the axis moves over the half-way point between two of your calibrated detentes. They won't change otherwise. Regards Pete

Can you be more specific, please? What do you actually do and what is the exact result? BTW I always need to know version numbers -- if you are using one older than 3.75 please update and try again. And a sight of your FSUIPC LOG file (from the FS Modules folder) would be useful. No idea. Does it install something into the Modules folder too, or is it a completely separate program? If so, and you don't run it, it shouldn't have any effect. Regards Pete

Have you downloaded the FSUIPC SDK? The answers are all there, together with exampl programs in several languages. You'll have to write a program. You could write a program to do that if you have documentation for Excel file formats, but it seems a long way round. You'd still want to send it to the PLC. Regards Pete

So it's using Windows Server 2003, which I believe is a development from Windows 2000? All my Windows programming books tell me that the Win32 API (application programming interface) is compatible across the range (unless you use very new stuff particular to later developments), so, since WideFS was developed on Win95 (originally), and continued working through Win98, Windows 2000, WindowsXP and Vista without any problems or specific changes ever actually needed, I'd be really amazed if it didn't work on Windows Server 2003. Regards Pete

What's a "Small business Server"? What version of Windows is it? WideFS runs on most versions of Windows since and including Win98, though I'm a little dubious about WinNT4 and earlier on that line. Sorry, no idea whether Active Sky works on whatever version of Windows you are talking about. If it's a current version of Windows, wouldn't these things be supported in any case? Doesn't Microsoft try to provide some level of compatibility? Regards Pete

Sorry, I don't know Cockpitsonic (hardware or software?), so I cannot say, but it seems likely that you have to actually set a non-zero value, or even a single bit, not write zero to 564D as you are doing. Don't they supply any documents to tell you which bits in which offset do what? Checking my lists of offsets allocated to third party programs, I see that the whole range, 5600 to 56FF, is allocated to pmSystems, from Project Magenta. Has "CockpitSonic" made use of the same offsets, or are you actually using Project Magenta? Where did you get the offset value 564D from? If you are really asking about pmSystems, then you should really be asking in the PM support forum. http://www.mycockpit.org/forums/forumdisplay.php?s=884 (There is one specifically for pmSystems). However, looking at the pmSystems "sysvar.txt" definitions, 564D shows this: 564D .0 FireHandleEng1 564D .1 FireHandleEng2 564D .2 FireHandleEng3 564D .3 FireHandleEng4 564D .4 FireHandleAPU 564D .5 FireWheelWell which shows that the wheel well fire is indicated by bit 5, not the value "0" in 564D. Bit 5 is 2^5 or 32 in decimal (x20 in hex), so you need to use the "Offset Byte Setbits" control in FSUIPC with a parameter value of 32 or x20. Regards Pete