Ampere K. Hardraade wrote: > Agreed. FlightGear is not written with threading in mind. Neither does > Simgear or plib. This mean none of them are thread safe. Splitting the > mainloop into two is definately not going to work. You are going to have to > rewrite the entire application. >
I would say that we were quite aware of threads when we built flightgear. We are also quite aware of the severe problems you can quickly create for yourself in a real world application once you go beyond the simple producer/consumer example in your text book. FlightGear spawns one thread to do as much of the tile paging work as possible in a separate thread. This is painful though because tile paging is complicated, and you can't do anything opengl related outside the main render thread. Model loading invokes texture loading which invokes opengl calls. <boom> application blows up. So FlightGear was written with threading in mind, and we have avoided it as much as possible. Curt. -- Curtis Olson http://baron.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Flightgear-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-users
