Josh

Interfaces that are used in 3D graphics do not have a window to return, since they were not created on any window.

The core problem of this issue is now solved and will be included in an upcoming update.
I never did get the nonuniform feature working. I am not sure if it even works, and I am not sure if it has a negative impact on performance, and I just don't care,
 

Yeah, it should work if you use CreateBufferStream to create a stream. This command does not require a buffer as an argument, and it is better not to provide one.
Then, before saving or loading call stream:Seek(0) to make sure the file position is at the beginning of the file.

I am changing it so that event listeners store a weak pointer to an extra object and automatically self-delete if an extra object is defined but gets deleted elsewhere.

Try calling camera->SetDepthPrepass(false) and don't use any lights.

Fixed, an update will be available later today.

I believe this issues is solved. Please let me know if that is not the case.

Okay, this was simply caused by the animation send state sort of getting out of sync when different worlds are used. Once I figured out what it was it was an easy fix.
I think @Dreikblack deserves a big round of applause.

The shader family needs a separate set of options for when alpha masking is active. Does this solve your problem?
{ "shaderfamily": { "root":"Shaders/PBR.fam", "static": { "float": { "opaque": { "default": { "base": { "vertex":"Foliage/PineTree/Leaves.vert.spv" }, "depthPass": { } } }, "mask": { "default": { "base": { "vertex":"Foliage/PineTree/Leaves.vert.spv" }, "depthPass": { } } } } } } }  

Fixed.

fIXED.

Here it is with a small fix. I will have an update out soon for you:
"materials": [ { "displacement": [ 0.05000000074505806, -0.02500000037252903 ], "metallic": 0.0, "pickmode": true, "roughness": 1.0, "shadow": true, "texture0": "Materials/Developer/trigger.dds" } ],  

This is what you need at the bottom of MouseMovementController::Start:
///Create a new NavAgent for the player character this->agent = CreateNavAgent(this->nav_mesh); this->agent->SetPosition(entity->GetPosition(true)); entity->SetPosition(0, 0, 0); entity->SetRotation(0, 0, 0); entity->Attach(agent); The player's position and rotation are retained as the local offset and rotation when it is attached to the navagent. This allows you to set an offset, or reverse the orientation of the player. However, as we have seen, this can be confusing and cause unintended consequences, so maybe the command should include an optional offset position and rotation instead.

Fixed

Fixed!

Yes, that is correct.  glTF file require PNG or JPEG images. DDS is supported as an extension, but to remain compatible with other loads a copy of the image is included in PNG format:
https://github.com/KhronosGroup/glTF/blob/main/extensions/2.0/Vendor/MSFT_texture_dds/README.md
One of the goals of Ultra is to make sure all your models can always be loaded back into your modeling program and edited. Models are never locked / destroyed / finalized. When your game is distributed you will probably just want to not include the PNG files.

Texture slots need to be defined in the shader family file:
{ "shaderfamily": { "textures": [ "Diffuse", "Normal", "Metal/Rough", "Displacement", "Emission", "Occlusion" ], "root":"Shaders/PBR.fam", "static": { "float": { "opaque": { "default": { "base": { }, "depthPass": { } } } } } } } I took a look at maybe inheriting the texture slots from the root file, but that would overwrite any texture slots in the derived file, and I think the current behavior is best.

Fixed.

As discussed, glTF files use embedded materials and this was the intended behavior. I have also agreed to add a feature that allows materials to be externally referenced but currently this is not a bug.

I found the error and fixed it. This was caused because I recently made a change that allowed better-defined geometry in mesh colliders, like mixing quads and triangles (or any polygons). This can prevent objects from getting caught on invisible edges on the seam between two triangles, for example.

I have made the required change to the Joint class and it will be included in the next update. The other issues were reportedly caused by circular reference in user-created components, so I will close this issue now.

I am a little bit worried this might cause problems, but I made this change and we'll see how it goes.

Fixed. (It's the sphere's collider that you are seeing.) 

Fixed for next build.

Okay, I also called SetEnvironmentVariableW and that passed the var to the child process.