Win 10 Sluggishness -- Observation

[CaptDave]

Not looking for help -- yet -- but reporting on my own Win 10 problems. I had no problems whatsoever until a few days ago; now it takes close to a minute just to see a response to a mouse click or a key press. I know I accidentaly installed some software I didn't want (trackpad on the laptop moves the mouse if you breathe on it but needs a sledgehammer to "click") and removing it doesn't seem to have helped, but I'm still working on it.

If anyone does happen to have seen the same problem, of course, I'm open to suggestions! In the meantime, I'll keep researching and if I come up with anything I'll let you know.

[VPaulus]

Are you playing in windowed mode or full screen?

[Lowpe]

what does your command line look like? Switches?

[BBfanboy]

I have had huge slowdown in click response when my anti-virus starts a scan of my disk.

[inqistor]

I had something like this, using wireless monitor, but I'm guessing you are still connected by cable?

[CaptDave]

Apologies for such a tardy response. Work-related issues have kept me away from the forums for quite some time.

To answer the various questions:

1. I play in full screen mode. I've never noticed much trouble switching between programs, though I know others have.

2. This is on a laptop so yes, the screen is connected by cable.

Turned out to be a switch issue, as could have been predicted. Somehow in my various experiments I ended up deleting the -dd_sw piece. Until I put it back in, along with -cpu2 (did both at the same time so don't know if either one alone was a sufficient solution), it was taking about 1.25 minutes to move to a new map location and even .75 minutes for the Q key to respond. Once in the main menu, of course, responses were instantaneous.

[bspeer]

I am having the same issue with Win10. VERY sluggish, makes the game unplayable. Playing on a PC with a high-end video card, solid state drives, the whole nine yeards.

[Korvar]

ORIGINAL: bspeer

I am having the same issue with Win10. VERY sluggish, makes the game unplayable. Playing on a PC with a high-end video card, solid state drives, the whole nine yeards.

Create a shortcut to the WitPAE executable file (not the autorun file). The file will be called War in the Pacific Admiral Edition.exe and will be in the folder where you installed WitPAE. If you installed the beta update, it will be in the beta2 subdirectory of that folder (as well as the main game folder).

Once you create the shortcut, you can right-click it and click "Properties". Under the "Shortcut" tab there will be a "Target" box. Add -dd_sw to the end of that target path, like this:

Code: Select all

[...] War in the Pacific - Admiral's Edition\Beta2\War in the Pacific Admiral Edition.exe" -wd -pxf1920 -pyf1080 -archive -deepColor -multiaudio -dd_sw -altFont

[bspeer]

Korvar, I tried your suggest, the attached is what I got.

[BillBrown]

Why are you trying to make a shortcut to the icon file?

[Korvar]

From the WitPAE folder:










It looks to me like you:
1) didn't put a space before -dd_sw
2) it looks like you successfully created a shortcut, but somehow targeted an icon file instead of the executable file?

Try following the picture steps above and see if helps. I always enter switches by left-clicking the "Target" box once, then hitting the [End] key to go to the very end of the file path, then hitting the [Space Bar] once, then typing whatever switch(es) are needed. Don't worry about any other switches until you get -dd_sw working.

Also keep in mind that I showed the steps for the 'regular' .exe file; for the unofficial beta (if you're using it), you'll repeat the same process, but from within the 'beta2' subdirectory of the WitPAE folder.

Once you create the shortcut, you can move it to your desktop, pin it to your start menu, or put it wherever else is convenient for you to start WitPAE.

[bspeer]

Why? Because I don't know what the HELL I am doing and should not have to do this to play a GAME!

[bspeer]

That did the trick, thanks!

[Korvar]

Success!

The important thing is that you stuck with it and got it working - now you won't have to bother with the .exe switches unless you want to tweak something. Continuing with the USN SeaBee "Can Do!" attitude will serve you well in the campaigns ahead! [:D]

[Lovejoy]

ORIGINAL: Korvar

From the WitPAE folder:










It looks to me like you:
1) didn't put a space before -dd_sw
2) it looks like you successfully created a shortcut, but somehow targeted an icon file instead of the executable file?

Try following the picture steps above and see if helps. I always enter switches by left-clicking the "Target" box once, then hitting the [End] key to go to the very end of the file path, then hitting the [Space Bar] once, then typing whatever switch(es) are needed. Don't worry about any other switches until you get -dd_sw working.

Also keep in mind that I showed the steps for the 'regular' .exe file; for the unofficial beta (if you're using it), you'll repeat the same process, but from within the 'beta2' subdirectory of the WitPAE folder.

Once you create the shortcut, you can move it to your desktop, pin it to your start menu, or put it wherever else is convenient for you to start WitPAE.

Bless you! I have never been able to get the command switches to work properly, and as a result I've never really been able to get into the game because of the massive lags and delays in responses to clicks. The explanation (with pictures) really helped me, and I was able to get it to work properly. 10,000 thanks to you!

[Korvar]

You're welcome! I'm glad you're able to play finally! Make sure to write your loved ones every once in awhile! [:D]

[pelthunter]

Thank you for this good aid post. I today got my first ever Win 10 and was pretty shocked on the performance with the tweak. Thank you.

[simovitch]

Does anyone know if these switches would work with GG's Eagle Day/Bombing the Reich, and if not, why? Do they have to be programmed into the Code?

Thanks in advance.

[BillBrown]

I doubt very much they would work and yes, they have to be a part of the program.

[simovitch]

Thanks, I figured as much. In EDBTR "-w" works as does "deepcolor". I was hoping for more of an answer to the "why" from a DirectX guru.

Specifically, how was the "-dd_sw" switch coded (C++?) over time to adapt to the evolution of Windows?

The "direct draw software emulation" toggle in EDBTR does nothing in Windows 10, and we are trying to fix this for an official patch.