[WIP] Moon Patrol conversion

[jotd]

It goes as follows:

- if you have a OCS amiga, the floppy shell will run the OCS version: no blue mountain layer, 25 fps
- If you have a ECS 68000 amiga, the game will run the ECS version but will disable the blue mountain layer
- If you have a ECS with 68020+ the game will enable the blue mountain layer
- If you have AGA, the game will run the AGA version.

With whdload, you can have the blue mountain layer on 68000, see how slow it is (unless you're using a superfast 68k emu like pistorm).

Floppy version will be soon updated to fix the crash at startup.

[Cris1997XX]

JOTD, I've got a question I wanted to ask for a long time...have you ever considered releasing your arcade ports on CDTV/CD32? Maybe as a sort of bundle or something, I think it would be a cool concept

[jotd]

yes, someone already asked me that. It would run all right with CDTV boot, even AGA games, no need for whdload or other.

[Don_Adan]

Originally Posted by Cris1997XX

JOTD, I've got a question I wanted to ask for a long time...have you ever considered releasing your arcade ports on CDTV/CD32? Maybe as a sort of bundle or something, I think it would be a cool concept

Then jotd will must change Insert Coin and Press Player button(s).
Now it have something from MAME, not from Amiga, like pressing 5 and 1 button.
CD32 has no keyboard.
Something like Joystick Up (maybe with pressed Fire together) as Insert Coin and Joystick Fire as Press Player button.

[Marconelly]

Originally Posted by Don_Adan

Then jotd will must change Insert Coin and Press Player button(s).
Now it have something from MAME, not from Amiga, like pressing 5 and 1 button.
CD32 has no keyboard.
Something like Joystick Up (maybe with pressed Fire together) as Insert Coin and Joystick Fire as Press Player button.

I think all jotd's games already have insert coin on button press and start game on joy up (1P) and joy down (2P). No need for keyboard

[jotd]

... and it's in the readme

[Seiya]

moon patrol with OCS configuration (512+512, 68000, OCS) not works. When i press "1" the game loading, but return to choice selection

[nikosidis]

Tried the game on A4000/030 now and the game work great! Everything seams spot on. Great sound quality! Will support this in the next update.

[Marconelly]

Originally Posted by Seiya

moon patrol with OCS configuration (512+512, 68000, OCS) not works. When i press "1" the game loading, but return to choice selection

If you have any extra drives, make sure they are unplugged to free up the memory. If that doesn't help, I'd try renaming the startup-sequence file on the floppy, and then when you boot from the floppy into CLI prompt, type mpatrol_ocs and see what happens. It should at least let you see the error.

[Seiya]

Originally Posted by Marconelly

If you have any extra drives, make sure they are unplugged to free up the memory. If that doesn't help, I'd try renaming the startup-sequence file on the floppy, and then when you boot from the floppy into CLI prompt, type mpatrol_ocs and see what happens. It should at least let you see the error.

i tried with winuae, so i can set every memory size, but it not seems a memory problem. I will try to rename the startup-sequence

[jotd]

I will check tonight.

[Don_Adan]

Originally Posted by Seiya

i tried with winuae, so i can set every memory size, but it not seems a memory problem. I will try to rename the startup-sequence

For me it looks like (in)famous Vasm default assembling option.
Change kickstart to 3.1 and check effect.

[jotd]

no Don first I'm using gnu as and second my games are designed to run on 1.3

[Seiya]

@Jotd
you don't need to check.

the game working with WinUAE using Quickstart A500 setup.
i need that game working from a front-end that use WinUAE, but through script.
All your games working with every script, but this new version of Moon Patrol no. It works with very old script (not winuae version).

It was a little strange that things and i thought that game had some bugs.

It's ok.

[Rob68K]

Originally Posted by Don_Adan

For me it looks like (in)famous Vasm default assembling option.

Would like to learn more about this as I'm currently working on a project using VASM and don't want to get caught out later in the process.

Many thanks.

[Don_Adan]

Originally Posted by Rob68K

Would like to learn more about this as I'm currently working on a project using VASM and don't want to get caught out later in the process.

Many thanks.

Vasm has as DEFAULT creating word relocs for Amiga exe files.
Word relocs are unsupported for kickstart 1.3. Must be longword relocs.

[Rob68K]

Originally Posted by Don_Adan

Vasm has as DEFAULT creating word relocs for Amiga exe files.
Word relocs are unsupported for kickstart 1.3. Must be longword relocs.

May I ask what the solution is?
Is there an override?

I'm actually testing on Kickstart 1.3 at the moment. I've experienced some unexplained memory corruption but I figured it might be something I'm doing rather than an insidious issue the the assembler.

[Don_Adan]

1. Use kick13 flag in Vasm.
2. Use different assembler.
3. Create fully PC relatìve code (no relocs).

If program is running/started on kick 1.3, then this is not relocs problem.

[jotd]

back on topic now please?

[Rob68K]

Originally Posted by jotd

back on topic now please?

Apologies