I think we can disable debugging on this class by default. What do you think?
Well, it should be fixed first, heh ;D
[quote="<MagicSpark.org [ BlueSky ]>,post:2,topic:27918"]
Well, it should be fixed first, heh ;D
[/quote]
Fixed? What is not working with it at the moment?
[quote="<MagicSpark.org [ BlueSky ]>,post:4,topic:27918"]
http://www.java-gaming.org/forums/index.php?topic=14118.0
Check particularly Niwak’s post
[/quote]
Hmm… OK. But it seems to work properly in almost every case. Well, I didn’t have this bug so far. So for most people this debugging output is just annoing. When someone actually has this bug, he can just switch debuggin on. Maybe we should have a general switch in a com.xith3d.Xith3D class to disable / enable debugging globally which can be overridden by a class.
Hmm… OK. But it seems to work properly in almost every case. Well, I didn’t have this bug so far. So for most people this debugging output is just annoing. When someone actually has this bug, he can just switch debuggin on. Maybe we should have a general switch in a com.xith3d.Xith3D class to disable / enable debugging globally which can be overridden by a class.
[/quote]
Well.
“Xith3D never checks the hardware capabilities ; it takes for granted a set of capabilities and if it doesn’t fit, it will just run as is with OpenGL firing errors” is not satisfying. Even if it does work it’s not clean.