Xelasarg wrote:Hang on, cycles are not MHz (or kHz). It's not even linear, you can only guess how fast the emulated machine is. 60000 cycles are not 60 MHz, but at least equal to something like a 120 MHz Pentium.
You don't need so much speed for Aladdin, set something around 12000 - 14000 cycles (~386/40 MHz), that should be more than enough. Have you tried changing output=opengl or output=ddraw in your dosbox.conf? Or you could use ykhwong's build (http://ykhwong.x-y.net/), I think it features a vsync option.
I have tested ddraw and all other outputs but it doesnt fix the jump lines.
So if there isnt any other settings left? i suppose the last thing to try is to make sure the added V-sync settings inside
ykhwong's build (http://ykhwong.x-y.net/) are correctly chosen
This didnt fix it so far
[vsync]
# vsyncmode: Synchronize vsync timing to the host display. Requires calibration within dosbox.
# Possible values: off, on, force, host.
# vsyncrate: Vsync rate used if vsync is enabled. Ignored if vsyncmode is set to host (win32).
# Possible values:.
vsyncmode=force
vsyncrate=75
I also wanna know what the ONLY
(it dont call itself for "opengl" longer?)
V-sync setting existing in ATI Catalyst...
(se my attach in my prev post)
...shall be setted to so it cant limit and possible override dosbox
own V-sync settings, perhps these 2 shall even co-operate with eachother?.
My windows/screen resolution
is 60 Hz through 1680X1050 i dont know if this
can ever affect inside dosbox, but i wanna report every possibility
eL_PuSHeR wrote:Tried it and it does a minor tearing, but so minor it's almost negligible.
I am playing with cycles max 50% and ddraw settings. For sound I chose SB and AWE32.
Setting it to 50 % instead of 30000 made Al move like a 😵 pensioner on my computer honestley. But i guess your computer can be so modern and faster! that the ingame tempo transform into the good old Aladdin days by setting it to 50 %?.