My fascination would not end only using simulation software or games with a strong simulation focus, but the idea to produce your own software got my attention already back in the 80’s. At that time the access to decent hardware and software was rather limited and the only viable option was to use a Commodore C64 (anyone older than 35 and with some techy genes should know this little grey-brown box). I cant remember any title with a simulation context other than subLOGIC’s FS II and the only software that would allow the creation of games without coding in Assembler was Garry Kitchen’s GameMaker.
Fast forward to present time (2012): There are dozen’s of graphic, physics and game engines – both commercial and opens source – available, ready for developers to jump into the field. It would be tedious to list them up and compare features, there are some other websites doing this better (please look at devmaster.net). I like to highlight a few engines that I am following for a few years and which (imo) have some impact in the industry.
A major challenge to the simulation and rendering topic is the steep learning curve. Not only you need to excel in programming but understand the concepts of 3D rendering and physics in order to get started. Most engines today are using C++, even with wrapper for other languages available, due to the higher performance you achieve(d) with native C (++) applications compared with Java.
We need to distinguish 3 types of engines here:
- Physics engine (does nothing but simulating physical systems with rigid body, soft body and fluid dynamics, inclusive of collision handling, without any graphical output)
- 3D Rendering engine (software framework to visualize 3D content, usually on top of OpenGL or Microsoft DirectX)
- Game (Simulation) Engine (combining the 2 features above and also offering GUI’s to create content and orchestrate flow and logic)