Does my Game class have too many responsibilities?
I like to trash people when their classes do too many things.  I was disappointed when I saw your class because it is not so bad.

However, I don't think this class should check if the display did open.  You should only create the Game once you know that the display is ready.

I'm not sure Game is an appropriate class name.

Naming member variables starting with an underscore comes from some other language; it is not standard Java.

You write too many comments.  Let the code speak for itself and you won't have to worry about keeping the code and the comments in sync.


The comment at the beginning at the class is clearly deprecated.
// schedule display to update @ 60 fps might not be true.