|
Post by sexyshinobu on Nov 21, 2009 10:25:21 GMT
^_^ I am able to open and run Tyrian in dosbox, and have it auto mount too... but the PROBLEM I am having is whenever I have it in Fullscreen, it slows so far down that its unplayable... It runs fine in window mode, but the issue comes up whenever it goes into fullscreen. SO what exactly do I need to help it run flawlessly in full window mode? If not then what do I need to have it like full window with out the excessive slowdown? I did read the custom part of the forum to try to make it faster, but it doesn't work well the second it gets to full window mode.
^_^ ABOUT my computer specs... its one of the highest end specs for a laptop to this day. custom build for video games ^_^ so it has the best specs required for any game that needs it.
|
|
|
Post by sexyshinobu on Nov 21, 2009 10:36:27 GMT
[sdl]
fullscreen=false fulldouble=false fullresolution=original windowresolution=1024x768 output=ddraw autolock=true sensitivity=100 waitonerror=true priority=higher,normal mapperfile=mapper.txt usescancodes=true
[dosbox]
language= machine=svga_s3 captures=capture memsize=64
[render]
frameskip=0 aspect=true scaler=normal3x
[cpu]
core=dynamic cputype=auto cycles=auto cycleup=500 cycledown=20
[mixer]
nosound=false rate=22050 blocksize=2048 prebuffer=10
[midi]
mpu401=intelligent mididevice=default midiconfig=
[sblaster]
sbtype=sb16 sbbase=220 irq=7 dma=1 hdma=5 sbmixer=true oplmode=auto oplemu=default oplrate=22050
[gus]
gus=false gusrate=22050 gusbase=240 gusirq=5 gusdma=3 ultradir=C:\ULTRASND
[speaker]
pcspeaker=true pcrate=22050 tandy=auto tandyrate=22050 disney=true
[joystick]
joysticktype=none timed=true autofire=false swap34=false buttonwrap=true
[serial]
serial1=dummy serial2=dummy serial3=disabled serial4=disabled
[dos]
xms=true ems=true umb=true keyboardlayout=auto
[ipx]
ipx=false
[autoexec]
mount c c:\users\sexyshinobu\desktop\videog~1\tyrian.
These were the settings that has actually helped my game work in a window form. Sure its not fullscreen but it stops any kind of slow down ^_^
|
|
|
Post by yuriks on Nov 21, 2009 18:09:18 GMT
You should get rid of output=ddraw, use something else. Also, set fullresolution to your display's native res.
|
|
|
Post by mdz8 on Dec 3, 2009 10:49:27 GMT
I'd like to suggest another possible way to better understand the problem.
Start at native resolution with no scaler and windowed. Take measure of your CPU% (it doesn't need to be accurate, just go for the windows utility). Test again using fullscreen and the same settings.
Redo the test using the scaler of choice with 'forced' resolution. Normal3x is fine.
As Yuriks says, it is possible fullscreen DirectDraw is managed differently than windowed DirectDraw. Personally, I have never seen much of a difference on my tests but as I said, looks like most systems I've dealt with were horribly screwed in the beginning...
I'd be interested in knowing the results. NOTE: as multicore processors hide most of those information, I am truly more interested in your CoreUtilization than CPU%... just multiply by the number of threads.
I expect performance will be almost the same regardless of (scaler, resolution) settings...
|
|