R0X ZER0

[wongck]

https://youtu.be/2-Xmvj6Q-N4

Thanks for making the video.
Been wanting to see how it looks like, really very nice.
I don't have an STE and don't have a jaq thingy... so I just watch the YT.

[calimero]

Game looks awesome! I looking forward to try it as soon as I get jagpad...


I have question regarding music: music in i tro is pure AY 3 chanell sounds? Is it possible to play such music on standard ST?
And in game music is also AY but sound effects are STe DMA samples? Why sound effect sometimes are skiped?

Thanks for explanation

[Frank B]

That looks like a very good *commercial* quality release! NICE!

[Tomchi]

Game looks awesome! I looking forward to try it as soon as I get jagpad...


I have question regarding music: music in i tro is pure AY 3 chanell sounds? Is it possible to play such music on standard ST?
And in game music is also AY but sound effects are STe DMA samples? Why sound effect sometimes are skiped?

Thanks for explanation

Thx.
Stu music is plain ym with timers yes, just grab the sndh in the datas.rz folder
Regarding sound effects, it uses native DMA replay, allowing one sample at a time so that it chews no CPU time.

[calimero]

Perfect! I love it

Complete game look high end, very professionally.

but doesn't STe have two channels? It should be able to play two samples without CPU, right?

[Tomchi]

nope

[AtariCrypt]

Yeah, I too figured the same as calimero :/
Whatever, this is a fabulous and TOUGH game!! Great release!!

[Stefan jL]

I thought the reason why it play one digital sound at the time was to have it as mono... same sound on right and left channel.

[calimero]

So on STe you need to use CPU if you want to have two chanels??

[Cyprian]

So on STe you need to use CPU if you want to have two chanels??

there is one DMA chanel with interlaved data for left and right chanel - LRLRLR

[junosix]

Wow, this looks hell of a cool! Well done.

[junosix]

Just dragged the STE out and had a go, very polished game!

[MM41]

After 20 minutes of intensive playing,
in three words great, great ,great !!!
Bravo Tomchi

[MasterOfGizmo]

This definitely needs a Jagpad? How many buttons are required? Does it use the number pad part of the Jagpad?

[christos]

This definitely needs a Jagpad? How many buttons are required? Does it use the number pad part of the Jagpad?

It uses 3 keys, a,b,c. So i guess a mega drive pad should be enough. But it couldnt just run on the mouse port with a two button joystick.

[MasterOfGizmo]

The question is: If I map a usb joystick to the STEs extra joystick port in the MIST board, how many buttons do I have to map to make the game work? Three buttons a, b and c is perfectly fine. I can also map two more to start and select buttons. But I don't know of any usb gamepad with enough buttons to map the keypad as well. So if the ordinary control buttons are sufficient then I'll see what I can do ....

[Tomchi]

For now it just uses A,B and C of the jagpad


(Concerning the routine that reads a usb pad to the PORT A, it also only uses 3 buttons , but that is not what you asked )

[Eero Tamminen]

At beginning it's hard at normal level, once one gets some bonuses, it gets easier.

For some reason the Credits screen overscan doesn't work properly with EmuTOS, only with real STE TOS. Could some interrupt handler in EmuTOS be slower?

[Tomchi]

For some reason the Credits screen overscan doesn't work properly

Yeah, I had same issue with a version of HATARI, this screen is 100% Gfa, as it was a bit of a rush before SV, I didn't investigate further as the stuff works on the real thing ...

[Eero Tamminen]

If you're interested, Hatari profiler would easily tell where the time goes.

Just invoke Hatari debugger in credits screen, do "profile on" and "continue". After a while invoke debugger again and "profile save profile.txt", and you can see from the "profile.txt" dissassembly annotations where the time went, and how much TOS used of it. Comparing TOS address areas CPU usage against TOS v1.6 would show where the differences are (EmuTOS 512k version come with debug symbols so one can see interrupt routine names and don't need to guess).

(I can do that at some point if you're not interested yourself investigate.)

[Tomchi]

Not that I'm not interested, just what you wrote is as understandable to me as chinese

Anyway, I bet for some wrong screen address and/or memory allocation

[sandord]

For now it just uses A,B and C of the jagpad


(Concerning the routine that reads a usb pad to the PORT A, it also only uses 3 buttons , but that is not what you asked )

I'm really curious how to wire that up...

[npomarede]

Not that I'm not interested, just what you wrote is as understandable to me as chinese

Anyway, I bet for some wrong screen address and/or memory allocation

Hi
nothing that complicated and no need to invoke the profiler (that would give no indication in that specific case, as sync-locked demo changing the background color are disabling OS completely anyway).
The solution is in fact quite simple : emutos starts in 60 Hz, but the credits screen requires 50 Hz to work correctly (ie 512 cycles per line)
Most european TOS are starting in 50 Hz, so the credits screen is OK, but you would get the same error with a US TOS.
R0X should just set video freq to 50 Hz at start and everything will go well with all TOSes

Nicolas

[vhenares]

I have been able to test it in the Hatari emulator, because I do not have JagPad. Being able to use it with the original ST keyboard would be very useful and easy. If I can help or contribute something, here I am available. Thank you.

[Eero Tamminen]

The solution is in fact quite simple : emutos starts in 60 Hz, but the credits screen requires 50 Hz to work correctly (ie 512 cycles per line)
Most european TOS are starting in 50 Hz, so the credits screen is OK, but you would get the same error with a US TOS.

Thanks, I hadn't noticed that 512k version with the default multi-language setting used 60Hz. Hatari "info osheader" claimed it to use PAL instead of NTSC.

R0X Zero Credits screen works fine with e.g. UK variant of 256k EmuTOS, or if one uses EmuTOS tos-lang-change tool to change 512k EmuTOS default language e.g. to UK one:
https://github.com/emutos/emutos/blob/m ... g-change.c