Pete Dowson

11D4 was only ever used when SIM1 was moveable and sometimes loaded with flights (especially before FS2002 ewhen it was "SIM1.SIM"). Since FS2004 (i.e. for three years now) 11D4 hasn't been used and is clearly marked as "not applicable" in the documentation. 3364 taken together with 3365 is used for "ready to fly" (check them to be zero) and works fine. If you set "Log Extras" in FSUIPC logging you can see it log when the bits in this change. 3364 is actually only non-zero during FS loading, but 3365 deals okay with menus and dialogues. Regards, Pete

Yes, mostly for output. The only inputs it will likely take are to provide routing/waypoint data. My Garmin GPSs offer simiar facilities. Yes, and all that is for output to a moving map. GPSout does the same sort of job from FS -- both your GPS and my GPSout are able to do similar things, connect to other programs like maps so you can follow your route. You use your GPS when travelling in the real world, you can use GPSout in FS when you are travelling in the FS world. Perhaps you need to think a little more about what it is you are trying to do? I get the feeling you misunderstand the whole point of GPSout! Regards, Pete

REDUCE the steering response on the ground? Hmm. I've always needed much better response on the ground. In the air it's a very subtle need for rudder adjustment. You seem to have opposite needs to me (and others). Maybe its's an airliner versus ? difference? What's wrong with calibrating it with a central dead zone, and then using the response curves to give less sensitivity near the centre. That's the best approach for all three main flying controls, and if you find steering on the ground too touchy, then it'll suit that too. Just calibrate in FSUIPC with a small centre "dead" zone and select a "slope" with a suitably flattened central response. Pete

But the sensitivities would be entirely different! That is the WHOLE point, which you are still missing entirely I'm afraid. :-( Really, if you are flying on a simple joystick, just use the rudder control for everything. The steering tiller facility is there for folks building proper cockpits with real tiller controls. Please ignore it, then. it really is not for you! Regards Pete

ErI very much doubt whether your GPS will accept NMEA input to supplant the position derived from its antennae. How do you switch them off? I have three Garmin GPS's and none do. I think obly the aviation models can be used in such a mode, then I think they use "AV400" protocol. This is so that they can be driven from better receivers in an aircraft. You are probably misunderstanding the entire point of GPSout. It is not "output to a GPS" but "output like that from a GPS". it is intended to feed signals to a moving map program (usually) just as a real GPS would. Pete

Well, it does say in the FSUIPC User Guide that both must be the same. You really should have mentioned that when ordering your new one, as SimMarket could have handled it for you. As it is you will have to send me an email (petedowson@btconnect.com) attaching or including BOTH notifications from SimMarket of the registrations/keys, and tell me which one you want to use. Regards Pete

No, you can't. FS only provides one control, and that's the rudder. There's no way in FS I know to control the nosewheel as such, only to steer with the rudder. You are looking this backwards! The Tiller facility in FSUIPC is there to provide a way of having two SEPARATE joystick axes both going to control the FS rudder, but calibrated separately, and with FSUIPC activating one on the ground and the other in the air with a gradual transition. Exactly. So you need a hardware tiller control (axis), assign it in FSUIPC's Axis assignments then calibrate it in FSUIPC's tiller calibration. Please do read the documentation, I'm sure it does explain exactly what the FSUIPC facility is. Regards, Pete

As long as you have a fully working Network with no firewall problems between them, and both/all PCs are running WinXP (or Win2K) then WideFS should work straight-off, with nothing other than installation for you to do. There's virtually nothing you should change or adjust in WideFS in any case. Ah, I see. Don't get WideFS until you have overcome that and got everything Networked and working happily together. Yes, you will cerrtainly need them Networked. I'm afraid I cannot teach you how to do that -- the Windows help should be okay, and there are plenty of other sources of help including innumerable books. Erthe Laptop is on a router, but the other isn't? What's this "cable lan line"? If they are Networked (i.e they talk to each other freely and easily, then what's the problem? Why do you say "the network part is what scares you" and then say scary things to me like "cable lan line" (???) and "router"? I'm afraid I don't follow. I don't have any web site I'm afraid, only this humble Support forum. ;-) Anything about what? Even if I had a web site why (how?) would I fill it with stuff about setting up Networks? I am no expert. I just did what Windows told me to. That's all I know. I am the last person to publish anything whatsoever about networks -- If I get into trouble with them I have to seek help like anyone else. I know things about FS, and I can program. I know very little about the more complex side of Windows or the modern hardware. Even the Network code in WideFS is merely mostly a copy of stuff from Microsoft examples. My part is the interface to FS and making it all work efficiently by judicious data formats and protocol design. Regards Pete

Aha, yes, 8Hz would be jerky. Maybe you could try interpolating intermediate positions if you cannot get something better? Pete

There's really been no change in that area, none at all. But what "X" in 3.6X/6.6X? Where are you configuring the Button? There's no information in what you've provided. If in FSUIPC, you need to check the assignment. That's the main suspect surely? "ActionKeys" hasn't been needed or used for several releases of WideFS, not just the last one. A log of the WideFS actions may be useful -- is your client actually connected? Please check the WideFS logs for both ends. Why bother to specify the ServerIPaddr in the client.INI? I see you are using "ProtocolPreferred" in the Server, so you must be using WinXP all round. You don't need to specify a Server at all. And there's really no point in having ProtocolPreferred in the Server with "Protocol=UDP" in the client -- take the latter out too. Regards Pete

Is the sim restricted to running at the same frame rate? 25 mSecs, if consistently achieved (is it?) would be 40 fps. It maybe better to aim at a lower rate so that both can sync more reliably -- eg, 40 mSecs for a 25 fps limit. It may also be better if run on a PC with dual cores or hyperthreading, where your program and FS are running in separate 'processors'. Finally, there are several modes in which FS can be when doing this. Before FS2004 you actually had to put it into Slew. In FS2004 you can try Slew, Pause, Zero simrate, or normal flight modes. Experimentation may be needed. Regards Pete

I'm sorry, but you'll need to ask Microsoft. In the past the Microsoft FS SDK's were always quite a bit after the main FS Release date -- in the case of FS2004 coming in trickles over a period of many months. However, from what I have read there are high hopes of having SDKs quite early for FSX, possibly at or soon after launch date. We shall see. Regards, Pete

I think for basic things like throttle and trim settings, the standard FS offsets work fine. After all, they are the values the SIM engine inside FS is using at the time, no matter what clever programming there may be in specific add-on aircraft to set them. Really, the main difference with some add-on aricraft in in the autopilot control -- the settings on the MCP. Surely your motorised throttle and so on only has to folow the current Sim settings for those values, not worry about the MCP values? Regards Pete

I keep things parallelled, don't fret. Pete

They are different controls altogether, and the same ones you get on the Keyboard. What for? I can sort of understand why you might want to disable axis inputs, in case you are getting jitter or interference, but surely you don't need to touch the buttons? Same would apply to the keyboard ...? Regards Pete

Here's 2.606! Pete GPSout2606.zip

Ah, a complete circle, eh? What is the serial port speed set? That's really the limitation -- if the defalut speed of 4800 is set then that's only 480 bytes per second which would only allow 48 bytes in each burst with a 100 m/sec delay. What would happen is that a big backlog of data would occur in the PC's serial port driver buffers, until they overflowed and you got some errors., then it might start all over again. meanwhile there's be an increasing delay noticable in the results on the device as it got further and further behind. I'll put the Q and C fields back as they were ... Pete

I thought it was the reverse. It most certainly doesn't use RAW values for axes. But for POVs it must do, surely. I'm sorry, but I really don't understand what is going on. Not since FS98/2000 days when I used EPIC. That's where that text comes from. Sorry. I think in those days there was no "POV_MOVE_EVENT" entry. But also, in those days, FS was using the standard joystick API in windows, and values went through more or less unmolested. Since they changed to DirectInput in FS2002 I'm afraid I lost interest somewhat and I don't really know what happens -- except that DirectInput seems to mess with values. I still use the original Joy API in FSUIPC, and have the facility to read axes in RAW form in the Axes assignments section. But currently there's no POV support there. I suppose that is something I could add -- reading RAW POV values like an axis. It is possible, but not just at present as it isn't a trivial job (lots of table changes to accommodate another axis type after XYZRUV), and I don't have the time to spare at present. If you still haven't solved it by November, say, get back to me and I'll see what I can do. For now I'm afraid it's a case of continued experimentation and debugging to find out what is going on. Sorry. Regards Pete

The FSUIPC steering tiller merely operates the rudder. FS itself currently does not provide a true steering axis at all. The only difference, having a second axis, is that it can be calibrated to be more effective (for turning), whereas for normal rudder operations in the air you wouldn't want such sensitivity. When just operating in increments / decrements it is identical to the rudder, so use the rudder keypresses. Regards, Pete

Still talking about FSUIPC I assume? Sorry, but if you want to use FSUIPC version 3.xxx (and 3.70 is current) then either your "carrier ops" program needs an application access key -- which it is most unlikely to have if it dates back over three years to FS2002 times), or you will have to purchase FSUIPC and register it as a user. I would have thought that the program would have come with, and installed, a Version 2 of FSUIPC, which was relevant to the FS2002 era, and needed no keys whatsoever. That is why I suggested in my other reply that you have an installation problem. Regards, Pete

The "latest version" of "carrier ops"? Sorry, that is nothing to do with me, I have never even seen it. If you really mean FSUIPC (and if so you should say), then they certainly should not have done that, but merely pointed you to http://www.schiratti.com/dowson where you can download it. Just because you installed FS2002 and crarrier ops on a new computer certainly doesn't mean you need a new version of FSUIPC -- you'd be better off using the one you were using on your old computer. If the carrier ops package was never ported to FS2004 then it may not have an access key for FSUIPC versions 3.xxx, which means you would have to purchase a user key. Ah, so you ARE talking about FSUIPC? You have not actually mentioned what it is you are talking about anywhere in your message at all, do you realise that? It would help if you did, you know! Where did you read that a Key would be sent to you? Have you been to SimMarket and purchased one? I've no idea -- probably because you didn't install it correctly. If you were using an unregistered version of FSUIPC, or version 2.xxx on your old computer, then the same would work on the new. It is not PC dependent. It all sounds like a botched install to me! Regards, Pete

I've really no idea how FS POV assignments work at all. Sorry. Does FSUIPC logging show what's happening at all? For a normal Hat there's usually an "off" event which usually does something like restore the forward view. Could your device be sending something like that -- a -1 or 0 when you release it? If so, that could certainly do what you observe. Does it actually change the heading before you release it and it goes to 360? Oh, one other thing. I think there can be two different hat resolutions, one which goes 0 to 360 and another which uses units which go to to 36000 (i.e. in 1/100ths). I'm writing from memory here so it may not be quite like that, but I do recall something like that. Possibly, if your device is configured (in the HID driver?) to give the wrong one the values would be out of range in any case? Regards, Pete

The main slew axes are disconnected by bits in offset 310B. All six should most certainly work -- they are all programmed in exactly the same way. I've just checked, in fact. the FS axes they deal with are those named AXIS_SLEW_AHEAD_SET AXIS_SLEW_SIDEWAYS_SET AXIS_SLEW_HEADING_SET AXIS_SLEW_ALT_SET AXIS_SLEW_BANK_SET AXIS_SLEW_PITCH_SET in that order. There's zero difference between how each of these are dealt with because it is the same code -- a bit match against the control codes for the above (65867 to 86872) less 65867. i.e. numbers 0-5 used to shift a bit mask for the bit on 310B. >> As a test, I set all eight bits and found that only the first three had the expected effect. << Log IPC writes, Monitor 310B to the log, and log axis events, then check the log to see what is happening. Pete

I know little about Elite hardware, except that I'm pretty sure it is non-standard. It won't be seen as a joystick type device by FS or FSUIPC if it isn't by Windows. In that case it is a bit like the serial port PFC devices, for which I do a module. However, I do provide good calibration facilities in the case of PFC. No, and no, sorry. Elite are solely responsible for supporting their own devices. I believe they use FSUIPC as well, but they've never once got in touch with me. Regards, Pete

Try 2.605, attached. Pete GPSout2605.zip