New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simulation.run(steps) continues past (steps) - need FreeGLUT patch in setup scripts #27

Open
brtietz opened this Issue Aug 21, 2014 · 2 comments

Comments

Projects
None yet
1 participant
@brtietz
Contributor

brtietz commented Aug 21, 2014

Simulations with graphics keep running, regardless of the number of steps provided as an input parameter.

Workaround: run your simulations without graphics.

Proposed Solution: The core of this issue is that our rendering engine (GLUT) takes over the simulation loop. The ultimate solution will require installation of FreeGlut, which is possible on Linux but would currently require extensive steps for Mac users. A patch script for FreeGlut should be developed, and added to the setup scripts. After this, minor tweaks can be made to tgSimViewGraphics to correct the behavior.

@brtietz

This comment has been minimized.

Show comment
Hide comment
@brtietz

brtietz Nov 12, 2014

Contributor

Just to add a little more importance/urgency to this one, this same issue is affecting our ability to debug. We can only step through the code until we need to render, at which point GlutMainLoop takes over and effectively forces a "continue" instead of a "next" in gdb.

However, it does take a Mac user to debug/test this, so I can't assign it to myself.

Contributor

brtietz commented Nov 12, 2014

Just to add a little more importance/urgency to this one, this same issue is affecting our ability to debug. We can only step through the code until we need to render, at which point GlutMainLoop takes over and effectively forces a "continue" instead of a "next" in gdb.

However, it does take a Mac user to debug/test this, so I can't assign it to myself.

@brtietz

This comment has been minimized.

Show comment
Hide comment
@brtietz

brtietz Dec 23, 2014

Contributor

As discussed in developer meetings - the ultimate solution to this may be to change rendering to Ogre or similar.

Contributor

brtietz commented Dec 23, 2014

As discussed in developer meetings - the ultimate solution to this may be to change rendering to Ogre or similar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment