Pete Dowson

You found a true serial cable (not USB?) for your device there? I didn't see that! Pete

Searching the 'net I found this quote on one site: Maybe yours in one of those. This was on http://pc-mobile.net/pdaserial.htm. I'm afraid it looks like you are out of luck. Sorry. Regards, Pete

What do you mean "for two years"? The current sales of FSUIPC are for Version 3 and cover the life of Version 3, however long that may be. There's no work being carried out on a Version 4 yet -- that would depend on whether any future versions of FS need substantial re-writes. I don't know all those aircraft. If they provide keystroke capabilities for everything you need, then, yes it is possible. If they only provide functions usable with the mouse, then you might be able to do it but you would probably need Luciano Napolitano's Key2Mouse to convert keystrokes (programmed in FSUIPC) into mouse movements and clicks on screen. I think the PMDG ones provide keystroke capability for most things. I should think the Level D 767 would do (their previous effort, the Wilco 767PIC did, after all), but I don't know anything about the ATR72. FSUIPC doesn't drive the indicators and readouts on any GoFlight modules, but there is an addon for FSUIPC called GFdisplay (downloadable from the Schiratti site too) which will. Unfortunately though it isn't terribly intuitive to program -- though plenty of examples are provided, they are for the default FS stuff and Project Magenta. Even if you do manage with GFdisplay, many of these sophisticated aircraft do not use the FS autopilot, and their A/P control read-outs (those on the MCP) are not always available to send to any display in any case. This is certainly the case with PMDG (though some folks have found FSUIPC locations by hacking), and probably the 767. So, sorry to be inconclusive. I suggest you seek opinions of those who are already trying these things. Certainly there are folks using GF modules on the PMDG aircraft. Maybe some will see your message here, but you might also get feedback on the GoFlight forum (is there one?) and the support fora of the individual aircraft. I think GoFlight themselves are also coming out with some software to provide more flexible programming for their modules, so you might want to check that possibility also before spending any (more) money. :wink: Regards Pete

It is in the FSUIPC SDK, and has been for years. Get the SDK from http://www.schiratti.com/dowson. Regards, Pete [/url]

Is that "really small"? That would be 5.343758 degrees. Without knowing where your aircraft was at the time, who can tell? Why don't you simply compare it with what it is supposed to be? Please look inside the FSUIPC SDK and get FSInterrogate out. Use that to compare all your extracts from FS. Regards, Pete

Probably the FS sensitivity is way down at zero. Make all sensitivities maximum and all null zones minimum. Check the message from Bob Church earlier in this thread. Regards, Pete

I couldn't get my Ipaq to recognise anything either. I was trying with PocketFMS -- but I couldn't even get that software synchronised with its own PC counterparts. All this PDA stuff is a different world for me I'm afraid, one in which I know virtually nothing and seem to be able to accomplish that much too! :cry: Besides which, moving maps and so on are far more attractive and readable on another PC, which is what GPSout was designed for. :) Sorry I can't help further, but maybe others can. Regards, Pete

No problems, simply re-register as before. Regards, Pete

Yes, but unless you kill ActiveSync, which I think sits in the background "owning" the connection, I don't think anything else gets a look in. Probably have to end the process forcibly in Task Manager. Thanks! I'll bear it in mind! :wink: Regards, Pete

How did you do that? I can't check it on FS2000 these days I'm afraid, but there shouldn't be a problem from the PC end. Go to http://www.systeminternals.com and download PortMon. Set that to monitor the output COM port (do this before loading FS). You should then see the NMEA strings going out at intervals. After that it is all up to the connection and the program at the other end. I don't know Anywhere Map. but maybe that needs some settings somewhere? Sorry, I cannot help much -- provided that the data is being thrown out of the PC the rest is something I have no control over. Er, yesthanks! There's a big 'IF' in there too! I don't really get about much nowadays except with my good lady wife. Eyes getting worse week by week. I did visit the Railway Museum in Sacramento a couple of years ago though. Regards, Pete

Probably a metre (3.28084 feet). Sounds like you aren't dealing with the fractional part? Mind you, in slew mode maybe FS doesn't either? Regards, Pete

I assume you can kill it in the Windows task manager (Ctrl-Alt-Del, select processes, look for it, select it, kill it ("End Process" bottom right)). You'd need to re-boot to get it running again of ocurse. Regards, Pete

Are you using C/C++ or something else? I can't advise on anything other than C. In C/C++ you can read it directly into the appropriate type of variable -- a long long or _int64 in this case. I know the FSUIPC_Read call takes a Byte pointer, but you just cast that. The length is still 8 (bytes) the address will be given as "(BYTE *) &lat", but the result will be a long long. Wrong in C/C++. I'd hope wrong in Delphi or VB. But if you are using one of the new-fangled managed languages, then I haven't a clue, but you may be right -- they seem to be very peculiar in this sort of way. Regards, Pete

To start with, why are you expressing largish 32-bit numbers as a series of 4 separate small numbers. They are not! That makes no sense at all! Either read them into 32-bit integers then convert them using the formulae given, or, better, if your compiler supports 64-bit numbers (long long or int64 or _int64 or somesuch) then read the whole thing into one of those. Either way you then need to convert it to floating point (a "double" in C/C++) before doing the multiplations and divisions. The 64 bit integer for Latitude reppresents the number of metres from the equator. The value for longitude is simply degrees but scaled for maximum precision in 64 bits -- i.e. so that 360 degrees is one more than the 64-bit capacity. Please use FSInterrogate to see what is happening. Regards, Pete

Sorry, I've really no idea. GPSout does not handle USB. There is no NMEA specification for the protocols running on anything but a serial connection in any case. Unless your USB connection can be made to look like a serial port then I doubt that it can be done. I certainly couldn't do it here with either a USB Ipaq or USB Garmin GPS. However, I did have the following for addition to the Text file provided in the GPSout package. I never added it because it didn't work for me, but it may help you. If it does, let me know and I'll add it anyway: Regards, Pete

Not sure why you'd need to do that. I've never touched the CFG file directly. This is the file where GFconfig saves its allocations, I assume? I don't think that is needed if GF has no driver in the FS Modules folder. Maybe running GFconfig AFTER deleting the module puts it back? Did you check? [LATER] I just checked, and it does! GFConfig puts the DLLs into the FS Modules folder! Anyway, you do NOT need to do anything with GFconfig if you don't have any of GF's modules installed. The one sets up the other. The important thing to note about the GF TQ6 is that it is, in fact, and unlike all the other GF modules, configured as a "standard joystick" with 6 axes and 4 buttons. Without GFconfig or the GF FS DLLs, and before running FS, just go to Windows Control Panel (Settings-Control Panel), choose the Game Controllers, and in there slect the TQ6's Properties. You wil see that you can test them all there, and calibrate. Do all that BEFORE running FS. Then run FS and so on ... Regards, Pete

So the 90 mile visibility you set for the top of graduation cannot actually be attained. However, the view down to ground, as opposed to that towards the horizon, is not a visibility issue. If that is clearing, it is either a graphics phenomenon or it's related to that thin stratus addion I mentioned. Regards, Pete

Sorry, then. I don't know what that is. There's nothing special about 15,500. But what is your max visibility set to in FS in any case? Pete

Ah -- you mean the view down to the ground!? That sounds like the thin stratus the FS automatically puts on top of the visibility layer to make it appear like mist -- it cannot actually produce mist downwards and not horizontally and upwards at the same time. Complaints with FS2000 and FS2002 about this led them to this rather odd "fiddle" of a solution. The cloud layer will be occurring at the top of whatever visibility layer that has been set -- check the FS weather dialogues to see what that is, or use WeatherSet2 which will also show it. Regards, Pete

The current supported version of FSUIPC is 3.48. None of the shots actually show "unlimited visibility" -- unlimited visibility shows a sharp unrealistic horizon line. They all look pretty good in fact -- and the ones you say are "unlimited" look more "limited" than what you call your misty one. Your upper visibility at 25,000 feet is set to 90 niles. Is that perhaps greater than the maximnum for "unlimited" you've set in FS's options? At 15,500 feet you are nearly halfway up through the visibility graduation you've set -- so the visibility here would be calculated from the visibility at 6000 feet (where you've set it to start) at x + ((90 - x) * (15500-6000) / (25000 - 6000) )) where x is the miles of visibility set at 6000. If this works out to the limit you've imposed in FS, then that is what happens. I'm not sure what you think the problem you have is -- these visibility options in FS have been around and used successfully for years. Perhaps you are not so sure what it is you are seeing? Most "sudden" changes, which you've not shown in the pictures, are due to clouds rather than visibility, at least when FSUIPC's smoothing is enabled. Regards, Pete

What are the visibility setttings in FS? Where is your weather coming from? What values have you set for graduated visibility? Have you enabled visibility smoothing? What is the "limited" value it jumps from? What version of FSUIPC are you using? Pete

Maybe someone here may know about SB and Multiplayer, but I'm afraid it's an area I know nothing about. Certainly that part of it isn't related to FSUIPC or WideFS, it's a separate interface in FS. I hope you get the answers you need from he SB folks, they are your best bet I think. Regards, Pete

GPSout doesn't care what the actual hardware connection really is, provided it looks like a COM port. Some (most?) USB connections actually emulaste a COM port -- look in Control Panel-Hardware-Device Manager and see if it lists it as an extra COM port. Sometimes the ActiveSync application used to talk to your device takes over the connection permanently in any case -- if so you probably won't see it at all unless you can stop that program. I admit to not having much luck with my Ipaq. Regards, Pete

Ouch! So it does! I wonder why the author put that in? It certainly isn't necessary to keep sending the same KeySends at over 6 per second -- the programming on the other end (in WideClient) doesn't need that! Thanks. I'll remove that line for future updates. Best Regards, Pete

I don't understand what you are saying. Neither 3.30 or 3.47 are supported programs in any case. The current version is 3.48. Please use that THEN explain what you think is wrong. You do not explain anything in the few words above I'm afraid. What am I supposed to undestand by "give correct fuel" and "give fuel 1". I appreciate that English may not come naturally to you, but I do need more information that this. Are you a registered (paid up) FSUIPC user, or using only freeware and accredited programs? Regards, Pete