Exodus The Last War patching : v0.1 patch on os4depot

@328gts

if you buy the downloadable version of the game, its in the ExodusISO.zip file, you find the files.

if you own the CD, you can rip it using cd-bruning tool,
or just run it from the cd maybe.

You need to copy the files from the cd to your HD before converting the files. or else it fails to convert the files.

I also struggled with the install process.
I got stcuk on CDDA stuff.

@kas1e

there is tag list for LockBitMapTagList function..



We can change that to include dest bytes per row.



With a few changes we only need one patch for all graphics cards.

@kas1e

ah ok thanks! I was using my CD & not iso hence why I couldnt see that file.

also noticed an error in the read me file...."ExodusCovGFX_ENG" should be "ExodusConvGFX_ENG"

@LifeForIt
Probabaly code adaptation will be need it and not just change of taglist ?

And you mean to remove all the current fix all together ?

Does this require updated Exodus?

https://www.amigafuture.de/app.php/dlext/details?df_id=2313
https://www.amigafuture.de/app.php/dlext/details?df_id=6

@kas1e

this code:



is changed to:



(Assuming you rename the labels.)

@LiveForIt

tricky yes but I'm happy to report that I've got Exodus_TheLastWar running natively (no E-UAE) on my X1000 with music and sound effects working great thanks to you & kas1e and all involved!

Had to slow down the scroll speed to min. since was just too fast....big difference from playing on my A4000 with 060

@328gts

Yes, will be bit faster, VBL is on AmigaOS4/AmigaONE is 60Hz, while on Amiga its typically 50Hz I believe. if Amiga games can’t keep up (cant update graphic in time) they drop down to 25fps, NTSC on Amiga is 60Hz.

Often timing is done by waiting for vertical blanking in the main loop, this means games like that never run faster than 60Hz (60 frames per second), if it can’t update graphic in time it takes to display the frame, then it wait for every other virtual blanking, this result in dropping frame rate down to 30 fps.

Simple timing like that major impact on multi player games, where one play can run 2 times as fast then other players.

@kas1e

Fixes the progress bar, and credits.



my patch, if anyone likes to try it.
only for HD/RX cards.

https://www.dropbox.com/s/kk8jwxkrikma ... dus_22_01_2021.patch?dl=0

Working good. The only major drawback is the 640x480 screen streched to 1920x1200 size looks blury. Is it possible to not to scale it up....with black borders o sth?

@mr2

We are only looking at bugs, but maybe it can be done.

@LiveForIT
Thanks, will check it and add if all will be ok. Only the code you quote needs to be changed? Nothing else?

For now, will be interesting to understand why when CD-Audio is enabled everything "pauses" every 3 seconds. I can of course replace it with my own cd-player routines, but that kind of sucks to find all the places where things need to be replaced...



@mr2
Quote:

Hmm, that's strange, I mean Exodus scale nothing, you just need to choose 640x480 mode (for which Exodus is written in mind).

How you was able to scale it at all to 1920x1080? Just by choosing that video mode? If so it means os4's scale it.

@kas1e

Only one rutine now use lockBytesPerRow.
(why the new patch only works on RX/HD)

The clear screen routine is also broken, but no one will notice, not a issue, too lazy to fix it.
(its possible it can produce some trach at end of screen)

@lifeforit
Can you upload your source from which you made a patch, that will be easy for me to check what was changed, etc

@kas1e

just decompile and compare labels are changed. That’s what I did.

@LifeForit
No luck for just uploading your source to avoid doing unnecessary things?

@kas1e

source diff between your patch and my patch

i decompiled your file like:

ira -a preproc exodus_file Exodus_hd_rx.asm



apply patch like

patch < new_patch.diff

@kas1e

Quote:

I mean, I choose 640x480 but monitor native resolution is 1920x1200. So to cover the whole area three monitor pixels are used to show one game pixel. That makes it blury. I thought about using smaller part of the monitor. I don't know if I explained it well .

@LifeForIt
Thanks! Will add that to the next version of patch. Maybe you can have a look at other things in the "TODO" from the readme? Any from the list is good

@mr2
Ah, you then use some monitor which does autoscaling to 1920x1080 on its own? Probably that those modern monitors which resize any resolution to the 1920x1080 and can't support proper 640x480? If so there is probably nothing we can do about it.

All the other "640x480" stuff autoscalles the same, right ?

@kas1e

Yeah, all 640x480 look the same...all above are scrambled. Nevermind, its OK as it is now :)