09 Apr 2018
This update lets you control the quality of exported textures, adds some new tools and export options. Read on for more details.
Koru reduces exported textures resolution for a reason: not all the devices can display high-resolution textures even if they claim they support it. However, sometimes you need a high-quality crisp artwork and it doesn’t really matter if it may fail on some old mobile phones.
We’ve added two options to address that: the first lets you setup the maximum resolution, so all the exported artwork is resized to fit. The second option lets you provide a list of exceptions - textures that should be left intact and exported “as is”.
When the scene is opened in browser, Koru engine still checks all the textures against the current hardware and downscales them to fit the hardware requirements, so it should keep working even on weak devices. However, we strongly advice to use this feature only if you really need it.
More details are here.
See the links above and our tutorials page for more details and examples.
Facebook recently added an option to show 3D models, so we decided to support it in Koru. Now you have a fourth “Facebook” option when you click the “Export” button. Give it a try, it is funny.
Note that Facebook offers quite a limited materials, so only the simple materials will be exported properly. There is also a limit of 3MB per 3D model and Koru provides detailed breakdown of exported scenes, so you can optimize geometry and artwork to fit the limits.
See here for more details.
There are two things that make your exported scenes big and increase the loading time: artwork and scene geometry. We addressed the artwork part with texture resolution limit option, and for geometry we added a new tool that optimizes meshes by keeping them looking the same.
It is under the Tools menu and it will show you visually the optimization process. You can try it on a complex model like the built-in “Owlet” model.
Here is the list of other minor changes and improvements in this update:
There is a couple of other small changes and improvements here or there aimed to make the software more stable and reliable.
We’re going to remove the “beta” tag in 2-3 weeks if everything will be fine with this release. All the base features are done, API is good enough, so we see no reasons to keep it beta anymore.
Give it a try, report issues and let’s make it officially production-ready next month!