Frederic Bouvier [Sun, 25 Mar 2012 12:37:01 +0000 (14:37 +0200)]
First, preliminary, code of the Rembrandt renderer.
The new renderer is activated by the --enable-rembrandt option, or in the preferences.xml file.
The renderer at this stage doesn't have shadows yet, and shows a lighting bug. The slash screen doesn't work too.
ThorstenB [Thu, 22 Mar 2012 22:36:39 +0000 (23:36 +0100)]
Don't crash on start-up when avionics sound is disabled.
FGFX::init/soundfx::init use "_avionics" unconditionally, so it has to be
valid, even when avionics sound is disabled. Also allow to properly
enable/disable avioncis sound at run-time.
scenery: Move flightgears paging back into the application.
This way of scenery paging is really application code.
Now that the simgear stg loader is seperated from the paging
code, this appication specific paging can reside here.
May be at some time also use the spt stuff here.
Torsten Dreyer [Tue, 13 Mar 2012 20:00:22 +0000 (21:00 +0100)]
Make use of auto-coordination more flexible
- move property /sim/auto-coordination to
/controls/flight/auto-coordination
- introduce new property /controls/flight/auto-coordination-factor
with default of 0.5
- auto-coordinate the rudder if auto-coordination is true and the factor
is greater than zero
backward compatibility for the old property is temporary provided by
a temporary Nasal hack in FGDATA/Nasal/aircraft.nas
Torsten Dreyer [Fri, 9 Mar 2012 20:00:23 +0000 (21:00 +0100)]
bind the sky disable cutoff distance to a property
There used to be a hardcoded visibility of 1000m below which the
sky was disabled. This distance is now bound to
/sim/rendering/minimum-sky-visibility with a default value of 1000
ThorstenB [Fri, 10 Feb 2012 20:16:39 +0000 (21:16 +0100)]
#589: 2D panels transparent at night. May also fix #591.
Since d91a617423fa5c269902a847494b3778b05ebcb4 (vectory color calculations)
all 4 elements of a color were scaled with the respective brightness.
The caused some panels to be transparent at night etc.
Before the change, only the 3 RGB elements of the colors were scaled,
while the 4th element (alpha channel?) remained unaltered.
Commit restores the alpha elements to their original behaviour.
=> "Quick hack" for 2.6.0. Need s.o. to double check the initial changes
and commit something clean to "next".
ThorstenB [Wed, 7 Mar 2012 19:43:52 +0000 (20:43 +0100)]
#591: Fix sky flickering at certain sun/view angles
Commit 5f0066c resulted in an incorrect angle calculation. At certain view/sun
angles "hor_rotation" and "rf1" would skip from the minimum to the maximum
value).
Also, an offset angle of 90 degrees (PI/2) is added, which seems to align
the sky effect with the sun position. Calculation is probably still wrong,
but seems less wrong than before - and the flickering is gone...
Torsten Dreyer [Tue, 6 Mar 2012 21:28:18 +0000 (22:28 +0100)]
Spring-cleaning: some minor optimization
- initialize uninitialized properties
- use prefix instead of postfix increments
- reduce visibility of variables
- use empty() instead of size() == 0 for vector and string
- pass string by reference, not by value
hla: Avoid using deprecated readObjectModelTemplate.
Avoid using the now deprecated readObjectModelTemplate() method
in HLAFederate. Make more use of the available general
initialization functions in HLAFederate.
ThorstenB [Sun, 19 Feb 2012 19:20:12 +0000 (20:20 +0100)]
More talkative cmake SimGear checks
Give details whether includes or libraries are missing,
or if (and how) the version mismatches.
Also require an exact simgear/flightgear version match.
Torsten Dreyer [Wed, 15 Feb 2012 21:43:15 +0000 (22:43 +0100)]
Navradio: provide property is-localizer-frequency
This property is true if the active frequency is tuned to a
paired LOC/GS frequency in the range 108.00 - 111.95 with a
odd 100kHz digit (108.10, 108.15, 108.30, 108.35 ...)
It only indicates, that this _is_ a LOC/GS frequency,
it does _not_ provide any indication if a LOC/GS station is
actually being received.
Torsten Dreyer [Wed, 15 Feb 2012 13:59:10 +0000 (14:59 +0100)]
Some xml-autopilot tuning
- Add update-interval-secs to the entire autopilot
- cache min/max values in InputValue
- a little more relaxed "equals zero" checking in the NoiseSpikeFilter
ThorstenB [Sun, 12 Feb 2012 16:39:01 +0000 (17:39 +0100)]
#663: fgadmin not working properly (with latest Fltk)
Some things about fltk seem changed, which broke fgadmin:
fl_filename_list could return negative number instead of 0.
fl_filename_list now has a "/" appended to every reported directory name.
free( list ) now caused a segfault - use fltk's method to free memory.
fgadmin should now work with new and old Fltk.
Torsten Dreyer [Sun, 12 Feb 2012 10:41:21 +0000 (11:41 +0100)]
Some autopilot works
- add new <update-interval-secs> for autopilot components.
This does what it says.
- add new method to PeriodicalValue to normalize symmetric around zero
- move the DigitalFilterImplementation out of the header file
- refactor NoiseSpikeFilter: spare some cpu-cycles and respect periodical
output
ThorstenB [Sat, 11 Feb 2012 16:11:13 +0000 (17:11 +0100)]
Ron Jensen: fixed a potential NaN and Segfault in JSBSim propeller code
The property /fdm/jsbsim/propulsion/engine/prop-induced-velocity_fps
gives wrong answers, and can become NaN under certain conditions. When thrust is
negative and forward velocity is small we can take the square root of a negative
number. This could occur, for example, when using reverse thrusters on landing.
The value comes out much too high when alpha is near 180, such as taxing with a
tail wind.
ThorstenB [Fri, 10 Feb 2012 22:41:33 +0000 (23:41 +0100)]
#656: COM1 frequency set to 0 at startup
Also, don't flood the screen with AI ATC messages when COM1/2 is set to 0
(ignore aircraft "transmissions" on frequency "0 MHz").
ThorstenB [Sun, 5 Feb 2012 14:13:58 +0000 (15:13 +0100)]
#591: night-time rendering issues, avoid negative color values
Fog color became negative at certain sun angles (around midnight), which
resulted in weird sky dome coloring issues.
Hack: simply clamp the value for now.
Torsten Dreyer [Wed, 1 Feb 2012 21:24:06 +0000 (22:24 +0100)]
initialize the heading-indicator/offset-deg in it's class
Don't initialize the offset in the main loop but in
the init method of the implementing class. This ensures
it gets initialized if you instantiate more than one
heading-indicator and does not initialize the property for
unsused heading-indicators (no more stray heading-indicator-fg
property anymore).
ThorstenB [Tue, 31 Jan 2012 22:19:02 +0000 (23:19 +0100)]
Fix string buffer issue with replay time display.
Unclean method of appending a string to a buffer would break with
some compiler optimization settings.