Bugs: Difference between revisions

Jump to navigation Jump to search
353 bytes removed ,  30 September 2007
→‎Known Bugs: Moved some fixed bugs.
(→‎Fixed Bugs: Moved some fixed bugs.)
(→‎Known Bugs: Moved some fixed bugs.)
Line 501: Line 501:


* This is an effect of the render-as-fast-as-you-can approach taken by FlightGear. Presumably the user still wants to be able to interact with the graphics when the simulator is paused. Activating sync to VBLANK might give the desired result  if the cpu is fast enough to have time over between the frames. (Since most of the work in glxgear is done by the GPU it can much easier saturate the GPU with little CPU effort than FlightGear can.)
* This is an effect of the render-as-fast-as-you-can approach taken by FlightGear. Presumably the user still wants to be able to interact with the graphics when the simulator is paused. Activating sync to VBLANK might give the desired result  if the cpu is fast enough to have time over between the frames. (Since most of the work in glxgear is done by the GPU it can much easier saturate the GPU with little CPU effort than FlightGear can.)
==== Out-of-bounds array reference in JSBSim ====
This is in the interpolation table code.
This bug has been fixed in the [[http://jsbsim.sourceforge.net/ SF CVS]] version of JSBSim.
==== Memory leak in JSBSim ====
This is in the "message" handling code.
This bug has been fixed in the [[http://jsbsim.sourceforge.net/ SF CVS]] version of JSBSim.


==== Glideslope service volume. ====
==== Glideslope service volume. ====
789

edits

Navigation menu