Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Hungry Horace]

ok, so this post is aimed at the AMOS part of the forum, but those in the Bloodwych part will understand why!!

I have stumbled across an excellent bit of data from the game Bloodwych, and i need to reproduce the way it work in AMOS for my game editor. The problem is, i've neve approached graphics in the this way, and i have no idea how to achieve the effect i want!!

I think i need to do some clever stuff with bitplanes, so It may require the AMCAF commands, but i really dont know.

Let me explain the scenario....

We have various characters to make up for the minimum amount of graphics / data possible.

- Each one consists of 4 body parts:  Legs, Arms, Torso, Head.
- There is also a 5th "part" which shows the entire body from a distance.
- Each of these parts can be re-coloured separately and combined together to produce a complete character.

- The game uses a complete palette of 16.
- The background (colour 0) is black and colour 15 is usually reserved for copper effects.
- During the re-colouring, if colour 15 is referred to, it is transparent.

- Each part has been stored on an IFF file in a "raw" form, ready for recolouring
- The colours used which get re-coloured are colours $0,$4,$8,$C
- Each of these four can be recoloured as any of the ull 16 colour palette.


I would like to know what is the best way to approach this, and/or if anyone has already amde code which will do this! There are some clever looking bitplane commands and some palette commands in AMCAF, but i confess i dont really understand them. I also have no idea, using the bitplane method, how i go about getting the colours to actually change (i have used it only to copy 1 plane at a time it seems) OR how to reposition my output at a different point of the screen.

This code doesnt need to be as fast as the original (although that would be great as i might re-use it later) so any solution is welcome!!

I have attached a zip file containing a graphics file for testing and short AMOS program that simply rips the 'raw' graphics out into a bob bank.

Cheers!!

[SamuraiCrow]

The easiest way to do it would be to use the P2C command from AMCAF to convert the image to chunky format.  Then you can renumber the entries at will and then use the C2P function to change it back.

Sent from my Prism II using Tapatalk

[Hungry Horace]

At the moment I am using a turbo point  ->turbo plot routine to "re draw" the image pixel by pixel but it's very slow as you can imagine.

I have looked through all the AMCAF commands but I can't find any chunky/planar commands at all?

[SamuraiCrow]

Look at the flame example.  It uses the C2P and P2C is similar.

The Turbo Draw commands in AMCAF should be safer than the F Draw commands in Turbo Plus.

Sent from my Prism II using Tapatalk

[SamuraiCrow]

Whoops I just read your post again and I see you aren't using Turbo Plus.  Sorry.

Sent from my Prism II using Tapatalk

[Hungry Horace]

I looked at the flame example and while very impressive it sadly means nothing to me without any context.

Is anyone able to provide a breakdown of how it works (re numbering individual pixels?) and how it would be implemented in this context.... The game I am trying to replicate is from 1991 and I can't image they use anything like that?

[SamuraiCrow]

There are two work banks in fire.amos which are the manual double-buffering.  The need for those is that you can Peek and Poke color numbers into the bytes using manual row-and-column manipulations.  In this case WX and WY are the window's maximum x and y coordinates.  There doesn't seem to be a planar to chunky batch conversion but at least "C2p Convert WORKBANKSTART, WIDTH, HEIGHT To SCREENNUMBER, X, Y" will batch convert the bank of pixel colors to planar screen pixels for you.

Given some additional thought, you'll have to create your own mask since 15 is the transparency key color instead of color 0.  The second-quickest way is to use custom minterms to logically OR the last 3 bitplanes together with the a copy of the first using the Blitter Copy command in a loop.  See the comments in the Mask Copy example for how to do this.

(The quickest way is to save the logical OR of the first 3 bitplanes in the mask with Blitter Copy, then or the 4th bitplane with the mask storing the result back in the mask with another Blitter Copy.  Just 2 blitter passes this way!  Unfortunately you have to use different minterms for each pass.)