Pete Dowson

You mean your user key? Have you bought one for FSUIPC version 3? Please check the documentation. You don't get user keys free. If you have registered FSUIPC 3 before then you don't need to again, unless you deleted your KEY file. Regards Pete

If you mean version 2.xxx then your FS2004 system would have been pretty unstable. FSUIPC makes lots of calls and access directly into FS code internals, and any one of those can cause a crash. If you haven't been experiencing any you have certainly been extremely lucky!! Furthermore, I know of nothing changed in FS9.1 which would make you more or less lucky! It is nothing to do with that. About 50% of all the code in FSUIPC had to be re-written over a 6 month period just to get it working at all in FS2004. I think in view of your misdemeanours it is! :wink: But you should also download the FSUIPC SDK and read the Access Registration document. Possibly look at the freeware keys sticky near the top of this forum. I would obviously be a bit reluctant to grant you any sort of free access after this, but I am open to persuasion, assuming you are producing freeware useful to others and will make it available as such. If it is for purely personal use it doesn't count as "ware" at all really. Anyway, I think, if you really take a good look at the SDK, and at the user facilities FSUIPC offers, you will come to the conclusion that it is money well spent. Regards, Pete

That's correct. I've never heard of it, and it is not an accredited program. It will only work with a user-registered copy of FSUIPC. I don't know what you did 6 months ago, but that gauge has never been issued with an access key. Maybe it was a different gauge you had back then? 108485 Module identified = "ah64.GAU" 108485 Illegal read attempt: offset F000, size 2 It looks like it wants to read something to do with AI traffic. Regards, Pete

You are doing it the wrong way round. The numbers are only feedback, to show you exactly what is going on. Pretend they are just bars moving up and down or something if you like. You should be concentrating on where YOU want the different positions to be on your joystick/pedals. You don't even need to look at any numbers except to verify that your control is being seen and is moving in the expected direction. Why don't you just follow the numbered steps in the documentation? The ones that follow the words "Now, to calibrate any axis, just do this:"? Surely they are clear? If not, why not? I've not had any reason to enlarge on what is there for years. The only mention of numbers is to check that they do change and that they change in the right direction, that's all. Regards, Pete

I assume this is with a user-registered installation of FSUIPC? It sounds like you have some Joystick options selected and operating. Edit the FSUIPC.INI file and delete the complete [JoystickCalibration] section. Do this before loading FS. If you want to use the Joysticks facilites in FSUIPC, do so but please take care to calibrate correctly. Follow the steps in the documentation. No, there are no actions taken by FSUIPC unless these are requested by a program, gauge or another DLL. FSUIPC is primarily an interface for other programs, it does very little itself, and all the things it does do can be seen in the options available to you. Whilst there is one for autopilot, to correct a wrong-direction Vertical Speed, there isn't one that says "veer off course". :wink: You never need to "remove" the DLL file to "reinstall" -- if you copy in the DLL it will overwrite the one that was there before. If you want to start again from default settings you need to delete the FSUIPC.INI file. That's the file which contains everything you've done to FSUIPC's options. Then you most certainly have the brakes badly calibrated in the FSUIPC.INI file. It will not touch ANY of the joystick/pedal inputs by default. Delete your INI file and start again. Regards, Pete

If you have it running in normal flight mode, yes, it will be doing that. What frame rate does FS show? (Shift+Z twice). I don't really know -- you'd need to experiment. Certainly at 100 mSecs you are only trying for 10 fps, so even if FS didn't do its own thing as well it would look jerky to most folks. 50 is better as that is 20 fps. But I think the most important thing to do is to try to match the FS frame rate. Try it at 50 and set the FS Frame Rate limiter to 20 (Options-Settings-Hardware-Display). If you try faster, match FS each time. There's no "flag" for doing this sort of thing. Microsoft didn't set out to provide such a facility so there's nothing ideal. Other things to try, though, are: * Setting the sim into slew mode, so that FS doesn't recalculate anything (offset 05DE) * Pausing the sim -- same reason (offset 0262) * Setting the Sim Rate to 0 (offset 0C1A) Not sure if any of those will get you what you want. This application of FS is not really my field. It's been done by WidevieW (for its clients or slaves), and by the program which displays scenery for Aerowinx 747 PS1 (see links on the download page), but I really don't know how smooth they look now which technique they adopted. Versio 3.30 is not supported since 3.40 was released. Version 3.41 will be released soon. Regards, Pete

For fixed point numbers that might have been true. It's only recent C compilers, for instance, that support "long long" 64 bit fixed point values --- most of my programs (like TrafficLook) were written without such luxuries and have to mess around converting two separate 32-bit values into one floating point one for both Latitude and Longitude. However, the "double" 64-bit floating point type is a standard Intel hardware supported representation and has been around for as long as there has been Pentium (and even 80x86 I believe) floating point hardware, and I'm pretty sure VB as well as C has supported them for a long time. Good. But I still don't know VB! :) Regards, Pete

Why bother to read it into an INCORRECT variable type (currency) then copy it into the correct one (double)? I am not a VB programmer, but surely it would be better to do this: Dim itttwo As Double If FSUIPC_Read(&H2038, 8, VarPtr(itttwo), dwResult) Then ...... Do whatever you like with the double value "itttwo" afterwards, but surely don't read it into a fixed point variable first! That makes no sense to me. Regards, Pete

Yes, of course -- the code in FS9.1 is not the same as in FS9.0, it is in effect a different version. If the FS9.0 version of FSUIPC was allowed to run inside FS9.0 it would crash the system at worst, and certainly not be able to work as intended at best. There are no such messages in FSUIPC. You must be thinking of something else entirely. What exactly is the message and what is producing it where? The changes from version 3.30 of FSUIPC to 3.40 are all listed in the History document and in detail in the Release Notes at the top of this forum. There are no others. How are you trying to get the Latitude and Longitude? If you just want to see it, FS has the function built in -- try Shift+Z. If you mean to read the position via the FSUIPC IPC interface, there is absolutely no difference whatsoever between any previous version of FSUIPC 3 and version 3.40 in reading such data by accredited programs. None at all. Try FSInterrogate and see! If you want more help, can you please be rather more explicit as to what you are talking about - programming? Another program? What? Regards, Pete

Hi Samuel, Enrico's uploaded a revised pmRemote build (build 23) which works okay. I'm pretty sure it must have been an expiry problem in 22. Regards, Pete

If you mean you do have to actually steer the aircraft to keep it straight on a taxiway on runway, then this is realistic. Like cars, you can't let them do their own thing unless you want any accident. All aircraft need some steering to stay in a straight line. However, assuming you mean that this is execessive and needs a lot of correection: If the brakes aren't slightly on, on one side (calibrate a larger dead or null zone for them), and the rudder is properly centred (make sure you have a good null centre zone there too), and you don't have any wind blowing you about (light GA aircraft are especially likely to weathervane, more so in FS than in the real world in fact), then the only other thing, apart from prop torque or prop wash over the rudder (but that will vary with throttle) would be rudder trim. However, if your rudder trim is off-centre, it will be off-centre in one direction, and not vary from side to side. Check also in FS's Options-Controls-Assignments that you don't have more than one control assigned for rudder axis (use the drop down to check all the joystick devices FS is listing). Regards, Pete

Look just above that line, to 0B7C. See? Every tank has a capacity value and a "% full" value. Apart from the tanks at offsets 0B7C to 0BA8 (the original FS98 ones), there are more at offsets 1244-1260, in the same format. You misunderstand. As documented, the % values are actually given as 128 x 65536 times the proportion. They aren't really percentages in fact (but they are described like that in FS). By DIVIDING by 128 x 65536 you get a proportion between 0 and 1. 0=empty, 1=full. I think this is corerect, anyway (I've not used them). If so, multiply by 100 for a proper percentage. The way these are described comes from MS toolkits and early FS5/95/98 documentation by others before me. Please try to use FSInterrogate for these sorts of questions. In general it is pretty good at deriving the correct value, and you can see how it works -- you can see the formulae it uses and get your results the same way. This is the main reason these development tools are provided. Regards, Pete

Well, yes, true -- because I have to use the magnetic track instead of the true track. I would certainly not entertain adding "fiddles" to GPSout to try to adjust the Magnetic Variation for FS's data freeze date to match another arbitrary date. The changes will be varied all over the world, and will still be changing in any case. Furthermore the main use of GPSout is to provide a correct moving map to match FS's scenery and NavAid data, not a new real-world flight GPS. The only, and correct way, to update FS's navaids and magnetic variation is to make or purchase updated scenery files. As I said, all of the magnetic variations are tabulated for every square degree in MAGDEC.BGL. Regards, Pete

You are in the wrong Support Forum, actually. You need the PM NewsGroup. However, in this particular case I may be able to help. Enrico uses the notation ".n" to mean "bit 0", so you do not say "5628.0 bit 0, it is either "5628 bit 0", or, in Enrico's terms "5628.0". As for what size is the byte, all bytes are, by definition, 8 bits in length. That's what "byte" means. However, sonce you only want to change one bit, surely the length is irrelevant? The length of 1 bit is 1 bit. Regards, Pete

You need to change one or other of the Keys. Both must be in exactly the same name and email (it does mention this in the documentation I think you'll find). If you send me both of the emails, the one for FSUIPC and the one for WideFS, and tell me which email address you want them to be in, I will make a new key for the other. If you want to change the FSUIPC registration you'll then need to delete the FSUIPC.KEY file from your FS Modules folder and re-register both. Send to petedowson@btconnect.com. Apologies if there's any delay, as I am out most of tomorrow (Tuesday) -- another visit to the eye hospital. Regards, Pete

Just download the ZIP from http://www.schiratti.com/dowson, and copy the DLL out of the ZIP into your FS modules folder. That's it. As I said, your registration covers all FSUIPC 3.xxx versions. You would only need to re-enter the details if you deleted your FSUIPC.KEY file, or re-installed Windows, or moved to another PC. Regards, Pete

You are mixing up two completely different ways of dealing with reverse. The reverser on page 7 is for a completely separate axis acting only as a reverser, it is nothing to do with calibrating a reverse zone on your main throttle lever. In the main throttle section on page 1, check the option to "map to 4 throttles". If you've calibrated there already you'll need to press "Reset" first to undo that. Now go to page 3 and calibrate throttle 1 with a reverse zone, an idle area and the forward thrust area. Follow the steps in the documentation. Regards, Pete

First, you do not purchase specific versions of FSUIPC. Your purchase is for any version 3.xxx. Second, you are certainly mistaken, because version 3.40 was not released until this month! It was released to coincide with the FS9.1 update, as changes had to be made to deal with the revised simulator. You need version 3.40 (or later -- version 3.41 is due soon). If you got FSUIPC in July that will be version 3.30 at best. As Microsoft said on their update site AND in their READ ME, you need to update to 3.40. To check the version of any of my programs or modules, simply right-click on it and select Properties then Version. Regards, Pete

Sorry, there's no point. I've investigated this. That parameter (WindVarFactor) is actually not used in FS2004 at all. The entire Weather code for FS2004 is separate from that for FS2002 and FS2000 (which are pretty much the same). I'm afraid that whatever you experienced when setting that parameter was merely a coincidence. I've looked to see if there is any way I can introduce it, and, really, there isn't. The system is so completely different. As far as I can see, the only way of getting wind and cloud turbulence (AND direction variance) is by switching my Wind Smoothing off. I will think about this, however, and see if there's a way I can detect the fact that there should be some turbulence, and allow this to occur even though the smoothing is applied. This will be a very complex operation, though, and I cannot start thinking about it until I have cleared the decks of those things I already have on my plate. Meanwhile, I strongly suggest you turn FSUIPC's wind smoothing off. If you avoid flying in parts of the world with a very dense collection of METAR stations (JFK, ORD, LAX, etc) then I really don't think you will see many of those nasty windshear direction changes in any case. As I said earlier, I actually found it quite difficult to make one happen in any case, when I was really trying! Regards, Pete

Hmmm. It sounds like that aircraft model is intercepting these things and acting on them before FSUIPC does. I can't really do much about that. Is there a DLL installed in the Modules folder by the aircraft? If so, you could try changing the InitDelay in FSUIPC, so it subclasses the main FS window (which processes all these inputs) after that mdule, so getting control before it. FSUIPC used to default to InitDelay=3000 but it's 0 in FS2004. Just put/change InitDelay=3000, or even higher, in the FSUIPC.INI [General] section before loading FS. If the 767PIC does all this from a Gauge, then there's no chance I'm afraid. I think you'll just have to "park" your trim axis or fly a different aircraft. Well, I really don't know what it's doing. The 767PIC was designed for FS2000 or FS2002 wasn't it? Is there a new one coming out? Regards, Pete

Yes, it is stored as Day of Year in offset 023E, with the Year in 0240. Check the Programmer's Guide in the SDK. Regards, Pete

No, I don't do that. But it won't help in any case. I just checked. Buld 22 of pmRemote doesn't even attempt to contact FSUIPC. There's no calls to it from the pmRemote program whatsoever. I reckon it has expired -- it was only a demo in any case. Maybe Enrico forgot to extend the expiry date in his build 22 update. I know build 20 expired. Regards, Pete

No, that is not a good idea. Best to simply calibrate the toe brakes so merely touching them does nothing -- i.e. with a bigger "dead" zone. There should be a reasonable amount of slack before any action occurs. Regards, Pete

There's the problem. The name of the gauge loaded is not the same as the name it is trying to register as. It is trying to "cheat" by pretending to be another gauge. Both those gauges do have (different) valid Keys, but the keys and names must match. I'd get back to your supplier and find out what's going on if I were you. Regards, Pete

You did remember to UNCHECK the automatic option to disconnect on AP, didn't you? If not then that mechanism will reset the bit. Regards, Pete