Windows 8 Problem

[spence]

I recently got a new computer (laptop) with Windows 8 installed. My old computer was a desktop with Windows XP. Everything worked fine on the desktop. Not so with the new laptop. Although the turn resolves just fine with no undue delays or other problems I find that making my move has become quite tedious due to a long (2-3 sec) delay between the time that I click on a unit and the time I can change anything about that unit. The same delay seems to intervene between every mouse-click in fact. Thus, whereas it used to take roughly 1.5 hours to run a turn resolution and make my own move I just spent about 3 and a half hours making my move.

Obviously I'd like to speed things up a bit. I haven't found any programs or applications that seem to be in conflict or running concurrently but I'm certainly no guru in this sphere so I'd appreciate any suggestions on how to correct this problem.

[n01487477]

ORIGINAL: spence

I recently got a new computer (laptop) with Windows 8 installed. My old computer was a desktop with Windows XP. Everything worked fine on the desktop. Not so with the new laptop. Although the turn resolves just fine with no undue delays or other problems I find that making my move has become quite tedious due to a long (2-3 sec) delay between the time that I click on a unit and the time I can change anything about that unit. The same delay seems to intervene between every mouse-click in fact. Thus, whereas it used to take roughly 1.5 hours to run a turn resolution and make my own move I just spent about 3 and a half hours making my move.

Obviously I'd like to speed things up a bit. I haven't found any programs or applications that seem to be in conflict or running concurrently but I'm certainly no guru in this sphere so I'd appreciate any suggestions on how to correct this problem.

What parameters are you using in your shortcut?

How many CPU cores?

Are you using compatibility mode?

What windows8 extras are you using (aero etc)? (I don't have windows8, but I've read enough to know you probably need to configure the machine to make it run leaner)

[wdolson]

Sounds like the problems we were having with multi-core processors and some video chipsets. There were several command line flags added for the first update. The first one to start with would be to add

-cpu1

This forces the multi-core processor to only use one core (the first one). There are problems with some versions of Intel processors and the game. The multi-core switcher hangs with some DirectX calls the game uses. There is also some problems with some video chipset drivers. You are probably having the problem on the laptop either because of the video driver or the processor is different. If the laptop is an AMD processor, then the problem is almost certainly in the video driver.

Bill

[n01487477]

ORIGINAL: wdolson

Sounds like the problems we were having with multi-core processors and some video chipsets. There were several command line flags added for the first update. The first one to start with would be to add

-cpu1

This forces the multi-core processor to only use one core (the first one). There are problems with some versions of Intel processors and the game. The multi-core switcher hangs with some DirectX calls the game uses. There is also some problems with some video chipset drivers. You are probably having the problem on the laptop either because of the video driver or the processor is different. If the laptop is an AMD processor, then the problem is almost certainly in the video driver.

Bill

Good points Bill, but can I take your point to its logical conclusion ... make sure your drivers are up to date. Most machines need an update [;)]

[wdolson]

Sometimes updating drivers will help, other times it won't. The problem with Intel processors is built into the hardware. The video driver problem is a software issue, but from what I know of the problem in the driver, it would be a major change and the video card makers probably don't figure it's worth it to fix.

Bill

[Oberst_Klink]

Vermonter,

check if you got a dual core CPU, run it with the command switches in windowed mode first:

-w -dd_sw -px1440 -py900 -cpu2 -archive

replace 1440 and 900 and substitute it for your resolution settings. In most cases, even with this new Tablet OS *that's what it is!*, it should do the trick.

Klink, Oberst

[spence]

Nothing so far has worked.

I put in the settings from Oberst Klink but that didn't work. Tried using Windows XP compatability Pack 3 and that didn't work. Tried changing screen resolution with no joy.

Various permutations of above also with no joy.

Any more suggestions?

I did notice that the "screen" is not as wide as the laptop screen and the cursor will not move outside the "screen". Maybe no help but different since moving the cursor to the edge of the "screen" does not immediately cause the screen to scroll.

[Kull]

ORIGINAL: spence

Any more suggestions?

It wouldn't hurt for you to post some info on your processor and video card. For the former, go into Windows Explorer, right click on "Computer" and select "Properties". Processor data will be part of what's displayed.

Not sure if there's an easier way to get the Video Card info, but one method is Control Panel, Hardware and Sound, View Devices, Right click the picture of your Computer/Laptop, Properties, Hardware Tab. That will show a long list of devices, one of which is the "Display Adapter". Left click it, click the Properties Button, and you'll get a box telling you the name of your adapter. Select the "Driver" tab and that will tell you who provides it and what the date is. Use that information to hunt for a newer version.

[temagic]

also, isn't it something with command line parameters (.exe -xxxx) not functioning any more with winblows 8? I thought I'd read that somewhere...

Anyway, what computer you've got there spence? Need some info (brand, cpu, gpu, dxdiag) if I'm going to be of assistance...

BTW. WitP: AE works on Ubuntu, without that annying 2-3 sec lag of yours... just in case you're thinking of 'making the switch' ( tm.asp?m=3032823&mpage=1&key=linux&#3032823 )

[Crackaces]

I find that making my move has become quite tedious due to a long (2-3 sec) delay between the time that I click on a unit and the time I can change anything about that unit. The same delay seems to intervene between every mouse-click in fact. Thus, whereas it used to take roughly 1.5 hours to run a turn resolution and make my own move I just spent about 3 and a half hours making my move.

One behavior that I have noticed recently and I have not changed anything on my WIN 7 platform besides upgrading WitP AE to the latest beta and updating the OS as per the automatic upgrades [so it could be an OS update that has changed this behavior] is a 2-3 second delay after activating another window and coming back to AE. Typically this occurs while transfering control from Tracker to AE, but I have noted the behavior happends on reactivating/returning focus to AE from any other application. Something might have changed in the AE code/or the windows lib's interacting with AE for handling the GotFocus() event. [Or whatever that event is called in the code you all all using that eventually is a callback to the GotFocus() event.].

One change between versions of .NET Frameworks is how the CausesValidation() property is handled [yes the property is either true/false but what gets called under the covers when that flag is true I believe has changed ] .. I am wondering if this change is affecting the game ??

Just a thought ...

[fcharton]

having moved from XP to Win7, I also noticed that on map clicks are significantly delayed. Using the menus work better, maybe that's your work around, spence... (being spence's opponent I have an interest in seeing this problem solved)

Michael, does the interface use GDI+ primitives by any chance? (in this case something about the mouseover/mousedown combination on the map graphics, as crackace suggested). If so, you might want to have a look at those, because they are less and less supported since Win7 (basically, handled as code, instead of graphic card primitive calls), and some of them have become very slow on modern machines. I don't know about DirectX, but you might have the same problem with Win8.

Francois (been there, done that)

[Dan Nichols]

When I went to Windows 7 64-bit, I had to include the -dd_sw switch to eliminate the click delay.

[Oberst_Klink]

I also would recommend to try out the switches for multi-core CPUs. I have no lag issues on Win 7 x32 and x64.

Klink, Oberst

[temagic]

I couldn't find anything about command line switches/options being disabled in win8. dunno where I read it. So, i guess that option is still there then. About the lag, the dd_sw switch should take care of it, as stated earlier in this thread by Dan. Alternatively, you can try to update DirectX and videodrivers. Also, try to run the game with Aero/metro whatitscalled disabled. Under shortcut properties, compatibility, 'disable visual theme'. You might want to try that first though, before turning off directdraw accelleration with the dd_sw switch. Anyway, good luck.

[Crackaces]

ORIGINAL: Dan Nichols

When I went to Windows 7 64-bit, I had to include the -dd_sw switch to eliminate the click delay.

I have run multiple experimenents and your findings are confirmed for the behaviors I reported in this thread also. I am not experiencing the delay now switching focus from any other program including graphical/CPU intensive programs and AE., and the combat animation also runs faster.

My OS environment is also Windows 7 64 bit running AE in 32 bit mode. [I also have one other slow down factor ... a Sony VAIO Model F -- the worse southbridge configuation/chipset availible on the laptop market at the time .. [8|] ]

[witpqs]

ORIGINAL: Crackaces

ORIGINAL: Dan Nichols

When I went to Windows 7 64-bit, I had to include the -dd_sw switch to eliminate the click delay.

I have run multiple experimenents and your findings are confirmed for the behaviors I reported in this thread also. I am not experiencing the delay now switching focus from any other program including graphical/CPU intensive programs and AE., and the combat animation also runs faster.

My OS environment is also Windows 7 64 bit running AE in 32 bit mode. [I also have one other slow down factor ... a Sony VAIO Model F -- the worse southbridge configuation/chipset availible on the laptop market at the time .. [8|] ]

I have Windows 7 64-bit and I did not put AE in 32-bit mode. What makes you think you need that??

[jarmovenal]

Hi, I'm new here, and my English is pretty bad. I've had a similar problem in the game. 64bit Windows 7 work properly without any increase in the command line. Win 8 updated the game was slow.
This monitor driver is the latest drivers and I downloaded the latest beta version (beta1119)also.
The operating system language is Finnish, so these terms can go wrong.
I got to work with the following settings:
Compatibility mode for XP (service pack.3). remove the display scaling off (DPI).
In the command line, -deepColor
I hope you understood my intention.

Jamoksi

[colavito1]

Just wanted to thank Jamoksi for his input as his fix cured the slowness I was experiencing with the orders phase in Windows 8.

Compatibility mode for XP (service pack.3). remove the display scaling off (DPI).
In the command line, -deepColor

I have a new Asus Intel Quad core with windows 8 and tried evrything including upgrading direct X, graphics card driver update, and all the switches recommended by Matrix Games. I eventually tried the above with the followingswitch setup in the Qickstart .exe. I copied the quick start from the tile screen and pinned it to the desktop taskbar for ease of switch testing and I start the game using that quick start icon.

-cpu4 -SingleCpuOrders -multiaudio -deepColor -dd_sw -altFont -f -px1600 -py900

I know it may be switch overkill but there is no lag now at all and I have full screen with the map. This made the game playable again.

Dont fault your English Jamoksi, I understood it well and thanks again.

[Hotschi]

Reading the problems listed here, I start to think that a quad-core is a waste of money, if one plays titles like WitP-AE and the like only.

I'm not saying that this is the case for you guys here, but I myself am thinking of getting a new laptop in the near future, and all I play are titles available from matrixgames - and maybe (maybe) Silent Hunter 4, but haven't touched this one since about 2 years. A dual-core should be sufficient - and no Windows 8 [:-]

[ADB123]

ORIGINAL: colavito1

Just wanted to thank Jamoksi for his input as his fix cured the slowness I was experiencing with the orders phase in Windows 8.

Compatibility mode for XP (service pack.3). remove the display scaling off (DPI).
In the command line, -deepColor

I have a new Asus Intel Quad core with windows 8 and tried evrything including upgrading direct X, graphics card driver update, and all the switches recommended by Matrix Games. I eventually tried the above with the followingswitch setup in the Qickstart .exe. I copied the quick start from the tile screen and pinned it to the desktop taskbar for ease of switch testing and I start the game using that quick start icon.

-cpu4 -SingleCpuOrders -multiaudio -deepColor -dd_sw -altFont -f -px1600 -py900

I know it may be switch overkill but there is no lag now at all and I have full screen with the map. This made the game playable again.

Dont fault your English Jamoksi, I understood it well and thanks again.

Hi - I just got a Dell Inspiron 17" laptop (that's if you have a very wide lap [;)] ) with Windows 8 and an Intel Core i7 processor. It ran WitP in "Glacial Mode" until I copied your switch line. Now it looks and runs great. Thanks a huge amount!