Hi, Starting today (monday) I will be working on a ground vehicle server that will manage the movement of ground vehicles over a road network. The server will be in charge of calculating the ground elevation and movement of each vehicle every second. Any connecting client (FG) will be passed this info in the form of an XML document. The client will then display the vehicles interpolating the the points inbetween those passed by the server.
The question to the group is there a c, c++ library available for easy tcp communication where a read returns the entire message (XML documents will be of differing sizes)? I have looked at SGSocket and will use it unless there is a better suggestion. The results of a server and interpolation results in synchroniztion between all clients and is not dependant on the processing power of the client. Based on an educated guess a 2.4G P4 with the client interpolating intermediate elevations will be able to serve about 500 vehicles. Seamus On Sun, 16 Nov 2003, David Culp wrote: > > Wowww, nice! > > ... > > Roger that, thanks Saratoga tower. > > I'll send you the code if you like. I've written a bare-bones AI system based > on David Luff's. The AI manager just instantiates an AI object (airplane or > ship) wherever you want it and tells it when to update. The AI objects are > AIAircraft (yes, even the ship) which have a simple FDM that moves it along > at any assigned speed, altitude, heading and bank angle. > > What I would like to see in FlightGear is: > > 1) A simple AI base class, like my FGAIBase, which is based on and very > similar to the present FGAIEntity. > > 2) A simple AI object class, like my AIAircraft, that would provide "dumb > AI", which are minimalist AI objects that move along scripted flight plans. > This would be for "dumb" aircraft and ships. > > 3) A "semi-smart" AI class for autos, which must be smart enough to know > where the ground is at all times. Seamus is working on these now. > > 4) A "smart" class, which is the present AILocalTraffic. These know where > the ground is, and have the ability to communicate. In the future they may > become interactive. > > 5) An AI manager that instantiates new AI objects from the above three types > for every occurance of <entry> ... </entry> within the <ai> section of > preferences.xml (just like the way environment layers are currently defined). > You could create any number of AI objects at any place and time this way. > > 6) A scripting standard for the AI objects. The script will serve as the > object's flight plan, specify when the object should be terminated, and > contain communications instructions (for the "smart AI"). > > > Is there any interest in uniting dumb and smart AI this way? > > > I brought some KSFO arrival charts home from work, and am planning to have a > "dumb AI" airplane appear at the beginning of each arrival every 2 minutes. > The Big Sur arrival will feed runway 28L, and the Modesto arrival 28R. After > landing the airplanes would turn off disappear. I'm curious what the frame > rate hit will be. These might need to be very low-poly models. > > > Dave > -- > **************************** > David Culp > davidculp2[at]comcast.net > **************************** > > _______________________________________________ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
