Patch 07 - Unofficial Public Beta - 1126b updated 17 Sept 2016

[btd64]

Reload the base game.
Then update to the latest OFFICIAL patch.
Then download and install the aug 2014 beta.

At that point, remember to start the game from the new beta icon on your desktop.

If all is well, and you get the window with your windows desktop showing on the sides, Then try the switch -wd
Window mode plus daily saves. I use this one plus about 4 or 5 others. Unfortunatly I can't remember the others, but they are here in the forum

Good luck and happy hunting....GP

[Anthropoid]

Yeah that is what I did. I suspect the problem arose because after downloading it, I:

1. Created a folder C:\Matrix Games\War in the Pacific AE\Beta
2. Moved the download there.
3. Unzipped it there
4. Ran the installer for the Beta patch

Why that would delete the scenarios I don't know but I'm suspecting it was meant to be executed with it sitting outside the directory in which WiTPAE is sitting.

[witpqs]

This will give you an idea of the basic structure. Everything is the same as the basic installation, then the Beta goes into 'Beta2' underneath the main folder.



Edit to add: Then just run it in there.

[witpqs]

At the risk of stating the obvious: the Beta comes in a .zip. You extract the .exe from the .zip, then run the .exe.

Make sure that your shortcut is pointing to the Beta and the the "Start In" setting of the shortcut points to the main folder (in the example above it's the one called "War in the Pacific Admiral's Edition", but you could have one called "PBM#1" and it would still work fine).

[Anthropoid]

I think I'll just copy paste my new functioning vanilla WiTPAE install directory and then fiddle with the Beta on an extra copy so if it repeats the problem I don't have to go through reinstalling and repatching a 3rd time.

Very surprised it did what it did. I have plenty of experience installing patches and mods. Only thing I can figure is it didn't like having the .exe for the patch run from a sub-directory in which the game is located. Or I might have failed to select something.

[witpqs]

I am sure that the Beta install does not even have any code in it to do what you described. It does not delete scenarios, it does not install new scenarios, it doesn't do anything with that stuff. Something else happened that you did not notice.

[Anthropoid]

ORIGINAL: witpqs

I am sure that the Beta install does not even have any code in it to do what you described. It does not delete scenarios, it does not install new scenarios, it doesn't do anything with that stuff. Something else happened that you did not notice.

They always _say_ these things are easy . . . but "they" probably have never dealt with an anthropoid installer [:'(]

My steps this time:

1. Uninstalled all vestiges of WiTPAE
2. Reinstalled WiTPAE
3. Ran Auto-updater on WiTPAE
4. Opened 'pre-beta' version of game to see it works
5. Played a bit and created some saves on Dec 8
6. Copied "C:\Matrix Games\War in the Pacific Admiral's Edition" directory and pasted it in the same level and renamed it: "C:\Matrix Games\War in the Pacific Admiral's Edition - PreBeta"
7. Downloaded the beta patch again to: "C:\Users\Anthropoid\Downloads"
8. Created a new sub-directory: "C:\Users\Anthropoid\Downloads\Matrix Games Beta DL" and moved the downloaded archive containing the beta there
9. Unzipped the archive
10. Ran the executable "C:\Users\Anthropoid\Downloads\Matrix Games Beta DL\FF6A296394E14BD18C86AE69886727C2\AEupdate1123x10"
11. Consulted the manual for the command line switches I wanted.
12. Right-click Opened Properties of the WiTPAE (Quick Start)item in my Start Menu
13. Added my command line switches to the Target line, resulting in: "C:\Matrix Games\War in the Pacific Admiral's Edition\War in the Pacific Admiral Edition.exe" -fw –cpu4 -px1280 –py960
14. Launched the game using: "C:\Matrix Games\War in the Pacific Admiral's Edition\Beta2\War in the Pacific Admiral Edition"

Here is what happened next:


If I launch it without the added command line switches it boots up fine and everything seems in order, but I'm guessing that, because I have two copies of the game installed (the "pre-Beta" copy I made as a pre-caution in case the beta installtion borked) the Quick Start item in the Start Menu is not working as it should when the command line switch syntax is added?

Or perhaps I just got some of that syntax wrong?

ADDIT: Okay I don't think it is the latter, because when I launch the game using the Quick Start item in my Start Menu (the one with the command line switches listed above added) it launches fine, but is of course the pre-beta version.

I'm a bit perplexed why the choice was made to do the beta patch this way, i.e., a separate .exe in a sub-directory to the game directory.

Wouldn't it have been easier to instruct users to make a copy of their pre-beta game, and then simply overwrite the files with the beta updater? Seems like the problems I'm having are derived from the fact that the beta patch runs the game off of a second .exe which is failing to do what the pre-beta exe does: auto-detect screen resolutions and auto run the game in fullscreen mode, which is the main reason I am having problems; I'm trying to get it to do that and it is giving me that PW error.

[Anthropoid]

Completely uinstalled WiTPAE. Reinstalled and reupdated. Applied Beta.

Applied command line switches to the Start Menu WiTPAE (Beta) (Quick Start) . . .

Hallelujah! it WORKS! [:)]

Beta patched version launched from beta patch Quick Start or desktop shortcut is booting with a full screen and everything is working!

Prologue: not sure what I was doing to mess it up, but all set up now.

[Skyros]

The dash- that you select for the switches will have an impact depending on if it is the minus sign from the 10 keypad or the - from the number row on the main keyboard. I can't remember which one works, I do know that I had this problem years ago and when I changed it it worked. I think it is the one from the keyboard and not the keypad.

I'm sure somebody here know for sure.

[witpqs]

Usually that pwhex not found is because your shortcut is pointing at the wrong place. On my own PC have the default installation place. I also copied that basic installation folder (and all subfolders) to make separate installations for PBMs and such. Here is a pic of a shortcut for running the Beta in one of those copies. I took the pic of the copy because the name is shorter and it will be easier to see things in the pic.

[witpqs]

This next screen pic is just a higher level overview of how to edit a shortcut.

[Lecivius]

In light of today's 'official' patch, do we patch over a beta patch game file? Update, then reload the beta patches? There are a lot of things in today's patch, and I lost track of all that Michael has done for us over the years.

[Mundy]

That's kinda what I'm wondering too. I'm assuming the last "real" patch trumps the beta, but with the two numbering schemes, I'm unsure.

Don't forget to copy over the dll file for tracker with the new one.

[Sardaukar]

Official is dated Dec 25 2014, so it's lot later than latest Beta. So I don't think anyone should install Beta over it.

And it's v. 1.7.11.24 which is later number than 11.23x10.

[michaelm75au]

1.7.11.24 is 1.7.11.23x10
I changed the patch release numbers to make it stand out when I was told an official release was in the works[:D].

[HansBolter]

ORIGINAL: michaelm

1.7.11.24 is 1.7.11.23x10
I changed the patch release numbers to make it stand out when I was told an official release was in the works[:D].

Three cheers for michaelm!

Hip Hip Hooray
Hip Hip Hooray
Hip Hip Hooray

[Trugrit]

Thanks Michael

Bravo Zulu![&o][&o][&o]

[michaelm75au]

Attached is a version of the DLL that should support a JAVA version higher than 6.
It is named pwsdll7.dll.

Tracker will at some point be made to use this version, however if you want to try it out now..
1. Unzip into the tracker directory.
2. Rename the old pwsdll.dll to pwsdll.dll.old (or something as a backup)
3. Rename the new DLL as pwsdll.dll
4. Run tracker using 32-bit Java 7 or 8

If you have any issues with it, just delete and rename the backup copy to pwsdll.dll

[Dante Fierro]

So.

Just wondering with the latest official patch out, did this official patch include all the tweaks and fixes done in Beta? Or is there differences between the two versions? I guess as a follow up question, will there be any further Beta releases after this latest patch?

Thanks. (PS: I was using the Beta version up to this latest release, and I have switched over to the latest release version. But not quite sure what I've lost or gained.

[witpqs]

ORIGINAL: Dante Fierro

So.

Just wondering with the latest official patch out, did this official patch include all the tweaks and fixes done in Beta? Or is there differences between the two versions? I guess as a follow up question, will there be any further Beta releases after this latest patch?

Thanks. (PS: I was using the Beta version up to this latest release, and I have switched over to the latest release version. But not quite sure what I've lost or gained.

Michael answered already, maybe in a thread about the new official release, that the latest official release and the latest Beta are the same code. He renumbered the version for the latest official release just to help people keep things straight.