urho3d VS magnum

Urho3D, an open source C++ game engine.

I believe Urho3d supports MacOS (see 'about' page on the legacy website).

Urho3D

If you're literally clueless your best bet is to first start learning with an existing clean-ish engine like Urho3D implementing whatever feature/screwing-around or start with a framework like nVidia's Donut that gets you your window and basic rendering in place.

I would recommend tracking through the gist of Urho3D's batch/batchqueue stuff as it's a reasonable setup that is very intelligible (if you speak C++), it's not the greatest thing on the planet but you should be able to roughly grok it in an afternoon. Doing draw batch-pumps greatly streamlines the final drawing code.

You could try Urho3D or its newer fork rbfx.

I use an engine called rbfx which is a fork of the Urho3D engine. A lot of it is just the fact that I've been using it for over a decade, so I am comfortable with it. I'm a programmer, not really comfortable with integrated editor engines such as Unity or Godot, and the easy C++ extensibility of the engine appeals to me. Plus it's decently powerful, and well supported on a lot of platforms (I build for Windows, WebGL, and very occasionally RPi for the most part) and is open source to satisfy that stubbornly libertarian side of my character.

You might be interested in Urho3D.

If you don't mind something experimental, there is a C# version of Urho3D that is in fairly active development. There is also a C#-scriptable branch of the Urho3D fork, rbfx, located here. Both of these projects are still pretty in-the-works, but are still pretty usable.

Magnum

If you want something that gives you more control you could use magnum.

Therefore, in terms of artist mindshare, Blender is the leading open source 3D creation program, but not the leading 3D creation program. I think Godot is already in a similar situation, and has been for a few years now. In comparison, most other open source game engines have focused on providing low-level functionality. These certainly fulfill a niche, but in my experience, most people want something that works at a higher level and comes with a built-in editor.

Magnum is worth checking out.

Since you want something lightweight, I'll assume you mean the former. If that's the case, then checkout bgfx or Magnum. Magnum does include some extra features typically found in a graphics engine.

You could try Magnum it wraps SDL and others, but you might find it maybe too low-level. It's certainly not Love2D.

C++ is similar to C in that there are multiple "styles" of use that vary from project to project. Other, usually newer languages (C#, Python, Rust, etc) tend to have a stronger sense of what idioms should be used. Whereas, for instance, some C++ projects (like some GUI libraries and game/graphics engines) will partially/entirely replace the STL (and older ones may have been around before C++ had a standard library aside from C's), or forbid the use of certain C++ features (example).

Magnum Graphics

> He has Vulkan support in here with a clearly marked file named Pipeline.cpp. The guy knows what a pipeline is...

There is a Vulkan API wrapper. However, there is no "Vk Renderer" -- no code seems to use the Vulkan parts of the code system, and the two projects seem unrelated.

> * Is this not a UBO interface?

There are ways of making a uniform buffer, however the examples don't cover them and the API doesn't adapt automatically. See how all of the setters assert if UBOs are enabled.

https://github.com/mosra/magnum/blob/cfc02599e54e02337dd56bb...

> * I don't see why you think there's limited support for multiple framebuffers...?

The code I do see is about binding/unbinding framebuffers in a stateful manner, e.g. AbstractFramebuffer::bind(), rather than supporting passes.

> None of your criticism seem well intentioned. It might behoove you to give people the benefit of the doubt and realize that you may be able to learn something from them, even if they're so clearly inferior to you.

To put it simply, I've taught enough graphics to know first-hand the kinds of misconceptions that OpenGL-styled APIs can cause, and I'm just a bit tired to see it continue. Admittedly I was a bit harsh, I don't mean any harm towards the author. There are just graphics APIs with interfaces I consider to be much better designed.