Josh

entity->kids is a read-only STL vector containing all the children.

I've updated the changes. Please let me know if anything else comes up, otherwise I will mark this as solved for now.

Your example above works now with the current engine build I just uploaded.

I get the same error when I run your code. Testing now. The saved game does open in the editor, which is kind of cool

Fixed thumbnail generation in editor.

If the entity creates a component, then it just needs to delete and re-create it in the Load method, or save the important properties into the saved JSON data. If a component references another entity that another component owns, it can call GetUuid() to retrieve that entity's ID and store it in the JSON data.

Fixed, I think. Thumbnails now reload dynamically when a file changes.

Yes. The idea is to load the entity states instead of having to re-create the entire scene. This can cause some restrictions on your code. Entities should not be created in code unless it is a result of some component code, and that component is responsible for saving and reloading any auxillary entity data. But if you follow the rules you get automatic quick/load states.

Yes, but you won't receive it until it is released.

It searches for each entity by UUID and reloads its state. It's okay for there to be different entities or entities missing.

The pre-order that is available on this site is just a pre-order. It means you will get your product once it is released. The non-Steam version will be released before the Steam version.

I agree with these recommendations. If the range of allowed values is 0 / 1 or -1 / 1 then it makes sense to move in small increments. However, for the other values it does not make sense to me, and moving in really small increments seems like it would be annoying. The spinner supports any double float values you type in, so even if the spinner increments are 1.0, you can still type in exact small numbers like 0.125.

It looks like ffmpeg is probably the easiest way to achieve this. Exact audio: https://stackoverflow.com/questions/9913032/how-can-i-extract-audio-from-video-with-ffmpeg Extract frames: https://stackoverflow.com/questions/10957412/fastest-way-to-extract-frames-using-ffmpeg I think that's pretty much it. All that's needed is to wrap it up in some nice easy to use commands.

The design I've been using for both maps and colliders is a JSON string, and then if there is any binary data, this is followed by a null character, and then the bin data. If there is no binary data then the file is just a normal JSON file. This is very simple, and I figure some tool or plugin will arise that allows editing of the JSON text info without destroying the binary data. If the size of the JSON string changes, that's okay because all the offsets that point to the binary data are counted from the start of the data. The Map:Reload() method is changed to only use one stream, and the example below is now using a file: https://www.ultraengine.com/learn/Map_Reload?lang=cpp The update is available now and I have tested it.

Looks like the uploads got cut off. I reuploaded them now and tested it.

Not yet but I am open to adding this in the future.

As for the save-to-file issue, I need to decide what I am trying to do here. My first implementation of the Ultra map format used an accompanying .bin file like glTF does, but after seeing how often people send glTF files and forget the .bin file I decided that was a bad idea.

I can confirm the way components are being saved in the built-in save routine was incorrect. They are not supposed to be stored in the "extras" field...

Preview app process can hang. Thumbnails not generating. Thumbnails not being recreated when file is newer than thumbnail file.

Editor seems to be loading Leadwerks maps with correct texcoords now. Issue is resolved I think.

Updated Lua template executables.

Updated editor and C++ library with changed brush texture mapping calculations, other recent changes.

Just call entity:Release(): https://www.leadwerks.com/learn?page=API-Reference_Object_Release

I changed the way brush texture scaling works. When using the programming API the value set in Face::SetTextureMappingScale is now in units of texels per meter, with a default value of 400. The brush texture mapping scale in the program options does two things: Defines the default scale a new brush's faces uses when it is created. Changing this setting does not change the texture mapping of existing brushes. Provides a conversion factor that is used in the face properties interface, because values like 1.0 and 2.0 are more intuitive than 400 and 800. The engine library has not been updated with this change yet. Some changes will still be needed to retain correct texcoords with Leadwerks maps. All existing Ultra maps will have wrong texture coordinates, but you can reset them by selecting all faces and setting their mapping scale to 1,1. The align buttons are probably wrong now. seems these are fine This resolves the problem of using two scale values and puts everything on the right track, while still allowing a user-defined default texel density.

I did some additional work to fix the increments on some spinners. Let me know if you spot anything else that is awkward.