Making the last Beta Official

[Kull]

ORIGINAL: Tanaka

Thanks for the tips and link to that thread. I have also tried with and without that -dd_sw switch and neither seems to have resolved the bleed issue but removing it fixed my lag issue. I seem to get the bleed issue more with the more graphics intensive Kamikaze Bellum map. I have always used full screen as I cannot stand windows mode. I will post to the thread you linked.

Just so you know, there is NO SOLUTION to bleedthrough in Full Screen mode. Some people don't have the problem (and nobody has been able to figure out why), but for those who do get it? The only fix is to use windowed mode.

Edit: Actually there is one solution - use the -dd_sw switch. Unfortunately that gives you the lag issue, so it's not a true fix. For reference, Microsoft added the "bleedthrough bug" to Windows 10 back in 2017. Here's the thread where it was first reported, and we all tried everything in order to fix it.

[Nomad]

I really do not understand why so many are opposed to using windows mode. Set up right it will use about 95% of the screen.
On my 2560 x 1600 monitor I use a window of 2550 x 1535.

[Tanaka]

ORIGINAL: Nomad

I really do not understand why so many are opposed to using windows mode. Set up right it will use about 95% of the screen.
On my 2560 x 1600 monitor I use a window of 2550 x 1535.

If I can get it to do that I will try. How do you get it to fill up 95% of your screen?

[Tanaka]

ORIGINAL: Kull

ORIGINAL: Tanaka

Thanks for the tips and link to that thread. I have also tried with and without that -dd_sw switch and neither seems to have resolved the bleed issue but removing it fixed my lag issue. I seem to get the bleed issue more with the more graphics intensive Kamikaze Bellum map. I have always used full screen as I cannot stand windows mode. I will post to the thread you linked.

Just so you know, there is NO SOLUTION to bleedthrough in Full Screen mode. Some people don't have the problem (and nobody has been able to figure out why), but for those who do get it? The only fix is to use windowed mode.

Edit: Actually there is one solution - use the -dd_sw switch. Unfortunately that gives you the lag issue, so it's not a true fix. For reference, Microsoft added the "bleedthrough bug" to Windows 10 back in 2017. Here's the thread where it was first reported, and we all tried everything in order to fix it.

Gotcha very interesting thanks!

[witpqs]

ORIGINAL: Nomad

I really do not understand why so many are opposed to using windows mode. Set up right it will use about 95% of the screen.
On my 2560 x 1600 monitor I use a window of 2550 x 1535.

+1

[Nomad]

ORIGINAL: Tanaka

ORIGINAL: Nomad

I really do not understand why so many are opposed to using windows mode. Set up right it will use about 95% of the screen.
On my 2560 x 1600 monitor I use a window of 2550 x 1535.

If I can get it to do that I will try. How do you get it to fill up 95% of your screen?

The easiest way is probably download and use SeaBee Alpha, find the sticky thread in the tech subforum.

A second way would depend on what kind of graphics card you are using.

[Zovs]

I second the Windows mode, that is what I use and I used Sea Bee to get about 90% screen coverage (maybe it’s 95%). It just works and looks good.

[actrade]

That doesn't work for me. I have a 2560x1440 resolution and when I changed it to 2550 (or 2540 or others) x 1430 (1420 and others) I get a very small window maybe 1/3rd of my screen?

[Nomad]

ORIGINAL: actrade

That doesn't work for me. I have a 2560x1440 resolution and when I changed it to 2550 (or 2540 or others) x 1430 (1420 and others) I get a very small window maybe 1/3rd of my screen?

Did you use the -pxf and -pyf switches? If you used -px and -py switches they will not work unless you set up a custom resolution.

[Tanaka]

ORIGINAL: actrade

That doesn't work for me. I have a 2560x1440 resolution and when I changed it to 2550 (or 2540 or others) x 1430 (1420 and others) I get a very small window maybe 1/3rd of my screen?

Yeah tried the SeaBees and it only takes up the full screen windowed if I keep it at 2560x1440. This makes things too small for me to see. I've been playing at 2048x1152 fullscreen without Seabees windowed and it works great. Just the annoying bleed I posted above during recons. I guess I can live with that to get the screen preference and game speeds I want. The only other oddity that I've noticed besides Emily base arcs not showing up is when fighters are set to 100 ft to strafe they show up out and above the combat box...

[HansBolter]

ORIGINAL: Nomad

I really do not understand why so many are opposed to using windows mode. Set up right it will use about 95% of the screen.
On my 2560 x 1600 monitor I use a window of 2550 x 1535.

What is to understand about a personal preference?

Why do people get treated like there is something wrong with them because they have one?

For some of us, windowed mode simply does not constitute a 'fix'.

[durnedwolf]

ORIGINAL: jwilkerson

The three high level phases of getting this done

1 - Produce initial public beta - this would include everything that would be in the final release
(( we would expect to iterate on public beta releases for a while, to fix issues found during the beta period ))

2 - Go GOLD
(( once we think we are stable, we'll work with Matrix to prepare the final version for release ))

3 - Public Release
(( Once the final version is ready - Matrix will release to the pubic ))

So right now, we're working on step 1. Once you see that available, you'll know we're in the beta period for this release !!

Would you consider updating/creating a tutorial - maybe along the lines of a YouTube video or three, that walks through best practices on how to conduct air/naval/land operations? And maybe a separate video on best practices while playing the side of Japan? I think a lot of people just don't know how to play as Japan and things you do (or don't do) at the beginning of the game for the side of Japan can really have a strong impact in the later stages of the game.

[HansBolter]

Found another bug to add to the list of things to fix.

When carriers are stationed at a port providing the infrastructure necessary to allow air squadrons to be able to take replacements, and replenishment carriers are also present with functioning replenishment squadrons, the air squadron interfaces provide two sets of buttons for manually drawing replacements, one for drawing from the pool and one for drawing from the replenishment squadrons.

Replacements get drawn from the replenishment squadrons regardless of which set of buttons is used.
Clicking on the 'draw from the pool' buttons results in the draw coming from the replenishment squadrons, not the pool.

[actrade]

ORIGINAL: Tanaka

ORIGINAL: actrade

That doesn't work for me. I have a 2560x1440 resolution and when I changed it to 2550 (or 2540 or others) x 1430 (1420 and others) I get a very small window maybe 1/3rd of my screen?

Yeah tried the SeaBees and it only takes up the full screen windowed if I keep it at 2560x1440. This makes things too small for me to see. I've been playing at 2048x1152 fullscreen without Seabees windowed and it works great. Just the annoying bleed I posted above during recons. I guess I can live with that to get the screen preference and game speeds I want. The only other oddity that I've noticed besides Emily base arcs not showing up is when fighters are set to 100 ft to strafe they show up out and above the combat box...

Doh! I just re-read this post and missed putting the F in the px/py...works like a charm as you can keep experimenting until it's perfect. Thanks!

[witpqs]

Here is an example of how the screen looks when that bug happens of failing to refresh all the layers when the screen is scrolled or shifts for other reasons (such as clicking on something).

To 'fix it' you need to try to scroll the screen in random directions until all the layers refresh.

It happens a great deal of the time and it would be very nice if the bug could be eliminated.

[seanmac456]

My biggests asks would be reducing the input delay in full screen and making it so it doesn't freak out if I alt Tab
A rather significant but immensely welcomed addition would be UI Hyper links when specific hexes are mentioned.
WASD camera movement would be welcome as well

[BBfanboy]

ORIGINAL: witpqs

Here is an example of how the screen looks when that bug happens of failing to refresh all the layers when the screen is scrolled or shifts for other reasons (such as clicking on something).

To 'fix it' you need to try to scroll the screen in random directions until all the layers refresh.

It happens a great deal of the time and it would be very nice if the bug could be eliminated.

Never had the bug - ever. My switches
"C:\Matrix Games\War in the Pacific Admiral's Edition\War in the Pacific Admiral Edition.exe" -altFont -archive -dd_sw -deepColor -px1680 -py1050 -w -fixedArt -skipVideo -multiaudio -SingleCpuOrders -cpu3

[Ian R]

I've had that occasionally, but mostly on a previous hardware set-up where it had been running for a while and I suspect the cache was filled up, reducing RAM space.

In my current rig it is a very infrequent, and very temporary, occurrence.

I'm thinking, not an actual Bug, but, might be helped by some tweaking of the switches that promote compatibility with modern graphics cards.

[witpqs]

ORIGINAL: Ian R

I've had that occasionally, but mostly on a previous hardware set-up where it had been running for a while and I suspect the cache was filled up, reducing RAM space.

In my current rig it is a very infrequent, and very temporary, occurrence.

I'm thinking, not an actual Bug, but, might be helped by some tweaking of the switches that promote compatibility with modern graphics cards.

Tweaking reduced reduced it from 'overwhelming' to 'a great deal of the time'. Never eliminated it.

It is temporary only in the sense that when you finally are lucky enough to jink the view just right, all the layers repaint.

[BBfanboy]

ORIGINAL: witpqs

ORIGINAL: Ian R

I've had that occasionally, but mostly on a previous hardware set-up where it had been running for a while and I suspect the cache was filled up, reducing RAM space.

In my current rig it is a very infrequent, and very temporary, occurrence.

I'm thinking, not an actual Bug, but, might be helped by some tweaking of the switches that promote compatibility with modern graphics cards.

Tweaking reduced reduced it from 'overwhelming' to 'a great deal of the time'. Never eliminated it.

It is temporary only in the sense that when you finally are lucky enough to jink the view just right, all the layers repaint.

Too many overlays? I never run with F6 Hex side detail or Z search arcs on while moving the map borders. The only range arcs I use are the ones for TFs which disappear when I de-select the TF.