Micro Blog(s) - March to December 2016

It's getting there, still more polish to go though.

 

New camera mode tests / ideas / funky things:


--- Post updated ---

--- Post updated ---

--- Post updated ---

--- Post updated ---
Ignore the black smoke, bugs ...

 

I don't usually work on visual stuff, rather just read/write lines upon lines of code.

But today is one of those days in which I need to crunch numbers, trying to get insights into how something works, with hard data rather than a vague intuitive feeling, and that's when graphs can be a great help:

First case corresponds to the pickup driving slowly, second one's driving fast, third one's performing a corkscrew jump.

 

(April Fools Post)

• Added compute-shader based censorship algorithm to resolve copyright problems with mods.
• Added drivers with simulated anatomical properties, censored to maintain pg-rating.

 

Just thought I'd show you guys the world machine doc I use to add the changes I make in blender (roads) to utah. To help iterate faster I've made it an almost automatic process inside world machine, the entire map pipeline is as follows:

• Design
• Build in world machine > exports height, material masks and overlay texture
• Import the map into Blender, add the roads using splines and some hand modeled areas > export height
• Using development snapshot of blender (16bit images) import the terrain and road heightmaps and merge both > export
• 2nd world machine document automatically loads up the updated height map, road material masks, original overlay texture and then in one automatic operation it retextures the entire map with the new information (roads and manual changes), creates a curvature based depth map, edits each of the 8 material masks to include the roads and finally exports all of the files back out again
• Import the lot back into BeamNG.drive

That makes it sound ... about as complicated as it is Here's a pic of the 2nd world machine doc that joins my changes with the original map:

 

(April Fools Post)

Latest improvements of our physics engine:

 

(April Fools Post)

Upgraded security cell rigidness to modern ETK standards

Video - Click to Play - Direct Link

Video - Click to Play - Direct Link

 

Just adding a bit of detail to the old Utah rocks.

 

We are working hard to improve the performance and quality of our render engine. A little part will be released on next update.

Added a reversed depth buffer for fix the flickering issues in levels.

 

some more issues for today ...
--- Post updated ---
We had to do some memory optimizations, worked out well, 7 GB > 2 GB

 

Working on camera things on a Sat morning at 6 am
--- Post updated ---
Some concept artwork from Lisa

 

Working on improved UI units ...

 

coffee pic

 

Some bits of the new camera mode (called 'Relative Camera').

 

@LuisAntonRebollo has been implementing a better antialiasing solution. Results speak for themselves


(click to see the full details)


(click to see the full details)

FXAA tends to blur not only the aliasing, but also textures (very noticable in the asphalt textures).
SMAA doesn't do that, keeping that crisp aspect ingame while removing the aliasing from the edges.
Performance hit is very similar as FXAA (You won't even notice )

 

Work on the backend: The crash reporting tool now actually shows the problems instead of "find yourself and have fun" method with >1000 files :|

 

Testing out new shapes for the navigation screen...


And other vehicles how up now

 

Worked on the editor a bit:

1) fixed smoothing finally, it works as intended now:


2) The sidebars will be 50 pixels wider and should fill the height of the screen on startup.


3) Implemented two new tools: Align with terrain and substract from terrain

 

#coffeepic @ 30 deg Celsius