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

[vroom6sri]

Originally Posted by Karlos

It's a team effort.

If you go into fullscreen (F10) and repeat the same test, how is it?

I'll see if I get time later today to test it.

[Karlos]

After I fix my my refactoring mess up, I'm going to look at the CHEESEY code that was removed. It has a trick that may be useful. It scales the textures down to 1/4 the size and still applies them correctly to the walls.

This means it ought to be possible to devise a method for mip mapping, which could be a way to speed up the rendering of more distant surfaces.

[abu_the_monkey]

Cool

[Karlos]

I've followed the dual wield UAE instances with the IO ports set to IPC Master and IPC Slave, both checked to direct only but no dice for me. The game waits indefinitely. I'm presuming this is a complication of my Wine setup.

[Karlos]

I found a slightly different way to test the generality of the code by just inverting the pointers then block copying the affected player 2 state over the player 1. This allowed me to reproduce the "unable to move" issue first but in single player. I've made the changes I'd missed before and it began to work, so I'm going to push those. Would be cool to get a legit test if you can find a moment.

[Karlos]

I think I added a different bug too - you can choose all the weapons even though you don't have any ammo ...

Fixed. Schoolboy error, got lea N(ax), ay conflated with move.l N(ax),ay

[Karlos]

Pushed. Just the player falling code to do now.

[vroom6sri]

Originally Posted by Karlos

If you go into fullscreen (F10) and repeat the same test, how is it?

Repeating the same spin-around-on-the-spot tests in full screen I get these results:

FIRST ROOM
6.2-6.7 FPS rising to 7.2-8.4 FPS when enabling the simplified walls.

IN FRONT OF THE BIG RED DOOR
5.6-5.9 FPS rising to 6.5-6.8 FPS when enabling the simplified walls.

[Karlos]

Are you able to do a similar test with the whdload build? You need to press numeric pad enter to go to fullscreen. It doesn't have a simple wall lighting option.

[Karlos]

Originally Posted by Karlos

Pushed. Just the player falling code to do now.

Done and finished. I just need to see if I can retest 2 player mode.

[vroom6sri]

Originally Posted by Karlos

Are you able to do a similar test with the whdload build? You need to press numeric pad enter to go to fullscreen. It doesn't have a simple wall lighting option.

Sorry I think I might be missing something here - I don't think (my copy of) the WHDload version of AB3D2 has an FPS counter does it?

[Karlos]

Originally Posted by vroom6sri

Sorry I think I might be missing something here - I don't think (my copy of) the WHDload version of AB3D2 has an FPS counter does it?

I thought it has one? Amipal used it for comparison in his video. Maybe your install slave is out of date?

[abu_the_monkey]

Sorry, been a busy day.

I will endeavour to test the 2 player this evening

[abu_the_monkey]

The fps counter for the whdload version might be set using an icon tool type?

[Angus]

Since version 1, I think......

Set in tootypes:
- CUSTOM1=1 for unlimited energy/ammos, F9 skip level (save position will
be disabled)
- CUSTOM2=1 for FPS display (only for 4MB version)
- CUSTOM3=1 to lock look up/down mouse moves

[abu_the_monkey]

Would be cool to get a legit test if you can find a moment

just played through a 2 player death match in level A and all seems to be working correctly

[vroom6sri]

Originally Posted by Angus

Since version 1, I think......

Set in tootypes:
- CUSTOM1=1 for unlimited energy/ammos, F9 skip level (save position will
be disabled)
- CUSTOM2=1 for FPS display (only for 4MB version)
- CUSTOM3=1 to lock look up/down mouse moves

I've got Version 1 but the custom types are different to above and none are for FPS. Can anyone share with me a full copy of a newer version WHDload so I can just unpack it and run it please?

[Karlos]

I just added an experimental crosshair and have discovered something I suspected previously: the weapon aim is significantly exaggerated relative to the view. That is to say, as you look up, your shots go further and further above the crosshair, and as you look down, they go further and further below it.

I can't decide if this is a bug or not. It could be intentional in order to make the most use of vertical aim when you only have a limited amount of look up and down space.

[Karlos]

Originally Posted by vroom6sri

I've got Version 1 but the custom types are different to above and none are for FPS. Can anyone share with me a full copy of a newer version WHDload so I can just unpack it and run it please?

Is it not just a case of setting CUSTOM2=1 ?

[abu_the_monkey]

Originally Posted by vroom6sri

I've got Version 1 but the custom types are different to above and none are for FPS. Can anyone share with me a full copy of a newer version WHDload so I can just unpack it and run it please?

in The Zone!