Kishore wrote:
On Wednesday 20 Apr 2005 5:32 pm IST, Curtis L. Olson wrote:
Generally, if you are just using FlightGear as a visualization tool,
you can just set position and orientation and you should see the
world move past you as you'd expect. But if you add more data, you
will start seeing things like instrument gauges, HUD, etc. come to
life.
This is kind of what i wanted to do for right now and it works. I shall then try to add more data later as i progress.
Replying to something you said in your other message. FlightGear by default doesn't smooth incoming data. That might be an interesting feature for someone to add though ... it's something that can get complicated and tricky very quickly depending on what you are trying to accomplish, especially if your input data rate can vary or isn't exactly compatible with the FG render rate. You either have to predict future position (and have a way to smoothly resolve errors in your prediction) or you need to lag an iteration behind ... and that's not always trivial/possible if the input data isn't coming in at perfect time steps, and/or if the FG render loop isn't running at a matched rate (or even multiple/divisor of it.)
There is some smoothing code in the "replay" subsystem, but this has the advantage of knowing all the datapoints in advance so it doesn't need to do any prediction, and it knows the exact time step of the upcoming datapoint so it can do the interpolation exactly.
Regards,
Curt.
-- Curtis Olson http://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
_______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
