Jump to content

Turbo Game Engine (Leadwerks 5) beta updated



A new beta update is available for subscribers. What's new?

Point and spot lights are now supported in the new Vulkan renderer, with either PBR or Blinn-Phong lighting. Lighting is controlled by the shader in the material file. There are two main shaders you can use, "Shaders/PBR.spv" and "Shaders/Blinn-Phong.spv". See below for more details.


JSON Materials

Materials can now be loaded from JSON files. I am currently using the .json file extension instead of "mat", "mtl", or something else. If you load a scene and a JSON file is available with the same name as a material in that scene, the material will be loaded from a JSON file instead of the Leadwerks 4 .mat files. For example, you can create a JSON file named "brick01.json", place it in the same folder as "brick01.mat" and the new engine will load the JSON material if the brick material is used in a scene. However, it is not necessary to do this as the engine can also load Leadwerks 4 material files.

A Turbo JSON material file looks like this. The string tokens are more or less locked in now and it is safe to start using them.

	"turboMaterialDef": {
		"color": [ 1, 1, 1, 1 ],
		"emission": [ 0, 0, 0 ],
		"metallic": 0,
		"roughness": 0.6,
		"doubleSided": false,
		"blend": false,
		"albedoMap": "./concrete_clean_diff.tex",
		"normalMap": "./concrete_clean_dot3.tex",
		"metallicRoughnessMap": "",
		"emissionMap": "",
		"baseShader": "Shaders/PBR.spv",
		"shadowShader": "Shaders/Shadow.spv",
		"depthShader": "Shaders/DepthPass.spv"

You can also indicate a shader for the new engine to use in an old Leadwerks 4 material file by adding a text line like this to the .mat file:


You do not need to specify a shader unless you are using a custom shader. JSON material files, by default, will use the PBR shader. Leadwerks 4 material files, by default, will use the Blinn-Phong shader.

BC5 / BC7 Texture Compression
A ton of new compression formats have been added, including the BC7 and BC5 formats, which provide better quality than DXT compression. Visual Studio 2019 actually has some good built-in DDS tools, although the BC7 compressor Is very slow. A sample material is provided using DDS textures (see "Materials/Rough-rockface1.json").

Lua Commands
A set of simple global Lua commands has been added.

template<typename T>
void LuaSetGlobal(const std::string& name, T var)

template<typename T>
void LuaPushObject(const std::string& name, T var)

template<typename T>
T LuaToObject(const int index = -1)

int LuaCollectGarbage(const int what = LUA_GCCOLLECT, const int data = 0);
void LuaPushString(const std::string& s);
void LuaPushNumber(const double n);
void LuaPushBoolean(const bool b);
void LuaPushNil();
void LuaPushValue(const int index = -1);
bool LuaIsTable(const int index = -1);
bool LuaIsNumber(const int index = -1);
bool LuaIsString(const int index = -1);
bool LuaIsBoolean(const int index = -1);
bool LuaIsObject(const int index = -1);
bool LuaIsNil(const int index = -1);
bool LuaIsFunction(const int index = -1);
bool LuaToBoolean(const int index = -1);
std::string LuaToString(const int index = -1);
double LuaToNumber(const int index = -1);
int LuaType(const int index = -1);
int LuaGetField(const std::string& name, const int index = -1);
int LuaGetTable(const std::string& name, const int index = -1);
int LuaGetGlobal(const std::string& name);
void LuaSetField(const std::string& name, const int index = -1);
void LuaSetTable(const int index = -1);
void LuaPop(const int levels = 1);
void LuaRemove(const int index = -1);
void LuaSetStackSize(const int sz);
int LuaGetStackSize();
void LuaNewTable();

This makes our code simpler and more readable:

#include "Turbo.h"

using namespace Turbo;

	//Create a window
	auto window = CreateWindow("MyGame", 0, 0, 1280, 720);
	//Create a rendering context
	auto context = CreateContext(window);

	//Set some variables in the script environment
	LuaSetGlobal("mainwindow", window);
	LuaSetGlobal("maincontext", context);

	//Create the world
	auto world = CreateWorld();

	//Load a scene
	auto scene = LoadScene(world, "Maps/start.map");

	//Show off a PBR material
	auto sphere = CreateSphere(world);
	auto mtl = LoadMaterial("Materials/Rough-rockface1.json");
	sphere->Move(0, 1, 0);

	while (window->KeyHit(KEY_ESCAPE) == false and window->Closed() == false)
	return 0;

You can gain access to the beta and support development by subscribing for just $5.

  • Like 5


Recommended Comments

Join the conversation


Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.


×   Your previous content has been restored.   Clear editor


  • Blog Entries

    • By Josh in Josh's Dev Blog 5
      You might have seen this graphic comparing the size of the world in different games. I've played Fuel, and never reached the end of the world in that game. You can drive for a very long time on those roads.

      We want to use the new engine for realistic simulations of air and ground movements. At normal cruising altitude of a commercial airliner, the pilot has a view range of about 400 kilometers. The image below shows that area (800 x 800 km). You can see the areas of the biggest games ever fit neatly into the corner of just our visible area.

      The gray space above is not the total world size, it is just the area you can see at once from high altitude. The total world size is about 50 times bigger.
      This is what I am working on now.
    • By Josh in Josh's Dev Blog 26
      Gamers have always been fascinated with the idea of endless areas to roam.  It seems we are always artificially constrained within a small area to play in, and the possibility of an entire world outside those bounds is tantalizing.  The game FUEL captured this idea by presenting the player with an enormous world that took hours to drive across:
      In the past, I always implemented terrain with one big heightmap texture, which had a fixed size like 1024x1024, 2048x2048, etc.  However, our vegetation system, featured in the book Game Engine Gems 3, required a different approach.  There was far too many instances of grass, trees, and rocks to store them all in memory, and I wanted to do something really radical.  The solution was to create an algorithm that could instantly calculate all the vegetation instances in a given area.  The algorithm would always produce the same result, but the actual data would never be saved, it was just retrieved in the area where you needed it, when you needed it.  So with a few modifications, our vegetation system is already set up to generate infinite instances far into the distance.

      However, terrain is problematic.  Just because an area is too far away to see doesn't mean it should stop existing.  If we don't store the terrain in memory then how do we prevent far away objects from falling into the ground?  I don't like the idea of disabling far away physics because it makes things very complex for the end user.  There are definitely some tricks we can add like not updating far away AI agents, but I want everything to just work by default, to the best of my ability.
      It was during the development of the vegetation system that I realized the MISSING PIECE to this puzzle.  The secret is in the way collision works with vegetation.  When any object moves all the collidable vegetation instances around it are retrieved and collision is performed on this fetched data.  We can do the exact same thing with terrain   Imagine a log rolling across the terrain.  We could use an algorithm to generate all the triangles it potentially could collide with, like in the image below.

      You can probably imagine how it would be easy to lay out an infinite grid of flat squares around the player, wherever he is standing in the world.

      What if we only save heightmap data for the squares the user modifies in the editor?  They can't possibly modify the entire universe, so let's just save their changes and make the default terrain flat.  It won't be very interesting, but it will work, right?
      What if instead of being flat by default, there was a function we had that would procedurally calculate the terrain height at any point?  The input would be the XZ position in the world and the output would be a heightmap value.

      If we used this, then we would have an entire procedurally generated terrain combined with parts that the developer modifies by hand with the terrain tools.  Only the hand-modified parts would have to be saved to a series of files that could be named "mapname_x_x.patch", i.e. "magickingdom_54_72.patch".  These patches could be loaded from disk as needed, and deleted from memory when no longer in use.
      The real magic would be in developing an algorithm that could quickly generate a height value given an XZ position.  A random seed could be introduced to allow us to create an endless variety of procedural landscapes to explore.  Perhaps a large brush could even be used to assign characteristics to an entire region like "mountainy", "plains", etc.
      The possibilities of what we can do in Leadwerks Engine 5 are intriguing.  Granted I don't have all the answers right now, but implementing a system like this would be a major step forward that unlocks an enormous world to explore.  What do you think?

    • By Haydenmango in Snowboarding Development Blog 6
      So I've been researching snowboarding lately to get an idea of what animations and mechanics I need to create for my game.  I have learned lots of interesting things since I've only seen snow once or twice in my entire life and have never even tried snowboarding or any other board sports (skateboarding, surfing, etc.) for that matter.
      Snowboarding tricks are quite interesting as they are mostly derived from skateboarding.  Snowboarding tricks pay homage to their equivalent skating tricks by sharing many concepts and names.  For example basic grabs in snowboarding share the same concepts and names as skateboarding: indy, mute, method, stalefish, nosegrab, and tailgrab.  Something interesting to note is in snowboarding you can grab Tindy or Tailfish but this is considered poor form since these grabs can't be done on a skateboard (due to the board not being attached to the skaters feet) and grabbing these areas is generally something a novice snowboarder does when failing or "half-assing" a normal grab.  Check out this diagram to see how grabs work -
      So, after reading lots of text descriptions for tricks I was still confused by what all these terms meant and how they were actually applied.  So my next step was to look up these tricks actually being done and I found some really cool videos showing off how to do various tricks.  This video in particular is the best reference material I've found as it contains nearly every trick back to back with labeled names and some tweaks -
      Sadly my rigged model doesn't handle leg animations with the snowboard that well so I can't animate as many tricks as I want to.  Regardless there will still be around 15 total grab/air tricks in the game.  Now it's time for me to stop procrastinating and start animating!  
  • Create New...