glTF VS entt

My understanding is that this is an evolution of the Autodeks Standard Surface (https://autodesk.github.io/standard-surface/), which itself is a subset set of the glTF 2.0 material with its PBR extensions (https://github.com/KhronosGroup/glTF/blob/main/extensions/RE... )

Together this means there is a lot of alignment between these models. I wouldn't be surprised to see a glTF 3.0 that adopts the OpenPBR as its main material definition, skipping the current extension complexity.

OpenPBR for material exchange combined with MaterialX for shader graph exchange combined (https://materialx.org) with OpenUSD for geometry and scene graph exchange, means together we are headed into a world where high quality 3D assets are exchangeable between content creation tools.

Search animation related topics, like skinning and weights. This is constantly debated. As for the compression it is just standard with the format, there are some old topics on it.

An open standard that is very capable (but cannot find if it can do streaming) is https://github.com/KhronosGroup/glTF

It still misses some important things in the area of shading and animation for full transfer of all qualities you find in a modern 3d creation app like Blender.

I wondered this in the past as well and I found this issue, which has a lot of discussion on it and includes some plausible possible reasons, though it seems it's not entirely clear anymore why it is like it is: https://github.com/KhronosGroup/glTF/issues/821

So the special thing about this is we didn't touch any of the PBR maps on it. At all. That was all automatic, I wrote a solving program. What I will reveal about that is the gltf spec I solved against is over here: https://github.com/KhronosGroup/glTF . We're looking at using this with some 3D scanning businesses in NYC at the moment.

https://github.com/KhronosGroup/glTF/blob/main/specification...

In the future, this can be properly done with the KHR_animation_pointer extension: https://github.com/KhronosGroup/glTF/pull/2147

I think ideally you would extend the gltf material to add control over e.g. renderOrder, colorWrite, depthWrite, then implement the extension in your gltf loader

Probably not directly, but I'd look for frameworks that work with GLTF to have proper scene and asset management.

Probably it’s some kind of Sheen. This effect gives the material a velvety fabric / fur impression, which would work well with the Tom Nook character.

EnTT is a popular alternative to flecs for C++, which has different performance/memory characteristics.

https://pastebin.com/VPypiitk This is a very small experiment i did to learn the metaprogramming features. its an ECS library using the same model as entt (https://github.com/skypjack/entt). In 200 lines or so it does the equivalent of a few thousand lines of template heavy Cpp while compiling instantly and generating good debug code.

Some walkthrough:

Line 8 declares a SparseSet type as a fairly typical template. its just a struct with arrays of type T inside. Next lines implement getters/setters for this data structure

Line 46 Base_Registry things get interesting. This is a struct that holds a bunch of SparseSet of different types, and providers getters/setters for them by type. It uses code generation to do this. The initial #insert at the start of the class injects codegen that creates structure members from the type list the struct gets on its declaration. Note also how type-lists are a native structure in the lang, no need for variadics.

Line 99 i decide to do variadic style tail templates anyway for fun. I implement a function that takes a typelist and returns the tail, and the struct is created through recursion as one would do in cpp. Getters and setters for the View struct are also implemented through recursion

Line 143 has the for expansion. This is how you overload the for loop functionality to create custom iterators.

The rest of the code is just some basic test code that runs the thing.

Since we wanted a common game simulation that would be on both the server and the client we looked into a few libraries that would fit our ECS needs. It was decided we were going to write this common part of our game in C++, but rust was considered. C++ was a familiar language for us so naturally EnTT and flecs came up right away. I had used EnTT before, writing some small demo projects, so our choice was made based on familiarity. In order to integrate with Unity we created a small C interface to communicate between our simulation code and Unity’s C#. Here’s close to what it looked like. I removed some parts for brevity sake.

Are you sure you don't want to use a C++ package manager? Libtcod is on Vcpkg and with that setup you could add the fmt library or EnTT. fmt fixes C++'s string handling and EnTT fixes everything wrong with the entities of the previous tutorials.

There's also a performance question. While we can now use Blueprint nativization to convert Blueprints to C++ the result will be a fairly naive version, fast enough for most purposes but not if you're trying to push every bit of performance. This is where you're looking at making sure you're hitting things such as using the CPU cache as well as possible for an ECS system (Look at ENTT or Flecs if you want to see what they're about and why you'd want one), or a system needing to process massive amounts of data quickly such as the Voxel Plugin.

For a modern engine you’re probably best looking at Unity’s DOTS. You may also want to check out some of the different open source ECS libraries such as flecs and EnTT are two popular ones for C++, but there’s lots of them. Largely you’ll see lots of different approaches taken, all with their own pros and cons. Not all of them will be performant (some focus more on the design benefits) while others will be optimised for certain use cases. What you should prioritise will depend on your specific needs.

You can think of DynaMix as combining one of these libraries with an ECS like entt(https://github.com/skypjack/entt)