Bad Mood : Falcon030 'Doom'

[dml]

It runs fine at 75Mhz, can even go higher but the stuck key syndrome
becomes worse and worse. Approaching 95Mhz may be the tipping
point.

Keep in mind though, 95Mhz is my normal boot up speed. I run all
my other software from there with no problems. No crashes, freezes
or anything else. I tried 100mhz and above but then I do get random
crashes during bootup and after. 95Mhz has been very stable for me.

It is quite strange. I can't rule anything out until I set up a real CT60 and try. However there are no timing-related optimizations in BadMooD outside of the 3D rendering viewport or AI manager. i.e. nothing during startup, the title screen or menus. That stuff only kicks in once the first level loads.

So any speed-related issues earlier than that are - unexpected!

It's still possible something is wrong with the interrupt setup code - but that's all. If not that, it must be a hardware or CT60 driver issue.

Will look closer at the interrupt setup code when I have time, in case there is a race condition, but it does seem a bit unlikely.

[calimero]

Just to ask: what is latest and greatest version for unmodified Falcon? (and is it possible to turn on FPS counter in it?)

Version for unmodified Falcon is capped to 12FPS, right?

[dml]

Just to ask: what is latest and greatest version for unmodified Falcon? (and is it possible to turn on FPS counter in it?)

Version for unmodified Falcon is capped to 12FPS, right?

The last one was plain v0.33 and is capped to 12FPS.

I was going to rebuild all the machine variants as v0.34 and get them linked properly from the site once the 060 looked like it was working on different boxes.

[calimero]

nice

I did not have time for play last few days so I did not even try last few builds for 060...

[ctirad]

I have a bugreport. I tried the latest BM on machine with Blow UP FX RAM card (10MB of pseudo FastRAM on expansion slot, so I have 14MB RAM but divided to 4MB of STRAM + and 10MB of "FastRAM") and the game thinks it is an 4MB machine and freezes at "audiodevice:: open" line. The alpha version worked on this machine.

[dml]

I have a bugreport. I tried the latest BM on machine with Blow UP FX RAM card (10MB of pseudo FastRAM on expansion slot, so I have 14MB RAM but divided to 4MB of STRAM + and 10MB of "FastRAM") and the game thinks it is an 4MB machine and freezes at "audiodevice:: open" line. The alpha version worked on this machine.

Ok, thanks. I'll look into it - but there might be a delay as I'm working on something else currently.

Pretty sure I know what's wrong so it should be an easy fix...

[calimero]

hi doug,
what is the status of -timedemo in latest BadMood build? (and where I can find it )
Is posible to compare it to timedemo on PC Id Software version of Doom?

[dml]

hi doug,
what is the status of -timedemo in latest BadMood build? (and where I can find it )
Is posible to compare it to timedemo on PC Id Software version of Doom?

Hi,

Unfortunately it's not possible to make a representative timedemo with BadMood. To do so requires using the same demo file from PC, which BM is not compatible with. It can only play its own recorded demos.

This is because the game AI and related code was modified to make it run fast at 16mhz. By reverting those changes it becomes possible to use the PC demo files, but then it will run very slowly - so there's no point really.

[dml]

Oh and where you can find it - in the d/l area of viking272's site: http://devilsdoorbell.com/

However the build is due for a refresh, with some recent improvements. I won't get around to it though until I'm done with this other thing.

[calimero]

ok, thanx!

than I guess only solution would be to start same level, with FPS counter, on both machines and compare these numbers

how can I enable FPS counter in BadMood?

[dml]

ok, thanx!

than I guess only solution would be to start same level, with FPS counter, on both machines and compare these numbers

how can I enable FPS counter in BadMood?

Errr... you could try the '0' key.

I can't actually remember if the FPS counter is in the release build. If not, I'll add it for the next update.

Also bear in mind the FPS varies with....

- monitor type
- window size
- detail modes (there are 4 mode combinations on H/V axes)

...so you'd have to decide what to compare with. A typical player's preferred config, or a 1:1 comparison with PC (which isn't necessarily the same thing!)

[dml]

BTW I think now that it would be possible to redo the Doom engine to use Quake-like rendering, such that the FPS would be approximately the same at low detail, and for typical scenery, but would actually be faster for high-density scenery, because the Quake engine impl. on Falcon is much more work-efficient for non-pixeldrawing aspects.

Probably not worth the effort overall given limited benefits for Doom levels but interesting to consider

[calimero]

Hi,

Here's one more try: https://dl.dropboxusercontent.com/u/129 ... _test7.zip

I just try this version 7 on CT63 76MHz, cleand (ctrl) boot, RGB, and it works good.
I also try it with NVDI and it works good.

btw this version have "game tick" as original DOS Doom, 35Hz?
...and there is no FPS counter when press '0'...


and on viking272's site: http://devilsdoorbell.com/ there is only 0.32 version ?!?

[dml]

Hi, well I'm glad you found one that works.

I don't remember what the tick is configured at - some of the 060 tests were set to 35Hz like PC, and with HQ audio. I expect tou'll find the answer near the original post for the link.

All of the 030-targeted builds are configured to 12Hz tick IIRC.

I'll add FPS counter next time I make a release. I have some other changes pending. Just busy at the moment with the other thing.

[calimero]

but all 060 builds work on my configuration so far... I did not try other speeds except my standard 75-76MHz

DarkLord have issues when running 060 at more than IIRC 90MHz...

[DarkLord]

Yeah, that was pretty much it. Lower speeds worked okay though. Great stuff.

[dml]

Hi! I've been busy again.

Have re-optimized the DSP core for BadMooD. Not huge changes, but a bit faster anyway. Have also added a FPS counter on the '0' key since it was missing in previous builds.

https://dl.dropboxusercontent.com/u/129 ... m_v035.zip


There are 030 and 060 versions, plus 060 version with no FPS capping. The 030 version is minus MMU stuff so it stands a chance of running in Hatari these days.

I introduced a new floor texturing bug in the smallest window size with chunky columns enabled - floor rotates in the wrong direction - but I don't think anyone needs such tiny windows on the mighty F030 so I'll fix it another day

BFN!

[Atari030]

Brilliant, thanks.

[calimero]

thanx dml.

I already asked but forgot answer: does 060 version runs with internal 'click' as original PC Doom speed (at 30 clicks per second) or it run as 030 version (12.5 clicks; if I remember correctly...)?

[dml]

I already asked but forgot answer: does 060 version runs with internal 'click' as original PC Doom speed (at 30 clicks per second) or it run as 030 version (12.5 clicks; if I remember correctly...)?

There are 2 variations for 060 in the zip. One is capped @ 12.5Hz just like the 030 version, and the other is uncapped.

The main difference in 060 versions vs 030 is stricter DSP synchronization and avoiding direct control over the cache.

[calimero]

I did not refer to frame per second (graphics) but internal ticks (or clicks or however is called speed of internal game logic calculation - e.g. where are enemies, did you fire, did you get hit...)

[dml]

I did not refer to frame per second (graphics) but internal ticks (or clicks or however is called speed of internal game logic calculation - e.g. where are enemies, did you fire, did you get hit...)

The framerate capping is a consequence of the game tick rate, not the other way around. i.e. the framerate can't overtake the frequency of the game update events. BM normally has a 12.5Hz tickrate and the framerate can't go past this (doing so would require interpolation etc).

So the 'uncapped' version is actually still capped - but at 35Hz. This matches the AI tick resolution of the PC version.

[calimero]

ah, I understand it now. Thank for explanation! I am going to try all version now

[nemodhs]

Great to hear you still find ways to optimize this engine.

Unfortunately I can't get this one to run on my Falcon.

I goes to a black screen with a disk icon in the upper left corner and from there nothing happens anymore.

The last other version I tested (0.32) works well with the same installation and machine (14MB RAM, FPU, TOS404).

[dml]

Hi, ok thanks for letting me know. I'll take a second look. It's possible I screwed something up during testing or preparing.