July 15, 201213 yr I thought the problems with Gmap were fixed with the latest update, but I just decided to run a job out of Ketchikan, and couldn't get Gmap to connect to Flight. I haven't run a job in weeks, so I figured maybe it wouldn't connect when running a job. After rebooting, and starting things up in different sequences, it occurred to me , maybe this is the problem like when you had to go to Hawaii first to connect, so I went to Anchorage and it immediately connected. Couldn't get it to connect at Johnson Petersburg either which was the destination on the $100 hamburger job. Also tried PAWG, and no connection there either.
July 15, 201213 yr Just connected at Ketchikan fine so perhaps you weren't using the latest beta release after all?? Try downloading it again, maybe? I guess these suggestions are obvious ones that you have likely tried already so there may well be some other obscure cause.... Rick
July 15, 201213 yr Author Just read on the FS widgets forum that others have had trouble after installing the new Beta with connecting from Ketchikan and airports close to there.
July 16, 201213 yr Just a suggestion - but I have found that if I jump straight into a Job and try to connect Gmap that it invariably fails to connect unless I first start the engine (if it is in a cold state).
July 16, 201213 yr Author Just a suggestion - but I have found that if I jump straight into a Job and try to connect Gmap that it invariably fails to connect unless I first start the engine (if it is in a cold state). Will try that, thanks. Sent from my SGH-T679 using Tapatalk 2
July 16, 201213 yr Author Well somehow I had an older Beta in my program folder instead of the latest one dated July 5, 2012. Downloaded the latest one, installed it, and now everything is working..... :Party:
Create an account or sign in to comment