Flightgear segmetation fault when invoking with --nmea=socke

vosskaem · n00b Joined: 01 Mar 2005 Posts: 6 Location: Germany

Everything runs fine but when I try to invoke flightgear with

Donny · n00b Joined: 06 Jun 2004 Posts: 59

I use --nmea=socket,out,0.5,192.168.0.48,3001,udp
3001 is the port, must be the same as Atlas.
Maybe this helps.

vosskaem · n00b Joined: 01 Mar 2005 Posts: 6 Location: Germany

It works now!

Looks like fgfs has bad synthax checking :-(

I used a dot instead of a comma between port and protokoll identifier. Every wrong parameter produces a seg fault...

Thanks
Volker

Donny · n00b Joined: 06 Jun 2004 Posts: 59

Correct, I had that seq fault problem with the mutliplayer options, used also wrong syntax and then it seq faults.

In case you want multiplayer here is one multiplayer server:
http://www.pigeond.net/flightgear/fg_server_map.html
There you can see if there is someone flying and also follow your own plane if you have joined.

This is the command to join that server:
fgfs --callsign=Yourname --multiplay=in,10,192.168.0.48,5002 --multiplay=out,10,pigeond.net,5002 --aircraft=AN-225

Replace "Yourname" with a name.
The multiplayer=in ip needs to be your internal ip if you are on a lan behind a firewall router, from the system fg is running on.