Pete Dowson

Oh, NOW I see! I thought you were referring to two facilities provided by EPICINFO which should give the same format but don't. No, everything is perfectly correct. When you read any offset using the generic offset reading facility, EPICINFO has no idea whatsoever what it contains and therefore cannot convert it for you. If you want them both in the same format, read the NAV1 "use" frequency from offset 0x0350 the same way. If you need them in decimal you will have to convert them in EPL. I don't remember what maths facilities are in EPL now but you need something to do this, for each byte: (10 * ( x / 16)) + (x % 16) where * is multiplication, / is division (losing remainder) and % is getting the remainder. Or (10 * (x >> 4)) + (x & 15) where >> is 'shift right by' and & is 'logical AND'. Alternatively, if you can send one digit at a time to the display, then just use shifts and 'ands'. i.e (x >> 4) for the first digit in a byte and (x & 15) for the second digit. I think that Ralph was trying to make the new EPL quite C-like, so maybe my nomenclature here is the same in EPL. Sorry, I am very out of touch with all things EPIC these days! Regards, Pete

Try it. I doubt the format has changed. If it doesn't work you just revert to your carefully saved copy of the FS2002 one. Regards, Pete

Not sure I understand. "Reads bits directly" would imply that you get what FS gives me -- and that is hex BCD, i.e. 0x1560 for 115.60. Do the older PHs convert those to decimal? If the two are different this is probably a bug. I'm afraid I cannot test changes to any of my EPIC stuff these days as I don't use EPIC at all. I am therefore rather reliant on feedback, and no one has mentioned this before. If you can clarify for me (show me a log line for NAV1 use and NAV1 standby so I can see what is hapening), I'll try to fix it and send you an update to test. Please send details to me at petedowson@btconnect.com so I can reply with and attachment. It may be a day or two. Regards, Pete

No, but there should be no need. Just keep the voltage up, or let it diminish faster or slower. The programmer's Guide lists where the Battery voltage is stored. Try changing that. Regards Pete

Just copy the DLL into your modules folder. Unless you deleted the FSUIPC .KEY file you don't even need to re-register. Registrations for FSUIPC 3 cover all version 3 updates. Regards, Pete

Sorry, I really cannot solve that sort of problem -- it will be some problem with drivers for sure. It will no doubt affect all non-Direct3D dialogues in full screen mode. I do have a Radeon 8500 XT Pro on one of my PCs and it all works perfectly on that -- if you cannot find later drivers get back to me and I'll see what version I have. (The PC isn't on at present, it isn't in this room). Regards, Pete

Ugh! That's not nice. Strange. I know of no reason for that. Possibly Weather logging is enabled (FSUIPC Logging page) and either the disk is very full or fragmented, or you have Windows write caching turned off? Ah, well if you removed FSUIPC.INI it would have generated a default which, of course, would not have Weather logging enabled. Do you have any Weather gauges which might be trying to read the weather during the changes? The other thing which can slow things down is when there's an unaccredited program attempting to access a non-registered copy of FSUIPC, but since you have access to the wind smoothing that can't really apply to you. Can you check the log file of FSUIPC for me, please? Are there streams of errors reported? If so it is likely that you have a partially-installed FS9.1 update. For this please check my announcement at the top of the Forum. Well, certainly try temporarily removing any non-FS DLLs from the Modules folder, other than FSUIPC. Also test with a default aircraft, no add-on gauges, to see if it may be an add-on gauge killing the frame rates. There's no change in weather handling in 3.40. What was your previous version? Have you updated your FS9 to FS9.1? Regards, Pete

Check the Freeware Keys list in this Forum. It's a "sticky" near the top. Pete

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