Pete Dowson

Maybe, in FS2004I am not sure. I didn't think anyone was using the FS98 weather offsets any more. I've tried to maintain support for them through FS2000, FS2002 and FS2004 but they are so far divorced from what really goes on in FS2004 that it gets quite hairy, and with all the new, impressive, weather programs long ago moving over to more powerful and appropriate interfaces I doubt these have been tested thoroughly enough. If they are truly AGL, can you try flying or slewing over hills and see if they go up and down all the time as the ground rises and falls beneath you? Let me know. You see, if it doesn't, then what is that lower wind doing? Is it going up and down with the ground? If so and the next layer is not far above, what happens when they collide or intrude, is the layer above obliterated, or is that too rising and falling, and so on up to 60,000 feet or wherever? I don't think the spot-check way you are measuring / checking is really so reliable. You are expecting FS to set the weather the way you are thinking it should be set. The proper way to see what FS thinks the wind layers are is to go into the Weather Dialogue each time, and read the altitudes in the Winds section. Another more reliable way would be to switch on the wind display (Shift+Z) then slew upwards and see which altitude the wind DOES actually change -- make sure any FSUIPC wind smoothing is off first of course. Please let me know. I think after 3 years of FS2004 it is a little late to change it, and some comparisons with FS2002 and FS2000 would be needed to to verify whether I have the programming wrong or the documentation, and really, at this time, I don't have the time. But I'd be interested and I'll certainly note it. BTW you can also compare it with what the FSUIPC AWI reports (by using WeatherSet) and also the NWI (WeatherSet2). The AWI is really the 'modern' weather interface which matches closely what FS2004 is capable of. Regards, Pete

Not just laptops, also many Desktops/Floorstanders. I've had great success with some I bought very cheaply. Nice small things, just really a lead with a USB plug on one end and a COM socket on the other, just a little bigger than normal. They are real cheap, made in China, and the only name on the packaging is "Best connectivity" . I've had bulky expensive name brand ones which are a pain and don't work properly, but these (around GBP 6, or $10 I suppose, each) are excellent. Regards, Pete

Well, that is all that has changed which could possibly affect anything in the joystick calibrations. It is really sounding as if, somehow, your FSUIPC.INI file has got corrupted. Why not just re-calibrate, or find a backup? It's part of the aircraft-specific facilities and applied to Buttons, Keys, Axes and Calibration sections. Since you don't use Aircraft Specific sections you wouldn't have noticed it, so it isn't of any consequence. Yes, that's what you need to do. This merely confirms very strongly that you need to calibrate. It sounds very much like you have got it using default values, which would be designed to place the "centre" in the centre, of course. FSUIPC has no idea about your 'detente'. You have to calibrate the centre around that position. It is so easy to do, please just check the instructions. It is but 30 seconds work! No, not at all. The values in your INI file are messed up. Please just re-calibrate. Regards, Pete

Yes, but I will be incorporating GPSout and AutoSave in the user facilities of FSUIPC 4, with their own options pages. They'll be available to registered FSUIPC 4 users. Regards, Pete

Well, it wasn't so bad when I got it -- I started with FliteMap when it was still MentorPlus, and one-time upgrades were a lot cheaper than they are now. I somehow wangled reasonably priced matching NavAid and FliteMap updates all the way to 9.0x and about Jan 2005 or so's NavData (I think, not sure without looking). Yes. I've never used it, mind. Yes, I did contemplate getting Jepp View, but for World-Wide coverage that was/is expensive. These days, though, I tend to only fly in Europe so I suppose it could be a consideration -- if it doesn't involve and update to 9.16! ;-) I do have an out of date complete set of Jeppesens in lovely leather binders (World-Wide) -- bought those bit-by-bit over a period. Nice for browsing -- I do still like paper, unfortunately. But for all practical purposes I now use nDac from NaviGraph. Regards Pete

Sorry, the "FS" was a typo for "FSUIPC" (ALL versions since joystick calibration wasadded about 8 years ago). No, that was well before 3.70 and is quite independent. The only new thing affecting Joystick Calibration settings in 3.70 was the "ShortAircraftNameOk=Substring" option, related to aircraft-specific settings. Did you read all my last message? If so haven't you any other answers? Pete

As you will have seen from Mr. Fournie's explanation, it appears that FliteMap is dead w.e.f version 9.16. You have no moving map features in that version. :-( Regards, Pete

Thanks for the info. Butouch! Boy, am I glad I am still on a version before 9.16! Thanks, I'll take a look, but I'm pretty much tied into FliteStar at present through my plan conversion utility (FStarRC) which gives me FliteStar-made plans in Project Magenta, FS and Radar Contact formats. [LATER] Just had a quick browse. They don't state coverage anywhere, but it does appear to be very US-centric. I tend to fly (sim-wise) 90% Europe, with EGCC as base. My Jeppesen FliteMap is a Corporate World-Wide edition, with NavData updated last year ready for FSX. ;-) Regards, Pete

Okay, so let's see what you said: 1. Is this with a default aircraft. If not, change to a default aircraft first. 2. Are you assigning axes in FSUIPC or in FS? 3. If you are using FS with separate axes for each engine, then there are a total of 5 zones on the axis range -- below full reverse null zone, then the reverse range, then a null idle range (the "centre" settings), then the forward thrust range, and finally a null zone above full thrust. It sounds very much like you have calibrated the throttle wrongly, OR 4. Are you using the facilities for Aircraft-Specific calibrations, and if so, is this one such specific assignment set? If so, please note there is a bug in 3.70 which occurs in aircraft-specific calibrations if "ShortAircraftNameOk=No". Try changing that to "Yes" or "Substring" for now. This bug was reported by one user (only) so far and doesn't seem to occur on all systems, but I have tracked it down and the fix will be included in the next FSUIPC update. Meanwhile this parameter change is a good work-around without any side effects. If that is truly the case then it clearly needs re-calibration. The values in the INI file are only ever set by you, when calibrating. They are never changed by the program otherwise. Regards Pete

Sorry, there is no such thing as FSUIPC 5.536. It probably won't exist for at least another 3 or 4 years. Please downgrade back to the current version, which is 3.70. When you've got a valid and correct FSUIPC installed and tested, come back by all means. But I cannot help with non-existent version at all. Sorry. Regards, Pete

Do you mean FliteMap? As far as I knew, you paid extra for the GPS input facility in FliteStar, and then it was called FliteMap (although admittedly the installed binary is still FliteStar.exe! ;-) The version I am using is 9.04 and I have no problems at all. Strange they would reduce the list so much, especially only in a point update. My version 9.04 (Build 7523) lists loads of GPS's by make (left scroll window) and model (right scroll window). Almost all of the Models are also listed with different protocols after the model number, including NMEA 0183. There's also a "make" called "Generic" for when you don't know or care, and the 'models' there include Aviation protocol and different NMEA varieties accepting different (explicit) sentences. I have it set to Garmin -- GPS 95 NMEA 0183, but it works with most of them in any case as long as they are NMEA. My GPSout sentences are RMC,GGA,GSA. If Jeppesen have for some reason removed most of the GPS input facilities (which would seem very odd), then all I can suggest is trying every one till it works. You could also enable all the NMEA sentences in GPSout (but keep the frequency low and the speed high as this will really clog things up otherwise) until you find one of the FliteMap settings which work, then start removing sentences to see which you really need. I assume you can still set the speed too? They haven't fixed it at the default NMEA speed of 4800 have they? That would be awful. I use mine at 38400, the highest in the drop-down for speed setting. Regards, Pete

Ah .... FSUIPC sees a Hat as 8 switches/buttons, whereas I think the PAN facility reads it a little like an axis -- the Hat values being the parameters. Are you sure it isn't continuous, like an axis? Re-assign it in FS and use the Event and Axis logging in FSUIPC to see what FS is passing. I really have no idea because I don't know what the old HAT switch assignment is doing. I don't have one, you see. But first, please tell me, WHY are you trying to do this the hard way, by editing the INI file? Have you looked at the Buttons assignment facilities in FSUIPC. Surely it must be 1000% easier to do it on-line, where you can move the hat, assign a control by name and so on .... you have me quite puzzled! Since I don't know what your "old Hat" was doing, and I can't try this way (not having any such hat), I really can't say. Surely it is easy for you to test? Are you saying you've not even tried it? I don't know, because i don't know what your Hat does in FS in the first place. Check the logging as I suggest. It may work better if you program it as a PAN VIEW with a parameter to tell it the direction -- typically hats return a direction either in degrees (0, 45, 90, 135, etc) or in 100ths of a degree (0, 4500, 9000, 13500 etc). The log should help tell, otherwise you'd need that JoyView program I've uploaded here a few times. If you can't find out from logging, let me know and I'll see if I can find it and attach it here too (or you can scan the threads here with papaer clips indicating attachments). Note that, if the Hat is providing continuous changes, like an axis, I will consider adding it as an extra assignable Axis in FSUIPC. I would be completely dependent upon folks like you to test this for me, but otherwise I don't think it would be a big problem -- just a matter of finding the time! Regards, Pete

Yes, but if you are also trying programming you have to be classed as a programmer too, and programmers do certainly need to think logically and be able to read and get into such details with care and understanding. That does even apply to VB programmers, I assure you. Otherwise maybe programming is not a hobby for poultry farmers? ;-) Regards, Pete

Erthe subject of your message says "how do I register my program ..." but the text says that YOU would like to register. Which is it? Program access to read and write FS values is not the same as User access to all the documented user facilities. Did you look at the documentation at all? The registration business is all described quite early on. You don't need to read it all. Regards, Pete

In the first byte you will have the code for 'Z' (90, or hex 5A). In the second there are all the shift codes. For simple Shift just bit 0 must be set. Bit 0 is the lowest bit, value 1 (2^0 = 1). You simply make a value from all the bits you want set. Isn't the documentation clear enough on this for you? Can you clarify what it is you don't understand, please? You should write the whole 4 bytes as one 32-bit value (an integer in VB, probably, or is it a long?). This would be no different to writing any other 32-bit (4-byte) value. In the case of Shift+Z the whole 4 bytes, assuming no other options are to be set, are, in order hex 5A, hex 01, hex 00, hex 00. Now, as a 32-bit value you have to remember that the first byte is the LEAST significant (i.e. lowest in value), so in hexadecimal the 32-bit value is: 0000015A or in decimal simply 346 (being the 256 for Shift, plus 90 for Z). No, Window ennumeration has never been a facility in FSUIPC, probably because it has never really been asked for. It is also not always obvious how to determine these. The Window Class for all such is "FS98CHILD", so that doesn't help a lot, and the title is, I think, dependent upon language version -- maybe it can be looked up in the LANGUAGE.DLL. Ideally, perhaps the Windows ID number should be used. This corresponds to its position in the Menu and its number in the PANEL.CFG file, as well as the Shift+N value used to toggle it on and off. But there again, any window can have any title as dictated by the PANEL.CFG, so determining which might be a GPS is problematic. Regards, Pete

Do you mean the keycode for FSUIPC's hot keys for applications, or what? I'm not sure of the context. Regards, Pete

There won't be an offset for a control action like that. You can either simply write zero to both aileron and rudder control offsets, or send the actual FS control corresponding to the '5' button to offset 3110. I can't remember what control it is, but you can find out easily enough by switching on FSUIPC's event logging (in the Logging tab of the Options), and pressing it -- look in the resulting Log file. Pete

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