Mission Loading Screen

DarkSynopsis? You figure out anything on this?

I'm not looking foward to rewriting the op code, but here is what I was thinking.

There are 2 push instructions that push the image-x and image-y values on to the stack before the Call to SetRect. These 2 values will stretch the image if increased.
these combined is 2 bytes enough to call a jump short. There is empty space below the function that could be used as the offset.

We should insert a unconditional jmp short and check values with our known image resolution of 800 x 600 and if they equal modify the values and return
if ebx == 600 and edi == 800, set the values to our screen resolution and return.
Otherwise push ebx and edi and return
This way only 2 locations for each additional screen resolution could be updated in the future.

Hopefully there are no other calls to this function with images with the size of 800 x 600 and it should work.

Warning:  All hacks are done at your own risk.  Don't try them at home


I've worked on this long enough... Here is the fix!

:::: This willl stretch the image to any predetermined resolution :::::

This is the jump to new method.

Here is an explanation of the above opcode.


Here is the new opcode for the method
Offset - 2C2D00 and an explanation:


I'm running some extensive tests to see if any crashes occur during game play, or map building activities.

Please post your crashes here, and please provide the following:
1. What you were doing when it crashed?
2. Single or Multiplayer?
3. In-game or in Debrief or menu screens?
4. What Resolution your running your game in LRM?
6. if in-game what is the map name?[/li]

It is amazing how far you have come in reverse engineering! Awesome job!

So if we are to set the new standard for the Last Resort mod at 1920x1080 for map load screens with map makers and then hack the code it will shrink the image to whatever resolution we want?

For instance if the map maker has the load image at 1920x1080 but the player chooses 1366x768 as their 2D setting we can hack the proper game executable to display the load image in 1366x768? Also will it be able to display the original community made 800x600 map load screens that haven't been upgraded in 1366x768 at the same time?

That is a good point. So far I have managed to get 800 x 600 images to load full screen. What I should have been trying to do is, just set the values to what ever we want, and not add anything to the size of the image.

hack the code it will shrink the image to whatever resolution we want?

I haven't tested shrinking the image just stretching the default 800 x 600. The 800 x 600 in my previous post are variables passed in from the image.

I will run a test in a minute and throw a 1920 x 1080 image at it just to see if it will resize it to 1366 x 768.
The only problem I see is trying to use the mov instruction to modify the registers. The add and sub instructions modify the registers indirectly. With the current method of implementing the change, we cannot use any of the registers for variables and we must preserve (keep up with) the stack.

The new code can be what ever we want, since we are not trying to squeeze it in-between other functions. It is located in a code cave towards the end of the exe.

It is really cool that you have figured out how to do things like this.

It may be that it can't be as flexible as we hope. It may just have to be that the 800x600 is still the standard but we have the option of including replacement high-res load screens. This feature won't be available to map makers unless they submit new graphics to be included in future updates of the mod.

This will be a large undertaking to get quality images that will be suitable replacement load screens.

- What you come up with has to be flexible enough to allow us to still use 800x600 load screens (specifically for community made maps).

- The Sierra load maps can be enlarged and included in each of the Last Resort .RES files and then used in conjunction with hacked game executables.

For example:

Thanks, all for the cause.

Gonna run some test now to see if it shrinks the image... Any ideas on how to handle the image resolutions?
we coud just continue checking and jumping. Remember it checks for the y-value first and exits if no match, so we technically could do it again for the LR standard..

Update: I just noticed, the Loading Text is still in the same spot..

UPDATE #2: It shrinks it..... Kewl, started with a 1920 x 1080 and shrunk it to 800 x 600. It also appears to be working with the mov instruction which is less bytes. That opens up some head room on the handling of Map_Loading Images.