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

[amipal]

Originally Posted by Angus

Least I can do in the face of all the fantastic and mind boggling work Pipper, Karlos, Abu, Grond etc are doing and contributing to. :-)

Indeed, they're done truly amazing work!

[Karlos]

Originally Posted by amipal

Indeed, they're done truly amazing work!

I'm not sure how my next PR is going to be received. I'm taking big chunks of extracted global variables and moving them to a manually consolidated bss section. It should make for a smaller executable but damn, it's a lot of change.

[abu_the_monkey]

Originally Posted by Karlos

Just a quick one, .bss sections are zero initialised by AmigaOS, right? I know it's commonplace elsewhere.

I believe this is true. one of the books I have says the loader allocates the space and fills with zero before starting executable code.

[Karlos]

Originally Posted by abu_the_monkey

I believe this is true. one of the books I have says the loader allocates the space and fills with zero before starting executable code.

Well it seems to be working and I've moved dozens of globals to it so far..

[Karlos]

@abu

Could I trouble you to compile and test from the maintenance/identifier-upgrades branch on my fork? I've been making quote a lot of change and while it works for me, would appreciate a second opinion.

[abu_the_monkey]

no worries,
I will give it a spin in a bit.

[abu_the_monkey]

@Karlos
just played through the first couple of levels and nothing seems broken.
not exactly a thorough test mind.

[Karlos]

Originally Posted by abu_the_monkey

@Karlos
just played through the first couple of levels and nothing seems broken.
not exactly a thorough test mind.

Given the nature of the changes I think if there were any real breaks we'd have seen them almost immediately ?

[abu_the_monkey]

Originally Posted by Karlos

Given the nature of the changes I think if there were any real breaks we'd have seen them almost immediately ?

yes I would have thought so.

[abu_the_monkey]

I haven't tested on real hardware in a while, should have a couple of hours tomorrow as the wife is going Christmas shopping with her mum.

[amipal]

Bit of testing from me. First numbers are the half-screen size, second set full-screen. Testing just the first level (hopefully descriptions are enough for locations):

A1200, BlizzardPPC w/50Mhz 68060, 128Mb 60ns Fast RAM, AmigaOS3.9 BB4.

WHDLoad v1.1...
First corridor - 13 fps 9fps
Ammo room - 19 fps 9 fps

WIP as of 8th Dec '22...
First corridor - 22 fps 12fps
Ammo room - 28 fps 15fps

[abu_the_monkey]

@amipal

not too shabby

cheers for posting some performance stats.
any 030 owners care to share?

[abu_the_monkey]

Originally Posted by amipal

Bit of testing from me. First numbers are the half-screen size, second set full-screen. Testing just the first level (hopefully descriptions are enough for locations):

A1200, BlizzardPPC w/50Mhz 68060, 128Mb 60ns Fast RAM, AmigaOS3.9 BB4.

WHDLoad v1.1...
First corridor - 13 fps 9fps
Ammo room - 19 fps 9 fps

WIP as of 8th Dec '22...
First corridor - 22 fps 12fps
Ammo room - 28 fps 15fps

@Angus

is this about the same on your setup?

[Karlos]

That's not bad at all. Fullsceen has over 2x the pixel count of the 2/3 size too. There was a 1/n table lookup optimisation that pipper put in for rendering the flats perspective that replaces division. I bet that made some difference. If we find a place that has a massive floor zone, how do those numbers look?

[Angus]

Originally Posted by abu_the_monkey

@Angus

is this about the same on your setup?

Yes, I'm not too sure about the WHDLoad version, but the numbers on the recompiled version look similar. There was one place I could briefly get 29.9 fps but never 30, which made me wonder if there was a built in limit somewhere.

[amipal]

Originally Posted by Karlos

That's not bad at all. Fullsceen has over 2x the pixel count of the 2/3 size too. There was a 1/n table lookup optimisation that pipper put in for rendering the flats perspective that replaces division. I bet that made some difference. If we find a place that has a massive floor zone, how do those numbers look?

It feels like a massive difference over the WHDLoad v1.1 slave version.

[Sneezeface81]

Originally Posted by abu_the_monkey

@amipal

not too shabby

cheers for posting some performance stats.
any 030 owners care to share?

Hey! Here is how it performs on my A1200 030@40MHz w 16MB.
Took latest .lha from the Zone, launched tkg_fps.

WAKEUP ROOM (half-screen size)
[1x1] avg 6fps; max 9.5fps;
[1x2] avg 10fps; max 13fps;
[2x1] avg 11fps; max 16fps;
[2x2] avg 14fps; max 20fps;
Max fps measured looking at the wall.
Looking at the very first closed door fps drop to half of the max value (in each pixelsize).

ROAMING LEVEL A
[1x1] 5 to 7fps (half-screen size); 2 to 3fps (full-screen size);
[2x2] 10 to 15fps (half-screen size); 6 to 8fps (full-screen size);

With double width pixel sizes(2x1,2x2) the moving floor artifact is noticeable and also the rendering artifact affecting vertical walls (this one only in full-screen).

Cheers!

[Karlos]

The closed doors and lifts are likely down to overdraw. I've not categorically proven it but I assign a high degree of probability to it.

[abu_the_monkey]

@Sneezeface81

cheers for posting some stats

edit: the double width modes do not work correctly at the mo.

[AlphaAmiga]

What is the latest best version to download? I would love to see where it is at