Skip to content
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

Visualizer lags while panning #69

Closed
tkuchida opened this issue Mar 2, 2017 · 3 comments
Closed

Visualizer lags while panning #69

tkuchida opened this issue Mar 2, 2017 · 3 comments

Comments

@tkuchida
Copy link
Member

tkuchida commented Mar 2, 2017

Platform: Win 7 Pro 64-bit
Hardware: AMD Radeon HD 7450
Version: opensimWin64Alpha01.zip
Browser: Tested on Firefox 51.0.1 and Chrome 56.0.2924.87

FPS fluctuates between ~15 and >100. Previous GUI alpha release ("visualizer_alpha_01" from opensim-org/three.js) did not lag.

@aymanhab
Copy link
Member

aymanhab commented Mar 2, 2017

Could it be settings in the browser as reported earlier by @carmichaelong (sorry I forget where were the flags for GPU hardware acceleration).

@tkuchida
Copy link
Member Author

tkuchida commented Mar 4, 2017

Thanks! Yes, it's probably just a browser setting since the visualizer works smoothly on my ⚓ of a laptop (I probably fixed it there when testing the first alpha but neglected to propagate the change at my desk). @carmichaelong's detailed description and fix can be found here. I'll close this issue once I've confirmed.

@tkuchida
Copy link
Member Author

tkuchida commented Mar 5, 2017

Resolved. Detailed explanation follows.

My default browser is Firefox for reasons that are not relevant here. Upon loading a Model, the GUI spawns a new tab in the default browser. The visualizer was lagging in Firefox so I launched Chrome to test there, but did not close the Firefox tab. Surprisingly, leaving the Firefox tab open causes Chrome to lag as well. Closing the Firefox tab (or even just switching to a different tab) resolves the issue. I guess it was my fault for not imagining that this could happen.

@tkuchida tkuchida closed this as completed Mar 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants