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
Processing 2.x/3.0 on Mac (10.10.2); framerate in P3D halved vs. Processing 1.5 #3210
Comments
We can't do anything with that information unless you post a sketch for us. |
Sorry Ben, cleaning it up and will do in a minute |
Hmm, sorry, here: http://we.tl/FJblyy8SYi |
Hm, I'm seeing 60 fps on my machine with 3.0a7 and it doesn't seem maxed out, though at the moment I'm on a fast machine. @codeanticode Any thoughts here? We should be much speedier with a7. And separately, setting
|
What happens when you just up the maxtrail particle count until even your fast machine struggles? Like mentioned before, I'm seeing a 30fps difference between 1.5 and 3.0
|
Yeah, I pasted it since links like that usually don't work by the time we can do anything about them. I'll close this as fixed for 3.0a8. |
Thanks Ben, and yes. Cheers for looking into this. Let me know if I can help
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Running the same sketch (line / vertex based) at different OSes using P3D gives various results:
Processing 1.5, OSX 10.10.2: 60 fps (using OPENGL renderer)
Processing 3.0a5, OSX 10.10.2: 25 fps
Processing 3.0a5, Win8 64bit: 55 fps
The text was updated successfully, but these errors were encountered: