bfindlay

Pete - thanks for getting back to me. I hope you and your wife had a good trip! I did get it to work - it was an extra space in the 'sentences' line in the config file. I re-read the manual line by line, detected the error, and voila- it works perfectly. I have not tried to fine tune what in the minimum I can reduce the sentences line to, I just set the port speed in the gps, the com3 port on the computer, and gpsout config line to the max the gps could support (115k or so if memory serves) It updates immediately upon launching FS2004, and the refresh rate seems as fast as when I actually fly with it. It is a hoot to fly a course in RL, (mountainous terrain, here in the Yukon), then check it in the sim to see how close FS2004 comes to the real thing. (Ie on course at this waypoint exactly, where is the peak off to the left. I am blown away by the fidelity of the geographic info (FSGenesis terrain). Thanks for such a wonderful product. If I ever get back to using FSX (unlikely - bought a brand new top of the line computer for it this september, and still couldn't get frame rates out of the low teens), I will definitely register FSUIPC 4!! Addicted to the GPS out!! ;-) Cheers.

Can I use GPSout with an unregistered version of FSUIPC (3.7.5.0)? (FS2004) If not, then how do I configure it after I register? I have the GPSout module in there, and have the .ini pointing to com3, and my gps is using com3 in the hardware>device manager. I have the gps (Lowrance airmap 600c) set to accept gps nmea input, as well as NMEA v2 input, and have the protocols to accept set at 'GLL, RMC and RMB, GGA, GSA and GSV (no on the APB, as I cannot drive the autopilot in FS2004 with it). The baud rate matches, and the .ini for gpsout reads: [GPSout] Sentences=RMA, RMC, GGA,GSA To my eye, this should work, but when I check under 'satellites' in the gps, it just sits there and says, 'waiting for NMEA input'. How do I get this unit to talk to FS2004???