glTF VS MonoGame

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.

To highlight this shift, we are introducing a new website which is now fully automated with Github. The paint is still fresh, but we hope to expand it with more information about the MonoGame Foundation, like how it operates, and how to join it or contribute.

https://github.com/MonoGame/MonoGame /

Yes, it is possible, but you need to use a game framework not a game engine.

Example of a game framework: http://www.monogame.net.

Monogame, though it doesn't do much hand-holding: https://github.com/MonoGame/MonoGame

Webassembly support is spotty, though in progress AFAICT.

Used by a few 2D games like Stsrdew Valley and Celeste.

Some that I am aware of and that support at least Windows and Android are (Monogame)[https://www.monogame.net/], (Cocos2D)[https://www.cocos.com/en/cocos2d-x], (LÖVE)[https://love2d.org/]. But there are likely many more. Even more basic ones which are just another abstraction layer on top of SDL (like (Oxygine)[https://oxygine.org/]).

- https://www.monogame.net/