Frustrating Display glitches (Full Version)

All Forums >> [New Releases from Matrix Games] >> War in the Pacific: Admiral's Edition >> Tech Support



Message

Jmsimer -> Frustrating Display glitches (7/21/2017 10:30:57 PM)

Apologies if this has been addressed - I could not find it in a forum search.

I have two problems...
1) If I run the game in windowed mode, occasionally it locks up instantly and completely when I open the operations report. Since that means I lost everything since the last save, I usually run in full screen.

2) Running in full screen, I have had problems that usually start with the ops report showing with carriage returns in the wrong places, then very quickly I will start to get black background on text, then the bottom-of-screen icons go black, and before long just about everything goes black. It USED to be that if I saved and exited the game completely, then restarted the game, all wouldbe right again...
But since switching to Windows 10, when I exit the game at this point I often find my windows display has gone black, and I can't alt-tab or otherwise switch to other programs. I can't get the display to reset, so I have to restart the computer.

I've tried "set affinity" and it improves game performance but has no impact on either problem.

Here is the command line I use: "C:\Matrix Games\War in the Pacific Admiral's Edition\WITP_Affinity.exe" -cpu2 -multiaudio -f dd_sw -deepColor -px1366 -py768."



Jmsimer -> RE: Frustrating Display glitches (7/21/2017 10:34:45 PM)

Here is my "dxdiag" file...



Korvar -> RE: Frustrating Display glitches (7/22/2017 12:29:35 AM)

Let's start with that you're missing the "-" on 
-dd_sw
How does that affect the issues you mentioned?



BillBrown -> RE: Frustrating Display glitches (7/22/2017 12:53:04 AM)

Plus I am not entirely sure what WITP_Affinity.exe does, but cpu2 sets the exe to use only cpu #2.

From the patch notes:
-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.

So it would seem that the two are redundant.



Jmsimer -> RE: Frustrating Display glitches (7/22/2017 3:04:38 AM)

I dropped that particular "-" in the process of adding and removing the dd_sw switch a few times to see whether it had any effect. It does not appear to matter if the switch is on, off, or (in the most recent case) inadvertently mistyped.



Jmsimer -> RE: Frustrating Display glitches (7/22/2017 3:06:08 AM)

Good point, they probably are redundant. However, I have tried it with and without the "affinity" set, and it does not make a difference for this particular error.

The "affinity" trick was described a few years ago on this forum.

quote:

ORIGINAL: BillBrown

Plus I am not entirely sure what WITP_Affinity.exe does, but cpu2 sets the exe to use only cpu #2.

From the patch notes:
-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.

So it would seem that the two are redundant.





Korvar -> RE: Frustrating Display glitches (7/22/2017 6:26:43 AM)

From your DXDiag file I noticed that your Win 10 isn't updated (that may intentional) and that you're not using DirectX 12. Not that WitPAE uses DX12, but it's just a general trend I'm seeing from the file. And did you do a fresh install of Windows 10 or was it an upgrade installation?

Have you tried a fresh re-install of WitPAE? I don't suspect that this is the issue but it's relatively quick to check it off the list.

Also, see my post regarding a complete re-installation of your video drivers.



Jmsimer -> RE: Frustrating Display glitches (7/22/2017 3:45:50 PM)


Good catchon the windows. Turns out the system stopped installing updates months ago and I got no error messages, so now I am fixing that. The black screen problem has been occurring for years, but only recently became more frequent and starting screwing up the display even after exiting the game. So I'll try fixing the updates and see if it has any effect.
quote:

ORIGINAL: Korvar

From your DXDiag file I noticed that your Win 10 isn't updated (that may intentional) and that you're not using DirectX 12. Not that WitPAE uses DX12, but it's just a general trend I'm seeing from the file. And did you do a fresh install of Windows 10 or was it an upgrade installation?

Have you tried a fresh re-install of WitPAE? I don't suspect that this is the issue but it's relatively quick to check it off the list.

Also, see my post regarding a complete re-installation of your video drivers.




BBfanboy -> RE: Frustrating Display glitches (7/22/2017 5:15:10 PM)


quote:

ORIGINAL: Jmsimer


Good catchon the windows. Turns out the system stopped installing updates months ago and I got no error messages, so now I am fixing that. The black screen problem has been occurring for years, but only recently became more frequent and starting screwing up the display even after exiting the game. So I'll try fixing the updates and see if it has any effect.
quote:

ORIGINAL: Korvar

From your DXDiag file I noticed that your Win 10 isn't updated (that may intentional) and that you're not using DirectX 12. Not that WitPAE uses DX12, but it's just a general trend I'm seeing from the file. And did you do a fresh install of Windows 10 or was it an upgrade installation?

Have you tried a fresh re-install of WitPAE? I don't suspect that this is the issue but it's relatively quick to check it off the list.

Also, see my post regarding a complete re-installation of your video drivers.



Sounds like a graphics card problem. First thing to try is checking if the card is seated properly. Make sure you have bled off all the static electricity in your body before doing this, or wear non-conductive gloves. I usually touch the screw on a light switch cover since it is grounded via the switch box ground wire.



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
1