The argument --systemwide-directory has been added, for systemwide installations, to choose an installation directory other than the default /opt. Use -h or --help to get the proper syntax.
Updated some email addresses too.
You may have noticed already that, sometimes, entity count jumps quite a bit, then drops quickly back down to its previous levels. This is often due to explosions. They tend to generate a number of entities that are added to the universe at the moment of the explosion and are removed shortly after, once their life has expired. This happens every time as part of the simulation, regardless of where the explosion takes place. Very often, the amount of entities being generated results in momentary stutter.
This change tries to minimize the side effects of explosions happening. We now generate all those extra entities only if the object that exploded was visible in the first place. Regardless of visibility, the explosion is rendered normally if it has happened within scanner range (so e.g. an escape pod exploding will always have a visible explosion, although it stops being visible past 5000m or so).
It works like the %J### one, but it takes two triplets of numbers rather than one, namely the system ID followed by the galaxy ID. This way we can refer to planet names in galaxies other than where the player is. %J### remains for compatibility reasons. Updated Constrictor Hunt mission strings to eliminate hard coded references to Xeer in the mission texts. (#290)
Added resource files and enabled manifest embedding on Windows. This allows us to handle high-DPI and newer Windows versions support in one go (and is the recommended by Microsoft way for handling these things), can provide a way for potential future manifest settings to be added, simplifies existing code and adds an icon to the Oolite Windows executable.
* Scripting: Makes pitch/roll/yaw for playerShip writable
* Fixes bounds checking issue when passing negative deltas
The increase/decrease_flight_pitch/roll/yaw methods in ShipEntity assume that deltas are always positive. The increase_ functions only check upper bounds, decrease_ functions only check lower bounds.
Now checking both upper and lower bounds in all of them, so they cope well with negative deltas.
