Pete Dowson

FSUIPC already provides a control, which you can program on button or keypress, to set the AI traffic level or toggle it between your setting and 0. This only applies to FS2004. If you are operating through the IPC interface you can send keystrokes or buttons there too, but obviously you'd need to program the chosen method in FSUIPC's options. Regards, Pete

I am really pleased you find it useful! Makes the work on it so worthwhile. :D Regards, Pete

Sounds good. But it won't be so efficient for FS sending all of the sentences if only one or two will do. Can you find out what sentences the programs actually need? If it isn't documented, then by trial-and-error I presume. Then I'll put some details in the GPSout "read.me" for others. Oh, and the full names and web-sites for the programs too, please. Thanks & Good flying! :) Pete

Well if you mean on Enrico Schiratti's site, I know for certain that it was 3.20 since Saturday. It sounds like either your PC or your ISP are caching the file. Try flushing you browser's cache. If that doesn't work, try again, or contact your ISP and complain. I don't know of any easy solution. It seems to happen with some ISPs every time -- in fact I think Enrico put a note up about it on that very page. Did you check? It may give some advice. If it's another website then contact them please and tell them to update. I distribute to many different places, though I know they don't all upload it. I don't maintain any web-sites as such, by the way. Any problems really need to be dealt with by whatever service you choose to use. Regards, Pete

If by "my module" you mean FSUIPC, then, no. It is passive, not active. Other things interface to it, it doesn't interface to anything but FS itself. You'd need to write an interface program. see the FSUIPC SDK, available from www.schiratti.com\dowson. The only module I've written that does anything on a LAN is WideServer, which talks to WideClient using TCP/IP or IPX/SPX. But it isn't broadcasting. It uses sequential addressed protocol only -- IP or SPX. And the data is specific between those modules, both part of WideFS. I don't know. Sorry. Maybe some other readers will know. Regards, Pete

Sorry, I don't fully understand what you mean. There is a GPS implementation in FS -- are you wanting to interface to that? In FS2004 you can read out quite a lot of the GPS stuff (see the Programmer's Guide, offsets 6000 and following), but I'm not sure what happens if you try to write to that area. If you mean you want to be able to tell the FS A/P to follow a specific heading, then, yes, of course you can do that -- enable Heading hold at 07C8 and then set the Heading required at 07CC. If the A/P is enabled then it will guuide the direction of the aircraft. If not, then the Flight Director (if enabled) will hlep the pilot follow the route. Regards, Pete

Okayplease let us know if you do. there may be others interested too! Regards, Pete

It sounds like you've connected your PCs as a Network. There are no IP addresses used in a one-to-one serial connection. It's just three wires -- read, write and common, with the read and write crossed over. GPSout and FliteStar connect by serial cable. there is no GPS input to FliteStar other than on a serial port as far as I know. Did you check? The README file I supply clearly says "connect your flying PC to your moving map PC with a serial "null modem" cable (ie send and receive crossed over), and configure your map program accordingly.". I do not know of any NMEA standard for GPS connection via Network, whether Ethernet or USB or any other means. I think it only works with a simple dedicated COM port (serial) connection. If you know of a moving map application which can receive standard GPS input by any other means please let me have full details, and also the GPS devices which can provide such output. Have you checked the FliteStar documentation to see how it wants the connection? My FliteMap only allows COM ports to be selected, with selectable line speed. You can run it in test mode to see what is arriving and whether it is accepted. Sorry, I have no idea. I didn't realise you could get Palm PDAs with ordinary COM ports -- my Garmin iQue 3600 (using Palm OS 5) has only got the usual USB connection for HotSync. Regards, Pete

Just overwrite the DLLs (and the WideClient.EXE's). The registrations are kept in the FSUIPC.KEY file, for both. Keep a copy of that safe, print it as well. The INI files only contain your preferences and settings. Regards, Pete

Sorry, no, I have no idea how to deal with that then --- it seems a rather odd of Microsoft to supply a control to reload aircraft if it doesn't actually reload from the files. Maybe it is only relaoding the AIR file or the performance data from the CFG file? Maybe it's for those who design aircraft who need to keep tweaking parameters and re-testing the flight characteristics. I can only hope that someone who knows about these things can chip in and help. Maybe there's an aircraft designers forum or newsgroup some place? Otherwise, it is looking as if you will have to resort to reloading the flight after all, isn't it? Regards Pete

Ah, sorry. I didn't see you said "I registered WideFS - version 5.50". I should have corrected you there. There was NO registration, no payment at all, for FSUIPC before version 3 nor for WideFS before version 6. There's no registration which you could have made for 5.50 which will carry over to version 6.xx. Sorry to have misled you. But if you were running with FSUIPC 3.11 before you couldn't have been using WideFS 5.50 in any case -- only WideFS 6.xx works with FSUIPC 3.xx. Regards, Pete

Only that FSUIPC will recognise GoFlight buttons and dials, so you can assign to those any of the keypresses or controls listed in FSUIPC's keys or buttons pages. Please read the User Guide on this, I did try to explain. It is probably of more interest to users of Project Magenta and other non-FS cockpits. Only if those products accept keystrokes or can be controlled through documented FSUIPC offsets (PM is one of the latter -- althogh it accepts keystrokes too). Note, however, that FSUIPC does not drive GoFlight displays or indicators. I'm not sure what to do about those yet. Maybe another add-on later. Regards, Pete

Yes, of course. I dare not take things out once put in. Folks would complain and not upgrade. I cannot support old versions. Pete

No, certainly not. Your registrations last the life of FSUIPC 3.xx and WideFS 6.xx respectively, at least. I don't want folks using old versions. I cannot support old versions! Regards, Pete

The FSUIPC facility only adjusts the seconds to keep the SAME difference between FS time and the system time all the way through the session (well, until you load a flight with a new time, or change the time yourself). Please just re-read the User Guide on this option: If you want the FS time to be equal to the system time, I think that's an FS flight-loading option, although mainly I find I have to go into the Time menu and set it. Regards, Pete

Almost all external applications which use FSUIPC to talk to FS will work on a WideFS client too. There is a list on the right-hand side of the page at http://www.schiratti.com/dowson. Some of those will be aircraft or FS panels, so they won't work that way, but the rest should. It's unusual to come into WideFS in this way -- it's more usual to have a need, and use WideFS as part of the solution! :lol: There are moving maps like Ted Wright's NAV3, which is a real good candidate for this. Of course my own WeatherSet and TrafficLook. Any of the external weather programs like FSMeteo or ActiveSky. Fancy instrumentation such as that from Project Magenta.et cetera. Regards. Pete

There's only ever one proper valid current version of FSUIPC, and at present that is 3.20. Get it from http://www.schiratti.com/dowson. Please check the announcements at the top of this forum for more details of versions. Regards, Pete

Well, they are the values FS is computing and using. Are you sure you are converting correctly? The GS is in METRES/SEC not KNOTS, so you need to convert to compare. 1 knot = 1 nm/hr. 1 nm = 1852 metres Therefore 1 metre/sec = 3600/1852 knots, i.e multiple m/sec by 1.94. There shouldn't be any difference between the two as far as GS, TAS and IAS are concerned. It's you headwind that stays directly on your nose as you turn which is the most peculiar. I really cannot think of any possible explanation for that! Regards, Pete

So you didn't even need to use the "ThrottleSyncEngine2=Yes" option I put in for you? That's good. It sounds like the levers are within reasonable tolerance after all. :) Pete

No, sorry. It is an oversight. In fact version 3.153 is identical to 3.20 -- the number 3.153 was the final Release Candidate during testing, and no change has been made to code since then. I used all the increments between 3.141 and 3.153 in the extensive testing over the last month. Regards, Pete

No, sorry. I think that program was based on a Microsoft tool and there should certainly be one for FS2004 in their forthcoming Traffic SDK, whenever that is released (hopefully it won't be long now). I really am not interesting in duplicating stuff. Regards, Pete

Sounds extremely weird. I hope other SB users can help here. FSUIPC is not controlling winds -- what is controlling the weather in your setup? There is a problem in FS2004 with occasional 180 degree windshifts, but you would most certainly notice these as they would affect the performance of the aircraft quite markedly! I have never heard of headwinds that follow your nose as you turn -- that sounds impossible to produce in FS2004 for sure. I don't know where SB is reading things, nor whether you are using a default FS204 GPS or an add-on, but you could monitor the places inside FS where these things are maintained. In FSUIPC options, select the Logging page and look at the right-hand side. Here you can enter up to 4 variables to be monitored. The GS is at offset 02B6 and is type U16. This is in metres/sec so you would need to do a rough conversion in your head to see if it looked right (a bit more than half to get knots). The default FS2004 GPS GS is at offset 6030, and is type FLT64, also in metres/sec. You can therefore compare them quite easily. You could also monitor the ambient wind direction (0E92, U16, in units making 360 degrees = 65536), and ambient wind speed (0E90, U16, in knots). These should be identical (in result) as the Shift+Z wind display. If you want to monitor TAS or IAS in place of any of those: TAS is at 02B8, as a U32, in knots x 128 IAS is at 02BC, same To monitor them in the message window on screen check the "Adv display" checkbox below. To log them in FSUIPC's Log, check that box -- but don't do that for too long as it make the file grow vey fast, and may also affect frame rates. I'd be interested to find out how you are getting a turning headwind to match your heading (!), but please note that I am away on holiday from this Thursday 19th Feb until Thursday 11th March, inclusive. Regards, Pete

Good. Of course FSUIPC is not driving the indicator LEDs or displays on Goflight equipment, so you don't win all ways. I'm not sure what to do about the displays. I may consider doing a sort of "GFINFO.DLL", along the lines of my EPICINFO.DLL, but I won't have time to do this for some time, I'm afraid. Just in case there are any questions on all this, I have to tell you that I will be away on holiday from this coming Thursday 19th Feb till Thursday 11th Mar, inclusive. Regards, Pete

Hmmm. That's a little worrying for me as I've done nothing specific which would account for that. I wonder what is going on. If your FSUIPC is not user-registered it may possibly be explained by the better method of identifying the modules and gauges calling FSUIPC's interface, but it doesn't seem likely that you aren't user registeredand none of that code is active for fully registered copies. I am glad you are pleased but I remain puzzled. :? Regards, Pete

Apart from the three visibility filters marked *** the FSUIPC filters really do nothing at all with default FS downloaded weather. Hmmm. I don't know. I just run them as they are, not fiddling with anything. I had a nice, short, flight today (the first one for "fun" for a while), from EGCC to EIDW -- my usual "test" run -- and used FSMeteo with today's weather and Radar Contact for ATC. Everything seemed perfect enough. The weather matched all the way, the graphics seemed accurate. I must admit I've never really seen any of these complete "mismatches" some folks have mentioned. I tend only to fly in Europe, and mostly out of EGCC. Perhaps this is a stateside phenomenon, or something geographical? Perhaps the weather sources for ActiveSky or FSMeteo are a bit more suspect over there? Sorry, I really haven't a clue. I think only the weather programmers can pull the information together to determine what exactly is going on. This is really down to FS graphics, over which I'm afraid I not only have no control but which about I am a complete dunce. However, the main (not only, mind) sorts of clouds which do that sort of thing are the very ugly 2D ones. In the Options-Settings menus find the Weather options and ensure you have, at least, the 3D clouds slider to to 100% (full right). In my opinion any other setting there wants shooting! For best results, set all the sliders on that page to max (all full right). This will probably slow your FS frame rates a bit. Then go get the Chris Willis high performance clouds from one of the web sites. (Sorry no link, but try Avsim or Flightsim). Things weather-wise in FS2004 are actually better than they were in FS98. They are better in some respects than they were in FS2000, but not many. They are heaps better in several ways (especially visibility) than they were in FS2002, which in my personal opinion was a step back from FS2000 in this department. But they are most certainly still far from perfect, and worse, they are very very complex -- it is understanding what the ? is going on sometimes which is the problem, not the weather itself. Really, in the end, just fly it and expect the unexpected -- just like English weather, it changes and is nowhere near 100% predictable. If you aren't a control freak it can be quite fun, mostly, honest! Regards, Pete