BepuConfiguration.NewInstance - inconsistent behaviour

Release Type: Release

Version: 4.3.0.2507

Platform(s): All

Describe the bug
If BepuConfiguration isn't added to game settings, it will be created at runtime. However, this behavior can differ:

• If the game settings asset exists -> configuration has no simulations, so nothing works
• If the game settings asset does not exist (code-only) -> configuration has a single simulation with default values

Having the latter always be the case would reduce a lot of confusion for users that didn't read the manual.

To Reproduce

1. Create a new project
2. Add some physics objects
3. Observe that physics don't work and there's a warning that there are no simulations
4. Delete the game settings asset
5. Set the graphics compositor and scene manually
6. Physics works

Expected behavior
A single simulation is added no matter if the game settings asset exists or not

Start at BepuConfiguration.NewInstance and reproduce the behavior with and without the game settings asset using the listed steps. Trace how the configuration is initialized in each case; done means both paths create one simulation with default values and physics works consistently.