Metro Siege: new arcade quality a500 brawler!

[alpine9000]

Originally Posted by Flytag

I have only stock CDTV with 1mb, I know that boot take some ram. If the music are audio track, it will free some ram? Or after boot free the ram for launch the game? Sorry my understand is limited.

If you only have 1mb - floppy version is your only option

[Don_Adan]

Originally Posted by Flytag

I have only stock CDTV with 1mb, I know that boot take some ram. If the music are audio track, it will free some ram? Or after boot free the ram for launch the game? Sorry my understand is limited.

If you have big collection of CDTV games, you can check startup-sequences for CDTV games which used full 1MB of chip ram to run.
Maybe exist trick or routine which free some extra bytes.
Something in "add21k" style routine.

[FOL]

Originally Posted by Don_Adan

If you have big collection of CDTV games, you can check startup-sequences for CDTV games which used full 1MB of chip ram to run.
Maybe exist trick or routine which free some extra bytes.
Something in "add21k" style routine.

Also altering the cd buffer sizes when making ISO, if using ISOCD.
This is how I got ROTR to run on my compilation disc. Was missing a few kb to boot. Altering buffers gave me the kb's I needed.

[Retro1234]

CDTV has some wierd bug, something to do with Audio or something that stops a lot of stuff working from CD.

Also very bad design with the CD drive enabled - memory is under 1 mb

[Don_Adan]

Dependent how many bytes is necessary tu run Metro Siege.
Someone can add/edit s-s and check something similar :

CDTV.TM ; if i remeber correctly name
c:add21k ;or add 44k
c:stack 1000 ; dependent how many stack is necessary by Metro Siege
c:avail flush
MetroSiege.exe ; run game

[tomcat666]

If you check a few posts back (or readme), the only version that runs on 1MB is the floppy track loader version. If you want system (which cd rom access does) you will need 2Mb of memory, readme also says this needs 020+ though...

[kremiso]

liking the Kim smooth and fast movement

hope in some more grab combo variations, if there is some little free memory
keep it up the good work

[alpine9000]

Originally Posted by tomcat666

If you check a few posts back (or readme), the only version that runs on 1MB is the floppy track loader version. If you want system (which cd rom access does) you will need 2Mb of memory, readme also says this needs 020+ though...

The reason we specify 020 is that’s the minimum system we test the HD version on. It probably does run “ok” on lower spec systems.

As you say, the HD version will not run on a 1mb system. Luckily we have a floppy version for 1mb systems.

[Bruce Abbott]

I ran it from the ISO image (mounted in RAM) on my A1200 with Blizzard 1230IV. Everything worked perfectly except that when I hit ESC from in the game the fire button stopped working.

I'm no expert at playing fighting games, but the character control felt just right to me. Difficulty in 1 player mode is just right too - hard, but too hard for someone like me to make progress.

The graphics are very impressive for OCS. Looks very good on my TV in PAL composite. Only thing that spoils it are the lines in the sky that attempt to dither it. Can you make it solid instead, like this?





A different palette and more graduations might make it look smoother too, if that is possible.

[DanyPPC]

With latest 7BA2 demo I have problems with 2nd button, now it pauses the game in order to jump, while space bar acts only for jump.

I have set the joypad in 2 button and CD32 mode (and it's properly recognized by the joy tester in the game menù), but same problem.

Original demo release doesn't have this issue.

[alpine9000]

Originally Posted by DanyPPC

With latest 7BA2 demo I have problems with 2nd button, now it pauses the game in order to jump, while space bar acts only for jump.

I have set the joypad in 2 button and CD32 mode (and it's properly recognized by the joy tester in the game menù), but same problem.

Original demo release doesn't have this issue.

Can you provide a few more details ? Emulation or real amiga ? Which emulator ? Which version ? HD version or ADF ?

Edit: There is an updated (experimental) beta which will (probably) solve your issues - see https://metrosiege.com/download/beta/ (4E46)

[DanyPPC]

Issue is present on Minimig Core fpga for MiST/SiDi128
On A1200/030 OS 3.9 all is ok.

Now I will test the new 4E46 release.

Thanks.

[DanyPPC]

Originally Posted by alpine9000

Edit: There is an updated (experimental) beta which will (probably) solve your issues - see https://metrosiege.com/download/beta/ (4E46)

Ok, problem is present when I force the system in NTSC (example with TUDE) and I start the game in NTSC.

In PAL mode no issues.

Tested also the new beta release.

[alpine9000]

Originally Posted by DanyPPC

Ok, problem is present when I force the system in NTSC (example with TUDE) and I start the game in NTSC.

In PAL mode no issues.

Ok - good find, I think someone else has reported a similar thing. It’s on my list to investigate. Thanks for testing.

[Retro1234]

Interesting that the Controller bug happens in NTSC -

[alpine9000]

Originally Posted by Retro1234

Interesting that the Controller bug happens in NTSC -

It's not completely surprising as the pad reading code is timing sensitive. The annoying thing is I can't reproduce it on my real NTSC Amiga, or WinUAE/FS-UAE etc.

[Retro1234]

Being a big fan of CD32 controllers etc I know there are some guys round here who have put together some CD32 reading code etc.

[alpine9000]

Originally Posted by Retro1234

Being a big fan of CD32 controllers etc I know there are some guys round here who have put together some CD32 reading code etc.

Most of the routines are functionally the same - the metro siege code has the same timing as the WHDLoad code. It could be something unrelated to the actually reading code, some other NTSC timing difference (interrupt at the wrong time?)

If it works in the joytester but not in the game (which I think is what was reported), that points to the later.

[DanyPPC]

Originally Posted by alpine9000

Most of the routines are functionally the same - the metro siege code has the same timing as the WHDLoad code. It could be something unrelated to the actually reading code, some other NTSC timing difference (interrupt at the wrong time?)

If it works in the joytester but not in the game (which I think is what was reported), that points to the later.

Ok, further test: when setting Minimig Turbo Speed to CHIPRAM the issue disappears (about 3 mips).

So I think the fastest Turbo Mode (11 / 13 Mips on SiDi128) answer to your question.

Sorry I didn't try this before, I think it's fine. No need to investigate the game code.