RE: Today's Wn 10 update is causing...

RE: Today's Wn 10 update is causing... (Full Version)

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

Message

Theages -> RE: Today's Wn 10 update is causing... (12/12/2017 4:57:52 PM)
quote: 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 -> RE: Today's Wn 10 update is causing... (12/13/2017 2:48:50 PM)
quote: ORIGINAL: Theages quote: 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 -> RE: Today's Wn 10 update is causing... (12/13/2017 2:56:23 PM)
quote: ORIGINAL: Capt Cliff quote: ORIGINAL: Theages quote: 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 -> RE: Today's Wn 10 update is causing... (12/13/2017 5:12:09 PM)
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 -> RE: Today's Wn 10 update is causing... (12/13/2017 6:20:05 PM)
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 -> RE: Today's Wn 10 update is causing... (12/13/2017 8:21:18 PM)
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 -> RE: Today's Wn 10 update is causing... (12/13/2017 11:49:11 PM)
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 -> RE: Today's Wn 10 update is causing... (12/14/2017 12:11:49 AM)
quote: 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 -> RE: Today's Wn 10 update is causing... (12/14/2017 5:55:56 AM)
quote: 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. [image]local://upfiles/5388/217BE3DB63A6481297A58CBEB62F6CBE.jpg[/image]

Lecivius -> RE: Today's Wn 10 update is causing... (12/14/2017 1:27:59 PM)
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.

wolfclan -> RE: Today's Wn 10 update is causing... (12/20/2017 12:41:30 AM)
It is worth trying out removing -dd_sw . It solved the problem for me with only a minor slow down in the mouse interface. I don't know what has happened over the years, but, I was experiencing the very slow mouse interface when I first entered -dd_sw, but not now, just a minor degradation

39battalion -> RE: Today's Wn 10 update is causing... (12/21/2017 4:58:29 AM)
Yes removing -dd_sw worked for me also. There is only a minor slowdown with the mouse interface. Thank goodness as the wallpaper bleedthrough was making the game unplayable.

bristolduke -> RE: Today's Wn 10 update is causing... (12/21/2017 2:36:04 PM)
quote: ORIGINAL: Chris21wen quote: 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. [image]local://upfiles/5388/217BE3DB63A6481297A58CBEB62F6CBE.jpg[/image] So in my case adding the dd_sw seemed to fix the problem. However, now the mouse does not work going down or going to the right. Works fine going left and up.

Rogue187 -> RE: Today's Wn 10 update is causing... (12/22/2017 1:37:15 AM)
After doing my windows 10 update, i am experiencing the bleed though of the background whenever i hover the mouse over a base, tf, airgroup...well anything and i am left with an image of my desktop on the screen until i pan the map. But recently it seems to gotten worse. The screen will flash and i will be staring at the desk top. If i pan the mouse, it will flash back to the game. I am running the game in full screen mode and not windowed mode. Is there any fix for this?

moore4807 -> RE: Today's Wn 10 update is causing... (12/22/2017 2:39:45 AM)
Rogue - you seem stuck like many of us. If we go to command line and remove -dd_sw switch, the result is glacially slow mouse and map movement - BUT no desktop/map fragments. If we install the -w switch, then add -pw + -py dimensions (which are a mystery to most to figure out correctly) BUT at least the partial screen works properly and mouse and map speeds are back to normal. Finally if I restore the command line switches back to original - I'm right back where I started from and have a buggy map, but at least I can play... Summary complete (or so I think!)

Capt Cliff -> RE: Today's Wn 10 update is causing... (12/22/2017 2:30:19 PM)
quote: ORIGINAL: Lecivius quote: ORIGINAL: Capt Cliff quote: ORIGINAL: Theages quote: 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. Sorry but I am not seeing that problem. My mouse works fine with no lag.Here are the commands I use; -deepColor -cpu2 -archive -autosave -f

Lecivius -> RE: Today's Wn 10 update is causing... (12/22/2017 2:35:09 PM)
I have something similar. I will have to get my laptop out to verify.

BBfanboy -> RE: Today's Wn 10 update is causing... (12/22/2017 3:54:05 PM)
quote: ORIGINAL: Capt Cliff quote: ORIGINAL: Lecivius quote: ORIGINAL: Capt Cliff quote: ORIGINAL: Theages quote: 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. Sorry but I am not seeing that problem. My mouse works fine with no lag.Here are the commands I use; -deepColor -cpu2 -archive -autosave -f +1 Scroll Delay, mouse movement and speed of turn execution all improved when I added -SingleCpuOrders and -cpu2.

Chris21wen -> RE: Today's Wn 10 update is causing... (12/23/2017 5:13:25 AM)
Something I've not seem mentioned, could the order the switches are used in have any effect? Beyond my pay graded to say yeh or nay.

BBfanboy -> RE: Today's Wn 10 update is causing... (12/23/2017 5:20:44 AM)
quote: ORIGINAL: Chris21wen Something I've not seem mentioned, could the order the switches are used in have any effect? Beyond my pay graded to say yeh or nay. no effect AFAIK. Sequence never mentioned in any discussions.

witpqs -> RE: Today's Wn 10 update is causing... (12/23/2017 12:46:04 PM)
quote: ORIGINAL: BBfanboy quote: ORIGINAL: Chris21wen Something I've not seem mentioned, could the order the switches are used in have any effect? Beyond my pay graded to say yeh or nay. no effect AFAIK. Sequence never mentioned in any discussions. Concur, no effect.

wegman58 -> RE: Today's Wn 10 update is causing... (12/23/2017 6:43:09 PM)
quote: ORIGINAL: 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. I had the problem, copied the above, changed the px and py values to 1920 x 1080 and it worked. A bit smaller, but it worked. -w is the key

geofflambert -> RE: Today's Wn 10 update is causing... (12/24/2017 9:33:36 AM)
You know, Microsoft has phalanxes of people occupied with the work of figuring out how to make Windows fail to function with all sorts of apps and things like this game. It really doesn't take that much for them to be successful, and they are always three or four steps in front of you. In order to play in the same field as them, we need to design apps and games and stuff that do not function under their old systems, removing the necessity for them to create new failure algorithms.

witpqs -> RE: Today's Wn 10 update is causing... (12/24/2017 1:41:09 PM)
quote: ORIGINAL: geofflambert You know, Microsoft has phalanxes of people occupied with the work of figuring out how to make Windows fail to function with all sorts of apps and things like this game. It really doesn't take that much for them to be successful, and they are always three or four steps in front of you. In order to play in the same field as them, we need to design apps and games and stuff that do not function under their old systems, removing the necessity for them to create new failure algorithms. They don't always use the phalanx. [image]local://upfiles/14248/9971335E5E6B404F953D6F888DD1F80A.jpg[/image]

Bearcat2 -> RE: Today's Wn 10 update is causing... (12/24/2017 2:51:40 PM)
Removing -dd_sw worked for me also, was expecting slow scroll speed with that change; but there has been no effect, scroll is excellent "D:\Focus Pacific\War in the Pacific Admiral Edition.exe" -deepColor -x1920 -y1080

Korvar -> RE: Today's Wn 10 update is causing... (12/25/2017 10:04:32 PM)
It's good to hear that some of you are starting to resolve the issues related to ver 1709 of Windows 10. I tried it myself and had issues before even trying WitPAE, so I've reverted to 1607 and am quite happy. Keep in mind that utilities like Display Fusion (easier to use, but not free) or Cmdow can be used to tweak the position of the WitPAE so the title bar and window frame are hidden offscreen.

m10bob -> RE: Today's Wn 10 update is causing... (12/28/2017 4:38:34 PM)
Kinda cold out today...but I'm parked across the road from the Microsoft building in my '62 Studebaker pick up with a shed set up. Trying to sell these neat woodburned plaques as I can catch 'em coming out. The plaques only have the one message. "If it ain't broke...don't fix it."[8\|]

Korvar -> RE: Today's Wn 10 update is causing... (12/28/2017 6:01:48 PM)
One of the easiest things to do is to turn on deferred updates in "Advanced Options" (Settings -> Update & Security -> Advanced Options). It won't hold off the updates forever, but it allows them to be "in the wild" for some time before they are deployed to your computer. That said, I've turned off all automatic updates on my Win 10 machine and selectively do manual updates. [image]https://i.imgur.com/2buCAev.png[/image]

m10bob -> RE: Today's Wn 10 update is causing... (12/29/2017 3:11:36 PM)
quote: ORIGINAL: Korvar One of the easiest things to do is to turn on deferred updates in "Advanced Options" (Settings -> Update & Security -> Advanced Options). It won't hold off the updates forever, but it allows them to be "in the wild" for some time before they are deployed to your computer. That said, I've turned off all automatic updates on my Win 10 machine and selectively do manual updates. [image]https://i.imgur.com/2buCAev.png[/image] I don't need to outrun the lion...I just need to out run you...for a time, anyway, lol

Macclan5 -> RE: Today's Wn 10 update is causing... (1/8/2018 7:38:49 PM)
I am no rocket scientist in this interweb thingy... But two bits of lore I recall reading from Good Old Games. Something to do with old Baldur's Gate (original) as I recall. quote: I think the most important thing is the size of the window I use is a native size for my display Windows mode always works best when smaller than native size of display ?? quote: Scroll Delay, mouse movement and speed of turn execution all improved when I added -SingleCpuOrders Most these games engines were launch prior to duo-core let alone quad etc... Single CPU often works best for older games because they were designed that way ?? Not sure this is 100% accurate but both solutions work for me.

Page: << < prev 1 [2] 3 next > >>

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

7.140625