This page says “The WorldModel provides some physics features to a ViewportFrame.” - but this is misleading. As I understand it (and from experience) WorldModel can be used separate to the ViewportFrame and is a way of having a separate physics world. It would be better to frame this in a more generic way and explain that the ViewportFrame example is one use case.
Hi @Ed_Win5000 ,
Thanks for the report. I’ve updated the docs slightly, but what was previously there was essentially correct. There is no complete “simulation” run in WorldModel, so it’s not a “separate physics world”… just the “limited physics” like spatial queries as the update clarifies.
@IgnisRBX I think I get your point, that the parts inside a WorldModel aren’t simulated automatically, but the presence of StepPhysics (for plugins) and the overhead of having a WorldModel seems to contradict this.
I still don’t quite get why it focuses on ViewportFrames when there are other useful use cases - we use them for overlap checks for procedural levels generation on the server for example. It seems liable to discourage their use for other sensible uses.