forum.defence-force.org

Well, you had all these sounds in Space 1999 already.

It's what make the places memorable and alive.

Way too many Oric games are defined by either PING, SHOOT, ZAP, EXPLODE or pure silence, which is kind of a shame

Well, what's needed is sound
Either the whirrring of cameras moving, or foot steps, doors opening, computers beeping, etc...

What decides which color is used for the text of each character?
Could you somewhat use this information to pick-up the tone?

How does that work exactly?

If we have two orics, with two RGB outputs, how can we be sure that they are updating the screen at the same time, is that somewhat based on the main power source frequency, or is that purely chance based?

Chema wrote: ↑

Mon Sep 11, 2017 4:14 pm

But anyway I'd like to hear other opinions.. Dbug?

I think it sounds weird mostly because it's the same sound for both characters.
My idea was to have different pitch for the various characters, like for the woman here have her speak one octave higher.

But yes, that was the idea

This weekend a C64 demo was released that uses four Commodore 64 synced together to display a single larger image (each is responsible for a quarter of the screen): https://www.youtube.com/watch?v=QYsrmndXzWE My question is slightly different. Let say I have two Oric machines running at the same tim...

Very nice job
Now imagine if he had a more accurate printer

Could you attach a small zipped folder exhibiting the issue?

Updating the firmware of cumulus is relatively easy, the two difficulties are: - Compiling the firmware requires a specific toolchain - You need to compile the firmware twice - one for each type of display - After it's relatively easy to update the cumulus itself, but you need to use the right firmw...

Nice find.
So technically... it's a Cumulus firmware bug?

I checked the CRCs of the sectors and things are interesting. First of all, CRCs created by FloppyBuilder don't seem correct. They are all the same value, despite the sector contents. I checked the sources of FloppyBuilder and I think the CRC is computed for an empty sector and never again updated ...

I removed compression and interleave and tried in Oricutron (and in Euphoric too). Everything worked perfectly. I attach the disk image. I moved to Cumulus (a clean empty image) and the red bar appeared. I also attach the disk image. If you examine both files with an hex editor you'll see differenc...

I have absolutely no idea why FloppyBuilder (and other tools maybe?) use 22. It seems to work, however. I did not reinvent the wheel, I based the floppy creation code in FloppyBuilder on what was in Fabrice tools, because after all they were apparently working and were used everywhere :) Maybe some...

What about just copying the entire content of the line to a temporary buffer (say, the stack), and then restore it later? Something like that: ; Save to stack ldx #39 loop_push lda $bfb8,x pha ; Possibly change the content of the buffer here, like force to spaces, or BLUE paper ; lda #16+4 ; sta $bf...

So I assume the XOR is there so the progress bar does not impact whatever was displayed there before the loading?