Urho3D | Cross-platform 2D and 3D game engine | Game Engine library

I found the answer. When you call SetStyleAuto you should pass in a style XmlFile.

What does this even mean?

It means that Urho3D doesn't support direct usage of for example .obj or .3ds files but it provides an AssetImporter that can load these file types and output Urho3D's own model format (.mdl) or animation (.ani) files. What adds to the confusion is that .mdl is also the name of the proprietary model format for Valve's Source engine

Does "existing formats" mean existing standards (.obj or .fbx) or are the saying that .mdl and .ani is their "existing implementation"

Existing formats means the industry standard formats you can use as the input, such as .fbx, .blend, .obj etc. For a full list of the formats, you can refer to their Import Formats page on Sourceforge (not sure why they don't have the same list available on GitHub).

These inputs can then be converted to Urho3D specific .mdl and .ani files.

Edit: In case you encounter confusing parts of the documentation such as this one, you can also raise an issue on the GitHub repository that contains the documentation. For example, this specific documentation is hosted in MicrosoftDocs/xamarin-docs repository and the exact file that you're reading is this one.

This is exactly what dynamic dispatch (known in C++ as virtual) does: given a Base* (or Base&) that refers to an object of a derived type, a call to a virtual function will find the override even without any declaration of Derived (and thus even if the call was “compiled first”).

As to your “library-provided main” idea, that’s a lot harder: in general, how would he library know how to construct your object, and what would it do if you linked against two “extending classes”?

But it is possible, if the library designs for it: have the library provide a global pointer variable (which it assigns in main if you want to have a default), and have the extension class’s constructor assign this to it. Then just define a global object of that class type. If you need no default behavior, you can also just declare and call, but not define, an initialization function in the library and leave it to the extension to define it.

To empty a Scene, call Scene::Clear() on it. This removes all the Scene's Components and child Nodes. After this you can call a function that rebuilds the scene.

Alternately you could create a custom reset event that all Objects that require some form of resetting subscribe their HandleReset methods to. To restart the game you would then call SendEvent(E_RESET).

And here's the solution: the default debug output of the Urho3D renderer does not include the physics components. It has to be added manually.