Slitherine

quote:

ORIGINAL: Wikingus

I'd like to play the game for the first time in about 5 years, and much has changed (including my computer). I can't get the 'normal' version of the game to run smoothly - I have all the issues commonly reported with lag and delays, and none of the command lines have solved them.

The beta version works fine, but I get an error message if I try to change from -w to -f in the command line, or if I want to switch to my resolution (1920x1080). Any ideas?

quote:

ORIGINAL: RisingSun

quote:

ORIGINAL: Wikingus

I'd like to play the game for the first time in about 5 years, and much has changed (including my computer). I can't get the 'normal' version of the game to run smoothly - I have all the issues commonly reported with lag and delays, and none of the command lines have solved them.

The beta version works fine, but I get an error message if I try to change from -w to -f in the command line, or if I want to switch to my resolution (1920x1080). Any ideas?

Have you tried -Deepcolor?

quote:

ORIGINAL: Termite2

Assuming your monitor and video card are capable of 1920X1080; appears to be a command line problem; please copy your shortcut properties command line, so we can see what exactly you have done.
As an example: "C:\Matrix Games\War in the Pacific Admiral's Edition\Beta2\War in the Pacific Admiral Edition.exe" -px1920 -py1080 -deepColor -dd_sw

I am running WIN10 with no problem

quote:

ORIGINAL: Theages

The last posts really should be in a separate thread.

Try setting the compatibility options of the shortcut (tab: compatibility) to not use high DPI scaling. Windows 10 scales programs on systems with small size but high resolution displays.
eg: my 32" 3840x2180 has a scaling of 150% which some some programs interpret as its resolution being 2540x1440. Right-click on desktop and choose 2nd option from the bottom (something like "display settings" (in german: Anzeigeeinstellungen) to view this.

Even if your display has a native resolution of 1920x1080 maybe due to scaling WitPAE is recognizing it as something lower and refuses to set it outside the displays capabilities.

Please open a new thread if that doesn't solve the issue.

quote:

It will create a directory Beta2 off the main AE install directory, install the updated EXE and DLL, and create a shortcut on desktop to run AE from that new directory.
/quote]


Beta 2 directory now created, but next step (highlighted above) confusing. Will somebody take me by my dumb hand and tell me step by step from here? I'm sure over the years I have done this more than once but as time goes by everything fades. Probably should hang this game up.

I found the solution to my problems. See my thread "Error: Unable to find PW Data" below.


< Message edited by Buck Beach -- 1/10/2017 5:04:17 AM >

(in reply to michaelm75au)

quote:

ORIGINAL: Rafid

The Visual Studio "dumpbin.exe" tool says WITPAE is not large address aware (LAA) - tested beta v1.7.11.159, but I doubt it is different for any other version.

For an executable to be LAA two requirements need to be met:

1. A certain bit in the executable needs to be set to tell Windows that the executable is LAA. This can easily be set during compiling (by Michael) or actually edited by anyone afterwards (see e.g. https://www.techpowerup.com/forums/threads/large-address-aware.112556/). This is the easy part.
2. The program and all third party libraries it accesses need to use full 32 bit pointers and not only 31 bit with assuming the first bit is 0 when accessing the memory (some programs temporarily use this bit to store other information). This is tough to ensure since it basically requires a full code review, but most late 32-bit era codes seem to adhere to this.

If you want, you can use the tool in the above link to set the LAA bit in the executable. This will get the same result Michael can get without putting in a crazy amount of work. According to forums, people have made good experiences with it (it definitely worked for me the two times I tried it). In the best case you have working LAA version of AE afterwards, in the worst case (if 2. is not ensured) you get game crashes and then even Michael won't be able to do it within a reasonable amount of work.

In any case making a program LAA has only advantages if the game used to crash after hitting 2GB of used memory (I've never seen this in AE) or if it used to slow down due to memory restrictions, but this would require a self-imposed sophisticated memory management - I highly doubt AE has. So you can set the LAA bit yourself, but I wouldn't expect much from it. You might try if the linked tool helps with your other game of course.