WitP Windowed Mode : Can anyone please HELP me ?

[rustysi]

Also could you please kindly explain what these Switches which you added to you executable file do ?

They're in a file in your WitPAE folder named 'What's new'.

[pavel01]

The Readme File mentions these Switches :

Command Line Switches:

There are a number of command line switches that may be useful to players. To use these, Right click to edit the Properties on the “Quick Start” shortcut to the game (located in your Start Menu folder for War in the Pacific: Admiral’s Edition). You’ll want to add these to the end of the “Target” field to get them to work

-dual : Enables better support for processors with more than one core (i.e. Intel Core 2 Duo)
-colorBlind : Support for color blindness
-deepColor : Enables 32 bit color
-altFont : Enables alternate in-game font (Lucida Sans Unicode)
-w : Windowed mode
-wd : Windowed mode, daily autosaves
-ww : Windowed mode, weekly autosaves
-fd : Full screen, daily autosaves
-fw : Full screen, weekly autosaves
-r : Show Roads
-autosave : Daily autosave

It says nothing about these other Switches :

-cpu2
-multiaudio
-dd_sw
-SingleCpuOrders

Any idea of what these other Switches might do ?

Thanks !

[Yaab]

PerformanceSwitches

(Please note that the old –dual switch has been removed in favor of the below combination of
more configurable switches)

-SingleCpuStart : Starts the game in single CPU mode. Switches to multi CPU mode if
available later. We’ve found this to be useful on some multi-core systems, especially AMD
processors.

-SingleCpuOrders : Starts the game in single CPU mode and stays in single CPU for the orders
phase, switches to multi CPU mode for running the turn, then switches back to single mode for
the next orders phase. We’ve found this to be useful on some multi-core systems, especially
AMD processors. Use this or –SingleCpuStart, not both.
If either of the above are used with one of the -cpu# switches noted below, it will use the
specified CPU, otherwise both of these switches default to the first CPU. If a -cpu# switch and
one of these -Single switches are used, the turns will always be processed in multi-processor
mode.

-cpu# : (cpu1, cpu2, cpu3, cpu4) Switches set the cpu affinity for multi cpu systems. It will do
nothing for single cores and will default to using all cores if a core is designated which is not
there (for example using -cpu3 on a dual core system). We’ve found this to be very useful on
some multi-core systems, especially Intel processors.
If used alone, the -cpu# switches will keep the game running on the CPU specified all the time. If
used with the -SingleCpuStart switch, it will only use that core when starting the game. If used
with the -SingleCpuOrders switch, it will stay in single CPU mode for starting and the orders
phase, but will run in multicore. If one of the SingleCpu switches is used without a -cpu# switch,
it will default to cpu 1 when it is in single core.

-multiaudio : Invokes a fix that changes audio timing for multicore machines.

-dd_sw : Handles DirectDraw via Software. We’ve found this can make a huge difference on
many systems as far as reducing interface lag and making button clicking in-game more
responsive. On a few newer systems this can cause some visual glitches and slow combat
animations though, so give it a try and remove it if it’s not ideal on your system

[Dutch_slith]

-cpu2
-multiaudio
-dd_sw
-SingleCpuOrders

-SingleCpuOrders : Starts the game in single CPU mode and stays in single CPU for the
orders phase, switches to multi CPU mode for running the turn, then switches back to single
mode for the next orders phase.

-cpu# : (cpu1, cpu2, cpu3, cpu4) Switches set the cpu affinity for multi cpu systems. It will
do nothing for single cores and will default to using all cores if a core is designated which is
not there (for example using -cpu3 on a dual core system).

-multiaudio : Invokes a fix that changes audio timing for multicore machines.

-dd_sw : Handles DirectDraw via Software. We’ve found this can make a huge difference
on many systems as far as reducing interface lag and making button clicking in-game more
responsive. On a few newer systems this can cause some visual glitches and slow combat
animations though, so give it a try and remove it if it’s not ideal on your system.

[Nomad]

ORIGINAL: pavel01

The Readme File mentions these Switches :

Command Line Switches:

There are a number of command line switches that may be useful to players. To use these, Right click to edit the Properties on the “Quick Start” shortcut to the game (located in your Start Menu folder for War in the Pacific: Admiral’s Edition). You’ll want to add these to the end of the “Target” field to get them to work

-dual : Enables better support for processors with more than one core (i.e. Intel Core 2 Duo)
-colorBlind : Support for color blindness
-deepColor : Enables 32 bit color
-altFont : Enables alternate in-game font (Lucida Sans Unicode)
-w : Windowed mode
-wd : Windowed mode, daily autosaves
-ww : Windowed mode, weekly autosaves
-fd : Full screen, daily autosaves
-fw : Full screen, weekly autosaves
-r : Show Roads
-autosave : Daily autosave

It says nothing about these other Switches :

-cpu2
-multiaudio
-dd_sw
-SingleCpuOrders

Any idea of what these other Switches might do ?

Thanks !

That is from the readme.rtf that came with the original release and is dated 7/20/2009.
Use the readme.doc dated 8/19/2016 that came with the 1126a update.
There is also a whatsnew.pdf file dated 8/19/2016 that is the same as the readme.doc but in a different format.

[pavel01]

I have an update on my situation.

I contacted Slitherine Tech Support asking if they could help me out with a solution, and they suggested me to use Full Screen but with these Switches:

C:\Matrix Games\War in the Pacific Admiral's Edition\War in the Pacific Admiral Edition.exe" -f -pxf1366 -pyf768 -dd_sw -deepColor -altFont

And guess what?

I can now play the game Full Screen on this Laptop AND, when I exit it momentarily to check the Manual or Browse these Forums with Window key + D, when I get back into the game I no longer suffer those Graphic Glitches !!

So, it looks like that I can finally enjoy playing War in the Pacific: Admiral's Edition !!

I am posting this here so that if anyone else might be suffering my same problem, they might try what has worked for me.

Thank you all for their kind help !!

[Ian R]

ORIGINAL: pavel01

ORIGINAL: BBfanboy

Try putting an f in front of your px and py values (but after the hyphen). That is supposed to "force" the computer to accept the resolution.

Thanks, is it safe to "force" a given Resolution or might it happen some harm to either the Graphics Card or the Display hardware ?

The reason for asking, is that my impression is that the supported Resolutions are in steps...

All Resolutions are "Landscape"

1366 x 768 is the recommended one

then the other Resolutions "steps" on the slider are :

1360 x 768
1280 x 768
1280 x 720
1024 x 768

Do you think I could, for example, "force" a Resolution of 1350 x 750 (a little less wide and a little as high as compared to the 1366 x 768 which produces those 2 screenshots which I attached in my posts above this one) and this, without worrying that such "forcing" could damage the Graphics Card or the Display hardware ?

Sorry for the question, but my tech knowledge is quite limited...

Thanks for the help !!

Try: -wd -pxf1366 -pyf768. Note the inserted "f"s, for 'fixed'.

Edit: What BBfboy said.

If your screen size is a 16xN/9xN (where N = 100, or whatever) then the dimensions you "f"orce it to have to comply with 16/9.

I recently acquired a "15 inch" laptop, i.e. a 15.6" screen. I have it set to a window that takes the whole screen, and use cntrl-esc to drop it to the task bar. I simply set it to a forced window of -pxf1920 -pyf1080.

Perhaps that might work for you.

[eagle1]

This is what I use.

"C:\Matrix Games\War in the Pacific Admiral's Edition\Beta2\War in the Pacific Admiral Edition.exe" -px1366 -py768 -cpu8 -deepColor -cpu4 -altFont -dd_sw -skipVideo-d autosave

Hope it helps

[BBfanboy]

ORIGINAL: eagle1

This is what I use.

"C:\Matrix Games\War in the Pacific Admiral's Edition\Beta2\War in the Pacific Admiral Edition.exe" -px1366 -py768 -cpu8 -deepColor -cpu4 -altFont -dd_sw -skipVideo-d autosave

Hope it helps

Should be a space between -skipVideo and -d?

[Yaab]

ORIGINAL: pavel01


I have an update on my situation.

I contacted Slitherine Tech Support asking if they could help me out with a solution, and they suggested me to use Full Screen but with these Switches:

C:\Matrix Games\War in the Pacific Admiral's Edition\War in the Pacific Admiral Edition.exe" -f -pxf1366 -pyf768 -dd_sw -deepColor -altFont

And guess what?

I can now play the game Full Screen on this Laptop AND, when I exit it momentarily to check the Manual or Browse these Forums with Window key + D, when I get back into the game I no longer suffer those Graphic Glitches !!

So, it looks like that I can finally enjoy playing War in the Pacific: Admiral's Edition !!

I am posting this here so that if anyone else might be suffering my same problem, they might try what has worked for me.

Thank you all for their kind help !!

Your post inspired me to explore the 1366 x 768 resolution a bit more.

First, the 1366 x 768 is not listed as a supported resolution in my screen options.

Second, the 1366 x 768 is not listed as a true 16:9 resolution on the Web.

Thus, I have never considered 1366 x 768 resolution on my 15.6inch laptop for playing WiTP:AE. So I tried it and went with px and py in my switch and, voila, it works! I have a stable WiTP:AE fullscreen at 1366 x 768 pixels. At this resolution, the game is easier on the eyes than at the 1600 x 900 resolution I have used before.

[Gunner98]

Reading through these threads has been helpful. I have a question which I haven't seen come up before however.

I'm using this command line: "F:\Wargames\War in the Pacific Admiral's Edition\War in the Pacific Admiral Edition.exe" -wd -px1600 -py1024 -deepColor -cpu2 -altFont –dd_sw -skipVideo -r -fixedArt


First - is there a comprehensive list of switches anywhere? Not sure what 'dd_sw' does or if I need it but saw someone had it ... anyway.

Second and more important - using a 31 inch monitor and with resolution of 1920x1080 it is almost a perfect fit, width is perfect but height is slightly off because of the bottom windows Taskbar - it is better with 1600x1024 but losing the width is frustrating and it is still slightly over. Is there a switch which will bring the WiTP window to the front, over the taskbar?

[Nomad]

From a post above: Use the readme.doc dated 8/19/2016 that came with the 1126a update.

right click on the task bar, select task bar settings and tell it to auto hide.

[Gunner98]

Perfect! Thank you very much

[RangerJoe]

There should be a text file or something with all of the command line switches and what they do.

[HansBolter]

1366 x 768 is the native resolution of my laptop and I never had any issues running the game in full screen mode at that resolution.


Full Screen is the only way to go. Windowed mode simply sucks eggs.

[tomeck48]

I don't use a laptop. Desktop with two monitors. I added the second one since when I have the game on my #1 screen I can't minimize it or anything. So I have the game on Screen #1 and Kull's spreadsheet on screen #2. My problem is that I can't get the pointer to move onto the second monitor (no problem there with anything else using two monitors). So in order to scroll the spreadsheet I have to save and get out of the game. Then go to the spread sheet and scroll down. Then load the game back up again.

I tried some of the windowed mode up thread but no luck. Any ideas?

[Nomad]

Run the game on your #1 screen in windowed mode, then you will be able to access your second monitor.

[tomeck48]

I definitely have it running on Screen 1 but I must be doing something wrong in SeaBee to get into Window mode. I tried the directions up thread but get to a point where my screen doesn't match what's in the instructions.

[RangerJoe]

ORIGINAL: tomeck48

I definitely have it running on Screen 1 but I must be doing something wrong in SeaBee to get into Window mode. I tried the directions up thread but get to a point where my screen doesn't match what's in the instructions.

How about this, take a screen shot the next time you make a post like this.

[Chris21wen]

I don't like running full sceen, switching to other aps cause all sort of wierd video effect when you switch back. I'ts been like this from the word go.

Experements I carried out years ago using the switch -px and -py only allowed me to use the native video card resolutions, e.g. 1920x1080, 800x600 etc. Any attempt to use any other res, say 1900x1000, results in it defaulting to 800x600.

The same effect seems to apply to switches -pxf and -pyf although they where some weird effects so I never used it.

For this reason I allows used a resolution one less than the max resolution of the video card which is 1920x080 in mine. Game runs at 1600x900.

Now the interesting thing about all this is I purchased a new computer with better in built graphics and now when I used -pxf and -pyf. Now I can run 1900x1000 which is exactly what I was trying to do all those years ago.

current