Build 4 is out!

Assets by megascans.se

New builds are up and can be downloaded at:

Getting started at:
http://armory3d.org/manual/getting_started/setup.html


Time for new preview builds! Lots and lots of work went into this one. More bugs have been squashed together with all around refinements. In case of critical issues, updated builds will be pushed. Previous Build 3 is still available at itch.

  • Improved rendering of translucency. Opacity socket in Armory PBR can now take direct value, separate image texture or alpha of Base Color. Translucent surfaces can now also cast shadows (basics only for now).
    Forward renderer is now also capable of rendering translucency. While the transition to new render path builder is complete, use deferred_high, forward_high or hybrid path to enable translucency.

  • Improved rendering of soft shadows. To enable select Camera - Properties - Camera Data - Armory Render Props - Soft Shadows - On. This feature is disabled by default as the performance is not yet as good as it could be. Also, setting lamp size too high can cause noisy result.

  • Primitive level of detail module has been implemented. New lod example added. System is not very usable yet but will be improved in next builds.

  • Primitive navmesh module has been implemented. New navmesh example added. Again, just the basics are in but a good foundation for further progress.

  • New Scene 3 - Animation page has been added to the manual.

  • New Generate mesh page has been added to the manual.

  • Preliminary Render Path builder at Camera - Properties - Camera Data - Armory Render Path. Some settings still do not work so usage is not yet recommended. This system will eventually replace default imported render paths to provide more flexibility.

  • Unsupported material / compositor nodes should no longer throw errors and halt build process. Instead, warning will be displayed in console.


Onwards
Main focus of next build is finally the material system, which is the biggest culprit of issues right now.

To make things safe, two material contexts will be available. Restricted context will continue to work with Armory PBR only and will focus on being spartan and fast. Full context will aim to support majority of Cycles nodes while still being as performant as possible. Complex materials may obviously require more power.

On top of that, all around fixing of issues and usage refinements will continue. As always, looking forward to your issues / feedback / ideas and see you out there! :slight_smile:

Should be fun. Testing now.

New video ? Maybe weekend?

I’ve bought build3.
How can i geht new build?

go to the page you download build 3 there you can download build 4 (armory.itch.io)

1 Like

OOoh, nice, onward with download!

@lubos I am so behind!, I still have not even had a chance to look at build 3! You are doing an amazing job! Please consider that email I sent you. :grinning:

Default scene test, as usual its my first test on any new build. So the default blender scene with a simple cube, a lamp and a camera. Using the provided blender version (from the unpacked downloaded file). And try to run that scene failed. I’ve logged an issue on git and provided the system console error.

After deleting every armory build and re-installing the latest (unzipping really) it now works! sorry for the inconvenience, I am just an artist and sometimes stupid on certain things like this :stuck_out_tongue:

Hey, just a quick tip in case someone else finds this useful, try focusing on one specific aspect of armory (in my case I just did this for the debug console) and finding all the bugs and ways in which you can improve that one aspect and make git-hub feature requests out of it. That way, assuming it all/mostly gets taken care of by the time the next build comes out, that feature will look wonderfully polished in comparison to the rest of the engine and it won’t have to get looked at for a while thus decluttering the “things to look at and test” pile and allowing things to be easier sorted out and critiqued.