output=surface

Yes... that worked. It runs much better now, only a few sudders in the sound but it's playable.

Thank you very much...

I wonder.. You have a very nicely tuned dosbox.conf. What forced you to use output=opengl??

I wonder why people keep on "optimizing" their dosbox.conf's with memsize=64........

I guess they never had any experience with DOS programs and assume that like Windows the more memory you throw at DOS the better.....when it's actually the opposite.

Another thing that might come into the "DosBox is slow!!!" (Probably nothing to do with the above poster....he has 768 and his problems are likely caused by using DosBox 0.63) is that with

Memsize=64 ....Host DosBox usage is 97m
Mensize=16 (Dosbox default)....Host DosBox usage is about 49m.

Now for us computer enthusiasts we mostly have 512-2gb of ram but I'm betting that the "average" DosBox user has 256-512 of physical ram with Windows programs and bloat eating up on average around 300+mb (Conservative estimate) of memory.

So for DosBox users with only 256mb of ram and most of it's already gone anyway using 64mb for DosBox would result in less DosBox performance and Host OS performance.

The only reason for increasing DOSBox memory above 16MB is for running some applications (or protected mode games) that will take advantage of it. For the rest of games (oldies) 16MB is enough (and even 4-8MB).

Games like Tomb Raider, GTA, Battlespire, etc. definately make good use of it!

robertmo wrote:

I wonder.. You have a very nicely tuned dosbox.conf. What forced you to use output=opengl??

I really have no idea how to configure dosbox...i saw the opengl and some other settings in a thread on adventure gamers forums and were supposed to be espesially for riddle of master lu...

arrggg....Some dosbox.conf settings are computer specific. Especially "output" and "cycles".....

Might need explain this better in the README but it probably wouldn't make much difference since most new users don't use it.

DosFreak wrote:

arrggg....Some dosbox.conf settings are computer specific. Especially "output" and "cycles".....

Might need explain this better in the README but it probably wouldn't make much difference since most new users don't use it.

The guy that had posted the settings said to change the output to "opengl" if you have anything above GF2 ...i had a radeon9600p so i thought it should be ok... I guess i shouldn't believe everything i read 😒

Nah, actually the "opengl" setting is terrible in DosBox for ATI cards if your using DosBox 0.63 and below.

It works just fine in the latest CVS builds of DosBox which you can grab from my signature below. (Use either gulikoza's or ykhwong's).

Also "opengl" will blur the graphics so if you notice a loss in graphics quality then use "openglnb".

DosFreak wrote:

Nah, actually the "opengl" setting is terrible in DosBox for ATI cards if your using DosBox 0.63 and below.

It works just fine in the latest CVS builds of DosBox which you can grab from my signature below. (Use either gulikoza's or ykhwong's).

Also "opengl" will blur the graphics so if you notice a loss in graphics quality then use "openglnb".

I tried ykhwong's bulid with opengl setting... The graphics worked fine but the sound did some weird things. It was like a record playing back, some times in high speed and sometimes slow.

In recent CVS the sound slows down/speeds up instead of skipping.

This may happen if your overloading DosBox....if your not overloading dosbox then it's a bug.

You can tell if your overloading dosbox by monitoring Task Manager and making sure that DosBox processor usage does not exceed 90%.

So if i overload it what shoul i do?.... reduce the cpu cycles? I use the same configuration as in 0.63.

Yeah, reduce cycles and use frameskip if needed.

I noticed that the latest DOSBOX is more sensitive to sound. I could run Windows 3.1 at 15000 cycles before, now only 8000 before my sound messes up. Oddly enough, at 15000 cycles I rarely reached 100% CPU.