archive.worldofdragon.org

John W. Linville wrote: I am working on a game for the Tandy Color Computer 1 & 2. A version for the CoCo3 might come in the future, but it is not the target right now!

The game is inspired by the homebrew game Downfall for the Atari Jaguar.

Blog: http://fahrfall.blogspot.com/

John W. Linville wrote: Hey...

As I took Fahrfall to various events last year, I made a few updates.
Unfortunately, until today I had neglected to post those binaries
for others to run...

More information is available on the Fahrfall blog:

http://fahrfall.blogspot.com/

Please let me know if you have problems with it! The code should
run on CoCo1, CoCo2, Dragon, or other compatibles (e.g. CP-400),
but not on the CoCo3(*).

John

Fahrfall on YouTube: http://www.youtube.com/watch?v=0k5do3j7eb4

EDIT: Attachment moved to the Uploads section.

I have tested the attached version on my real CoCo, and it works perfectly. For some reason there is no sound when its running under XROAR v0.29.1 CoCo or Dragon emulation.

EDIT: The sound works fine under XROAR v0.24.

Looks like a silly bug affecting single bit sound. Specifically I had code affecting the use of that pin as an input based on the sound output level, and it was doing that even when that pin *was* the sound output!

I'll push out a bugfix release tomorrow.

And to think I was playing Fahrfall earlier after his announce, but deliberately without sound, so I didn't notice!

I'll add this to the test suite - I test fairly frequently with Demon Attack (which generates sound by switching the MUX on and off), but didn't have anything specific that used single-bit sound.

Do I need to figure-out how to generate a DragonDOS binary?

Welcome to the Dragon forums, John! Appreciate your support for the (underloved) CoCo 1/2 and Dragon machines.

Regards,
Steve

Heh...sure, np! There is plenty of capability in these machines. The CoCo3 does have it's advantages, but lots of things can be done on the CoCo and Dragon.

sixxie wrote:Looks like a silly bug affecting single bit sound. Specifically I had code affecting the use of that pin as an input based on the sound output level, and it was doing that even when that pin *was* the sound output!

I'll push out a bugfix release tomorrow.

What happened to the bugfix release?

zephyr wrote: What happened to the bugfix release?

Whoops!

Here you go!

I, er, got distracted...