Graphics trouble

Here you can post questions about GP2, your favourite GP2 things and errorreports/problems!
User avatar
GP2tifoso28
GP2 Starter
Posts: 86
Joined: 29.09.2015, 14:21

Re: Graphics trouble

Post by GP2tifoso28 »

ismael wrote:The game is running, but has issues. At first, it started fine but then was crashing when I got to Car Setup. Then I thought I might be exxagerating in the resolution and chaged it to 1024x768. It works without crashing, but its sort like what I'm playing through D-Fend Reloaded, I can't add mirrors and no way trying SVGA. It's good for racing with All Trackside Objects and smoke in the mirrors, and cycles must be at 105%.

(Is it possible, and/or convenient, to make cycles higher than 105% with Ctrl+F12?
I don't think so mate, with the cycles set to max dosbox will just use all the available processing power. I don't think its possible to overclock it. I would suggest re installing the game and attempting it on a clean install, because I found my game sometimes did strange things when modding it, which is why I now copy and paste a clean install every time I mod and always leave an unmodded version on my PC.

In the configuration file you can try changing the output from opengl to surface or ddraw, as I dont think these use as much power. Also, under [cpu] you can try changing the CPU type from auto to pentium_slow. The auto setting may be detecting a 486.

Another thing to try is to right click on your shortcut and add -noconsole into the target box. This will remove the unnecessary secondary dosbox window which may be consuming processing power.

My fear is that your PC can not emulate at a higher rate to what its doing. According to this https://www.dosbox.com/wiki/Performance ... quivalency you are sitting somewhere between a 486 and a Pentium 133... and I can say from personal experience that an actual 486 wont run GP2 in VGA at anywhere near full graphics.. and with SVGA it would probably blow up. Im not sure how accurate that actually is though because I'm running on a core 2 at 2.33 GHZ with 2gb RAM and Windows Vista and can play GP2 fine in SVGA even with GP2LAP.

Maybe someone else lurking around here has some more suggestions?
roland ratzenberger
GP2 Racer
Posts: 356
Joined: 18.03.2010, 23:51

Re: Graphics trouble

Post by roland ratzenberger »

GP2tifoso28 wrote:OK mate, now delete whatever text is in your configuration file and paste this text into it. Notice right at the bottom of this are the commands that you would normally have to enter into the dos prompt every time you open dosbox. Now it will be automated and GP2 should launch just by clicking the shortcut you created on your desktop. Copy everything below and let me know how it runs.

# This is the configurationfile for DOSBox 0.74. (Please use the latest version of DOSBox)
# Lines starting with a # are commentlines and are ignored by DOSBox.
# They are used to (briefly) document the effect of each option.

[sdl]
# fullscreen: Start dosbox directly in fullscreen. (Press ALT-Enter to go back)
# fulldouble: Use double buffering in fullscreen. It can reduce screen flickering, but it can also result in a slow DOSBox.
# fullresolution: What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
# Using your monitor's native resolution with aspect=true might give the best results.
# If you end up with small window on a large screen, try an output different from surface.
# windowresolution: Scale the window to this size IF the output device supports hardware scaling.
# (output=surface does not!)
# output: What video system to use for output.
# Possible values: surface, overlay, opengl, openglnb, ddraw.
# autolock: Mouse will automatically lock, if you click on the screen. (Press CTRL-F10 to unlock)
# sensitivity: Mouse sensitivity.
# waitonerror: Wait before closing the console if dosbox has an error.
# priority: Priority levels for dosbox. Second entry behind the comma is for when dosbox is not focused/minimized.
# pause is only valid for the second entry.
# Possible values: lowest, lower, normal, higher, highest, pause.
# mapperfile: File used to load/save the key/event mappings from. Resetmapper only works with the defaul value.
# usescancodes: Avoid usage of symkeys, might not work on all operating systems.

fullscreen=false
fulldouble=false
fullresolution=desktop
windowresolution=1366x768
output=opengl
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper-0.74.map
usescancodes=true

[dosbox]
# language: Select another language file.
# machine: The type of machine tries to emulate.
# Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe.
# captures: Directory where things like wave, midi, screenshot get captured.
# memsize: Amount of memory DOSBox has in megabytes.
# This value is best left at its default to avoid problems with some games,
# though few games might require a higher value.
# There is generally no speed advantage when raising this value.

language=
machine=svga_s3
captures=capture
memsize=63

[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.
# If 'forced' is appended, then the scaler will be used even if the result might not be desired.
# Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x.

frameskip=0
aspect=false
scaler=hq3x

[cpu]
# core: CPU Core used in emulation. auto will switch to dynamic if available and appropriate.
# Possible values: auto, dynamic, normal, simple.
# cputype: CPU Type used in emulation. auto is the fastest choice.
# Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 386_prefetch.
# cycles: Amount of instructions DOSBox tries to emulate each millisecond.
# Setting this value too high results in sound dropouts and lags.
# Cycles can be set in 3 ways:
# 'auto' tries to guess what a game needs.
# It usually works, but can fail for certain games.
# 'fixed #number' will set a fixed amount of cycles. This is what you usually need if 'auto' fails.
# (Example: fixed 4000).
# 'max' will allocate as much cycles as your computer is able to handle.
#
# Possible values: auto, fixed, max.
# cycleup: Amount of cycles to decrease/increase with keycombo.(CTRL-F11/CTRL-F12)
# cycledown: Setting it lower than 100 will be a percentage.

core=dynamic
cputype=auto
cycles=max
cycleup=10
cycledown=20

[mixer]
# nosound: Enable silent mode, sound is still emulated though.
# rate: Mixer sample rate, setting any device's rate higher than this will probably lower their sound quality.
# Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# blocksize: Mixer block size, larger blocks might help sound stuttering but sound will also be more lagged.
# Possible values: 1024, 2048, 4096, 8192, 512, 256.
# prebuffer: How many milliseconds of data to keep on top of the blocksize.

nosound=false
rate=44100
blocksize=1024
prebuffer=20

[midi]
# mpu401: Type of MPU-401 to emulate.
# Possible values: intelligent, uart, none.
# mididevice: Device that will receive the MIDI data from MPU-401.
# Possible values: default, win32, alsa, oss, coreaudio, coremidi, none.
# midiconfig: Special configuration options for the device driver. This is usually the id of the device you want to use.
# See the README/Manual for more details.

mpu401=intelligent
mididevice=default
midiconfig=

[sblaster]
# sbtype: Type of Soundblaster to emulate. gb is Gameblaster.
# Possible values: sb1, sb2, sbpro1, sbpro2, sb16, gb, none.
# sbbase: The IO address of the soundblaster.
# Possible values: 220, 240, 260, 280, 2a0, 2c0, 2e0, 300.
# irq: The IRQ number of the soundblaster.
# Possible values: 7, 5, 3, 9, 10, 11, 12.
# dma: The DMA number of the soundblaster.
# Possible values: 1, 5, 0, 3, 6, 7.
# hdma: The High DMA number of the soundblaster.
# Possible values: 1, 5, 0, 3, 6, 7.
# sbmixer: Allow the soundblaster mixer to modify the DOSBox mixer.
# oplmode: Type of OPL emulation. On 'auto' the mode is determined by sblaster type. All OPL modes are Adlib-compatible, except for 'cms'.
# Possible values: auto, cms, opl2, dualopl2, opl3, none.
# oplemu: Provider for the OPL emulation. compat might provide better quality (see oplrate as well).
# Possible values: default, compat, fast.
# oplrate: Sample rate of OPL music emulation. Use 49716 for highest quality (set the mixer rate accordingly).
# Possible values: 44100, 49716, 48000, 32000, 22050, 16000, 11025, 8000.

sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
sbmixer=true
oplmode=auto
oplemu=default
oplrate=44100

[gus]
# gus: Enable the Gravis Ultrasound emulation.
# gusrate: Sample rate of Ultrasound emulation.
# Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# gusbase: The IO base address of the Gravis Ultrasound.
# Possible values: 240, 220, 260, 280, 2a0, 2c0, 2e0, 300.
# gusirq: The IRQ number of the Gravis Ultrasound.
# Possible values: 5, 3, 7, 9, 10, 11, 12.
# gusdma: The DMA channel of the Gravis Ultrasound.
# Possible values: 3, 0, 1, 5, 6, 7.
# 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=false
gusrate=44100
gusbase=240
gusirq=5
gusdma=3
ultradir=C:\ULTRASND

[speaker]
# pcspeaker: Enable PC-Speaker emulation.
# pcrate: Sample rate of the PC-Speaker sound generation.
# Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# tandy: Enable Tandy Sound System emulation. For 'auto', emulation is present only if machine is set to 'tandy'.
# Possible values: auto, on, off.
# tandyrate: Sample rate of the Tandy 3-Voice generation.
# Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# disney: Enable Disney Sound Source emulation. (Covox Voice Master and Speech Thing compatible).

pcspeaker=true
pcrate=44100
tandy=auto
tandyrate=44100
disney=false

[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).
# (Remember to reset dosbox's mapperfile if you saved it earlier)
# Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none.
# timed: enable timed intervals for axis. Experiment with this option, if your joystick drifts (away).
# 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=false

[serial]
# serial1: 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 (optional).
# for directserial: realport (required), rxdelay (optional).
# (realport:COM1 realport:ttyS0).
# for modem: listenport (optional).
# for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
# transparent, port, inhsocket (all optional).
# Example: serial1=modem listenport:5000
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial2: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial3: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial4: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.

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=auto

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

ipx=false

[autoexec]
# Lines in this section will be run at startup.
# You can put your MOUNT lines here.

mount c c:\dosbox\c
c:
cd gp2test
gp2.exe



hello my friend ,, i have used your configuration file and gp2 in my laptop runs better than ever.. but with only one problem.. mouse is locked and i cant use it when i play.. of course it is not a big problem because i can make also the work through keyboard but if you could tell me a way to fix that i would be gratefull.. IN ANY CASE THANK YOU A LOT
User avatar
GP2tifoso28
GP2 Starter
Posts: 86
Joined: 29.09.2015, 14:21

Re: Graphics trouble

Post by GP2tifoso28 »

Hi Roland, I'm glad it works well. One thing I would suggest first is to make sure you put your resolution in where it says windowresolution=1366x768.. make sure you insert the correct value there or else it might cut off some of the picture, because this is set up for a 4:3 aspect ratio.

Regarding the mouse issue, I've had the same problem before and what works for me is to not switch to fullscreen until after the opening sequence has finished (or you've pressed escape to end it, I like to watch it though), then wait for the menu to come up and click on the screen. The mouse should now work and you can switch to fullscreen. That's what works for me.

If that doesn't work I would probably try changing autolock=true to autolock=false. This is experimental and I have no idea what it actually does because I haven't personally tried it. However, this is what dosbox says about the matter - "autolock: Mouse will automatically lock, if you click on the screen. (Press CTRL-F10 to unlock)".... sounds like it may have something to do with the problem.

Hope that helps let me know how it goes mate
roland ratzenberger
GP2 Racer
Posts: 356
Joined: 18.03.2010, 23:51

Re: Graphics trouble

Post by roland ratzenberger »

GP2tifoso28 wrote:Hi Roland, I'm glad it works well. One thing I would suggest first is to make sure you put your resolution in where it says windowresolution=1366x768.. make sure you insert the correct value there or else it might cut off some of the picture, because this is set up for a 4:3 aspect ratio.

Regarding the mouse issue, I've had the same problem before and what works for me is to not switch to fullscreen until after the opening sequence has finished (or you've pressed escape to end it, I like to watch it though), then wait for the menu to come up and click on the screen. The mouse should now work and you can switch to fullscreen. That's what works for me.

If that doesn't work I would probably try changing autolock=true to autolock=false. This is experimental and I have no idea what it actually does because I haven't personally tried it. However, this is what dosbox says about the matter - "autolock: Mouse will automatically lock, if you click on the screen. (Press CTRL-F10 to unlock)".... sounds like it may have something to do with the problem.

Hope that helps let me know how it goes mate

ok mate i will try your proposal,, but in any case thank you again, because as i have said it is not a big problem
roland ratzenberger
GP2 Racer
Posts: 356
Joined: 18.03.2010, 23:51

Re: Graphics trouble

Post by roland ratzenberger »

GP2tifoso28 wrote:Hi Roland, I'm glad it works well. One thing I would suggest first is to make sure you put your resolution in where it says windowresolution=1366x768.. make sure you insert the correct value there or else it might cut off some of the picture, because this is set up for a 4:3 aspect ratio.

Regarding the mouse issue, I've had the same problem before and what works for me is to not switch to fullscreen until after the opening sequence has finished (or you've pressed escape to end it, I like to watch it though), then wait for the menu to come up and click on the screen. The mouse should now work and you can switch to fullscreen. That's what works for me.

If that doesn't work I would probably try changing autolock=true to autolock=false. This is experimental and I have no idea what it actually does because I haven't personally tried it. However, this is what dosbox says about the matter - "autolock: Mouse will automatically lock, if you click on the screen. (Press CTRL-F10 to unlock)".... sounds like it may have something to do with the problem.

Hope that helps let me know how it goes mate

hello again mate.. i have tried you suggestion.. to begin with you were right , in windowed mode the mouse works perfectly,, but when i try fullscreen the mouse does not work.. i prefer to play in fullscreen as far as i am concerned.. but as i have said the game in overall runs very smootly and needless to say your solution is much better than the one that i had proposed earlier on this thread. to sum up i have no problem to <<sacrifice>> the mouse if i the gp2 runs so smoothly as it is .. the menus can aslo can be fixed be keyboard,, and the driving has only to do with keyboard,, so not a big deal,, but i wll try some races in the windowed mode just to see how it is... THANK YOU AGAIN MATE
roland ratzenberger
GP2 Racer
Posts: 356
Joined: 18.03.2010, 23:51

Re: Graphics trouble

Post by roland ratzenberger »

GP2tifoso28 wrote:Hi Roland, I'm glad it works well. One thing I would suggest first is to make sure you put your resolution in where it says windowresolution=1366x768.. make sure you insert the correct value there or else it might cut off some of the picture, because this is set up for a 4:3 aspect ratio.

Regarding the mouse issue, I've had the same problem before and what works for me is to not switch to fullscreen until after the opening sequence has finished (or you've pressed escape to end it, I like to watch it though), then wait for the menu to come up and click on the screen. The mouse should now work and you can switch to fullscreen. That's what works for me.

If that doesn't work I would probably try changing autolock=true to autolock=false. This is experimental and I have no idea what it actually does because I haven't personally tried it. However, this is what dosbox says about the matter - "autolock: Mouse will automatically lock, if you click on the screen. (Press CTRL-F10 to unlock)".... sounds like it may have something to do with the problem.

Hope that helps let me know how it goes mate
something that i didn understand is this.. can you start dos box in windowed mode and then put it immediately to fullscreen? when i say immediately i do not mean via dos box configuration


EDIT: after a little search i have seen that what i say is possible by using ALT+ENTER.. is this what you use??
User avatar
GP2tifoso28
GP2 Starter
Posts: 86
Joined: 29.09.2015, 14:21

Re: Graphics trouble

Post by GP2tifoso28 »

Yeah mate that's what I mean. Set it to Window mode, start the game, then leave it in Window mode until the first menu comes up. Now there should be 2 mouses on screen, your windows mouse and your dosbox mouse. Click your windows mouse around the GP2 screen (anywhere within the dosbox Window) and now the DOS mouse should activate. Now if you press alt+enter it should go to full screen with the mouse. That's what I normally do, I hope it makes sense
roland ratzenberger
GP2 Racer
Posts: 356
Joined: 18.03.2010, 23:51

Re: Graphics trouble

Post by roland ratzenberger »

GP2tifoso28 wrote:Yeah mate that's what I mean. Set it to Window mode, start the game, then leave it in Window mode until the first menu comes up. Now there should be 2 mouses on screen, your windows mouse and your dosbox mouse. Click your windows mouse around the GP2 screen (anywhere within the dosbox Window) and now the DOS mouse should activate. Now if you press alt+enter it should go to full screen with the mouse. That's what I normally do, I hope it makes sense


problem solved mate.. now mouse works perfectly... thanks again man :D :D :D :D :D :D :D
User avatar
GP2tifoso28
GP2 Starter
Posts: 86
Joined: 29.09.2015, 14:21

Re: Graphics trouble

Post by GP2tifoso28 »

No problems mate enjoy :)
ismael
GP2 Racer
Posts: 395
Joined: 02.05.2016, 14:58

Re: Graphics trouble

Post by ismael »

Once again, thank you all for your notes. Perhaps my problem is the one mentioned above by RRemedio, and the computer is just not powerful enough. Now I learned about the DOSBox equivalency https://www.dosbox.com/wiki/Performance ... quivalency and that's problably the root of the problem here. Anyway, the game is now a little faster and these advice will be precious after my next laptop upgrade!
Post Reply