I recently upgraded to Ubuntu 12 and, having changed nothing manually, even the most minimal Gosu program now crawls. I imagine it's an OpenGL issue, but any ideas as to where to look to better debug the situation would be greatly appreciated.
To begin your quest, you may consult the glxinfo program.
$ glxinfo | grep "direct rendering"
If this prints out "no," you're in trouble.
$ glxinfo | grep "rendering string"
$ glxinfo | grep "vendor string"
These should print info about your OpenGL pipeline. If they say LLVMpipe or Mesa, instead of Nvidia, ATI, or Intel, you're in trouble.
You might also want to try running another OpenGL program. Depening on the power of your computer, Nexuiz might be a good test, and would be in the Ubuntu repos.
Thank you for taking the time to respond, Jamer. Alas, glxinfo is not presently on my machine nor, seemingly, in the repository. Gosu does run, though, just very, very slowly. I'm guessing that my not having glxinfo is the first bad sign. As for testing another OpenGL program, I would of course be happy to, but Nexuiz is an extra gB of space I'd rather not use up.
I've reinstalled Gosu to no avail. I've also made sure that I have all of the necessary libraries in place, and it seems that I do. However, every single one of them is "set to manually installed". Do you know if this is a result of them initially being compiled during initial installation of Gosu?
This is quite unfortunate, but at least now I know this issue does not just affect me.
I am fairly certain this issue is either in Ruby or Gosu, as Minecraft does not seem to run any worse than it did before. I don't normally get 60fps in Minecraft though, so that may not be the best benchmark. However, I've programmed some things in Java using JOGL for a class, and those do not seem to be running any slower. Even so, that's just my personal opinion, I don't have data to back it up with, as is the case with the Gosu/Ruby regression.
Ouch. The worst part is that I can't really debug this issue in my VM which does not have OGL acceleration to begin with. :(
Let me know if there's some data I can give you which would help D:
I really feel like it should be Ruby's fault more than yours though.
Oh, you could actually verify if your last statement is correct :) You only need to make (not install) Gosu for C++ to give it a try: http://libgosu.org/downloads/gosu-linux-0.7.43.tar.gz
If I had to guess, I'd say the X11 code in Gosu does not use the latest and greatest in X11 extensions :(
ah, I forgot to mention this important bit:
The problem seems to affect me only when I'm scaling to particular resolutions using Gosu::Window#scale. Thus, I suspect some issue with mipmapping.
Starting to think my issue (if it's not just a personal problem) is different from the OP. I will file an official github issue report if I can narrow down the cause of the problem.
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill