miho wrote:I successfully installed FG 1.9.1 and Atlas on my notebook on Windows 7 and both are running fine with the Bay Area scenery. I see a map of the area but it looks a bit odd. The ILS markers e.g. don't align with the runways at the airports. I am not sure if that is a known issue or a feature. I tried attaching a screenshot but some quota prevented me from it....
miho wrote:yes, the ILS beams were offset and it was an old version issue. I installed another one from a website I found mentioned in another thread. That solved the offset beam issue but re-introduced the lack of connection with FG. I checked the firewall again, but that didn't make a difference. I am a bit lost and frustrated. I installed some other scenery manually and also played with terrasync at the same time. Turned it off again but that wasn't the issue, either.
I'll investiagte further later...
miho wrote:Here are my command lines:
The output from the FGrun command line window:
C:\Program Files (x86)\FlightGear\bin\Win32\fgfs.exe
the command line I am using for starting Atlas:
c:\Program Files (x86)\FlightGear\bin\Win32>atlas.exe "--fg-root=C:\Program Files (x86)\FlightGear\Data" "--path=C:\Program Files (x86)\FlightGear\data\Atlas" --udp=5500
I have tried it with and without the --udp=5500 option. It did make a difference in the older Atlas version but not this 1.0.0 any more. I did also check the UDP packets from FG and they are fine. I can see them on the loopback interface. I also tried another socket on both FG and Atlas, 5505. No joy, either. Is there a way of getting Atlas to output more debugging info?
miho wrote:I haven't got a UDP packet handy but noticed that the old Atlas (IIRC downloaded as 0-3-0)version works fine while the new one (reports version 1.0.0) does not. One suspicion of mine is still the firewall but why would the new version be treated differently?
Users browsing this forum: No registered users and 0 guests