Open Beta Test 2 - Last Resort Mod

Where is beta test 3?

I was close to releasing and then decided to add new features and change a few things of how the mod works.

Presently I am pausing to give myself a few days to re-think some things.

Problem 1:  The "no menu" feature isn't working as expected.   It works fine in single player but for some crazy reason it gives a data file CRC error in multiplayer if you try to join other people's games (or they try to join yours).    If I can't figure this out should I just completely remove this feature?

Problem 2:  I wanted to remove the dynamic renaming of game executables but this revealed a new problem.   It appears Windows 10 applies a shim to "swat.exe" that fixes the DDERR_GENERIC error on most people's machines.   Installing the replacement XVID movies fixed this new problem but what is the more elegant solution?  Which is the lesser evil?

 

Sadly I can't figure out how to fix either problem (mentioned in my last post).

I may have to remove the "no menu" feature because it would only work with single player and just create confusion. As for going back to dynamic renaming of Swat 3 I will have to do this because I don't want to create a new flood of people who suddenly have to use the replacement movies that didn't need them before.

When you are making a unique "mod" like Last Resort we always have to aim for the least tech-savvy person and the lazy person who can't be bothered to read.

The no menu issue is so bizarre, as for the movie issue, I guess the only other solution would be to have the launcher install them instead of it being a separate download.

Assuming a codec that Windows 10 / Older? has as a default it used it shouldn't cause issues for anyone, at least no more than they would have got anyway?

Ya, the "no_menu" issue is really bizarre. I made a new version of the mod so that the no_menu behaves the same way as the other hacked 2D resolutions and still get that error (ie using a file "00.res" in LastResort special folder)

I have gone over the "no_menu" hacked executable with a fine tooth comb. There are only 4 differences - 2 hacks didn't need doing because it is 800x600 already and 2 hacks weren't needed for a custom menu.dat filename. Yup already tried a version with a custom menu.dat filename also.

Using a custom "menu.dat" filename would defeat the purpose of the "no_menu" anyways.

As for the movies the problem would start if someone used the file verification feature of Steam or GOG launcher. The movies would be replaced by the originals. They would need to re-install the mod again.

Some people (like myself) can get Swat 3 working fine with the original movies.   If the Last Resort Launcher uses a renamed hacked executable instead of "swat.exe" that could then cause movie issues for those same lucky people like me.   This is a tough one because I do prefer the simplicity of not dyamically renaming executables.    I am also kind of surprised some anti-virus apps haven't complained about it with a false positive.

Update:  in other words I am scared of creating more people like our friend Jac who can't get the movies working.   Perhaps there are more of them that aren't showing up just because right now the dynamic renaming of all executables to "swat.exe" is masking another problem for some people?

I have been avoiding the beta problem mentioned above for a few weeks now but I am getting the itch to finally attack it.

I will drop the "no menu" feature for now and also revert to dynamic renaming of the game executables. This will be a pain since I have to merge two versions of the launcher software.

cant wait for a final version, bursting at the seems