FreeGameDev Planet - Games

Also check out the development planet.

February 25, 2015

Valyria Tear

Code Monkey!

Hey there, :D

Just some news from the Episode 1.1 technical refinement release.

First of all, I've finished migrating and fixing the current game scripts following the new scripting API.
Thanks a lot to authenticate and SuiteCake for providing code cleanups and feed-back along the way. \O/

authenticate also fixed the minimap rendering with intel drivers and I owe him a beer for that.

I've also streamlined a bit the map code to follow the standard coordinate system used by the rest of the engine, in preparation for future different zoom ratio support. ;)

I'll be at reorganizing the game data now that I have enough of it to be sure of how I do it. ;)
And then, I'll have a go at porting the HoA features from the map editor so that starting to work on the new 1.1 content will be much easier.

Stay tuned!

by Yohann Ferreira ( at February 25, 2015 08:45 AM

February 24, 2015

FAR Colony

Alpha 10-iter#02: Dev Update [ the current todolist ]

I only display what is already done (x) and what I actually working on (o):

Colony Simulation Model (CSM):
   (o) all existing CSM events (Colony Established, Dissident Colony, Governmental Destabilization, Health-Education Relation, Social Disorder, Unrest and Uprising) were been revised and completed.
   (o) all the events already implemented have their own unit. Additionally their code is audited and corrected.
   (x) event: Health-Instruction Relation: the modifiers are changed for a global ratios that  modify instruction as a whole.
   (o) the entire code that process the events is reworked and optimized.
   (o) completion of the event cancellation code which lacked of many data transfer.
   (o) a now useless cancellation method is removed.
   (o) the events have now custom statuses, those indicate more clearly than a cryptic integer value in which mode the event is.

   (x) new entries:
         (x) csm: cohesion data.
         (x) faction: faction template.
         (x) faction: Magellan Unity.
         (x) time flow system: real time and turn-based time flow (main description).

   (o) full code audit (refactoring, code cleanup, optimizations, bug fixing like the one which concern the decimal setting) of the following units:
         (o) farc_csm_core.
         (o) farc_csm_events.
Socio-Political Matrix:
   (x) funky calculations of the SPM items modifiers is now fixed.

Work, work, work.

Just notice that I also work on the design document to cleanup some mess I made by building the CSM.

Stay tuned.

by Jeff B ( at February 24, 2015 10:39 PM

February 21, 2015


Simulating the ever-changing scenery

The secrets of the environment settings

If you look at aerial imagery of a region every day for a year, it never changes. Yet if you would fly over the same region in reality every day, it would almost never look the same twice. In reality, nature is a dynamically changing environment, and what you see from a cockpit reflects this.

Some of these changes have to do with weather – on a cloudy day, the light is different from bright sun, the shadows are muted, the amount of haze may change so that faraway terrain looks fainter… and these are readily captured by the weather simulation.

Yet there are more subtle effects. For instance, snow may linger on the ground even on a sunny day with temperatures above freezing if the original layer was thick enough. Snow may fall, but not remain on the ground if the ground is warm enough. In essence, whether you see snow or not depends not so much on how the weather is now, but how it has been the last days, weeks or even months.

Such changes to the scenery in FG are taken care of by the environment settings which control how the terrain is shown. You can find the menu as an entry under Environment.

Currently, the full range of environment effects is only implemented for the Atmospheric Light Scattering (ALS) framework starting from medium quality settings, however the snow effect is available for all rendering frameworks.

Let’s explore some of the things this can do:

Seasonal changes

This is how the default terrain is shown without any environment effects – a summer day in Grenoble:

Moving the season slider somewhat to the right brings autumn coloring into the scene – deciduous tree patches change colors to orange-red, fields and grass appear yellowish:

Changing to a yet later season causes deciduous trees to shed leaves and changes most of the vegetation to a dull brown:

Modifying the snow line and thickness allows to add a sprinkle of snow to the valleys, simulating the first snowfall of late fall:

Finally, adding more snow changes the whole scene into deep winter:

In coastal regions, the appearance of water can also be changed. Here is the coast of Norway near Bergen in summer:

Using the snow and ice sliders allows to simulate winter with lots of drift ice in the sea:

Using a combination of the season and snow settings, it is hence possible to simulate a lot of the seasonal changes during the year. But that’s not all.

Dust and greenery

Have you noticed how colors fade during a long spell of dry weather, to be restored only when rain washes the dust away? Or how a desert might look green for a few weeks after rainfall, to change to its usual dusty appearance later? The environment system also provides those options – let us take a look at the Sierra Nevada. This is how the chain appears from China Lake (with a good measure of snow added to the peaks):

Using the dust slider makes all the colors fade and lets the scene appear dry:

Using the vegetation slider instead gives a fresh green touch to the desert as if after a rainfall:

Changes may be subtle and affect more than just color. Consider this close-up of a dry runway:

The environment settings allow to make it wet (this will happen automatically when the weather predicts rain, but terrain can be wet without current rainfall). This creates puddles and alters the whole reflectivity of the surface – look at how the light changes:

Finally, adding snow covers the runway partially in snowdrifts:

Why can’t this happen automatically?

The environment subsystem just renders as it is told, it is hence easy to misuse it – think snowfall and ice cover on Caribbean islands for instance. Sometimes, the question gets asked why this is implemented that way, and why parameters aren’t just set automatically.

The answer to that is – based on what should they be set? Flightgear does not include a global climate simulation as would be needed to determine how likely it was that there was e.g. snowfall during the last days or weeks, or that there was a dry summer and hence everything should look dusty.

The idea is that the user can adjust these settings, either based on how the scene currently looks at a location, or based on what the user wants to experience (it’s a simulation after all – there’s nothing wrong with simulating a tropical day in Hawaii on a bleak winter day).

If used with some care, the environment settings offer a chance to experience the same scenery in a hundred different ways, each time subtly different.

If misused, the settings deliver weird to crazy results of course.

For the sake of completeness, for low-performance systems which are unable to run shader effects, using the commandline option –season=winter offers at least the choice between the default summer textures and a snow-covered set of textures, although no control over snowline and thickness.

by Thorsten R. at February 21, 2015 12:08 PM

February 20, 2015

Rigs of Rods

[Image heavy] Some pictures. :3

I was just bored, decided to post few little screenshots of what's upcoming with RoR 0.4.5 (Aka NextStable)
The change log is being updated but it is visible here: Changelog

Something new here, the Main menu!

The rig editor:
(loading a vehicle)

(vehicle loaded)

(few options)

Ingame settings:

(ingame key mapping)

Game informations:

Tuned selector:


Pause menu: (And possibility to change maps/go back to menu without exiting the game)

Bonus picture:

by max98 at February 20, 2015 10:57 PM


0.6.0-beta1 Hotfix for Windows

We’ve just released updated Windows installers to remedy save corruption and a related crash.

Simply download and re-run the installer. It’s fine to run over top of the existing install, and you do not need to re-download ndata.

Windows (32-bit)
Windows (64-bit)

The issue affects all versions of Windows, as long as save compression is enabled (which is the default). You may also want to delete all backup saves, located in %APPDATA\naev\saves\ with the extension .ns.backup, though this isn’t required.

by Deiz at February 20, 2015 08:18 PM