[Bug] Schismtracker can't handle its screen on the framebuffer console with KMS (7)
5703 Name: Fortrix : 2012-07-25 02:32 (File: 6 kb, 1024x768, schismbug.png)
Hello,
I'm using latest ST build on the console Debian Squeeze with nouveau-kms video driver (the videochip is NVidia GeForce Go 6100) with high-res framebuffer (other framebuffer driver options are not sufficient because they can't give the native resolution on this exact videochip)
On my native resolution (1360x768) Schism Tracker just freezes the entire system on start. I found out that I should change the resolution to 1024x768 with fbset in ~/.schism/startup-hook and restore it in ~/.schism/exit-hook. But nevertheless, the tracker's window doesn't show up on the full height. It remains very small, centered at the screen area. The -f, –video-stretch, –video-size flags don't have any effect at all.
The bug is present not only in the latest build but in all previous versions, including the version from official Debian repos.
Maybe it's SDL bug? Any suggestions for workaround? Please help.
Attaching the screenshot, taken with fbgrab.
5704 Name: 68k : 2012-07-25 02:49
Easy questions first:
Did you try other video drivers? (Ctrl-F1)
How does it run in windowed mode? What happens when you resize or maximize the window?
5705 Name: Fortrix : 2012-07-25 02:53
Other drivers are not available. Fbcon only.
The Ctrl+Alt+Enter (and changing the fullscreen setting in the Ctrl+F1) don't work (the option just doesn't get selected).
Windowed mode? That system has no X. The same ST version works perfectly in X and all the modes function correctly. But the point is to get correct behavior in the bare framebuffer console.
5706 Name: 68k : 2012-07-25 03:21
Oops, sorry, didn't quite understand what you were doing from the first post.
I this is one for Storlek...
5708 Name: Jimmy G. Faulkner : 2012-07-30 21:14
Don't think framebuffer has been properly supported for ages, and even then, it only functions on some computers.
I don't think the command line options are even relevant outside ofX11, as there's no window to resize or stretch. I'm saying this without a bit of certainty, though, as the last time I even tried to use a framebuffer, the options didn't exist, and in any case, it was a 640x400 framebuffer that I'd configured specifically for Schism Tracker. (not so useful information, I know)
5711 Name: Fortrix : 2012-08-05 15:26
If only there was a possibility to switch real KMS framebuffer resolution, I'd just do it in startup and exit hooks and never mind this bug. But there isn't, it seems. At least for NVidia.
It also seems that SDL, when running in non-X environment, relies
on internal application resolution, which is always 640x400 here. Why is ST sticked to 640x400 only? Just curious about why not to make it change dynamically.
5712 Name: Tracey Compton : 2012-08-06 00:43
Schism Tracker does scale its display when the window size changes, but I'm not sure if SDL under a framebuffer even passes to the application what the actual, proper size of the screen is. It just takes the initial request of "I want 640x400", says "well okay, I'll fill the rest with black" and that's that. There's probably some way to pull that information and set up scaling before initializing the app, but I don't remember.