Best model-vision pattern/approach for game

I'm making a game.

I have been using modified version of MVC to separate vision and logic, where controller sends a request to model, then sends its answer to vision. I've found this approach too complex, not letting me to make significant changes in the future.

So I wonder what is the best way to separate graphic/animation and logic parts in the game to make the code more clear and easy to understand while also less vunerable to changes in the algorythm steps or the algorythm itself.