Oh My Goodness!

[Zovs]

So I finally decided to try to use SeaBee to help me get the game to play better in the screen resolution I like best (3840 x 2160) and my first three tries in full screen were not successful, so I switched to wd and tried the default and my jaw just about hit the floor. I made one small adjustment and oh my goodness!

The SeaBee settings I used:


The OMG view:


The GME mods (I only tweaked them so that GME could use them properly):


Read up to chapter 8...

Think of that song Oh, What a Wonderful World while playing/learning this game!

[RangerJoe]

DAT's right![8D]

[Zovs]

[:D]

I also made a couple of screen shots for 5120 x2880

[Ian R]

You might want to pick a core affinity (other than core 1) - I forget what problem it fixes, but have been using the switch "-cpu2" for years. Something to do with how Intel processors work.

There is a section in the readme that came with the latest patch that suggests that the cpu switches (there are some other possibilities) tend to help smooth running. In your set-up you have "singlecpustart' checked - that one might have a fix in it relevant to AMD multi core processors.

[RangerJoe]

I think that it has something to do with either Windows or Antiviral programs, which CPU they run on.

[Zovs]

Thanks fellows. I am pretty happy with the way it is running now.

[Axe1999]

Hey, how did you manage to upscale the resolution higher than your screen? If I do that, I get a small(ish) square window that I cant resize, in windowed mode with identical settings to yours.

[Zovs]

Axe1999,

I don't know exactly how this all works really. My windows 10 can run in the following screen resolutions:

5120 x 2880
3840 x 2400
3840 x 2160
2880 x 1800
2560 x 1440
1920 x 1080

Plus a number of smaller ones but only those listed above display on my monitor anything useful or functional for me.

When I first installed WitP-AE I followed TrueGrit's install instructions and manual setup the switches. This worked good enough to get the game installed and running. But I could never get full screen (and still can't) to work, and for any of the windows sizes I set the WitP-AE game windows was always the same size and that frustrated me enough to give the SeaBee program a try.

When I loaded SeaBee by default it set the screen size to 1920x1080 and I said why not and after it created the shortcut for me and I tried it worked! Hence my OMG post lol. I have since used SeaBee to configure several shortcuts for me, but I a only really am using two, one for the 5120 x 2880 (SeaBee: 2500x1300) and one for the 3840 x 2160 (SeaBee: 1920x1000) screen resolutions.

I don't know why it works like this:

Windows Screen size:5120 x 2880
SeaBee screen size: 2500x1300

Window Screen Size: 3840 x 2160
SeaBee screen size: 1920x1000

But it works for me like that and I am ecstatic!

i.e., hence my Oh My Goodness!
lol

[Axe1999]

Hmm doesnt seem to work for me. Oh well, thanks for the help. I wanted to setup an 'upscaled' game where I could see more map at once

[Zovs]

All I can suggest is to use Sea Bee and try every lower screen resolutions you can.

[Ian R]

ORIGINAL: Axe1999

Hmm doesnt seem to work for me. Oh well, thanks for the help. I wanted to setup an 'upscaled' game where I could see more map at once

Are you using a 16:9 (x multiple) resolution?

EG: I can only get the -pxf and -pyf switches to work if I stick with 16n :9n resolution settings. "n" can be anything up to 120 with my system, but they only work with a 16:9 ratio. I'm actually using -pxf1872-pyf1053 to get some margin around the window, i.e., n= 117.

I don't know how it works on systems with very large resolutions available, that were not common 5-10 years ago when the patches were releases. You might need to run some trial & error tests.

Edit: make sure the dashes in the target line in your shortcut are the short version; sometimes if you cut and paste your switches in from elsewhere, the dashes appear as the longer version, and then the switches don't work.

[Axe1999]

ORIGINAL: Ian R

ORIGINAL: Axe1999

Hmm doesnt seem to work for me. Oh well, thanks for the help. I wanted to setup an 'upscaled' game where I could see more map at once

Are you using a 16:9 (x multiple) resolution?

EG: I can only get the -pxf and -pyf switches to work if I stick with 16n :9n resolution settings. "n" can be anything up to 120 with my system, but they only work with a 16:9 ratio. I'm actually using -pxf1872-pyf1053 to get some margin around the window, i.e., n= 117.

I don't know how it works on systems with very large resolutions available, that were not common 5-10 years ago when the patches were releases. You might need to run some trial & error tests.

Edit: make sure the dashes in the target line in your shortcut are the short version; sometimes if you cut and paste your switches in from elsewhere, the dashes appear as the longer version, and then the switches don't work.

Yes using 16:9, 2560x1440 px specifically. Tried using both SeaBee and manual switches. Anything over native screen resolution results in not usable screen, i.e. cut off vertically at Kodiak or something like that and not being able to move to the US WC.

[Nomad]

Why would you think that using a display size larger than your native screen resolution would work?

[Ian R]

Try using the -pf switches to set your window to

(a) your native screen resolution; and

(b) some smaller windows.

Anecdotal experience suggests that going over 1920:1080 in your standard type 16:9 monitor doesn't work with AE. Having said that, my understanding is the switches 'unlock' some code that was added, so that AE was compatible with, and could use the improving graphics/resolutions that came into common use over its decade of development and post-release patches. 1920:1080 is the largest window some/many users have been able to "force" it to use with the switch.

Perhaps someone with a better understanding of the technicalities could explain them, but it is worth noting that the px/py switch was originally added to provide wide screen support in the third official patch - almost 12 years ago. (V1.01.02a – February 28, 2010). At some later point, Michaelm may have added the forcing switch to enable higher resolutions, but the possible windows sizes are not open ended.

[Zovs]

Agree with the points above, you have to set the AE px/py switches smaller than your native window size.

My settings:

Native Windows Screen size: 5120 x 2880
SeaBee set screen size: 2500x1300

Native Window Screen Size: 3840 x 2160
SeaBee set screen size: 1920x1000

[Trugrit]

For me the perfect resolution for the game is 1920 x 1080 on a widescreen monitor.

I run full screen and I use the f prefix ( pxf1920, pyf1080 ) to force and hold the resolution
when I minimize the game. I still get some bleed through on the main splash screens and
occasionally in the game but not a big issue.

My current command line:
-fd -dd_sw -altFont -cpu3 -multiaudio -pxf1920 -pyf1080 -deepColor -SingleCpuOrders -skipVideo -archive

That resolution gives me perfect range rings and big enough text.

This game does not require very high resolution.
For me, high resolution just makes everything smaller and it is hard to see the small icons like the mine icon.

This game is not like a first person game where high resolution is necessary.

I also play Arma3 single player and for that game I really need to be able to tell the difference
between a marine and a Japanese soldier at 600 yards in a jungle environment with low light
Conditions. I run the graphics all the way to ultra.

[Tanaka]

Try these settings. Works great for me on a big screen and high end machine.

"E:\WITPAE\Beta2\War in the Pacific Admiral Edition.exe" -fd -skipVideo -deepColor -multiaudio -archive -altFont -cpu1 -px2048 -py1152

[Axe1999]

ORIGINAL: Nomad

Why would you think that using a display size larger than your native screen resolution would work?

With upscaled resolution you get smaller UI, which I prefer opposed to bigger one on native resolution. It works in other games, and it apparently works for OP, as he tested up to 5120x2880 px. But it is not a big deal, I can live without it.

[Zovs]

Based on my calculations of my native window screen size and what SeeBee did mine looks like half of my native window size. So your native Windows is 2560x1440 so I’d try 1280x720 for the shortcut and see if that helps or not.

[Ian R]

ORIGINAL: Zovs

Based on my calculations of my native window screen size and what SeeBee did mine looks like half of my native window size. So your native Windows is 2560x1440 so I’d try 1280x720 for the shortcut and see if that helps or not.

I'm not sure if the limit is native resolution or some fraction thereof - I think it also has some relationship with the graphics support code in the exe and how it is/is not compatible with current 2021 level graphics adaptors and software drivers, and windows 10 & updates environment, etc etc etc. I don't claim any expertise, though, that is just a general understanding. Your system/hardware/software may just play nicely with the AE code/switches, where others' do not.

This is actually something you might want to cross post in Mr Rutkins' final patch thread - can they update the graphics support switches to current screen resolutions and hardware/software compatability. please.