Hello everyone,I have written a small standalone server for flightgear and I want to do a field test. It is reachable via koala.endevour.de:5000The server is in pre-alpha stage and there are some issues with it. E.g. your callsign must be unique (I will remove this restriction soon).I am not sure how many clients it can serve, we will see. Please test it and feel free to email me your experiences/suggestions.You can reach me at: fgsf AT o-schroeder DOT de

Woo... Ahh... I will be sure to try it out. :-hah

I have set up a quick webpage with some more info about the server, and yes: the source code is available there, too.http://www.o-schroeder.de/fg_server/Enjoy

Some of us on the mailing list are planning to give this a shot within a couple of days. You should join the mailing list if you haven't already. After all, that is the place where developers hang out. You could also answer some of our questions. :-hah http://flightgear.org/mail

We are having a lot of fun right now, and FlightGear's IRC has never been so lively. Unfortunately, there are some bugs. The biggest bug that we are seeing is all the planes being jammed together regardless of their actual position, as illustrated by these pictures:http://www.students.yorku.ca/~ampere/fgfs-screen-001.jpghttp://www.students.yorku.ca/~ampere/fgfs-screen-002.jpg

By the way, it seems that only those of us who use the CVS version of FlightGear has the above problem.

Here is another bug: if somebody comes on the server with a plane that nobody else has, everyone's FlightGear would crash. I think some checksum is in order.A nice addition would be an interpolation function that makes a plane move from point A to point B smoothly. Right now, there is way too much jitter.Still, good job on the server. :-hah

Great job! it was a pleasure even in this alpha stage.BTW, I think it's a good idea to enforce the callsign uniqueness,just like in real life...I was using debian testing 0.9.8 version, and, except for the strangeWARNGING: a disabled/broken routine has been called. This should be fixed!printed a lot of times on the console, and the infamous crash due to the missing aircraft models, had no problems at all. At 10Hz the other models update jitter is smth I could surely live with. However, I was only looking at relatively slow-moving things, like the bo105 and the c172.It was really difficult to fly and talk at the same time. The best solution was to hold a laptop for the IRC in the lap, and fly on the desktop machine :-) in helicopter I could not do that in hover, though --- too busy juggling the controls. Some kind of voice com is needed, but it might adversely interfere with the quality of the data stream.Thanks everybody!

>Great job! it was a pleasure even in this alpha stage.>BTW, I think it's a good idea to enforce the callsign>uniqueness,>just like in real life...I think if two or more people have the same callsign, they should be grouped to the same aircraft.

I am subscribed to flightgear-devel.

I guess that is an issue of the rendering engine within flightgear. When joining the scene, fgfs drops you at the starting position, regardless if someone else is already there or not. Thus all clients are overlapping at this position and fgfs tries to render it as good as it can.

This can be a real issue. The server does not know (it simply can't) which planes a client has installed. And fgfs has no real chance to handle this. There are two ways for fgfs to survive:1) simply ignore a client with an unknown airoplane2) render a default airoplaneBut from 2) there are other issues. E.g. what happens if fgfs renders, lets say, a cessna c172 as default, but the client in fact uses a T38 travelling near supersonic speed?So 1) would be the first choice to use.Anyway, I think this should better be discussed on the mailing list.

No no. When somebody's plane speeds up, I see it goes forward, disappears at about 100m infront of my plane, then appears 100m behind my plane, and the whole process repeats. When I am flying, other people's planes tag along with me. This occurs only with the users who use CVS. Those who use 0.9.8 don't have this problem.From what I can tell, the planes tag along with the camera. If I go to tower view, I see all the others' planes appear around where the camera is.

I am on the IRC right now. If you don't mind, you can login and we can discuss this further.

It is basically a good idea to keep callsigns unique. But another client trying to join with an already used callsign will have no chance to notice that. It will simply get no packets from the server and say "This crap does not work".Unfortunatly there is no kind of "handshake" between server (or another instance of fgfs) and fgfs. And there is no way of communicating with other clients either.But these things can be changed, if someone is willing to modify the networking code of fgfs.