hmuni006 / mupen64plus

Automatically exported from code.google.com/p/mupen64plus
0 stars 0 forks source link

fullscreen problem #453

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

 - linux 32 bit
 - latest hg pull of mupen64plus
- Plugins used:
rice opengl video

Whenever I try to run a game in full screen, the game doesn't show up fully. 
Here is the error I got:
04:20:51 PM: [Video] Warning : Couldn't open hi-res texture directory: 
/home/dylan/.local/share/mupen64plus/hires_texture/CONKER BFD/
04:20:51 PM: [Video] Warning : Failed to set GL_SWAP_CONTROL to 0. (it's -1)
04:20:51 PM: [Video] Warning : Failed to set GL_DEPTH_SIZE to 16. (it's 24)

Original issue reported on code.google.com by darthdyl...@gmail.com on 10 Aug 2011 at 8:30

GoogleCodeExporter commented 8 years ago
Those are all relatively mundane warnings and shouldn't prevent you from 
getting fullscreen.  Can you attach a screenshot (or from a digital camera) to 
illustrate what you mean by "the game doesn't show up fully"?

Original comment by richard...@gmail.com on 10 Sep 2011 at 5:37

GoogleCodeExporter commented 8 years ago
It's not the best screenshot, but it's enough for you too see the problem.
by "the game doesn't show up fully" I meant that half of the game is on one 
side, and the other half of the game is on the other side. This problem was 
fixed by changing the "gl_depth_size" to 24. but know I have another problem in 
fullscreen, intense flickering. This makes the game unplayable on fullscreen. 
This is what the screenshot shows.The screenshot is attached. I've also noticed 
that this doesn't happen when I log into gnome. It happens whenever I use 
fluxbox, blackbox, e17, window maker, etc. (yes, I tested it on all of those 
environments.) However, it's very slow on gnome, which  is the reason I use e17 
(my primary desktop) instead.

Original comment by darthdyl...@gmail.com on 11 Sep 2011 at 11:15

Attachments:

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Looks like a driver/compositor problem. Did you test it with mupen64plus 2.0 on 
a more recent Distribution.

Original comment by s...@narfation.org on 18 Dec 2013 at 11:51