change resolution in windows supertuxkart

#CHANGE RESOLUTION IN WINDOWS SUPERTUXKART CODE#

#CHANGE RESOLUTION IN WINDOWS SUPERTUXKART CODE#

Slight detour in the above thread - I code for a project ( Mudlet the MUD Client) that uses antique OpenGL direct rendering - using pre-GLSL code from the OpenGL 1.4 era. How do with check how much memory is available to OpenGL? In the past this was done by config.txt, but that's ignored now at some level? So we get this off texture thrashing effect? Is this related to model? I wonder if it has something to do with memory allocation? Perhaps somehow/someway there is only a limited set of memory being reserved for video/texture memory. I haven't really changed anything other than updating the firmware. I can also get it to play at an acceptable FPS if I drop the resolution and every setting to low, but the texture popping still makes it unplayable. Q3 and OA are unplayable with low FPS and texture popping in and out like crazy. I assume they are running the same ioquake build? I see this effect on both Quake 3 and OA. I'm assuming it's forcing that new unfinished default OpenGL2 renderer - which looked completely broken last time I checked on a Pi3.

OA doesn't support whatever debian downstream does for an engine (we only support this).

Change resolution in windows supertuxkart