Josh

it won’t change once it is assigned but it may not be assigned right away.

1.0.3 Added Entity::GetIndex(). This should ONLY be called from the rendering thread (in a RENDER or TRANSFER hook).

1.0.3 Just noticed "Tools > Build GLobal Illumination" was missing in the editor menu. This is rather important.

1.0.3 Shader family files now use extension .fam. Material files now store shader family file paths, relative to the material or to the project. Material editor is not updated yet to support this correctly. Post-processing effect files now use extension .fx and are moved to the Shaders directory. Material textures are now stored with paths relative to the material file (prefixed with ./) or relative to the project.

In Leadwerks, use tolua++: https://github.com/LuaDist/toluapp Ultra uses sol3, which is much easier and better: https://github.com/ThePhD/sol2

This should do it: "backfaceculling": false

1.0.3 Added screen-space reflection integrated into the basic lighting. Call Camera::SetSSR(true) or enable it in the editor viewport options. Removed SSR post-processing effect. Changed syntax of CreateMeshCollider. Design of push constants block in GLSL totally revised.

Yeah, and then there is the issue of ordering of multiple objects that both have depth testing disabled...the second camera is more versatile anyways.

It's not enough just to disable depth testing. You have to render that object last, which means it needs to appear after all transparent objects. But then transparency has two render paths, once for conventional transparency, another for transparency with refraction. So I just haven't bothered trying to work that all out, and I'm not sure it's even worthwhile when a second camera works perfectly.

I've had some trouble disabling depth testing. Not sure what is going on. I ended up using a second camera and rendering that on top of the scene, and had much better results with this.

This is fixed in today's update. CreateMeshCollider arguments have changed. You can either input a triangle or quad mesh, or a vector-of-vectors of Vec3s. The first is the simple usage, the second one handles faces with any number of edges, and different numbers of edges for each face.

Did you open this in the model viewer? Maybe there is an extra node in the hierarchy?

I still don't know what your distance from the origin is, but it does look like floating point imprecision.

You might be able to store your data in a texture, and then use the vertex ID as the lookup to get the extra data you want to retrieve.

They get converted into a quaternion so they can be stored in four bytes. I got the idea from Crytek.

Why not just call UpdateTangents to calculate them?

Vertex colors only work with non-skinned meshes because they are stored in the bone indices slot (or bone weights, I don't remember which). They only use one byte each and store values from 0 to 255.

The engine commands won't run any faster in C++ than in Lua. Physics and graphics will run at the same speed, it's just your own game code that executes faster.

That's what a pre-order is! That email was a mistake, sorry about that.

Thank you. Development is going fast but if I hit some snags I will take whatever time is needed to get it right.

Keys will be sent out closer to release, but I believe you can enter them pre-release and it will just unlock when the app is published.

I would love to do that someday. I like physical products.

Your collection isn't really complete until you have multiple copies of each one, in my opinion.