Pete Dowson

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

One of my PCs (actually the Notebook) is on a Wireless LAN -- I use USRobotics devices with "Turbo" mode (matching, theoretically, the 100 mbs wired LAN speed). I'm no expert either. It's all trial and error with me. But, certainly, I don't like letting anything assign IP addresses. I do that myself. You should be able to overrule the router and assign your own, fixed, IP addresses. Check the documentation and/or on-line help. I can't remember what I had to do with my router (its a Zoom) but I followed the instructions that came with it. If you don't do this it is likely that the IP address is different each time. However, that said, if you are using TCP/IP with WideFS, why not just refer to the Server by name (the ServerName parameter) and stop trying to tell it the IP address? That way, WideClient asks Windows for the IP address, so even if it changes it should still be okay. But, you also say: So I doubt if the ServerName will work either. Something is evidently blocking access. I doubt if it is anything to do with being wireless or not. I'm afraid I am not able to solve network problems like this as I don't understand them enough either. Your best bet is to ask Katy Pluta -- either via the Project Magenta support address or over in the FS2004 Forum. Regards, Pete

Sorry, I don't think that's possible as it stands. You'd need to resize the PM GC window slightly, to make rom for a small Wideclient window 9just the title bar showing, say, then click on that title bar. Most of the effort I've put into supporting cockpits has revolved arond getting away from keyboards altogether, so you can do whatever you want with buttons, for example. Isn't it possible for your hardware to produce button presses instead of keystrokes? Regards, Pete

If you want to use the Ch Mixture lever (the one with the red knob, probably?) as a reversing lever, and it already works as a Mixture axis in FS, then simply go to the FSUIPC page with the Reverser shown, and calibrate that axis following directions in the User Guide, the same as any other axis. If you haven't got that axis assigned to Mixture you need to do that first in FS Options-Controls-Assignments. Regards, Pete

Ah, right. Probably they have teething problems. I expect they will be able to help you much better than I, then. I thought you were implying that you were being bounced around and I was your last resort. There are many hundreds of programs, gauges and DLLs out there which use FSUIPC in some way or another, and I know very few of them. I cannot possibly offer support for them, I'm afraid. The correct way, especially for live programs like this, is for the authors or publishers to support their programs. Really only they can do it. If they need help with the interface they use to FSUIPC then they can get that from me. For me to try to help you sort out what is going on between their program and FSUIPC is really very inefficient and likely to be quite unproductive. Regards Pete

It has a button or microswitch on it which is repeating all the time? That's odd. Or is this something programmed in the driver for the throttle device? Regards, Pete

WideFS, yes, but you already said it was okay for FS AI traffic, didn't you? If WideFS is working enough to drive other things in your display it will certainly do the same for this stuff. It makes no distinction whasoever, all the data is just data, it doesn't know what it means. ... and they refuse to support their program? Has it ever worked? Do you know anyone else for whom it worked? Well, you can switch on FSUIPC "IPC Write" logging (Logging page in FSUIPC options), and do a VERY SHORT test in which you'd expect to see some aircraft, then ZIP up the FSUIPC LOG file and I can see if any correct traffic data has been written. This may provide fuel for your argument with the Ivap authors who won't otherwise support their product. But please keep it very short. Best not to enable the IPC Logging until you know you will see some soon, then close FS completely after you are sure you should have seen some. Email the ZIP to me at petedowson@btconnect.com. Really I would rather support the programmers who wrote it if they seem to need help, as any explanation I give you will only have to be repeated second-hand this way. Regards, Pete

Sorry, I cannot support AIBridge. I know absolutely nothing about either it or multiplayer. Possibly AIBridge doesn't work with your "Ivap" program or whatever it is. Why don't you ask them first? I am very sorry to be so brief on this, but it really is not my subject, I have never flown on-line and know nothing about it. The support you need must come from the programs you use. The only way FSUIPC comes into this is that it receives data from somrthing for others to read. Regards, Pete

No. FSUIPC cannot see the mutiplayer traffic, so that is fed into FSUIPC forcibly, by AIBridge or whoever wants to. All that happens in that case is that FSUIPC becomes a storage medium for the traffic data. Regards Pete