Im calling that on my Main class Constructor.
Let me explain:
I have my main class constructor and i create StandardGame on it, instantiate my custom gamestates and put the on the GameStateManager.
Set them as active and then call the code from the first post.
This code works well until the lastest revision.
This is not Gl thread isnt it?!
Your call to future.get() blocks the current thread until your submitted task is complete. Problem is, you're blocking the thread that processes the game task queue (GL thread) so your submitted task will never be executed. If you're already in the GL thread, there's no reason for your task submit/future.get code and you can safely remove it.
Thats right. Ive already done that.
Im curious that my code worked well until a recent revision.
But the way, its not a problem anymore.
Thanks for help!
It may have been the patches I submitted to fix some issues with threading. My guess is your main code was accidentally running outside of the opengl thread.