Martin Spott writes: > This would support the idea of a general interface abstaction between FDM on > one and the whole I/O stuff (keyboard, mouse, joystick, sound, screen) on > the other end. This might fit for different purposes: > > 1.) Exchangeable FDM on local machine > 2.) remote FDM with 'stupid' front-end > 3.) multiplayer-server > 4.) AI ... > > > Paul's idea resembles me of the way X clients communicate with the server. > Local clients prefer shared memory (at least on several commercial Unices, I > believe it's the same on XFree86), remote clients use TCP/IP. I don't know > how portable this could be .... ?
The ExternalNet FDM is a reasonable first stab at a generalized remote FDM interface. FlightGear can send over initial condition and reset commands, and the remote FDM passes data back. There's certainly a lot of room for improvements and extensions, but it does work. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
