Stuart Buchanan [Sun, 22 Feb 2015 21:37:18 +0000 (21:37 +0000)]
stgmerge enhancements
Various stgmerge enhancements to make it functional:
- Now runs against an entire tile directory, reading each stg file
- optionally optimizes the mesh (untested)
- outputs to a second directory
- control over the size of merged meshes
bcoconni [Sun, 15 Feb 2015 10:37:13 +0000 (11:37 +0100)]
JSBSim syncing. The changelog is:
* The Pitot angle can now be tweaked with the <pitot_angle> tag in the <metrics> block.
* The refuel rate is now configurable with the <refuel-rate> tag in the <propulsion> block.
* Fixed C++11 compliance. JSBSim can now be compiled with a C++11 compiler.
* Avoid a spurious mass report to be issued when resetting.
* Fixed the moments computation. Previously they were computed with the previous time step CG position.
* Fixed a bug where the CG update was delayed to the next time step when point masses location were modified via the FCS.
Clear GroundLightManager on exit to avoid segfault
While mostly harmless since you're exiting anyway, it's an annoying
distraction when the real problem is "unexpected exit" (e.g.
https://bugs.debian.org/763285 ), and blocks testing with LeakSanitizer
Torsten Dreyer [Wed, 11 Feb 2015 07:33:45 +0000 (08:33 +0100)]
Add formatted KDI572/574 properties
Syd Adams:
I've added an update to dme.cxx /dme.hxx.
It adds a formatted KDI572-574/nm , min and kt string properties meant
for text animations for these instruments.Existing instruments will funtion
as usual, no breaks. The purpose here is to eliminate yet another nasal
workaround which usually needs to repeat some of what the code already does.
The 3 properties are empty when the dme is off (no need to check for power),
dashes when powered up but no source , out of range ,etc.
The are formatted to the KDI-572/573/574 limits ...
0-99.9/100-389 for distance to station,
0-99 minutes for time to station,
groundspeed 0-999 kt.
bcoconni [Sat, 17 Jan 2015 13:58:48 +0000 (14:58 +0100)]
Fixed a bug that made FG crash when repositionning the aircraft or resetting the simulation. Thanks to Rebecca Palmer for the bug report and the bug patch.
James Turner [Fri, 26 Dec 2014 12:20:51 +0000 (15:20 +0300)]
In-app launcher for Mac, based on Qt5.
The old Mac launcher doesn’t work on Yosemite, add a tiny
Qt-based launcher inside the main process (no need to fork /
exec) which runs before the OSG window is created.
Will be merged for 3.4, hopefully with no impact on other
platforms.
bcoconni [Mon, 15 Dec 2014 19:12:18 +0000 (20:12 +0100)]
Synced JSBSim. Adds the following new features:
- Ability to modify the location of external forces via the property tree
- Ability to specify manually the inertia matrix of "point masses"
- Improvements of the water injection feature in the turbine code
Torsten Dreyer [Wed, 3 Dec 2014 09:29:30 +0000 (10:29 +0100)]
Fix hangs while scenery-loading
don't start the traffic manager before the FDM is initialized
The FDM needs the scenery loaded and will wait for all PagedLOD Nodes
to appear if they are close (less than 1000m) to our initial position.
That's required for scenery models but not for AI traffic.
James Turner [Thu, 13 Nov 2014 21:02:58 +0000 (21:02 +0000)]
Drop ground-nets cache on scenery path change.
Unfortunately we can’t drop loaded ones, since the in-memory structures don’t have ref-counting, and we don’t
know what AI plans may be referencing them.
bcoconni [Sun, 23 Nov 2014 13:53:54 +0000 (14:53 +0100)]
Save a memory allocation each time a property node is wrapped in Nasal. Instead use a direct access to the reference counter and explicitely delete the node if the ref counter is decremented to zero during the ghost destruction.
Torsten Dreyer [Wed, 19 Nov 2014 16:26:58 +0000 (17:26 +0100)]
Optionally use SCREEN_SIZE_PIXEL for LOD
This patch enables AIModels to use the size on the screen for LOD instead
of distance from eye point.
With /sim/rendering/static-lod/ai-range-mode-pixel set to true
/sim/rendering/static-lod/ai-detailed now contains the minimum size of the
model on the screen to be displayed. Values of 10-50 seem to make some sense.
Torsten Dreyer [Sat, 11 Oct 2014 18:23:13 +0000 (20:23 +0200)]
Allow input systems to be disabled
To avoid trouble when running multiple instances on one machine, disable
e.g. joystick input for second instance by
--prop:bool:/sim/input/no-joystick-input=true
Also allowed:
--prop:bool:/sim/input/no-event-input=true
--prop:bool:/sim/input/no-mouse-input=true
--prop:bool:/sim/input/no-keyboard-input=true