Pete Dowson

What "TQ" is that? If it's the Goflight, doesn't it have a little separate reverse lever which operates a button to put it into reverse? If not the GF TQ, then what instructions are you following to calibrate your throttle, and what is this "detente"? FSUIPC's main single thorttle calibration, on Page 1 of 8, doesn't provide for a reverse range. No idea, I'm afraid. I am having trouble picturing what you are doing. First, though, have you calibrated the levers properly in Windows (Game Controllers, or whatever drivers they came with)? The other thing to check is that you have full sensitivity and no null zones set at all in FS's Sensitivities menu. Remember, FS processes all this before FSUIPC sees it -- FSUIPC is merely manipulating things at the final moment before FS's sim engine gets hold of the values. Regards, Pete

Not read only (well, the GPS area may be), it is just that writing a value has n effect because it will immediately be overwritten again by the simulation engine. Is this Reality software the gauge or DLL I'm vaguely aware of? If so it doesn't use FSUIPC. I expect it reads this stuff like any gauge would -- through the panels interface to obtain values direct from FS. There's really no way I can influence that. Virtualy all "Offsets" these days are only available to FSUIPC clients Regards, Pete

On further testing, I don't think it is a change in 9.1. As far as I can see, AdvDisplay has NEVER been able to detect a reload of the same panel -- it works perfectly well if you change to another aircraft then back again! Checking the code, I think it has always been like this, for years! Strange that no one has reported it before! Anyway, I think I should be able to fix it fairly quickly. If not soon it will be Monday. Either way, I am sure it isn't anything to do with flashing panel parts. That may be what brought your attention to the disappearing AdvDisplay window, but I'm sure it isn't related. Basically, what is happening in my DLL after the panel is reloaded is that all of the Window handles that AdvDisplay knows are different and it then simple isn't aware of anything it needs to do. So it does nothing! I need to find a way to detect a panel reload and treat it like a new panel. Regards, Pete

Okay, I was wrong. I don't get flashing panels, but I am losing the docked AdvDisplay window when reloading the aircraft. That's very strange. I don't understand what has changed there. It isn't anything to do with having RC running or "hide when empty", and the FSUIPC Hotkey doesn't bring it back either. Evidently something HAS changed in FS9.1 which affects AdvDisplay. Terribly sorry. I'll get onto this right away. But it may be next week some time before I have a solution. We have guests over the weekend. Regards, Pete

What panel part is it docked to? Is the name for it correct in the [AdvDisplay] section of the PANEL.CFG file? There are some advanced panels which AdvDisplay has difficulty docking to automatically -- with those you can either try doing it manually (by editing the CFG file), or just use "Lock" instead of "Dock" and the FSUIPC hot key to hide and re-display is when you want to. You main panel flashes on and off??? Phew. That's a serious problem!! Do you have "render to texture" set in the Options-Settings-Hardware-Display options? If so turn it off. That's the only "feature" I know of that can cause panel flashing. No, it sounds rather like you have a problem which also affects AdvDisplay. There's been no change to anything in AdvDisplay in well over a year and it seems to work perfectly here [bUT! Now see next message!]. I know of no change in FS9.1 which would upset it, and least not program-wise. Try windowed mode instead of full screen. Does that make a difference? Have you changed any of your video settings? Maybe the FS9.1 update, which included a revised "Display.cfg" file I think, upset some of the settings FS is using for your particular display -- during testing one such problem was discovered in its Matrox Parhelia settings, fixed before release. If you tell me exactly what your video card is I should be able to compare the Display.cfg entries before and after FS9.1 -- I have a "virgin" FS9.0 installation still, for base testing. Regards, Pete

That's okay. Version 3.411 is there now, I just checked. Regards, Pete

Many USB connections emulate ordinary serial ports (COMn) at the PC end. See if yours is listed in the Settings-Control Panel-System-Hardware-Device manager list under "Ports COM and LPT" or similar. I know my iPaq isn't, nor my Garmin iQue 3600. :cry: Things aren't that easy. If the socket on the PDA is true USB the electrical and protocol characteristics are entirely different. Regards, Pete

Have you asked him why they don't work? Maybe he's using something particular to FS9.0 and they won't work with the 9.1 update? Regards, Pete

Big Ouch! I just checked -- you are quite correct. The calibrations for 5 of the axes are to a maximum of 32768 when they need to be to 16384. The axes affected are: Page 1: Throttle Page 2: all (Prop pitch, Mixture, Left and Right brakes). This means, as you say, that the best calibration will only use 2/3rds of your axis travel. Yuck! The bug was actually in 3.40 but it was masked (cancelled) by the other bug which I just fixed -- fixing the one revealed the other. Sorry. I'll get a revised version out (it will be 3.411) some time tomorrow. Thanks for reporting it so quick. I just wish my other testers were as good! :wink: Regards, Pete

It wasn't to do that, but to restore the state of FSNav -- docked or undocked. I always had FSNav undocked on a separate monitor and it annoyed me that it would never rember that. In fact it never remembered the position or size either. Then the author of FSNav said he'd fixed it so it did remember, so I removed all that code and discarded it. It was a problem anyway as it depended on things in FSNav that changed on each version. In actual fact, the fix that he made to FSNav was to remember position and size, but not the state docked/undocked. I gave up at that point. Program a button to operate F9 in the FSUIPC Buttons page. The "InitialButton" option just specifies which button you want to simulate "pressed". The format is joystick number, button number. Nothing in that line for "F9", you simply say which button is to be pressed. If you don't want to use a real button, change it in the INI file afterwards to any button you don't have. Isn't this clear enough in the document? If not I'll look at improving what is written, but please tell me what you are misunderstanding. Regards, Pete

Really? I'll check it out over the weekend. Not sure how that could happen. Regards, Pete

I notice you have a very high screen resolution set (1600 x 1200). Is the problem perhaps related to video settings? Try a lower resolution, or possibly different anti-alias or other settings? All this sort of thing boils down to trial and error for me (and you too, by the look of things), but there are folks taking a more professional and scientific approach to setting up computers correctly for best results. They aren't free, but they seem to have good testimonials, so they may be worth a try. Look at the FSGS Support Forum, not far from here. Regards, Pete

Yes, it should be possible, though I've not tested it for FSNav (I don't use it I'm afraid). In fact it was for that purpose the facility was added -- are you the chap who asked for it many moons ago? It actually made it into version 3.40 a month ago. Version 3.41 is available now. To see what's added in each new version it is best to peruse the History document (or the details for each release reproduced at the top of this Forum). Otherwise it is easy to miss stuff buried in one or other of the documents. Regards, Pete

You'd need a simulation mode rather than a demo mode, I think. Anyway, I just checked my Etrex Vista. This also says "NMEA In/NMEA Out" in the selection menu in the device itself. However, the manual definitely lists this as "NMEA Out" only. There's no mention of NMEA In. I think it's a little bug in the firmware in the device itself -- they have the menu wrong. The manual is correct. GPSout will be sending data -- rather a lot in fact with all those options you've selected! You can check what happens on a serial port using a neat little free program called "PortMon" from http://www.systeminternals.com. Not sure what the initials are, but it is related to utilising external receivers to get more accurate positioning -- "differential beacon receivers" according to the Garmin manual. The unit will be using satellite signals from another receiver as well as its own for determining positions very accurately -- probably a similar technique to using more than one radio telescope to get more accurate space readings or images. I think that sort of stuff is used by surveyors and the like when laying out building plots and so on. It's no use for FS. Regards, Pete

The IN and OUT numbers on the left aren't set by you. They are the live real numbers -- IN from the joystick and OUT to FS after calibration. The numbers you can set are those on the right, under each of the separate "Set" buttons. Those are set by you to calibrate the axis and stay fixed unless you change them. Jitter on your joystick inputs isn't cured or caused by calibration. If the digital filter I provide since FSUIPC 3.40 isn't enough to smooth those jitters then you will need to investigate the cause. Things like poor power supply, bad connections, and interference from other devices can cause jitter on joysticks. If yours is connected to a game port then jitter is even more likely -- especially if you use a game port on a sound card. Drifting when you are taxiing? Do you steer with rudder pedals or have auto-rudder set and use aileron? There's several possible reasons for failing to keep straight -- incorrect calibration of the centre is one, yes, but rudder and aileron trim also need checking. Please note the version 3.41 of FSUIPC is now available, and fixes some problems with calibration of axes which have no centres. Regards, Pete

Thanks for the clarification Florent! Regards, Pete

I've never heard of those gauges. I don't think they use FSUIPC at all in any case. What exactly is this "incompatible software" error? Is that a message box just saying that? I can't say I've seen one of those -- there is a message box which warns you of incompatible modules and gives the option to load or not load. Is this the one? If so, and you are selecting the option to ignore the error and continue, then it seems likely that those Gauges are, indeed, incompatible. Best not to load them in that case. With such similar names I take it they are from the same author, so if you really need to use them I guess the best thing to do would be to report the problem to him and see what he says. Regards, Pete

Hmmm. Interesting. Mine has an identical list to yours, but in that position only NMEA out is listed, no "in" at all. Try it. What can you lose? How do you tell it to ignore its own aerial readings from satellites? The NMEA out option has to work to do the reverse -- i.e. feed Etrex positional data to a PC or whatever, so there has to be another option to switch someplace. Regards, Pete

No, I don't think so. I have an Etrex Vista, and certainly that has no mode for NMEA input. Pete

Where do you get 10^9 from? The values aren't decimal! The fractional part is a value ranging from 0 to 2^32-1 and represents the number of 1/2^32 parts of a metre (i.e. 2^-32). Think about it. It is a fixed point binary number with the "binary point" at the 32:32 bit boundary. The whole number is 64 bits in length, with the high 32-bits representing the number of whole metres and the lower 32-bits the fractions. A value there of 0x80000000 would represent exactly half a metre, as the bit just below the binary point is the only one set, representing 2^-1, or a half. And so on. Each bit down represents half again, exactly as they should in binary. Regards, Pete

I can't. Please see the "sticky" near the top of the forum called "READ THIS IF YOU LOSE YOUR FSUIPC OR WIDEFS keys". Regards, Pete

The user aircraft is not an AI aircraft. The "AI" means "artificially intelligent"". The user aircraft is supposed to be flown by you, who presumably is not AI? Most all of the rest of the FSUIPC parameters, from 0000 to XXXX, are relating primarily to the user aircraft. That's where TrafficLook gets its data for. It isn't "TCAS table" information -- TCAS doesn't show the aircraft you are in as a target on the screen. It has a fixed symbol for the user aircraft. Just scan through the Programmer's Guide and see all the information you can read for the user aircraft! Regards Pete

No, sorry. But why? You can direct keystrokes, if that's what you want to do, by loading the programs with WideClient and directing KeySend parameters via the running serial. If it isn't keypresses you are wanting to implement, you could of course access FSUIPC yourself in your program and change focus or whatever, as you wish. If I understood what it was you wanted to accomplish (focus is a means of getting keystrokes, not much else) I could advise more accurately of course. Regards, Pete

No, sorry. The threads on the PM newgroup were about things like conflicting IRQs on video and network cards, and experiments with IPX/SPX using the Beta version of WideFS I supplied in the group. There's always someone with some Network problem. I'm afraid it's that sort of area. I tend to rely on Katy Pluta helping me out when I run into difficulties. Ah .. this is a general network problem on that PC, not one related specifically to FS or WideFS, then? I would recommend seeking help from Katy, either directly via the PM support email, or in the FS2004 Forum. My approach would be to try swapping out network adapters, cables, trying different sockets on the hub or switch, comparing all the parameters I could between the assorted PCs. and so on. in other words tral and error. I have had two bad network cards in the last few years, but none for a while. Touch wood. :wink: Regards, Pete

No, sorry. I don't even know how to get positions of clouds or rain. I assume something somewhere in FS must know (decide) these things, but it is buried pretty deep. It may only be in the graphics sections, which unfortunately I know nothing about. Regards, Pete