It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hi. Recently, for no reason I can fathom, all of my GoG games are booting up with a tiny image in the center of the screen. I alt-tab, but this just takes me to windowed mode. I alt-tab again, and I'm back in full screen with the image still tiny. I have NO idea why this arbitrarily happened, but it's happened to ALL of my GoG games. Please help.
avatar
drummond13: Hi. Recently, for no reason I can fathom, all of my GoG games are booting up with a tiny image in the center of the screen. I alt-tab, but this just takes me to windowed mode. I alt-tab again, and I'm back in full screen with the image still tiny. I have NO idea why this arbitrarily happened, but it's happened to ALL of my GoG games. Please help.
Go to start menu and click the game's graphic mode setup option or setup option and set fullscreen to YES.

Alnaternatively, go into one of the dos game's folders and look for a file labelled "gamename.conf" and open it as notepad/text file and list it's contents here so we can check for problems.
Post edited May 05, 2011 by GameRager
I think the most likely cause of this would be flat panel scaling being disabled in your graphics card settings. What make of video card do you have?
avatar
drummond13: Hi. Recently, for no reason I can fathom, all of my GoG games are booting up with a tiny image in the center of the screen. I alt-tab, but this just takes me to windowed mode. I alt-tab again, and I'm back in full screen with the image still tiny. I have NO idea why this arbitrarily happened, but it's happened to ALL of my GoG games. Please help.
avatar
GameRager: Go to start menu and click the game's graphic mode setup option or setup option and set fullscreen to YES.

Alnaternatively, go into one of the dos game's folders and look for a file labelled "gamename.conf" and open it as notepad/text file and list it's contents here so we can check for problems.
No, it's doing this in full screen if I understood the OP correctly. Posting the contents of the .conf file is a very good idea.
# Lines starting with a # are commentlines.
# They are used to (briefly) document the effect of each option.

[sdl]
# fullscreen -- Start dosbox directly in fullscreen.
# fulldouble -- Use double buffering in fullscreen.
# fullresolution -- What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
# windowresolution -- Scale the window to this size IF the output device supports hardware scaling.
# output -- What to use for output: surface,overlay,opengl,openglnb,ddraw.
# autolock -- Mouse will automatically lock, if you click on the screen.
# sensitiviy -- Mouse sensitivity.
# waitonerror -- Wait before closing the console if dosbox has an error.
# priority -- Priority levels for dosbox: lowest,lower,normal,higher,highest,pause (when not focussed).
# Second entry behind the comma is for when dosbox is not focused/minimized.
# mapperfile -- File used to load/save the key/event mappings from.
# usescancodes -- Avoid usage of symkeys, might not work on all operating systems.

fullscreen=true
fulldouble=false
fullresolution=original
windowresolution=original
output=surface
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper.txt
usescancodes=true

[dosbox]
# language -- Select another language file.
# memsize -- Amount of memory DOSBox has in megabytes.
# machine -- The type of machine tries to emulate:hercules,cga,tandy,pcjr,vga.
# captures -- Directory where things like wave,midi,screenshot get captured.

language=
machine=vga
captures=capture
memsize=16

[render]
# frameskip -- How many frames DOSBox skips before drawing one.
# aspect -- Do aspect correction, if your output method doesn't support scaling this can slow things down!.
# scaler -- Scaler used to enlarge/enhance low resolution modes.
# Supported are none,normal2x,normal3x,advmame2x,advmame3x,hq2x,hq3x,
# 2xsai,super2xsai,supereagle,advinterp2x,advinterp3x,
# tv2x,tv3x,rgb2x,rgb3x,scan2x,scan3x.
# If forced is appended (like scaler=hq2x forced), the scaler will be used
# even if the result might not be desired.

frameskip=0
aspect=false
scaler=normal2x

[cpu]
# core -- CPU Core used in emulation: normal,simple,dynamic,auto.
# auto switches from normal to dynamic if appropriate.
# cycles -- Amount of instructions DOSBox tries to emulate each millisecond.
# Setting this value too high results in sound dropouts and lags.
# You can also let DOSBox guess the correct value by setting it to max.
# The default setting (auto) switches to max if appropriate.
# cycleup -- Amount of cycles to increase/decrease with keycombo.
# cycledown Setting it lower than 100 will be a percentage.

core=auto
cycles=max
cycleup=500
cycledown=20

[mixer]
# nosound -- Enable silent mode, sound is still emulated though.
# rate -- Mixer sample rate, setting any devices higher than this will
# probably lower their sound quality.
# blocksize -- Mixer block size, larger blocks might help sound stuttering
# but sound will also be more lagged.
# prebuffer -- How many milliseconds of data to keep on top of the blocksize.

nosound=false
rate=22050
blocksize=2048
prebuffer=10

[midi]
# mpu401 -- Type of MPU-401 to emulate: none, uart or intelligent.
# device -- Device that will receive the MIDI data from MPU-401.
# This can be default,alsa,oss,win32,coreaudio,none.
# config -- Special configuration options for the device. In Windows put
# the id of the device you want to use. See README for details.

mpu401=true
intelligent=true
device=default
config=

[sblaster]
# sbtype -- Type of sblaster to emulate:none,sb1,sb2,sbpro1,sbpro2,sb16.
# sbbase,irq,dma,hdma -- The IO/IRQ/DMA/High DMA address of the soundblaster.
# mixer -- Allow the soundblaster mixer to modify the DOSBox mixer.
# oplmode -- Type of OPL emulation: auto,cms,opl2,dualopl2,opl3.
# On auto the mode is determined by sblaster type.
# All OPL modes are 'Adlib', except for CMS.
# oplrate -- Sample rate of OPL music emulation.

type=sb16
base=220
irq=7
dma=1
hdma=5
mixer=true
oplmode=auto
oplrate=22050

[gus]
# gus -- Enable the Gravis Ultrasound emulation.
# gusbase,irq1,irq2,dma1,dma2 -- The IO/IRQ/DMA addresses of the
# Gravis Ultrasound. (Same IRQ's and DMA's are OK.)
# gusrate -- Sample rate of Ultrasound emulation.
# ultradir -- Path to Ultrasound directory. In this directory
# there should be a MIDI directory that contains
# the patch files for GUS playback. Patch sets used
# with Timidity should work fine.

gus=true
rate=22050
base=240
irq1=5
irq2=5
dma1=3
dma2=3
ultradir=C:\ULTRASND

[speaker]
# pcspeaker -- Enable PC-Speaker emulation.
# pcrate -- Sample rate of the PC-Speaker sound generation.
# tandy -- Enable Tandy Sound System emulation (off,on,auto).
# For auto Tandysound emulation is present only if machine is set to tandy.
# tandyrate -- Sample rate of the Tandy 3-Voice generation.
# disney -- Enable Disney Sound Source emulation. Covox Voice Master and Speech Thing compatible.

pcspeaker=true
pcrate=22050
tandy=auto
tandyrate=22050
disney=true

[joystick]
# joysticktype -- Type of joystick to emulate: auto (default), none,
# 2axis (supports two joysticks,
# 4axis (supports one joystick, first joystick used),
# 4axis_2 (supports one joystick, second joystick used),
# fcs (Thrustmaster), ch (CH Flightstick).
# none disables joystick emulation.
# auto chooses emulation depending on real joystick(s).
# timed -- enable timed intervals for axis. (false is old style behaviour).
# autofire -- continuously fires as long as you keep the button pressed.
# swap34 -- swap the 3rd and the 4th axis. can be useful for certain joysticks.
# buttonwrap -- enable button wrapping at the number of emulated buttons.

joysticktype=auto
timed=true
autofire=false
swap34=false
buttonwrap=true

[serial]
# serial1-4 -- set type of device connected to com port.
# Can be disabled, dummy, modem, nullmodem, directserial.
# Additional parameters must be in the same line in the form of
# parameter:value. Parameter for all types is irq.
# for directserial: realport (required), rxdelay (optional).
# for modem: listenport (optional).
# for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
# transparent, port, inhsocket (all optional).
# Example: serial1=modem listenport:5000

serial1=dummy
serial2=dummy
serial3=disabled
serial4=disabled

[dos]
# xms -- Enable XMS support.
# ems -- Enable EMS support.
# umb -- Enable UMB support.
# keyboardlayout -- Language code of the keyboard layout (or none).

xms=true
ems=true
umb=true
keyboardlayout=none

[ipx]
# ipx -- Enable ipx over UDP/IP emulation.

ipx=false

[autoexec]
# Lines in this section will be run at startup.
mount C .
c:
cls
scidhuv.exe
exit

Any thoughts?
avatar
drummond13: Any thoughts?
All the relevant sections look good. What about my video card question though? I have an idea, but if that turns out to be a dead end I have another idea.
Try changing to: aspect = true
avatar
Vagabond: Try changing to: aspect = true
I don't think it'll solve the problem, but yeah I would recommend that anyway. I hate squashed games!
Post edited May 05, 2011 by eyeball226
Alas, changing to: aspect=true did nothing :(

My card is a Geforce GTX 260. I looked at the control panel for the card, but found no way to adjust anything called "flat panel scaling". Any suggestions on where this would be in its control panel?

What makes this so baffling is that all these games were working just fine even a week ago, and now all of a sudden all of them have the same problem. I haven't made any adjustments to my video card, or any major changes to my computer setup in general. I cannot for the life of me figure out why this is happening all of a sudden.
avatar
drummond13: Any suggestions on where this would be in its control panel?
It should be under "Adjust desktop size and position" in the 'Display' category.

Select either "Use NVIDIA scaling" (stretched fullscreen) or "Use NVIDIA scaling with fixed-aspect ratio" (non-squished fullscreen with black bars on the sides).
avatar
drummond13: What makes this so baffling is that all these games were working just fine even a week ago, and now all of a sudden all of them have the same problem.
It could have been caused by a driver update, or Windows update?
Some types of monitor are recognised as being a HDTV by the Control Panel - that can also cause weird (and annoying ) stuff to happen.
avatar
DreadMoth: Select either "Use NVIDIA scaling" (stretched fullscreen) or "Use NVIDIA scaling with fixed-aspect ratio" (non-squished fullscreen with black bars on the sides).
... funny.

That option isn't available to me. (Sorry, but I was wondering why everything kept being stretched out.)
avatar
Foxhack: That option isn't available to me. (Sorry, but I was wondering why everything kept being stretched out.)
What options do you have?
Are your drivers up-to-date? (the latest version is GeForce Driver 270.71 WHQL)

For reference, my Control Panel looks like this.

EDIT: If you have an ATi/AMD card.. then I have no idea, apart from making sure everything is up-to-date. Sorry.

It's possible that your monitor might have a function for aspect correction?
Post edited May 05, 2011 by DreadMoth
That's actually how I like my old Dosbox games usually... full screen on a 28" LCD is absolutely revolting looking with old 2D games.
avatar
StingingVelvet: That's actually how I like my old Dosbox games usually... full screen on a 28" LCD is absolutely revolting looking with old 2D games.
Playing without scaling is fine on some games, but 320x240 would be quite tiny when viewed on, say, a 23" screen with a 1920x1080 native resolution.
avatar
StingingVelvet: That's actually how I like my old Dosbox games usually... full screen on a 28" LCD is absolutely revolting looking with old 2D games.
avatar
DreadMoth: Playing without scaling is fine on some games, but 320x240 would be quite tiny when viewed on, say, a 23" screen with a 1920x1080 native resolution.
I make it larger than native, just not fullscreen. I think the last one I played, Return to Zork, I used 3x.
avatar
DreadMoth: What options do you have?
Are your drivers up-to-date? (the latest version is GeForce Driver 270.71 WHQL)
The control panel says something about using this on an HDTV. My monitor is an HD one, but it's not a TV.

Apparently it's because Asus DOES NOT PROVIDE DRIVERS FOR THIS THING. It makes us use the generic Windows ones, and as such, it thinks it's an HDTV. God damnit.