RISKY RICK FOR MSX !!! (post to make it a reality)

Page 19/19
12 | 13 | 14 | 15 | 16 | 17 | 18 |

By fano

Supporter (15)

fano's picture

24-11-2019, 16:10

Quote:

1) Compatibility tests

- Sony HB-F500P: passed
- Toshiba HX-23F: passed
- Sony HB-10P: passed
- NEOS MA-20: failed
- Acid1Test: passed
- Acid2Test: failed
- Turbo CPUs: passed

I'd say this is perfectly logical as program expects VDP at "standart" addresses, for MSX that owns VDP on specific addresses, we can make specific versions Wink

Quote:

The controls sometimes feel a bit sticky/unresponsive. Enabling the turbo seems to alleviate that.

What type of hardware is it ?

3) Suggestions
[quote
wrote:

- It would be nice to be able to press STOP to pause the game

Why not, it's a good idea.

Quote:

- Please add joyMega support. This way we could have specific buttons to FIRE and drop TNT (and START to pause)

Where i can find docs about this hardware, we could add this too.

Quote:

- The name input screen should also accept direct typing

The original Risky Rick was console oriented but why not, should be a bit short for Christmas release but we could do this on physical release.

Quote:

- Some background music is welcome and improves the immersion

That was a design choice so code was written around this.To make it short, actually adding ingame music needs rewritting large parts on the game engine.

Quote:

- Since the game is well-behaved with turbo, please enable it as a courtesy on machines that have the CHGCPU BIOS call

I'm not very aware about turbo mode but where is the benefit to add this ? is it activation of the R800, does it make Z80 CPU fast ? that was not easy to adjust VRAM/VDP timing on MSX compared to Colecovision (and i don't speak about awfull VBL polling "bug"), does the CPU change affect timing ? i'm afraid of breaking compatibility with RR that relies a lot on VRAM/VDP.

By sd_snatcher

Prophet (3092)

sd_snatcher's picture

24-11-2019, 18:10

fano wrote:

I'd say this is perfectly logical as program expects VDP at "standart" addresses, for MSX that owns VDP on specific addresses, we can make specific versions Wink

Tip: There's no need for specific versions. The VDP.DR and VDP.DW system variables point to the I/O ports of the VDP. :)

Quote:
Quote:

The controls sometimes feel a bit sticky/unresponsive. Enabling the turbo seems to alleviate that.

What type of hardware is it ?

I tested on:
- Sharp Hotbit 1.2
- Panasonic FS-A1ST
- Sanyo PHC-70FD with homebrew turbo

Quote:

joyMega: Where i can find docs about this hardware, we could add this too.

You can find info here, and here.

If you want to save time, there is a ready-made library available here.

Quote:

That was a design choice so code was written around this.To make it short, actually adding ingame music needs rewritting large parts on the game engine.

Wow! Ok, no problem.

Quote:

Turbo: I'm not very aware about turbo mode but where is the benefit to add this ?

The benefit is quicker screen changes and no slowdowns on crowded areas.

Quote:

is it activation of the R800, does it make Z80 CPU fast ?

On the Turbo-R, it will activate the R800. On some turbo kits (and webMSX), it will activate a higher clock for the Z80.

Quote:

that was not easy to adjust VRAM/VDP timing on MSX compared to Colecovision (and i don't speak about awfull VBL polling "bug"), does the CPU change affect timing ? i'm afraid of breaking compatibility with RR that relies a lot on VRAM/VDP.

Yes, it does affect the CPU-to-VDP timing. But:

1) It seemed to work just fine. I've seen no glitches anywhere

2) Tip: Be careful about strict timing constraints to access the VDP on the MSX. There are very different machines from different makers, and a lot of them with different CPU-to-VDP timings. For example:

  • On some MSX2+ models, the T9679A and T9769B chipsets add 2 additional waits cycles when the VDP is accessed. On MSX2+ models (and the TR models) with the T9769C chipset, 1 additional wait cycle is added. Even if the turbo isn't enabled.
  • In many MSX models, the VDP uses a different crystal from the CPU. This means that the two are not in sync.
  • On Turbo-R models in R800 mode, the S1990 engine enforces 27 cycles between VDP accesses.

By ArcadeVision

Resident (55)

ArcadeVision's picture

28-11-2019, 13:51

@ro : Thank you for the news up! Big smile

By DrWh0

Paladin (768)

DrWh0's picture

28-11-2019, 14:19

ArcadeVision wrote:

THE FINAL GAME WILL SUPPORT THE CURSORS KEYS
@Juanmi: You are now refunt. Thank you.

Thanks for adding cursor keys but, please add ingame musics, I hate deeply silent games...

By erpirao

Paladin (962)

erpirao's picture

28-11-2019, 17:55

Frankly, I understand that "we don't like" OPQA control, but as Arcadevision has already said, the test was a beta to test alternative controls.
and if the game does not have music in school, it does not seem right that the MSX version should have it
In short, it has already been said that the game will be controllable with cursors.

By ArcadeVision

Resident (55)

ArcadeVision's picture

30-11-2019, 10:24

Just to let you know that 25 days left to preorder the game and receive the Digital Ediion.
If you are on the big list, please, don't forget! Smile

PREORDER RISKY RICK MSX

By TotO

Supporter (3)

TotO's picture

01-12-2019, 18:52

erpirao wrote:

I understand that "we don't like" OPQA control, but as Arcadevision has already said, the test was a beta to test alternative controls.

Yes. And, it is nice to play with feet. oO

Page 19/19
12 | 13 | 14 | 15 | 16 | 17 | 18 |