O-Thrust

[Chema]

I am using Euphoric 1007 (the one included with OSDK 0.017) and I don't have these problems.

Not sure why OSDK comes with 1007, btw.

[Dbug]

Because I never updated it.
I tend to not update things that are not known as broken

[Silicebit.]

Symoon:

BTW, tested on another computer, with Euphoric 1.008 and had the problem too... Am I the only one ? Nobody else using Euphoric ? Am I normal ?

I use Euphoric Build 1009 (on WinXP) and O-Thrust runs fine.

Level1 Screen

Level2 Screen

[Symoon]

Ok guys, tested it on a 3rd computer and still had the problem. I was wondering if I should stop computing
Then came the light!

I have the problem with Euphoric when using the "RAM pattern" number 2. It's the RAM thing that is displayed when booting the Oric. You can choose it in EUPHORIC.INI file.
I'm using RAM Pattern 2 because it reminds me of my 1st Oric-1. But if I choose the RAM pattern 1, then the game works fine. That's also the pattern used by Oricutron...

So I guess there's a RAM initialization issue somewhere?

EDIT: thanks to you for testing, BTW!

[Symoon]

Found the bug: you seem to use the byte #0000 (very firt byte of the zero page) for the display, without initializing it to zero.
With the RAM pattern 2, it's initialized at #FF and the display bugs. That also means if any other program modifies this byte before loading Othrust, it will bug.

You can test it without modifying you RAM pattern, or even with Oricutron: run the emulator; POKE0,255 <return>; CLOAD"OTHRUST", and see

[Dbug]

Nice finding! Good work

[Silicebit.]

Well done Symoon!!!

[Silicebit.]

It's very very difficult, but.... I love O-Thrust!! Good work Nox!!

[Nox]

Thank you, and thank you Symoon for finding this bug, I couldn't have done that.
I just use the OSDK as-is and know nothing about configurations or the different hardware versions...
It's now fixed.

I'm also glad to hear that it runs on the real hardware!

[Dbug]

I just use the OSDK as-is and know nothing about configurations or the different hardware versions...

That's not OSDK specific, in a general way, you should never assume a particular state of the machine, so if you need something to be set to a particular value, a timer to run at a particular frequency, etc... you should make sure you set it yourself to the correct state.

[Symoon]

You're welcome, that was luck really. Fabrice also reminded me the affected RAM zones, so it was easier to check.
Glad if I can help on such an impressive work that is far above my abilities

[ibisum]

I am packing up a release of Oricutron for the Pandora gaming console .. are you interested in letting me include O-Thrust as a built-in ROM with this package, by any chance? All attribution to you of course, and it will be free to all Pandora users without a fee .. please let me know if you would allow this or not? I think it will bring you quite a few new users!

[Nox]

Yes, if you want it (in it's current state) you can use it, that would be nice.
I saw your other post, but didn't consider O-Thrust "worthy" (complete enough).

@Dbug
You are right. It's an error. But I cannot find it, somewhere I must access zeropage 0 directly
(without using a label), and searching the sourcecode for "0" is not a fun thing...
If I start a new project I will take more time for planning before starting to code...

[ibisum]

Yes, if you want it (in it's current state) you can use it, that would be nice.
I saw your other post, but didn't consider O-Thrust "worthy" (complete enough).

I *definitely* think its worthy, so I'll include it along Space:1999 as two games for the Oric from the new-releases scene .. and I'm sure we'll see some fresh new avid PandOricutron users coming into the scene ..

[Xeron]

Pandoricutron is a bit of a mouthful... I'd suggest "Pandoric".