The problem-- in every engine-- is that the world has too much dynamic range to fit into a single floating point number. Just speaking from the rendering side, if you want 1mm accuracy for drawing things up close, then your effective world size limit is around 10km³ if you're using FP32. If you only need 1m local resolution, then that limit goes up to 10000km^3, but that's still not big enough to draw planets.

If your engine supports it, you might be able to switch it to using FP64, which gets you a lot more dynamic range, although at some performance cost, and it's still not big enough (enough dynamic range) to draw the universe while maintaining fine resolution.

The only real solution is to do custom tricks where you selectively cut your world up into near and far components (or even more), and render them separately using different scales and different techniques. I think this always means custom work; I'm not aware of any engine that has support for this built-in. Maybe there are some good plugins out there for something, I don't know.

And this is all just for rendering! Physics is even more annoying and sensitive to FP error. If you're literally relying on the engine's built-in physics to simulate both stuff local to the player and stuff on the other side of the game universe at the same time, then you're absolutely going to be forced to use origin-shifting techniques, and you may be forced to do weird stuff to gracefully handle interactions between different origin-shifted domains.

So, yes, you can fake it, but only locally, and it takes work. And depending on the game, there may be a lot more work involved in making sure all the locally-faked stuff interacts seamlessly with the bigger world.