Look man checks these:
core=dynamic
cputype=auto
cycles=fixed 30000

thats my setup works like magic

BladeX wrote:

Look man checks these: core=dynamic cputype=auto cycles=fixed 30000 […]
Show full quote

Look man checks these:
core=dynamic
cputype=auto
cycles=fixed 30000

thats my setup works like magic

Thanks that was some 😉 increase, however
do you got an alternate value perhaps?.

The slow run is gone the tempo was corrected,
but there is what do you call it? "frame rate" issue
at the top of the screen when im in the air jumping

Im on win 7 by the way

That can be an bug in the game/dosbox executable, but it isnt in middle of game window. since its up there, idk if thats so big deal 😉. but no problem i always play whit those settings, they are like GUD!

Could it be a VSYNC issue?

That might be possible. Hmmm but that will be different, how you will fix that. I mean El you gotta have some ideas?

BladeX wrote:

That can be an bug in the game/dosbox executable, but it isnt in middle of game window. since its up there, idk if thats so big deal 😉. but no problem i always play whit those settings, they are like GUD!

Well for me its a bigger deal, i want it to feel like the 486 experience.🤑

The question is what would happen if i change your GUD! core value?
up or down

eL_PuSHeR wrote:

Could it be a VSYNC issue?

Is that sync related to my windows 7 screen settings or dosbox config?
if so.

Yeah you must have some idea? EL 😅.

My GUD core value hmmm well 30k is 30Mhz prozz what i read in dosbox wiki and so on and so on so if you want the feeling more better and better just raise the value the bigger it is the faster it goes.

And that vsync boeh... idk at all maybe its like 256 colours + run 460x600 /or what ever screen) to now showing that (+ full screen).

I dont suppose you would wanna try magic carpet??

BladeX wrote:

My GUD core value hmmm well 30k is 30Mhz prozz what i read in dosbox wiki and so on and so on so if you want the feeling more better and better just raise the value the bigger it is the faster it goes.

And that vsync boeh... idk at all maybe its like 256 colours + run 460x600 /or what ever screen) to now showing that (+ full screen).

I dont suppose you would wanna try magic carpet??

What do you want me to do with that info? 😊

"256 colours + run 460x600"

Is it a setting inside dosbox config (if so where in the doc!?)
or a setting for setting windows resolution before even start dosbox?

Im not sure i wanna get myself all the way to
http://www.youtube.com/watch?v=92dIgMVNLgc
with this thin red line at the top of the screen.

Seriosly 🤣 i dont know what magic carpet is, but it
takes to long for my brain to learn to handle new emulations
so i think i stick to Dosbox.

maybe not confuse you anymore 😀 but atleast the slowdown is gone.

Also the Magic carpet is dosbox game and i know very easy way to deal whit the so called hard "emulations" these people say whit dosbox... mrhm!

But meh its hard to find players to play anything. 😀

So good luck i suppose!?

BladeX wrote:

That might be possible. Hmmm but that will be different, how you will fix that. I mean El you gotta have some ideas?

Try tinkering in your graphic card driver control panel for some vsycn settings, if available.

hmmm so thats how you do that, i was wondering how ya change the settings. But are you sure Klopp will understand this? i mean how will he know where to look 😳.

Nowaydays most graphic cards have a control panel of some sort. Just browse all options. It's must not be that difficult.

Hmmm well it is true that my AMD (Ati) radeon graphics card, came whit its own options system. Where to trim dat on some programs... hmmm i guess youre right, it cant be that hard to figure something like this out. THX again mate i hope your computer fares you well 😁

BladeX wrote:

hmmm so thats how you do that, i was wondering how ya change the settings. But are you sure Klopp will understand this? i mean how will he know where to look 😳.

eL_PuSHeR wrote:

Nowaydays most graphic cards have a control panel of some sort. Just browse all options. It's must not be that difficult.

I think i changed V-sync now, bur it didnt remove the annoying lines,
its pretty much of this glitches for it to disturb the gameplay.

I changed to 60000 mhz CPU setting now, thats almost the value of
my old 486, it didnt remove the v-sync glitches.

Perhpas sett even higher than 6000? 66000...

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.

On the graphics driver side, the VSync setting should be the one for OpenGL apps (assuming there's any other).
On the DOSBox side, set output=opengl or openglnb.

One warning about VSync, though: If DOSBox takes advantage of a VSync setting like that, slowdowns are expected in some portions of some games. A good example is the title screen fading in Commander Keen 4-6 being *much* slower with VSync turned on.
I am not currently aware of a way to solve the slowdowns while also having proper VSync. So, either you have no severe slowdowns, or you have less tearing, but not both.

EDIT: Ah, someone else has already replied while I've been close to doing the same. That happens. 😀

Wikis arent always 100% accurate, what i made in 1 of my posts. But yes there is always explanation to everything (unless its unknown origin) so yeah. Topics starting to be rather big, idk should this start to be closed or something since its probably gonna end to keep the glitches and just continue gameplay.

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.

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 %?.