Josh

Sun properties have been moved into a new dialog, available with the Edit > World Settings menu.

What version of the editor are you using? The version number appears in the title bar.

Please upload your project so that we can try it out.

It will be binary, although I have not added it yet.

The physics properties in Blender have some rigid body shapes that map closely to Newton. Might be interesting to you:

I just ran this in the console with no errors:

0.9.6 First build of 0.9.6 available on beta branch, adds saving to the asset editor for the new version of our model format. Embedded materials are saved as external files. They still get displayed the same way in the asset editor as embedded materials, and when you save the model it resaves the material files, so any changes you made will go into those files. This works out nicely.

Here is my loading code. I think this is final. A new section was added for node attachments to bones ("ATCH"): G3DModelLoader.cpp

I am not sure. Do you know how to set breakpoints in VSCode? That might allow you to view the global vars.

I think it might be a good idea to render point and spot lights in this manner using a sphere or cone mesh with a special shader. You would need the material set to use blending, and the mesh would have to reference the light it belongs to. That would save you from stepping through a lot of empty space.

Makes sense to me. The local variable goes out of scope when the function finishes, and the variable is collected and the value deleted. In Ultra, we can actually make use the Lua's garbage collection

Changes: Animations block will be preceded with the tag "ASET" "COLL" tag renamed to "PHYS" Vertex stride must be 88

Here is some code if you want to make a Lua module: https://github.com/UltraEngine/Lua/tree/main/Modules The simpler way is to create a C API for the lib and interface with that, maybe using the Ultra buffer class to construct a data structure in memory.

I am thinking about a new sample action-oriented game. What player view should it use?

You have an old build in which I make a mistake and compile it using a main file I was testing. You must sync your project to get the updated EXEs: https://www.ultraengine.com/learn/projectmanager

If you are using the debug build, it should not "hang". It should show an error and open the code file on the line where the error occurs.

The error is on IntersectsPoint. I am testing it in the editor console. Ah, I see. There is an extra padding argument you must supply: aabb:IntersectsPoint(Vec3(0), 0) I will add an overload so this is not required.

I am happy to say the #1 issue you voted on is now resolved in the just-released version 0.9.5, which works great with AMD cards.

Version 0.9.5 is now live on the default / stable branch, on Steam and on our site.

Here is an updated version of the textures. texture_templates2.zip

The update that fixes this function's declaration is out now.

Bug fixes Camera::SetMSAA renamed to SetMsaa Camera::SetSSR renamed to SetSsr

To install this, extract the Zip file contents to Blender/4.1/scripts/addons, then in Blender select the Edit > Preferences > Addons menu, search for "MDL" to find this plugin, and check the box to enable it. @SpiderPig Since our PBR materials system is derived from glTF, this page might be useful to you: https://docs.blender.org/manual/en/2.80/addons/io_scene_gltf2.html

What I am saying is I think this problem will automatically go away if I switch to GPU culling.