Compileable version of Alien Breed 3D II - The Killing Grounds

[abu_the_monkey]

Originally Posted by Karlos

Just going back to the idea of doubling the sky background width, I think backdrop overrides per level might be useful too. One of the thoughts I had is that, since there are teleporters in the game, various surface sites you go to don't have to be in the same location, or at the same time of day, etc. This allows for greater artistic freedom.

backdrop overrides sound like great additions to me.

[Karlos]

Originally Posted by abu_the_monkey

backdrop overrides sound like great additions to me.

It shouldn't be any more difficult to do than any of the others. No time just now but it's on the list.

[abu_the_monkey]

indeed, there is never enough time

just noticed we passes 4000 posts . that went quick

[Karlos]

Originally Posted by abu_the_monkey

indeed, there is never enough time

just noticed we passes 4000 posts . that went quick

Gasbags.

Back on topic, sort of, I am keen to understand how difficult it is to expand the bitmapped aliens to 8 view directions. The game linker tool already has some options there but obviously this was was not added as a feature to the game itself. I don't know if the data structures are defined though. It would be cool to have support but that does then create the problem that there's no assets.

[Karlos]

I've fixed the hard 250 limit on the jetpack, the carry limit is now respected. To test this, I added a devmode counter that reports the fuel count. It reveals several things:

1) You only get 250 fuel from the charger so have to activate this more than once. That'll probably be defined in the game link file somewhere, but maybe this is OK, you can use the charger twice in succession after a short delay. That might even prove to be a useful mechanic.
2) As soon as you have the jetpack, every jump is powered and fuel is consumed. This doesn't seem ideal. Maybe it should be possible to drop the jetpack. You could use the excuse that the weight of it prevents you from jumping, so it could theoretically be dropped and recovered, in order to preserve fuel.
3) The rate of fuel consumption is constant and unconnected to the fps rate of the game. 500 fuel gave me 10 seconds of continuous flight at both 50fps and 8fps.

This actually surprised me as it's just decrementing by a constant amount. I think the game logic is obviously synced to the vertical interrupt, regardless of the buffer flipping.

I haven't yet added a HUD fuel level indicator.

[abu_the_monkey]

Originally Posted by Karlos

I've fixed the hard 250 limit on the jetpack, the carry limit is now respected. To test this, I added a devmode counter that reports the fuel count. It reveals several things:

1) You only get 250 fuel from the charger so have to activate this more than once. That'll probably be defined in the game link file somewhere, but maybe this is OK, you can use the charger twice in succession after a short delay. That might even prove to be a useful mechanic.
2) As soon as you have the jetpack, every jump is powered and fuel is consumed. This doesn't seem ideal. Maybe it should be possible to drop the jetpack. You could use the excuse that the weight of it prevents you from jumping, so it could theoretically be dropped and recovered, in order to preserve fuel.
3) The rate of fuel consumption is constant and unconnected to the fps rate of the game. 500 fuel gave me 10 seconds of continuous flight at both 50fps and 8fps.

This actually surprised me as it's just decrementing by a constant amount. I think the game logic is obviously synced to the vertical interrupt, regardless of the buffer flipping.

I haven't yet added a HUD fuel level indicator.

excellent!

[Karlos]

Given that the legacy HUD is a bit of a pain in the backside, especially at lower sizes, is it time to move to a completely on screen one?

The only advantage it had on AGA was that it was all planar to begin with, but we have to convert it and the digits etc. to chunky. It's not a big deal but an overlay might be nicer and we could use the whole vertical height for the render buffer.

[Karlos]

The thought that prompted this was the idea that I'd be putting an on display fuel gauge for the jetpack as there's nowhere in the border for it to go anyway.

I'm not sure the selected weapon indicator is especially useful, either. We could dispense with the whole border stuff

[abu_the_monkey]

Originally Posted by Karlos

Given that the legacy HUD is a bit of a pain in the backside, especially at lower sizes, is it time to move to a completely on screen one?

The only advantage it had on AGA was that it was all planar to begin with, but we have to convert it and the digits etc. to chunky. It's not a big deal but an overlay might be nicer and we could use the whole vertical height for the render buffer.

Originally Posted by Karlos

The thought that prompted this was the idea that I'd be putting an on display fuel gauge for the jetpack as there's nowhere in the border for it to go anyway.

I'm not sure the selected weapon indicator is especially useful, either. We could dispense with the whole border stuff

not against the idea, but wouldn't want it to look overly modern and as long as switching to 2x1 (or 2x2 if we ever get that sorted) doesn't make it an unreadable mess.
the selected weapon indicator also lets you know what weapon's you are carrying.

[Karlos]

Originally Posted by abu_the_monkey

not against the idea, but wouldn't want it to look overly modern and as long as switching to 2x1 (or 2x2 if we ever get that sorted) doesn't make it an unreadable mess.

That is an excellent point mind. For RTG this can be overcome if we are prepared to render into the actual bitmap directly for plotting the HUD as opposed to doing it in the chunky buffer. I was thinking of something like that for the existing messages. It is a bit annoying but doable as long as you don't want any fancy transparency.

For AGA mode, this approach isn't viable in a double height mode due to the way the doubling is achieved.

the selected weapon indicator also lets you know what weapon's you are carrying.

Sure, but the weapon you are carrying also lets you know the weapon you are carrying ;

OK, I realise what you mean, single versus triple shot plasma and such, We could use a single digit to show which weapon is selected.

As for the style, I am definitely thinking to keep the existing seven segment LCD style display. Done with map style transparency and kept discretely in the corners it could look cool. Maybe it;s worth mocking up some designs.

[abu_the_monkey]

Originally Posted by Karlos

That is an excellent point mind. For RTG this can be overcome if we are prepared to render into the actual bitmap directly for plotting the HUD as opposed to doing it in the chunky buffer. I was thinking of something like that for the existing messages. It is a bit annoying but doable as long as you don't want any fancy transparency.

For AGA mode, this approach isn't viable in a double height mode due to the way the doubling is achieved.



Sure, but the weapon you are carrying also lets you know the weapon you are carrying ;

OK, I realise what you mean, single versus triple shot plasma and such, We could use a single digit to show which weapon is selected.

As for the style, I am definitely thinking to keep the existing seven segment LCD style display. Done with map style transparency and kept discretely in the corners it could look cool. Maybe it;s worth mocking up some designs.

sound good, mock something up and see what the people say

[Karlos]

Mimimalist HUD. Positioned bottom right, away from any messaging.

Shows selected weapon, relevant ammo count, hit points and jetpack fuel.

[StevenJGore]

Ooh, very slick! Apologies if I missed this further back, but presumably this means the viewable screen area (of the 3D) is now bigger due to not having the HUD across the bottom?

[Karlos]

Originally Posted by StevenJGore

Ooh, very slick! Apologies if I missed this further back, but presumably this means the viewable screen area (of the 3D) is now bigger due to not having the HUD across the bottom?

That's a mockup.

Size wise, the most increase you could hope for at 320*256 would be about 24 pixels, which would be the 8 unused pixels from the original text renderer plus 16 pixels or so for the border bottom.

The motivation for this, more than anything is to help support lower resolutions better, e.g. 240 tall, which is a much more common RTG target.

[abu_the_monkey]

Originally Posted by Karlos

Mimimalist HUD. Positioned bottom right, away from any messaging.

Shows selected weapon, relevant ammo count, hit points and jetpack fuel.

I like it

Originally Posted by StevenJGore

Ooh, very slick! Apologies if I missed this further back, but presumably this means the viewable screen area (of the 3D) is now bigger due to not having the HUD across the bottom?

only by 8 lines the size is set to 240 high and may not be easy to change due to a bunch of maths and science and stuff.

[Karlos]

Originally Posted by abu_the_monkey

...and may not be easy to change due to a bunch of maths and science and stuff.

Yeah, how much of a ball ache was the floor v wall perspective issue?

[abu_the_monkey]

Originally Posted by Karlos

Yeah, how much of a ball ache was the floor v wall perspective issue?

Massive !

[Karlos]

Having said that, you may recall we are rendering 8 rows that aren't c2p'd or copied over as part of that hack, so maybe we get those back for no extra cost.

[abu_the_monkey]

Originally Posted by Karlos

Having said that, you may recall we are rendering 8 rows that aren't c2p'd or copied over as part of that hack, so maybe we get those back for no extra cost.

that's what I was thinking and would be a nice bonus

also letter boxing should work smoothly when shrinking the screen as the hud bitmap would not be being reloaded every update.

[Dunny]

Originally Posted by Karlos

Mimimalist HUD. Positioned bottom right, away from any messaging.

Shows selected weapon, relevant ammo count, hit points and jetpack fuel.

That's lush that is. Get on it mate