Today's Wn 10 update is causing...

[Major Shane]

I have had the same problem since installing the Win10 update. Thanks to this post I was able to solve the issue by taking two actions.

1. I turned off the transparency button that "witpqs" mentioned in his post above. This didn't solve the problem, but it improved my scrolling speed.

2. I added the "-w" to the command string. I have my task bar to small icons, auto hide. My command string is: "C:\Matrix Games\War in the Pacific Admiral's Edition\War in the Pacific Admiral Edition.exe" -px1366 -py768 -skipVideo -archive -fd -altFont -deepColor -cpu4 -SingleCpuOrders -SingleCpuStart -multiaudio -dd_sw -d -w"

I did not make any changes to the Win 10 updates. My computer is running Win 10 on and AMD A8-7410 APU with AMD Raedon R5 Graphics 220 GHz.

[caballo71]

I have the same problem w10, last update.

Try the option of the Witpqs message. It did not work And I left it as my w10 was configured.

I just tried the window -w configuration has really stopped showing the problem, with a small loss obviously on top because of the appearance of the program name.

"C: \ GAMES \ WITP-AE \ War in the Pacific Admiral Edition.exe" -skipVideo -SingleCpuOrders -fixedArt -altFont -multiaudio -dd_sw -deepColor -fd -px1280 -py1024 -d -w

I will try with some resolutions, as one of you comments, to try to win some screen.

[Capt Cliff]

I don't have this "Make Start, Taskbar, and action center transparency" switch in my Colors settings window!!??...

[Capt Cliff]

Problem NOT solved ... BUT MAYBE! I added the -f command and it seems to disable the flaggy windows key and no more bleed through. But after closing all my windows and restarting the game the bleed through was back. Is there a way to disable the Window Flag Key? That might solve the problem.

OK! I added a px and py value to the command line -px3000 -py2000 ... with a -f command. Just a -f command don't work. Now here's something weird if I run it with 2 or more other windows open, say Chrome and control panel or what ever, then the problem seems to go away or is not as bad. But it is still lurking. If I close all windows and run WitP the problem comes back ... This is nuts ... I still need a stable fix.

[Capt Cliff]

ORIGINAL: Theages

I have done some testing. It seems that running Fullscreen (the -f switch) will always have the "bleed-through" effect.
Using the -w switch (windowed mode) does not seem to have this effect. The problem with windowed mode is the size of the window.
When you use your monitors native resolution for the -px and -py switches, the window is too big. Especially the taskbar is overlapping the game window. The Hide Taskbar option will alleviate this, but there are still some pixel overlapped by the tiny bar on the bottom.

To solve this problem you have to adjust the size of the window.
For a monitor with a native resolution of 1920x1080 (at 60Hz) that would mean to set the window size using -px1980 -py1000.
If your graphics card does support this resolution (unlikely) that is all what it takes.
On my Intel HD 530 that resolution does not work, since 1980x1000 is no valid monitor resolution.

BUT: The Intel driver allows to define custom monitor resolutions. My native language is german, so I have guess at what the english translation is. I think it should be something like this: In the taskbar there is an icon for the Intel Graphic Settings. Opening this settings leads to a screen, where you click on the Display picture. On the following screen choose Custom Resolution. Confirm with Yes. Enter the values for Width (1980), Height (1000) and Refresh rate (60). Click Add. Confirm with Yes.
That's it.

If your window seems to wide you can also use a lower value instead of 1920. NOTICE: sometimes the value you enter is not the value that is created. Eg.: when I entered 1900 x 1000 x 60, the created resolution was 1904 x 1000 x 60. You have to adjust your -px and -py values accordingly.

For different GPU manufacturers there should be a similar method.

Using the -w command and you px py values always gives me a small window that I can not enlarge. I have a Radeon R7 370 so I am not sure what it's max px py values are but the window display is about 33% of my total screen capability. I tried px3000 and py 2000 but the window size is always the same.

[Capt Cliff]

Ok, I tried something I found on the web something about bleed through with other programs. Go to Control Panel > System > Advance System Settings > Performance Settings > Advance and change Adjust for best performance to Programs. It seems to work BUT it does occasionally bleeds through but it is some what manageable, just click on an empty sea hex. We need a stable fix!!

Sorry to say but the above method is not working! I even tried the disabling of the Enable Peek function to no avail! The desktop continues to bleed through onto the game display. It is definitely a mouse over problem. Are there any program switches that deal with the mouse?

The game is unplayable in this condition, unless you play in window mode (-w) with a postage size screen display! Inputting px & py values has no affect on the -w window size. Using -w + -f doesn't work either. Sad end for this game.

[caballo71]

I have tried with several screens, in the end I am left with the resolution -px1280 -py1024 -w -d
If I do so directly, I do not see the industry line.
So I had to go back to properties and run this program in compatibility mode for W8.
So I can see that line (not entire) without much screen loss in that resolution.
If I want to see that line in its entirety I have to go to py960

[Capt Cliff]

A solution, at least for me. I eliminated the -dd_sw switch from my command line and it worked. *knock on wood*

[caballo71]

That configuration works for me .. Thank you.

[USSAmerica]

Ok, so my desktop started asking me to update to this Win10 version. I still have my laptop so I went for it. Now, I have always played in windowed mode and didn't change any of my switches so I was pleasantly surprised to not see this bleed through issue after the update. I think I am confirmation that windowed mode does not have this problem. Can anyone else confirm this?

[Theages]

ORIGINAL: Capt Cliff

Using the -w command and you px py values always gives me a small window that I can not enlarge. I have a Radeon R7 370 so I am not sure what it's max px py values are but the window display is about 33% of my total screen capability. I tried px3000 and py 2000 but the window size is always the same.

Your problem is, that the AMD Driver does not "know" the resolution, you set with -px and -py. Therefore the game falls back to its standard resolution.
3000x2000 is no standard monitor resolution. You either have to use a standard resolution (eg. 2560x1440) or define a custom resolution in the driver settings. I don't have an AMD card, so I can't test it. The option should be somewhere in AMD Radeon Settings on the Display tab. DON'T choose it as desktop resolution, just define it.

Going Fullscreen (-f switch) will work, but many are plagued by the abysmal scrolling speed (when not using -dd_sw). Up to Win 8.1 I didn't have any lag (using Intel and NVIDIA drivers). Win10 introduced the problem, causing me (and many others) to use the -dd_sw switch (DirectDraw is emulated by software and not done in Hardware (GPU driver)).
Up to Win10 version 1703 the bleedthroughs were only from other open windows or taskbar icons (eg. the time updating), with 1709 the bleedthroughs happen with nearly every mouseover popup, when you move the mouse away and the map should reappear (instead the underlying desktop portion is shown).

[Capt Cliff]

ORIGINAL: Theages

ORIGINAL: Capt Cliff

Using the -w command and you px py values always gives me a small window that I can not enlarge. I have a Radeon R7 370 so I am not sure what it's max px py values are but the window display is about 33% of my total screen capability. I tried px3000 and py 2000 but the window size is always the same.

Your problem is, that the AMD Driver does not "know" the resolution, you set with -px and -py. Therefore the game falls back to its standard resolution.
3000x2000 is no standard monitor resolution. You either have to use a standard resolution (eg. 2560x1440) or define a custom resolution in the driver settings. I don't have an AMD card, so I can't test it. The option should be somewhere in AMD Radeon Settings on the Display tab. DON'T choose it as desktop resolution, just define it.

Going Fullscreen (-f switch) will work, but many are plagued by the abysmal scrolling speed (when not using -dd_sw). Up to Win 8.1 I didn't have any lag (using Intel and NVIDIA drivers). Win10 introduced the problem, causing me (and many others) to use the -dd_sw switch (DirectDraw is emulated by software and not done in Hardware (GPU driver)).
Up to Win10 version 1703 the bleedthroughs were only from other open windows or taskbar icons (eg. the time updating), with 1709 the bleedthroughs happen with nearly every mouseover popup, when you move the mouse away and the map should reappear (instead the underlying desktop portion is shown).

I solved the problem by removing the -dd_sw command ... problem solved.

[Lecivius]

ORIGINAL: Capt Cliff

ORIGINAL: Theages

ORIGINAL: Capt Cliff

Using the -w command and you px py values always gives me a small window that I can not enlarge. I have a Radeon R7 370 so I am not sure what it's max px py values are but the window display is about 33% of my total screen capability. I tried px3000 and py 2000 but the window size is always the same.

Your problem is, that the AMD Driver does not "know" the resolution, you set with -px and -py. Therefore the game falls back to its standard resolution.
3000x2000 is no standard monitor resolution. You either have to use a standard resolution (eg. 2560x1440) or define a custom resolution in the driver settings. I don't have an AMD card, so I can't test it. The option should be somewhere in AMD Radeon Settings on the Display tab. DON'T choose it as desktop resolution, just define it.

Going Fullscreen (-f switch) will work, but many are plagued by the abysmal scrolling speed (when not using -dd_sw). Up to Win 8.1 I didn't have any lag (using Intel and NVIDIA drivers). Win10 introduced the problem, causing me (and many others) to use the -dd_sw switch (DirectDraw is emulated by software and not done in Hardware (GPU driver)).
Up to Win10 version 1703 the bleedthroughs were only from other open windows or taskbar icons (eg. the time updating), with 1709 the bleedthroughs happen with nearly every mouseover popup, when you move the mouse away and the map should reappear (instead the underlying desktop portion is shown).

I solved the problem by removing the -dd_sw command ... problem solved.

It does solve the problem, but causes a huge lag in the mouse interface. You can 'click' on something, and then sit back and have a cup of coffee waiting for a response.

[ReadyR]

I read this thread and got really depressed. My Windows 10 Update resulted in the same bleeding issues and really spoiled the game for me. Having waited for years for retirement to have the time to devote to this game, and having spent the last 18 months or so getting into it...I was just starting to have real fun. Now this. I spent last evening trying everything people have mentioned...for me playing with full screen mode is impossible. However, when playing in windows mode, everything runs smoothly. The issue is how to get the window itself to a playable size. Tried two things...using the Magnifier feature of Windows to allow me to see close up when I am working on units. That is not ideal but offered some promise. Others might want to see how it works with their play style. The second thing was to play around with the px and py settings in the command line. I found that for my screen a setting of px1600 and py of 900 gives me about 4/5ths of my screen. Not perfect but very playable, without the resort to a Magnifier. Hope this helps someone out there ...

[Theages]

4/5ths of the screen would mean your screen resolution is 1920x1080. Am I right?
You could get a bigger window when defining a custom resolution. How to do that depends on your graphics card (Intel, AMD, NVIDIA etc)
For Intel see my first post in this topic.
For NVIDIA see also here

[ReadyR]

Thanks. You are right on my resolution. I am using an AMD and can't seem to get past the default values for resolution that they have in their graphics control centre widget.

[patrickl]

Well my laptop has downloaded 1709 but requires restart to finish installing the update. As long as I hit shut down and not restart, I pray I don't see 1709 around. [:)]

[witpqs]

ORIGINAL: patrickl

Well my laptop has downloaded 1709 but requires restart to finish installing the update. As long as I hit shut down and not restart, I pray I don't see 1709 around. [:)]

Eventually HAL will lock you out of the pod bay until you gasp for air and capitulate.

[Chris21wen]

ORIGINAL: USSAmerica

Ok, so my desktop started asking me to update to this Win10 version. I still have my laptop so I went for it. Now, I have always played in windowed mode and didn't change any of my switches so I was pleasantly surprised to not see this bleed through issue after the update. I think I am confirmation that windowed mode does not have this problem. Can anyone else confirm this?

Yes. I'd go further, I've never had any problems with any update playing in windowed mode once I settles on this.

"C:\Matrix Games\WitP AE\Beta2\War in the Pacific Admiral Edition.exe" -px1600 -py900 -cpu4 -SingleCpuOrders -dd_sw -altFont -multiaudio -deepColor -skipVideo -archive -w

I think the most important thing is the size of the window I use is a native size for my display. I tried using the max 1920 x 1080 as I did sizes in between and got weird effects until I settled on 1600 x 900 way back even before Windows 10.

[Lecivius]

I'm seeing a consensus on the 2 threads going that running in windowed mode clears this problem. I may have to tinker with that a bit.