Pete Dowson

Sorry, I'm confused. what other way? Did you check what happens when you apply limits, as i suggested? See FSUIPC's wisibility page. All the facilities in FSUIPC for graduated visibility, applying lower and upper limits, use the same part of FS as that 2DF0 offset. Please cross-check. What you describe sounds very much like a typical video driver problem. These visibility fiddles are nothing to do with the weather, they operate on the graphics control part of FS. Regards, Pete

Really? Only 16? That is surprising. Sorry, I know nothing at all about multiplayer. Check offsets 3F00-3FFF in the programmer's guide in the SDK. Regards, Pete

You cannot 'set' the IAS at all. The IAS is a result of computations in FS, not a control. You control IAS by throttle and pitch, mainly. You most certainly can control the gear with 0BE8. Wite 0 to make the gear retract, or 16383 to get the gear down. That's the control you have. You cannot "set it" to a particular position, only start it moving up or down. Locations 0BEC - 0BF4 are readouts to tell you where the gear is at any time. Writing to them has no effect. Regards, Pete

No, not via FSUIPC. Only the multiplayer interface can introduce "guest" aircraft. You can do that with multiplayer. Check the Microsoft official SDKs. No. the type comes from the aircraft data loaded from the Aircraft folder. You can, through FSUIPC, cause another "flight" to be loaded which, in turn, loads a different aircraft from the Aircraft folder. Loading a different aircraft into FS is a very major event. 90% of the locations which FSUIPC accesses to get the data for its interfaces are destroyed and re-created when a new aircraft is loaded. Regards, Pete

The verson of FSUIPC you are using is not 3.40 or later, then. Earlier versions are not compatible with FS9.1 (which has tha build number 9.01.40901). The current version, available from http://www.schiratti.com/dowson is 3.45. Just download it, and copy the FSUIPC.DLL into your FS Modules folder. If you were registered and you deleted all FSUIPC.* files, you will need to reenter your registration details. Otherwise just replacing the DLL will bring you up to date. Regards Pete

That sounds like a video card or driver problem. What happens if you limit visibility to similar values using the FSUIPC options? They drive the setting in the same way. 0F8C is nothing to do with the fiddles used to override visibility values. That's just a conversion of the weather read-outs available in more detail elsewhere. Regards, Pete

I think Bob's answer is correct, nonetheless. If you want revers on thr throttle axes FSUIPC has to use a different set of FS controls which run from 0 to +16384 for forward thrust and use negative values for reverse. The standard throttle controls available in FS itself support forward thrust only, with values -16384 for idle to +16384 for max. By using FSUIPC's individual throttles you are probably confusing the programming in the panel. You will have to do as Bob suggests I think. Regards, Pete

Sorry, I am really very very busy at present and cannot go chasing threads. If folks want help with anything they'll need to provide details here. Regards, Pete

Thanks. I'll need to install FS2000 on my test PC so I can debug it. Evidently the message I am expecting to see isn't arriving for some reason. I'm not sure I can solve it, but I'll take a look. Incidentally, all the stuff I put in 3.466 and 3.467 to try to make sensible decisions about when to propagate time changes is useless. It does manage to reduce the number of what may be thought of as "unneceassry" or spurious AI traffic reloads, but in so doing it defeats the object of trying to prevent later crashes. In my first proper lengthy (1 hour is lengthy for me these days!) test flight with this and FSRealTime running, I got an AI Traffic loading hang half way through. :( I'm going to make a couple of options (INI file settable) for now so that folks can make their own decisions, until I can work out a proper solution. Regards, Pete

Just replace the DLL(s). You don't need to re-register unless you delete crucial files, re-install Windows, or transfer to another PC. Regards, Pete

Did you try using a simple Search? Searching on "RPM" brings me to offsets like 0896, 0898, 08C8, 0908, 2400, 2408. And that's just for engine 1! Should be enough for any one! :wink: Please try using search, it saves me the almost impossible task of making an index! :? Pete

Why not enable the FSUIPC wind smoothing? Pete

If you want to release it as freeware for use on unregistered FSUIPC installations you will want an access Key. Check the FSUIPC SDK for the Access Registration document -- section 4 onwards. When you are ready, supply the details and I will make a key. Best to build it into the program for automatic access, as it saves users a lot of hassle. You'd be surprised how many ways there are of not entering an application key correctly! :wink: Regards, Pete

I replied to your email already. Regards, Pete

Are they all trying to plug into a single game port? What's an "AV-1"? First thing to check is connections and cabling. A standard game port can support 4 axes and 4 buttons (though some products use combinations of the 4 buttons to provide up to 15, provided you only press one at a time). But to get all the devices actually connected there would be Y-cable connections and so on. If those are wrongly configured nothing may work. Next thing to check is that your game port is actually enabled. Look in the Windows device manager, see if an active game port is listed at all. If not then it may be because it is disabled in your BIOS settings, or because there's no driver installed for it. If the game port is on your sound card you'd need to check your sound card drivers. Then make sure it is all recognised in Windows' game controllers. For one game port it will look like one device to Windows, so it may need a special driver. If your hardware devices came each with their own drivers and they all connect to one game port, you have a problem because you can only use one of the supplied drivers. You could see if one of the generic drivers provided by Windows works (2-axis joystick plus rudder plus throttle -- I'm ignoring the AV-1 at present because I don't know what it is. Failing all this I'm out of ideas I'm afraid. Maybe you will find help in a hardware forum, or the general FS2004 Forum. That is if no one else here can help. Regards, Pete

Personally I've not found the taxi wind to be needed in FS2004 as it was in previous versions, so I never use it. I really thought it was more for beginners? Of course it wasn't implemented in FS2004 for the first year or so because I couldn't find a way to influence the wind directly. So maybe I became more proficient! :o :? :wink: The idea is interesting, though it is complicated also by the wind smoothing option, especially on take off. When you say "ATIS wind" that isn't necessarily the real wind affecting the aircraft. I would be acting on the "ambient" wind, which is also the only one I can control directly -- providing I rewrite it every frame, which I do. If you would like to try it I will take a look and maybe will send you a special test version of FSUIPC by email. You test it on assorted aircraft and let me know (there's no point in my evaluating it as I am reasonably happy without taxi wind at all). After the next version (3.47) which I hope to release within a week, There will have to be a longer gap (other commitments plus a holiday!), so maybe I'll send something to try this weekend. Maybe I have to call this "progressive taxi wind" or "proportional taxi wind" and still allow beginners to use 1 knot? :wink: Regards, Pete

It's Dowson, actually, but you can call me Pete. No, not at all. The key checking I referred to was for USER keys, if you re-read it. The application keys for those freeware modules have not changed. The difference between 3.40, issued nearly 6 months ago, and all the releases since then is the tightening up of checks on USER keys. If you are not using any then it doesn't apply. If you are, and the applications work without them, then I need to investigate. Please do not try to put other words in my statements. there is a series of possibilities. One is that there is a problem which will be shown in the Logs, but since you only tried 3.40 and 3.45 and nothing in between even those may not be so helpful. The second is that you are using User keys and there is either a problem with them due to my tighter checking, so I need to look and see, or, indeed, that the keys are not genuine. I am not selecting any one of those, but it one case I need logs and in the others I need the KEY file. Do you understand now? Maybe, I don't know. I have absolutely no information to go on. Sorry. The only thing you've told me is that they worked in 3.40 six months ago nearly, but not in the supported version today. For all I know they may work in the interim test version supplied in the announcement above. Okay, thank you. But please also try the interim version. Maybe by the time you arrive home it will be 3.467, which I am testing here and should put up in place of 3.466 some time Friday. Regards, Pete

I cannot support such old versions, sorry. Please see some of the announcements at the top of this Forum. Current versions are FSUIPC 3.45 and WideFS 6.45. Far too much has changed since the very old versions you are using. I cannot work out anything from small extracts from log files. Please make sure you are using supported versions, and if you still have problems show me the log, not a distorted line like this. Thanks, Regards, Pete

Yes. As it says in the documentation, both FSUIPC and WideFS have to be registered with the same personal details. The old details really should have been mentioned to SimMarket at the time. However, all is not lost. If you send both your FSUIPC emailed Key notification and your WideFS one too, to me at petedowson@btconnect.com, I will make you a new Key for one or the other. Just decide which details you want and I'll re-do the other. If you opt to change you FSUIPC Key you will then need to delete the FSUIPC.KEY file from your FS Modules folder and then re-register both. Regards Pete

Here's a version (1.913) with the connection checking unlocked. You will still get them if one of these conditions is true: 1. No COM port specified or it cannot be opened (e.g. something else is using it) 2. The version of FSUIPC installed is earlier than 3.45 3. You have selected the 737NG cockpit as your 'console'. Good flying! Pete PFCDLL1913test.zip

Well, that was not a recent version at all, but several versions ago -- dating back nearly six months! The main change just after that was the tightening up of user key registration, because of a number of counterfeits being made. So far ALL cases like the one you report have been related to bad user keys. To test that, remove the FSUIPC.KEY file from the FS Modules folder, then load FS and re-register the freeware programs via the "register an application" button. If that fixes it, Zip your original FSUIPC.KEY file and send it to me at petedowson@btconnect.com. I need to see why it doesn't like your keys. If not, I still need to see the logs. There is certainly no rush to fix anything in 3.45 if it has been this way, for you, since after 3.40. After all, 3.40 was only a supported release for about a week and no others have reported problems with these specific modules in the months between. Regards, Pete

Yes, they should do. But I did lock them for some tests. Maybe I forgot to release that lock, I'll check that. Thanks. Regards, Pete

Can you be more specific, please? How are you trying to turn them off, and what console are you telling PFC.DLL you are using (I don't mean what you are actually using, just what you've told it). There's nothing turning any brakes on or off in any of the checking code. It merely checks inputs, there's not one output call in the whole thing. It sounds like you have so button operating that. Please clarify. Well, I'm not sure. But I've found USB serial port adapters, providing you get a recent driver which doesn't stall like my first one used to, more reliable and generally faster (more "responsive", rather). After all, although the simulated serial port they provide is limited to the set speed, the USB channel itself is much faster. It also is not reliant on the sort of interrupt handling that the real COM ports are -- I tend to think the IRQ handling side of the serial port drivers is one of the problem areas. On top of that MS and the hardware folks have been concentrating on USB (and firewire) as the connecting method of today and the future, whilst the poor old COM and LPT ports are left to fend for themselves, poorly. Regards, Pete

Really? There's been no change in that checking. Have you tried the test version of FSUIPC available through the announcements above? What previous versions please? Be specific. If your last "previous version" was 3.40 then a lot has changed. If it was 3.44 then little to nothing has in this area. It is quite significant, therefore. I can do nothing whatsoever at all without information. Show me the log. Providing you have no logging options you should be able to show the details here. It would have been better to do so straight away than go though the boring part of me saying I don't know because there's no information, don't you think? :wink: Regards Pete

You would certainly have to edit the INI file. Multiple actions on a single button are not possible via the options window. As I said, the system is not designed for passing strings at all, only 8, 16 or 32 bit numbers. That's why you have to convert your strings to look like numbers. After writing the string to 3380 you have to send the command to 32FA, as described in the Programmers Guide. That's another 16-bit value on the same button, but it must be last (higher numbered line). FSUIPC doesn't "update AdvDisplay". Messages are sent to Flight Sim. If AdvDisplay is running it intercepts them. If it isn't they display on the screen in the translucent green window over the top. All that is in the Advanced User's manual, the definitions of all of the FSUIPC-added controls are listed there. Regards, Pete