set fullfixed=false 😉

-Brian

Hi Brian,

The fullfixed doesn't work for me, I do never use Dosbox because the problem: the big black area around the dosbox window (not true full screen). My parameters?

fullscreen=true
fulldouble=false
fullfixed=false
#fullresolution=1680x1050
fullwidth=1680
fullheight=1050
output=surface
hwscale=1.00
autolock=false
sensitivity=100
waitonerror=true

How can I do to have full screen?

Thanks in advance,

Alt+Enter 😀

Uh???

ALT+enter??? 😀

I've tried that, of course, but it isn't true full screen mode, it's a partial screen, with a big big black around it.

I want true full screen! 😉

uncomment 'fullresolution' and change it to the size of your screen's native resolution. Or go into your display control panel and tell your video card to stretch the image to the screen.

Of course, I've tried this 😀

Any other idea?

Thanks in advance,

No, because if it still isn't working, you're doing something wrong. 😀
scaler=normal2x

Scaler is right, too.

I'm doing something wrong? But...there's only one configuration file, or not?

My configuration file, /home/user/.dosboxrc

fullscreen=true
fulldouble=false
fullfixed=false
fullresolution=1680x1050
output=surface
hwscale=1.00
autolock=yes
sensitivity=100
waitonerror=true

Any hint?

Thanks in advance.

Normally the configuration file is dosbox.conf.

More data:

rootito@scabito rootito $ dosbox
CONFIG:Loading settings from config file /home/rootito/.dosboxrc
DOSBOX:Unknown machine type auto
ALSA:Client initialised [65:0]
MIDI:Opened device:alsa

Dosbox is running .dosboxrc fine, not another configuration file 🙁

Any hint?

"DOSBOX:Unknown machine type auto" That doesn't really make sense, either.

Yes, it's not the problem.

Changing it to vga, full screen doesn't work yet 🙁

Configuration file is right, dosbox is running the right configuration file, but fullscreen isn't running yet.

Should I report it to developers? It's very strange...

That would seem more of a problem with X...
Try turning on X logging or reading the logs if it is on to see if it's complaining about mode changes at all.

Yes, but X runs fine another Games as Unreal, Quake, etc...

I've X Windows working properly from more than one year ago, changing resolutions or not.

The log:

(II) NVIDIA(0): Setting mode "640x400"
SwitchToMode - Succeeded
GetModeLine - scrn: 0 clock: 31500
GetModeLine - hdsp: 640 hbeg: 672 hend: 736 httl: 832
vdsp: 400 vbeg: 401 vend: 404 vttl: 445 flags: 6
GetModeLine - scrn: 0 clock: 31500
GetModeLine - hdsp: 640 hbeg: 672 hend: 736 httl: 832
vdsp: 400 vbeg: 401 vend: 404 vttl: 445 flags: 6
SwitchToMode - scrn: 0 clock: 188100
hdsp: 1680 hbeg: 1800 hend: 1984 httl: 2288
vdsp: 1050 vbeg: 1051 vend: 1054 vttl: 1096 flags: 0
Checking against clock: 188100 (188100)
hdsp: 1680 hbeg: 1800 hend: 1984 httl: 2288
vdsp: 1050 vbeg: 1051 vend: 1054 vttl: 1096 flags: 0

Dosbox doesn't switch to 1680 resolution properly! 😒 Sets the mode and nothing...

Ugh...I don't know what to do...

You can try running xrandr from an xterm; that'll display a list of available resolutions and might be suggestive. I couldn't find anything in the SDL docs but I suspect that's the place to look.

The problem was overlay. I think it's no clear at the description, but that was the problem 😀

overlay=opengl

😀

PD: Thanks to Robert!

rg_pablo wrote:

overlay=opengl

Nonsense. Overlay is overlay and opengl is opengl. These are two different options.

Mirek