VOGONS


First post, by Finchley Minsk

User metadata
Rank Newbie
Rank
Newbie

Hello,

I am running Windows 7 x64.
60" Widescreen LCD.

When running DOSBox full screen, the screen zooms in so far that a good majority of it is truncated.
Aspect ratio settings have no effect.
This is true for any output/scalar setting, aside from surface/normal2x.
I have tested this with both DOSBox 0.74 and Daum x64 27-01-2014.

Some screenshots with explanations. Taken from the Daum version.

1sm.jpg
2sm.jpg
3sm.jpg

Herein lay my present conf:

fullscreen=false
fulldouble=false
fullresolution=desktop
windowresolution=original
output=surface
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper-0.74.map
usescancodes=true
language=
machine=svga_s3
captures=capture
memsize=16
frameskip=0
aspect=true
scaler=hq2x

Some notes:

-This error occurs with Daum right out of the box. With Vanilla DOSBox, any output setting aside from surface, and any scalar setting aside from Normal?x
-Error does not occur on my laptop.
-Error occurs at any monitor resolution setting. Monitor resolution range 800x600 - 1920x1080.
-Error occurs regardless of fullresolution= setting.
-I have gone through my OSD settings as well as my video driver options, to no avail.
-I have searched through Google and VOGONS for quite some time before deciding to make an account here.
-Help me Obi-Wan Kenobi, you're my only hope.

Thanks,

-Finchley Minsk, neither a finch nor actually from Minsk

Last edited by Finchley Minsk on 2014-05-29, 10:55. Edited 2 times in total.

Reply 1 of 10, by ripa

User metadata
Rank Oldbie
Rank
Oldbie

Try fullresolution=0x0 or fullresolution=1920x1080. 0x0 means desktop resolution.

Reply 2 of 10, by Finchley Minsk

User metadata
Rank Newbie
Rank
Newbie
ripa wrote:

Try fullresolution=0x0 or fullresolution=1920x1080. 0x0 means desktop resolution.

Sorry, I tried these before making the post. I didn't realize I hadn't mentioned that in the post.
Will update to include this.

-Finchley Minsk, draws mustaches in newspapers

Last edited by Finchley Minsk on 2014-05-29, 10:55. Edited 2 times in total.

Reply 4 of 10, by Finchley Minsk

User metadata
Rank Newbie
Rank
Newbie

I'm truly sorry. Once again I took for granted something about my post.

I have gone through my OSD settings as well as my video driver options prior to making the topic; to no avail.
I will update the topic to reflect this.

I want to say I appreciate any and all help and advice offered in this thread.
You're awesome, you!

-Finchley Minsk, uses lactose intolerance like a super power

Reply 5 of 10, by Finchley Minsk

User metadata
Rank Newbie
Rank
Newbie

Hello, I am sad to say I have not yet resolved this issue.

I, a light-hearted, happy-go-lucky fellow, am deeply saddened.

Reply 6 of 10, by Finchley Minsk

User metadata
Rank Newbie
Rank
Newbie

Yo dawgs,

Be trues when I says, only surface works decently fullscreen.
Direct3d and Opengl, straight up nopes in this hizzay.

digs bruvs?

Reply 7 of 10, by Finchley Minsk

User metadata
Rank Newbie
Rank
Newbie

Seriously? No one has anything to contribute?
I thought that the DosBox devs were on here, yet not one has the slightest interest in fixing a fault in their code?

"I haven't the slightest idea. Better ignore it and hope this is an isolated incident"

Shame on you.

Reply 8 of 10, by ripa

User metadata
Rank Oldbie
Rank
Oldbie

Lol.

I doubt there's anything wrong with Dosbox, since this is only occurs with your external display. If there's a problem, it's probably with your external display or graphics driver settings (you have not mentioned which graphics hardware you have - Intel, AMD, Nvidia, which model, which drivers, etc...). It's also possible that there's a bug in SDL, the library that Dosbox uses for graphics output. Have you tried other SDL-based applications?

Here's a few more shots in the dark.
1. Disable the external display's aspect ratio "auto-crop" feature.
2. Disable overscan in the external display's settings.
3. Disable overscan in your graphics driver settings.
4. Disable or enable or adjust any other settings like GPU scaling.
5. Upgrade or downgrade your video card drivers.
6. Try a different version of the SDL DLL.
7. Make sure you try a game instead of just the command line because text mode and graphics mode behave a bit differently in Dosbox.
8. Try a different video output port (e.g., VGA, DisplayPort, HDMI, DVI).

If these don't help, get the Dosbox and SDL source code and build the software and debug the problem yourself. Debug prints are always helpful.

Reply 10 of 10, by Jorpho

User metadata
Rank l33t++
Rank
l33t++
Finchley Minsk wrote:

Shame on you.

Yes sir, now that you, a light-hearted, happy-go-lucky fellow, have exposed what terrible people we are we will reveal the secret solution we have been keeping for this problem no one else has heard of. May $deity have mercy on us all.