It has been over a week of the first ever Armory testing and the amount of feedback is staggering. Tons and tons of bugs were reported - thank you! Seeing all the different Armory use-cases that one would never think of is fantastic.
Build 2 is out to address some of the top issues. And maybe bring a new bug or two, as it usually goes. Everything is still broken but at times it can already get super fun to just mess around.
The download is available on itch as before. I will keep sending the keys during the weekend to everyone who supported the project (if nothing explodes).
Store page to purchase Armory is now also public. However, get it only if you wish to support the project development. No production ready yet!
All texture formats that Blender can read are now supported. Armory will do conversion internally.
Fixed textures on Windows.
Fixed environment maps on Windows and Linux.
Fixed Python error when loading scenes.
Scene with no lamps now renders.
Fixed shader error when setting roughness strength of Armory PBR.
Fixed Edit Traits button on Windows and Linux.
Fixed instanced rendering.
Migrated manual to GitBook, no more tiny images.
Play in Viewport no longer freezes on Linux. Still not recommended to use it, there are issues embedding a player with X11. No statically linked libraries or GPU Cycles yet.
Meshes will properly display new modifiers. If modifier was already in place and properties were changed, it may be still needed to hit āInvalidate Cacheā.
For point lamps use cubemaps for shaows. Thatās what other engines like UE4, Cryengine V etc. do. Or you could also try adding raytrace shadows. Thatād add a big improvement, but would be more performance expensive(especially for softened shadows). Of course, you will know it better than me so all I can do is suggest
aah, that is the sound of progress. Not a man thinking for a second and then writing something done but rather one bashing his head into the desk yelling, āWhy wonāt this work!ā until it finally does.
Now we wait for build 3. Though, I do wish that my bug fixes get through in this one. I really havenāt been able to do the full blown testing yet and this is rather disappointing for me. Iāll just have to settle for bug fixes until then.
Please, wait for the final version, getting people disappointed is something I want to prevent. Do not waste your time on preview builds if you have expectations.
The preview is aimed only to aid in testing/support, I can not stress enough this is not a production ready software. All this is about is gathering a small pack of people who want to lend a hand in development.
I knew this already. This is the kind of program that the term ābleeding edgeā was meant for. Iām using the term disappointment loosely. You are doing just fine and I already completely understood that these builds were just for testing. Iām ādisappointedā that I canāt get in further to test the features beyond the installation. I was already heavily warned that this would be the case so it isnāt like I hadnāt already agreed to this. Just keep on chugging along and Iāll do the same to submit bug reports.
Basically there is nothing to build, apart from Blender if one needs the built-in player. The SDK servers as a package with everything included and prepared to work, and also as a way to fund the project while it gains maturity and more people willing to support it.
There is a page on how to jump to latest versions, but that is likely to be even less stable than currently fragile preview builds. Let me know in case of issues.
