Boulder Dash Forum

Another thing I want to say for a long time: Can you include a dialog in preferences where the joystick control keys can be defined? Would be nice if someone do not want to use the cursor keys for directions...

Wow, that replay function is *NICE*! Thanks. The ability to pick up and play in the middle of your replay is really cool - and the list of replays is easy to understand and manage.

I also greatly appreciate the faster scrolling in gdash - I almost never use sdash anyway. The horizontal smooth scroll currently works a little better than the vertical, as I can make the game "stutter" by moving to the bottom of the screen.

- Also I have been trying this out for a while before I posted anything, but there is something funky about the framerate with atari timing (it may be true also with others, but I never played on a C64, so can't be sure). The smoothness and consistency of the frames, which was really smooth on the original atari, has become worse with this release, even though it was never quite right to begin with. If you load up BD1 cave D level 2, the gameplay is very jumpy and un-smooth. (Is this the case with anyone else - just in case it's something with my computer?) I guess that the formula that is used to calculate the timing in the cave is accurate, but after that it should be quite smooth to play. Thanks for all the work on this.

-Ben

EDIT: My game crashes when I try to open the Preferences tab. ??

BadDog73 wrote:The smoothness and consistency of the frames, which was really smooth on the original atari

You talk about the game itself, or the scrolling?

BadDog73 wrote:EDIT: My game crashes when I try to open the Preferences tab. ??

Which preferences tab? What happens exactly?

I mean the game itself - the consistency of the framerate. If you play Boulder Rush and then play gdash, it's very apparent.

The main menu bar, PLAY > Preferences. I get a CTD suddenly.

BadDog73 wrote:I mean the game itself - the consistency of the framerate. If you play Boulder Rush and then play gdash, it's very apparent.

I think I know what the problem is - the game is in sync with the graphics. I will change that in the next release.

BadDog73 wrote:The main menu bar, PLAY > Preferences. I get a CTD suddenly.

Try these:
= Delete the GDash configuration directory, C:\Documents and Settings\your user\Application Data\gdash.
If it not works, try:
= Remove GDash from control panel, then delete C:\Program Files\GDash. Then reinstall.
Let me know what happened!

Yes, I thought it might be an incompatible config file, but unfortunately deleting the application data/gdash directory and then reinstalling the game does not fix it.

Sorry, wish I could give you more info...

I'll try the latest version of GDash on my PC with Windows XP SP2 this evening. Let's see if there is a problem on my PC, too. The latest Unix version is working on MacOS X 10.4.11 correctly without any troubles.

Can you explain what do you mean with "The main menu bar, PLAY > Preferences. I get a CTD suddenly." exactely?

That preferences dialog problem seems to be related to windows only. I tried it on a Win2003, and hanged the app. I will check it - now I can see what happens.

I updated the game, corrected the preferences dialog bug. Now it opens correctly also on windows. I did not change the version number, but the files on the jutas server are the new ones.

Hi, there seems to be a problem with level testing at the new version. No matter which level is actually shown, when I want to test my cave, it always goes to level 1...

hi

i uploaded a bugfix version, 20081216.
it has a new timing algorithm. turned out that the old one, which worked very well on linux, was very bad on windows.
this is much better on both. also the level-1-testing-only bug is corrected.
well, nothing else now.

by

Hi cirix,
I think sth must have gone wrong with your timing fix. I am a Win user (xp) and on my computer the timing on the latest Gdash version is by a factor 3/2(!) too slow (withOUT PAL timing!). You stated that the older versions ran wrong on Windows, but I haven't noted any timing errors then (and if there was a mistake, it was definitely not as severe as it is now!)

PS: The problem only concerns the absolute timing I've checked it: I set the frame time to 200 ms and walked 140 cells, and this lasted exactly 28 "Gdash seconds" (and 42 real seconds!)

Hi

that really SUCKS.
does the sdl version also run slow?
i make some older versions downloadable.

bye

As far as I can tell the latest version does not behave slower than the version before on my MacOS X 10.4.11. No difference if I use PAL timing or not. If I discover something strange I'll report that.

CWS: please try it on a windows, too!