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?
It looks fine to me. I just did a quick test here and Atlas successfully communicated with FG. As for debugging info, unfortunately, there's nothing in Atlas right now to do that.
I assume that Atlas and FlightGear are running on the same machine? I don't think this will help, but can you give me an example of one UDP packet - I just want to see what FlightGear is sending to Atlas.