problems with windows 10

[ericv]

I see that for example Taxcutter doesn't use -cpu4 and does use -SingleCpuOrders. I would switch that around. I would also always set -w. switching to windowed mode will solve a lot of scroll issues.

I got a not so decent i7 windows 10. with the following switches : -w -px1600 -py900 -deepColor -altFont -dd_sw -cpu4 and it works perfectly, together with that 1 GB map of combat reporter.

[von Beanie]

I've got a new Dell with an i7-6700 CPU with 16 RAM, NVIDIA GeForce GT730 video card and an older Dell 2407 WFP monitor.

For years on my 2012 Dell computer (with Windows 8.0) I've been playing non-Windowed without any scrolling problems; but using the old switches on the new Dell with Windows 10 (and the same monitor), it won't even show the game views (I only hear the sounds of the game running). When I cut out the -dd_sw switch I could finally see a cutoff version of the game screen.

As ericv notes above, his suggested switches allow the game to run on my new system without any problems EXCEPT the window only fills about 60% of my monitor screen and I can't find a way to enlarge the windowed screen. Are there any switches to enlarge the Windows screen to fill my monitor? I tried a variety of -px and -py setting and they don't seem to make a difference.

Interestingly, all of my other Gary Grigsby games seem to work fine in Windows 10. WITP-AE appears to be the only exception.


POSTNOTE: I was able to get it running fine on the Windows 10 machine in a non-windowed mode without scrolling problems. My problem was that in the setup of the new computer I selected to customize my display using the control panel, and because I expanded the screen view (because of my declining eyesight with age), the game would not fill the screen. By removing the display adjustments via the control panel the game works fine again on the Window 10 machine. For what it is worth, these are the switches and command line I'm using: "C:\Matrix Games\War in the Pacific Admiral's Edition\War in the Pacific Admiral Edition.exe" -deepColor -SingleCpuOrders -px1366 -py768 -fixedArt -archive -noFire

[Tony4245]

Awesome advice, guys. Thank you. I was having a HELL of a time with scrolling lag, and then some color palette weirdness when I'd open and close windows (like examining a port for example).

MUCH better now.
[&o]

[Tony4245]

As ericv notes above, his suggested switches allow the game to run on my new system without any problems EXCEPT the window only fills about 60% of my monitor screen and I can't find a way to enlarge the windowed screen. Are there any switches to enlarge the Windows screen to fill my monitor? I tried a variety of -px and -py setting and they don't seem to make a difference.

Did you try setting the compatability mode to, say, XP with Service Pack 3? Might work.

[wdolson]

ORIGINAL: von Beanie

I've got a new Dell with an i7-6700 CPU with 16 RAM, NVIDIA GeForce GT730 video card and an older Dell 2407 WFP monitor.

For years on my 2012 Dell computer (with Windows 8.0) I've been playing non-Windowed without any scrolling problems; but using the old switches on the new Dell with Windows 10 (and the same monitor), it won't even show the game views (I only hear the sounds of the game running). When I cut out the -dd_sw switch I could finally see a cutoff version of the game screen.

As ericv notes above, his suggested switches allow the game to run on my new system without any problems EXCEPT the window only fills about 60% of my monitor screen and I can't find a way to enlarge the windowed screen. Are there any switches to enlarge the Windows screen to fill my monitor? I tried a variety of -px and -py setting and they don't seem to make a difference.

Interestingly, all of my other Gary Grigsby games seem to work fine in Windows 10. WITP-AE appears to be the only exception.

What Grisby games do you have? WitP-AE is built on top of the engine used for WitP which in turn was built on the engine for Uncommon Valor which dates back to the late 1990s. 2X3 has had nothing to do with the WitP engine since 2007 or so when WitP was finished. Their games released since then have a different engine that interacts with Windows in a different way than WitP did.

Bill

[SgGhost]

Hi Guys

I have brand new pc, a I7-8700 with 16GB RAM with a 1T SSD disk with a Nvidia GTX1070 Ti and Win 10 64bit home edition.
The gameplay sucks big time because of the scrolling issues.

I am using these settings: "C:\Spil\War in the Pacific Admiral's Edition\autorun.exe" -w -px1920 -py1080 -dd_sw -deepColor
- and it still sucks when scrolling even if scrolling delay is set to 0 (zero).

The only other setting I have found that makes the game playable is to set the "Task force move radius" to OFF and the biggest reward is to set the "Plane range radius" to OFF.
Now Pearl Harbor can be selected and I can still scroll the map like I could before Win10 [:D][:D][:D]

/SgGhost out.

[MakeeLearn]

ORIGINAL: SgGhost

Hi Guys

I have brand new pc, a I7-8700 with 16GB RAM with a 1T SSD disk with a Nvidia GTX1070 Ti and Win 10 64bit home edition.
The gameplay sucks big time because of the scrolling issues.

I am using these settings: "C:\Spil\War in the Pacific Admiral's Edition\autorun.exe" -w -px1920 -py1080 -dd_sw -deepColor
- and it still sucks when scrolling even if scrolling delay is set to 0 (zero).

The only other setting I have found that makes the game playable is to set the "Task force move radius" to OFF and the biggest reward is to set the "Plane range radius" to OFF.
Now Pearl Harbor can be selected and I can still scroll the map like I could before Win10 [:D][:D][:D]

/SgGhost out.

You have to make a shortcut to the .exe NOT the autorun.
"C:\Spil\War in the Pacific Admiral's Edition.exe" -w -px1920 -py1080 -dd_sw -deepColor


You may want to install and use the Beta .exe

[Tbilisi]

I'm also running a recent build with an I7 8700 and GTX 1070. I had very slow map scrolling until I removed -dd_sw from the command line. Can't explain why, but it helped out on an older FX-8350 box with a R9 380. Not so the case here.