Pete Dowson

Well you are very lucky. I wouldn't trust it for a decent flight. Don't ever come to me with any problems if you are doing that. I don't want to know. There are no conditions on re-distribution, there never have been. What conditions would you like imposed? If by "commercial conditions" you mean terms of payments for license, then my case is stated perfectly clearly in Section 4 of the Access Registration document. I am very amenable to all fair agreements and have not yet been known to have any disagreement with anyone on any arrangement. There's no complications about how things "work" it is plain and simple, everything is in the open. If you cannot accept something so gentlemanly and easy to comprehend, then I don't understand you, that's for sure. :cry: Regards, Pete

Well, you didn't even try to run Squawkbox in that sesion, so nothing is shown in the Log and there would have been no failure reported, at least not by FSUIPC. You only ran FS altogether for 86 seconds, including loading and start-up time, and didn't run anything else. Where does this name "squawkboxKey" come from? Isn't the program named just Squawkbox? Perhaps if you registered the program by its given name you'd have a little more success? Please try it and see. Why invent a name for a different program altogether? Regards, Pete

Sorry, I cannot suppport version 3.01. Only show me Log files from 3.40 -- they may contain better data for me in any case. This most certainly shows you have not registered the application with the correct key. But what did you enter for the program name? Something is evidently entered incorrectly. What does the FSUIPC.KEY file contain? That's where the information you enter gets recorded. Please use FSUIPC 3.40. I don't want to see logs from older versions, especially not one from a version which is now 14 months old! Regards, Pete

No, I've not heard of anything like that before. The FSUIPC options window is simply a standard Windows dialogue or property sheet. If this is in full screen mode, try in Windowed mode (ALT+ENTER) and vice versa. Other posibilities are that something has replaced one of the standard Windows system libraries with a bad one -- the most likely candidate there is COMCTL32.DLL. Do a search for that and see what version it is (right click, Properties-Version). On my Win98SE system it is 5.81. If yours is earlier, try re-installing (Start-Run then enter SFC and press enter, to run System File Checker. You can specify the file to be installed then). Finally, the black screen does make it sound like it maybe a video card or driver problem -- that would certainly be indicated if it is okay in Windowed mode but not full screen. If you are using one of those old 3dfx Voodoo cards, for instance, then I suspect it cannot superimpose a standard Windows display in full screen mode. Regards Pete

My advice is to report it to PSS, and get support from their forum. Definitely sounds like a bug or possibly the installation of the aircraft went wrong? Could try un-installing and re-installing, just in case. Pete

There's already a free key for that gauge in the Freeware Keys list in this Forum. It's been there a long time. Regards, Pete

On a hard crash the file system doesn't get a chance tp flush its write caches to disk, so you lose everything in memory. I think you can tell Windows you don't want writes to be cached, and then it will actually write to disk each time a write to a file occurs, but this will affect performance. Regards, Pete

What additional axes? FSUIPC, like FS, has setttings for generic throttle, prop and mixture axes (one lever for all engines), but there are also complete pages with up to 4 (FOUR) separate Throttles, Prop Pitch, and Mixture axes. How could you not find them? Go to FSUIPC options, select the Joysticks tab. Now, see the title at the top where it says "1 of 8" or similar. You can press the little right-facing pointer to the right, and go to different pages where you will see all these "additional axes". Regards, Pete

You've got a load of logging options enabled there! I really don't need or want any of those enabled, unless asked, that information is not relevant and it just clutters things up and makes the Log too big! Not only that, but because you are using a registered version of FSUIPC, you won't get messages here telling you the gauge isn't accredited. Finally, you seemed to have finished one log and started another after about 506 seconds, with no aircraft being loaded or anything in this section. You evidently pressed "New Log" AFTER loading the aircraft, so the previous part of the log was renamed FSUIPC.1.LOG or similar. All I wanted was for you to reproduce your reported accreditation error and show me the log, not switch loads of options on and press the "New Log" button. So, to get back to where you must have been once, please do this: 1. Temporarily remove your FSUIPC.KEY file from the FS Modules folder, so you get this unaccredited message you reported. 2. Edit the FSUIPC.INI file and delete all the lines in the [General] section which say "Log = Yes". That will take out the extra logging before you load up FS and start filling the Log again. 3. Load up FS, load your aircraft, see the accreditation error message, Ok it and close FS. Then show me the log. Regards, Pete

So it comes under the heading of "unmaintained" freeware and "disinterested or unavailable authors" :) That really depends on whether it is possible. If they access FSUIPC using the method reserved for external programs, then no accreditation will ever work. If they access FSUIPC correctly, using the internal method, then, yes, I can do that easily enough. So that I can see whether it is possible, and also obtain the details I need, please show me a section of an FSUIPC 3.40 Log file with the attempt by the Gauge to access FSUIPC shown. Regards, Pete

Hmmm. Seemed the most likely problem, given the results. Not a popup, no. A message within the Window itself, near or at the top. There's no overall deletion facility for all buttons, no. You can certainly clear any individual button in FSUIPC's dialogue UNLESS it has multiple or advanced programming for it in the INI file. Once you have advanced program sequences, conditionals, etc, all that has to be edited in the INI file. That's why all the parameters are documented in the Advanced User's guide. Each section [Keys], [buttons] and [JoystickCalibration] can be entirely deleted independently in the INI -- when FS isn't running in the last case. The Key and Button programming is actually all reloaded when you change aircraft, so you can edit it "on-the-fly", so to speak, and simply change aircraft to get FSUIPC to see the changes (or deletions, if you like). Regards, Pete

It sounds like you have the Avionics options set wrongly. Please see the PFC DLL user guide. Under the heading "Avionics Options" there's a full description of all the COM1/COM2 variations you can achieve. Also make sure your console selection isn't for the Jetliner or Jet Cockpit (see Consoles tab). All that complication comes about because (a) there's no COM2 on FS2000 and (b) there's no COM2 on the Jetliner console. So the driver has to be all things to all men. :wink: Just read it carefully and set the options to suit what you have. Regards, Pete

Get the updated version of FSRealTime (version 1.67) which was developed for FS2004 and which is accredited. The access key for it was issued to the author in July 2003, when FSUIPC 3 and FS2004 were first released. It sounds like you have a very old version. I've seen the latest on flightsim.com. I think the ZIP is called simply "realtime.zip". Regards, Pete

Sorry, I've no idea. But you have double-checked that F12 is not assigned in FS too? (Options-Controls-Assignments)? FS's default assignments for brakes are F11 (left brake) and F12 (right brake). It sounds more likely to me that you simply have not deleted the assignment in FS. Never just assume that a key is free for re-use. Same goes for joystick buttons. If you were programming the keypress action in FSUIPC then, certainly, FSUIPC would see it first and "steal" it from FS (it can't do that for buttons, mind). But it sounds like your other programs are simply sharing the key? Mind you, didn't you say "Voice Buddy" wasn't loaded? So if it was supposed to "steal" F12 it wouldn't have been able to, would it now? Regards, Pete

If deleting the INI file allowed you to program a button you couldn't before, then the reason will have been that there was complex programming for that button in the INI file beforehand -- even simply duplicating the entries in the [buttons] section in the INI will tell FSUIPC to action that button more than once when it is pressed. Such programming cannot be handled in the dialogue and has to be dealt with by editing the INI file. All that stuff is dealt with in the FSUIPC Advanced User's documentation. If this was the case, and there's really no other explanation, then when you pressed that button and FSUIPC stopped you programming it, there would have been a message on the screen near the top of that dialogue explaining exactly why! If you had not achieved this by editing the INI file then it sounds like, somehow, it had been corrupted. If you fixed your joystick problems before by calibrating correctly in FSUIPC you should certainly not have deleted the INI file. To re-program all the buttons you only needed to delete the [buttons] section, which would have left all your joystick stuff intact. Now you will need to do all that again, unless, of course, you took the wise precaution of making a backup copy before deleting it? Always a sensible thing to do. Regards, Pete

If it sees the button it will act on it. It sounds like somehow Voice Buddy stops this working. Does it install its own driver, which perhaps doesn't deactivate or stop when you exit it? FSUIPC is very simple in its approach to buttons, it merely uses the basic Windows joystick API (no DirectInput or anything complex like that). A single read on each possible joystick number from 0-15 presents it with the state of all buttons that can be handled by the Windows API. (More can be via DirectInput, but FSUIPC doesn't use DirectInput, for sure). Reinstalling FSUIPC does nothing whatsoever! You replace one DLL by an identical DLL? What's the difference? Every time FS is started FSUIPC has been reset! It re-reads the settings from the FSUIPC.INI file and starts life again as if it had never run before. There is no other memory, and the program code is not live and does not change from run to run. Can what, exactly, be done by editing the INI file? If your button definitions are correct in the INI file they will be the same, correct definitions the next time FSUIPC loads. If you want to edit them to do something more complicated, go ahead, but there's nothing else short of going into the FSUIPC Buttons page and changing something there which will change what you had before. It seems to me you are clutching at straws, and in the wrong direction. Sorry. Regards, Pete

FSUIPC didn't start supporting local weather until FS2004. And then it was only because I had do -- global weather is meaningless in FS2004, it is just the starting default for local stations which don't have any other starting conditions defined. Regards, Pete

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