aldo85

After a pretty major code rewrite, ELS-DN is now beginning to take shape and I think it is at a point of functionality where I can begin to show some of the stuff it can do.  As promised a few weeks ago, I do plan on getting some video footage out, although that will require some of the front-end (controls, displays, etc.) to be complete which might take a little while.
 
As posted in the gallery a few hours ago, this is the latest screenshot of the code in action:
 


 
 
What ELS-DN can currently do:
Load vehicle configuration files Load pattern configuration files Process user-defined patterns Support up to 50 user-defined lights per car Support AI vehicles Simulate rotating beacon (almost fully) and LED lights (partially) Dynamically and automatically create environmental lights Flash the headlights and taillights individually (this has some problems which LMS is working on) Display an exact replica of the ELS display panel (uses the same exact code - Lt.Caine has been helping with this)  
Vehicle configuration files:
 
Probably one of the best bits about ELS-DN is the vehicle configuration files.  They work by creating a folder in scripts/ELSDN called Vehicles, and then creating a new folder for each vehicle inside there.  Inside each vehicle folder is a configuration file and a patterns folder which contains three separate folders for primary, secondary and warning patterns (those of you who've used ELS will be familiar with these).
 
 
The vehicle configuration file stores everything about the vehicle itself, including up to 50 custom light definitions (meaning you can create some really hideous Christmas trees), the model which the config file is assigned to and the default patterns for it too.
 
Vehicle configuration files are designed to be easily shared, all you have to do is plop the vehicle's folder into your Vehicles folder and it's ready to go.
 
 
Pattern configuration files:
 
The pattern configuration files allow you to make your own fully customisable patterns.  A pattern is either primary, secondary or warning in type and is assigned to a specific vehicle.  This means that every vehicle has its own patterns folder with its own patterns.
 
 
Next steps:
 
Unfortunately there's a lot of work that needs to be done on the user interface, in particular the controls and adding stuff like the ability to browse through patterns, etc.  On top of that, I need to complete support for different light types (LEDs and bulbs) and then think about siren controls, which may or may not make it into the first version.  Hopefully, though, I should have some sort of video to show fairly shortly.