I've never used this feature. Do we have alternative for this?
I mean (correct me if I'm wrong) I've always imagined this was for scenarios like: I have a game with a specific configuration and graphics compositor, but for iOS and Android I want a specific configuration with smaller textures and a special compositor that disables shadows and post-FX.

If it is like that, it is an useful feature to have for multi-platform builds.

@Ethereal77 What you are describing wasn't possible previously, as the graphics compositor was not in a configuration, so it couldn't be overridden. The things you could override were mostly not related to hardware or platform (e.g. physics) except for graphics level, which from what xen mentioned in the linked PR, it probably wouldn't have worked. Also specific filters didn't work at all.

An alternative right now is to override the game class and add your own logic there (which is probably what you would have to do for most graphics-related settings). In the future, there could be a more proper way, like a replacement asset, but for now I'm just trying to remove this mostly broken feature

1. Done
2. I don't know why, but the Stride.BepuPhysics.Navigation project isn't in Stride.slnx, which is probably how I missed it.
3. I addressed BepuConfiguration.NewInstance - inconsistent behaviour #3175 while I was at it. Now, when you have no BepuConfiguration in game settings, the physics will work just like you would expect them to, unlike previously where there would be no simulations and everything would remain static. This is the same behavior that is present in code-only (no game settings).