Josh

Fixed Camera::SetUniform texture overload. Added Camera::SetUniform material overload. Added Camera::SetUniform entity overload.

"No source file found" just means the original image file the file was converted from does not exist, or might not be included. Leadwerks does not save image files, it just converts images into the custom texture format. Ultra can actually load Leadwerks .tex files and save in different image formats.

0.9.6 In this build the terrain creation works more like Leadwerks, where it is created by first selecting the terrain tool. You don't have to worry about selecting the terrain to edit it, it just works. Try it and let me know what you think. The way it is stored in the map file has not changed. LOD for orthographic cameras is fixed.

Leadwerks does not work with non-western characters in the project path. You must select a folder with only "normal" characters in the path. (Ultra does support unicode).

I would actually like do make a modern version of our old tropical island from LW2

What matters is, what is best for us?

This change would allow us to get vegetation working sooner, with fewer bugs and ongoing problems.

0.9.6 Added right-click on file "Convert File to XXX..." menu item for all converters in asset browser. Added right-click on folder "Batch Conversion" menu item in asset browser.

Yeah, I am actually looking into some stuff like that now...

Doing that would require two things. With really big worlds, you need a terrain system that recursively subdivides, because normal terrain LOD isn't big enough. With a normal terrain LOD system where the terrain is divided into patches, eventually you can zoom out so far that each patch is just one pixel big. So you need a different way of handling that. You also need a way to warp the terrain to a sphere, and have it affect physics, raycasting, culling, as well as the rendering. I plan on doing stuff like this in the future, but not with our standard terrain system.

Yeah, but that will require an entirely separate terrain system, and it's not something important to worry about right now.

How do terrains make a sphere anyways?

I am considering moving terrain back to work the way it did in Leadwerks, where it was always centered around the origin and did not respond to rotation or positioning. This would simplify vegetation system quite a lot because I can handle all coordinates in world space. Otherwise, you have to do a lot of transformations and it is hard to get things to line up correctly. I think it also makes a better experience in the editor. Movable terrains can be prone to accidental movements, and having them selectable degrades the performance because the outline effect is quite expensive since it requires rendering the object twice.

Can you get the local rotation as a quaternion? You might look at the old Leadwerks exporter and see what the author did there.

Temporarily removed drag to select area, since it was interfering with some mouse tools. Added terrain texture size field in creation parameters box