Open GoogleCodeExporter opened 9 years ago
Try:
pingus --fullscreen-resolution=640x400
or
pingus --window -g 640x400
Original comment by grum...@gmail.com
on 2 Feb 2014 at 8:03
pingus -fullscreen-resolution=640x400
results in:
CommandLine_Generic::parse_args(): option requires an argument - - u
and
pingus --window -g 640x400
produces:
CommandLine_Generic::parse_args(): option requires an argument - - r
any other clue?
btw i am totally new to ubuntu and linux... so any help is welcome..
Original comment by henning....@gmail.com
on 3 Feb 2014 at 11:51
I have observed a similar issue in my Ubuntu machine, although in my case the
problem was that Pingus was configured to use a fullscreen 1920x1080, while my
current resolution was 1872x1053 (due to overscan settings for my TV). In your
case, it seems the problem is that 576 height is not enough for the (default)
800x600 resolution.
This is the error I got:
[ERROR] SDLFramebuffer::set_video_mode(): Unable to set video mode: No video mode large enough for 1872x1053
I have a patch for Pingus that seems to work fine (although it unveils another,
probably less important, issue). I will be posting it soon.
Original comment by mariospr@gmail.com
on 6 Jan 2015 at 1:51
See the patch that fixes the issue for me (also attached to this comment):
here:
https://github.com/mariospr/pingus/commit/5856a2e6989bc003b8dba0bf4a28e19f6f3da9
e2
Let me know what you think, and feel free to merge it if you think it makes
sense.
Original comment by mariospr@gmail.com
on 6 Jan 2015 at 2:11
Attachments:
Last comment:
As I mentioned above, the proposed patch unveiled another problem, which I
think it's unrelated, but not 100% sure. See below:
For some reason, even though the patch proposed above allows to start pingus
normally even if the desired resolution does not match the desired one, the
first time pingus is started the main window is misplaced: it's rendered with
the right resolution (e.g. 1872x1053) but with (0, 0) coordinate placed
offscreen, too far in the NW corner, as if it was not considering the overscan
setting.
I spent some time trying to find a solution for this, but in the end I
concluded that it's either an issue somewhere else deeper in pingus's engine,
or even in SDL_SetVideoMode(), and could not figure out clearly where exactly
the problem was.
Also, this is something that happens only the first time pingus is run with the
mismatched resolution: if you exit the game and start again, the resolution
will be fine again, same thing if you go to options and fiddle with the
resolution settings during the first run.
I haven't filed any bug related to this because it's still not clear to me what
the problem is. Perhaps someone with more knowledge about pingus and/or SDL
will be able to better figure out what the problem is.
Original comment by mariospr@gmail.com
on 6 Jan 2015 at 2:12
Original issue reported on code.google.com by
henning....@gmail.com
on 2 Feb 2014 at 1:50