Screen Issues after Windows Update, 27 Oct 2017

[BillBrown]

Have you tried using the -multiaudio switch?

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

[GI Jive]

I've had the same issue since updating Windows 10 a few days ago. When I scroll over a base, the pop-up that appears seems to be the desktop behind it. I can get beyond it by clickibg on the base but this is annoying and distracting. I'm not enough of a tekkie to fix it. I'm hoping someone else comes up with a fix that won't detract from playability.

[Theages]

Windows 10 1709 (Fall Creator's Update) indroduces a new driver model (WDDM 2.3), which means Microsoft has again changed the code for screen display.
On my laptop (a Dell XPS 15 (9550) I am using the same drivers as on Win10 1703 (Dell modified drivers for Intel HD530 and NVIDIA 960m).
Not using -dd_sw results in the known scroll lag. Using -dd_sw - and therefore disabling hardware implemented DirectDraw - results in increased bleed-through of desktop contents (the game is clearing the info boxes but does not refresh the underlying map), which got worse since Win10 1703. (same results when using Intel or NVIDIA)
The problem could be solved in 3 ways:
- Microsoft provides a fix for software DirectDraw preventing the bleed-through
- the GPU manufacturer "repairs" hardware DirectDraw (maybe cooperation with Microsoft is necessary)
- WitPAE code is updated to better refresh graphics.

Since WitPAE is rather old, MS and GPU manufacturers won't care.
I fear, updating WitPAE would require a major recoding effort, which is highly unlikely to happen.

[MarcA]

Well that's made the game unplayable. At least until someone updates something.

How did microsoft loose it's way so badly?

P.s. I also tried it out in compatability mode but it made no difference.

[USSAmerica]

I don't know what's different on my computer, but I don't have this bleed through issue, even with -dd_sw used. Can't say I'm upset. [;)]

Edit: Hmmm, I seem to still be at Windows 10 version 1703 instead of the 1709 update that is causing problems. My luck may run out soon. [X(]

[witpqs]

ORIGINAL: USSAmerica

I don't know what's different on my computer, but I don't have this bleed through issue, even with -dd_sw used. Can't say I'm upset. [;)]

Edit: Hmmm, I seem to still be at Windows 10 version 1703 instead of the 1709 update that is causing problems. My luck may run out soon. [X(]

It will be interesting to see. This cannot be the only community within the MS Windows 10 galaxy that would have such an issue.

[LST Express]

Was having same issue so I uninstalled the update and the game is working fine again.

[USSAmerica]

ORIGINAL: LST Express

Was having same issue so I uninstalled the update and the game is working fine again.

Hey LST, can you let us know exactly which update you uninstalled to correct the issue?

[LST Express]

Went back to 1703 from 1709.

[Chris21wen]

Seems I'm a lucky one I have no problems but I do turn off all the crap that comes with every new Windows 10 update, basically running with windows classic style. These are the switches I use but I've no idea why I use cpu4, must have been a reason but I'm a 'If it works don't f*** with it' guy. Wish Microsoft was

"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

[Chris21wen]

ORIGINAL: LST Express

Went back to 1703 from 1709.

As I understood it windows will automatically try and reinstall it unless you have the professional version? Could someone clarity that?

[Ginetto]

Windows 10 has been an enduring severe irritant with WITP-AE since the very beginning. Personally I've had to spend hours fiddling with switches before hitting on the right formula. For some reason fortunately my pc is still running on version 1703 of Win10. I dread the day when 1709 will be foisted on me.
So those of us who grouse that Matrix games should also still run on WinXP have all my sympathy, in spite of the ill-tempered comments of a few on how cheap etc it is to upgrade.
It's time now for Matrix to come up with a Win10-resistant WITP-AE version. The game is too iconic and important to see it wither away because Microsoft keeps playing around with its OS.
Any hope Matrix Games???

[BBfanboy]

ORIGINAL: Ginetto

Windows 10 has been an enduring severe irritant with WITP-AE since the very beginning. Personally I've had to spend hours fiddling with switches before hitting on the right formula. For some reason fortunately my pc is still running on version 1703 of Win10. I dread the day when 1709 will be foisted on me.
So those of us who grouse that Matrix games should also still run on WinXP have all my sympathy, in spite of the ill-tempered comments of a few on how cheap etc it is to upgrade.
It's time now for Matrix to come up with a Win10-resistant WITP-AE version. The game is too iconic and important to see it wither away because Microsoft keeps playing around with its OS.
Any hope Matrix Games???

Funny - I was thinking the opposite - that users should send Microsoft their complaints so that MS takes action to fix the issue in Win10.10. If this problem affects other gamers as well there may be enough of a groundswell to get them to fix the code.

Me, I stuck with Win 7 SP2 so I have a game that is no longer supported on an O/S that is no longer supported - and it works fine!

[Ginetto]

Yes. Ideally we should appeal to Microsoft, the manufacturer of the troublesome OS. But they are the proverbial 400 lb gorilla. Hopeless for us. Matrix Games, instead, knows who we are and have more empathy for our concerns.
Matrix Games, hint hint?

[Oldguard1970]

BBFanboy notes he is still using Win 7.

I spent $50 for a used desktop with WinXP. Now I can play Tiller's Civil War in addition to other older unsupported games.

Windows has a backwards compatibility feature that works sometimes, but not always. The old machine for older games serves as a work-around for the moment.

All the best, John

[wdolson]

ORIGINAL: Ginetto

Windows 10 has been an enduring severe irritant with WITP-AE since the very beginning. Personally I've had to spend hours fiddling with switches before hitting on the right formula. For some reason fortunately my pc is still running on version 1703 of Win10. I dread the day when 1709 will be foisted on me.
So those of us who grouse that Matrix games should also still run on WinXP have all my sympathy, in spite of the ill-tempered comments of a few on how cheap etc it is to upgrade.
It's time now for Matrix to come up with a Win10-resistant WITP-AE version. The game is too iconic and important to see it wither away because Microsoft keeps playing around with its OS.
Any hope Matrix Games???

It isn't really for Matrix to do, they are the publishers of the game. Henderson Field Design has the source code, as far as I know Matrix doesn't. The problem is the programmers from the AE project are all busy with their "day jobs".

I'm pretty sure the problems with running on Win 10 are DirectX compatibility issues and AE badly needs to be updated to more modern DirectX calls. I have thought about fixing it, but my life has been insane since June of 2016.

Bill

[decaro]

ORIGINAL: GI Jive

I've had the same issue since updating Windows 10 a few days ago. When I scroll over a base, the pop-up that appears seems to be the desktop behind it. I can get beyond it by clickibg on the base but this is annoying and distracting. I'm not enough of a tekkie to fix it. I'm hoping someone else comes up with a fix that won't detract from playability.

So am I. So are we all.
And I always cringe whenever I get a massive Win update.

[LST Express]

I'm still on version 1703 with no problems and Microsoft hasn't tried to force the upgrade on me again. But from reading these two threads it sounds like that will happen at some point.[&:]

[Chris21wen]

ORIGINAL: LST Express

I'm still on version 1703 with no problems and Microsoft hasn't tried to force the upgrade on me again. But from reading these two threads it sounds like that will happen at some point.[&:]

Please read my post in this thread tm.asp?m=4390639&mpage=2&key=