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

[Karlos]

Originally Posted by DanyPPC

There are situations when the framerate goes more down with previous version, even 5 fps.
The new executable is more strong, framerate interval is better.

So I think the new 020 executable is a good result for a 030 machine.

This is probably due to the new build process and making sure that the generic 020+ version doesn't contain any 040+ optimisations that are hardwired. So you don't get any 060 optimised inner code in this version, that's what the 060 version does and likewise it doesn't contain any 020/30 specific code.

[DanyPPC]

Thanks for clarification.

I remember originally TKG demo from Team17 worked better on a 030 machine.
The final game was released also in a bundle with Blizzard 1230 and Blizzard 1260.

The demo on 030 plays very well at 2/3 of the screen.
But the final release doesn't run at good framerate.

I know that TKG is a game very demanding for Amiga, and I'm not surpised today that it cannot run good on a 030 machine.
Anyway You have done the possible to make it to run better on AGA/030 Amiga.

Thanks a lot for your effort.

[Karlos]

There are at least 2 further 020/030 optimisations to apply. Firstly were still using an 040 tuned C2P in 2/3 mode because it's intended for partial rather than full frame updates. I think the optimised 030 routine should be configurable for 2/3

The other one is a throwback. The original code used a lot of cache manipulation on inner loops that were generally unhelpful on 040+. However they may well benefit 020/030. However they are quite inline and the best way to reintroduce them would be to avoid peppering the code with branches. So maybe unconditionally enabling those in an 020/30 target is an option - if they help

[DDNI]

Tested on a pistorm A1200. 25FPS and all good at 2/3 screen size, messages visible.

[Karlos]

I think I'll proceed on th assumption that it's working, though it's odd that the menu works for @abu but not the game. That definitely feels more like a software than hardware issue.

[Angus]

Originally Posted by Karlos

I think I'll proceed on th assumption that it's working, though it's odd that the menu works for @abu but not the game. That definitely feels more like a software than hardware issue.

Is it working in fullscreen mode for you, Abu?

[abu_the_monkey]

Originally Posted by Angus

Is it working in fullscreen mode for you, Abu?

no. only in RTG.

when I use the '*' to quit the game I briefly see the render buffer as the system frees it and puts me back to workbench. don't know if I have sound as audio is not hooked up but would assume so.

@Karlos
I haven't had the time to build and test the current main branch but an older version of the c build from mid feb is working in AGA on the A4000.

[Karlos]

I'll add it as a defect issue just so we don't lose it. Hard to know what it is. Is the whole screen black or can you see the HUD ?

[abu_the_monkey]

the whole screen.

I would defiantly continue with what you are doing as it seems to be only my setup that has an issue.

I will have to dig out my RGB to scart cable to check it is not the scandoubler causing problems, that said the older version does work
an odd one for sure.

[Karlos]

Can you delete (rename so we can dissect later) your Prefs file for the game and retest? This should rule out any broken gamma settings that got saved or are somehow misinterpreted on loading.

[abu_the_monkey]

Originally Posted by Karlos

Can you delete (rename so we can dissect later) your Prefs file for the game and retest? This should rule out any broken gamma settings that got saved or are somehow misinterpreted on loading.

no worries, I will do that at the next available opportunity.

not sure when that will be however.

[Karlos]

Originally Posted by abu_the_monkey

no worries, I will do that at the next available opportunity.

not sure when that will be however.

I definitely think this is a software bug. I'll add some sandwich checking to the gammon/bratwurst initialisation.

[Angus]

Originally Posted by Karlos

I definitely think this is a software bug. I'll add some sandwich checking to the gammon/bratwurst initialisation.

Sorry Karlos, in this thread that sort of phrasing is unacceptable. The correct syntax is: "I defiantly think this is a software bug." ;-)

[Karlos]

The border area corruption issue is fixed and I've made sure that the area used for rendering is correctly sized based on the number of lines etc rather than the eyeballed approximation used previously.

There is the outstanding matter of double height pixelmode in 2/3 screensize - that needs a separate copper list, or the existing copperlist updating to ensure the text area is not affected. However there are some worrying notes in the code around that, which I want to look into further before going full hacktard. So I will probably call this "done" for now and look into that as part of a more general display overhaul that will include the proposed repositioning of the display components in lower resolution modes.

[Karlos]

Squashed and merged back into main.

[abu_the_monkey]

Originally Posted by Karlos

Squashed and merged back into main.

top stuff

[abu_the_monkey]

@Karlos

It turns out your hunch was correct.
After renaming the game.prefs (I also renamed the game.stats just to be on the safe side) AGA screen modes are working on my A4000 and all works as it should.
Happy days

[Angus]

Originally Posted by abu_the_monkey

@Karlos

It turns out your hunch was correct.
After renaming the game.prefs (I also renamed the game.stats just to be on the safe side) AGA screen modes are working on my A4000 and all works as it should.
Happy days

"But Obiwan, with the blast shield down, I won't be able to see anything!"

[abu_the_monkey]

to be fair I should have done that from the off.
it was only because the RTG screen modes were working that confused me.
that and I can be real dumb sometimes

edit: I have not copied the .prefs .stats file over from the A4000 as that would require taking the thing apart and I have run out of time for now

[Karlos]

Originally Posted by abu_the_monkey

@Karlos

It turns out your hunch was correct.
After renaming the game.prefs (I also renamed the game.stats just to be on the safe side) AGA screen modes are working on my A4000 and all works as it should.
Happy days

I clearly have issues with the whole Prefs system. New features are meant to be non breaking lol.