VOGONS


First post, by Roller

User metadata
Rank Newbie
Rank
Newbie

gigabyte ex58-ud5
intel i7-960@3.20GHz
8GB RAM
nvidia 560ti
realtec onboard sound
win7 64bit
Albion 1.38
Gravis or SoundBlaster modes(both working)
640x480x8
DosBox 0.74

Whats happening is that the game has a visible game clock,

3D mode: 1 real sec = 1 ingame min
2D mode: 1 real sec = 3 ingame min

In other words game is running at triple speed in interior areas, and since there are alot of timed quests and characters get exhausted its getting difficult to handle.

setting core=normal didnt help, i could bring the time ratio in 2D mode to 1:1 with about 5400 counts, however everything else had gone slideshow. cputype=486_slow didnt help either.

It could be that the game is supposed to run at 1:3 ratio and just slowdowns outside, however there isnt any feelable slowdown, nor does it really make sense for a sun-day to pass in 3 minutes of real time.(and shops are closing at night)

Reply 1 of 8, by Jorpho

User metadata
Rank l33t++
Rank
l33t++

Have you tried setting cycles to fixed?

Reply 2 of 8, by Roller

User metadata
Rank Newbie
Rank
Newbie

yes, sorry for not mentioning it, double checked and started the game with following settings

core=normal
cputype=486_slow
cycles=fixed 6000

its either too fast in 2D or too slow in 3D, i cant bring them to the same speed. Well the game doesnt appear to be broken so maybe its supposed to be that way i cant quite tell. Have seen stranger settings imposed by game makers.

Here are Lets Play videos where the different clock speed is immediately visible( he is playing through dosbox according to his comments in part1 of that series)
2D: http://www.youtube.com/watch?v=rvfm-keXtwM
3D: http://www.youtube.com/watch?v=j2YwzSxUX90

Reply 3 of 8, by Jorpho

User metadata
Rank l33t++
Rank
l33t++

How about machine=vesa_nolfb ?

Reply 4 of 8, by Roller

User metadata
Rank Newbie
Rank
Newbie

Was already set

What i did now is launch VMware+win98, install the cd version of albion on it and run it straight from windows(worked surprisingly smooth). However it exhibited the same behavior. I dont know what to think of it.

Reply 5 of 8, by Jorpho

User metadata
Rank l33t++
Rank
l33t++
Roller wrote:

Was already set

Really?

How about NOLFBLIM ?

Reply 6 of 8, by Roller

User metadata
Rank Newbie
Rank
Newbie

well i have tried now

fulldouble=true/false
output=surface/ddraw
machine=vesa_nolfb/vesa_s3
...
aspect=false
scaler=none

loading NOLFBLIM.com before the game didnt seem to have any effect, interestingly the game seemed to cap @60fps in all cases. Loaded Fraps to check.

Reply 7 of 8, by Jorpho

User metadata
Rank l33t++
Rank
l33t++

I don't think you can measure the framerate of game running in DOSBox using FRAPS. You'll only get the Windows refresh rate.

Did you try VMware+Win98+NOLFBLIM? That is where it would be most likely to have an effect, I think.

Reply 8 of 8, by Roller

User metadata
Rank Newbie
Rank
Newbie

Fraps counts framebuffer switches so its possible to capture dosbox framerate if fulldouble=true. I believe thats how it is able to cap at 60fps too, the same way vsync would act. Ofc maybe dosbox still rendering all the 1000fps internally and drops them, would be quite funny, dont know. Regardless, nothing worked so far.