SPWAW Artillery Fix Version 2.1 - REMOVED

[Major_Mess]

ORIGINAL: monjoie

Hello,

i am back again to spwaw (thanks to the new enhanced fr),
but it seems the arty download link is not working anymore.

if we can have a fresh one...

You ask ....you receive.
change the extension to .zip, unzip and drop in the root folder.


cheers

mm

[Riitaoja]

ORIGINAL: MTM78

Hi all. Just reporting that the fix also does not work on my machine. CPU is: Intel i7 4700MQ 2.40ghz

Thanks for taking the time for these kinds of projects.

Hello MTM78 I send you a private message with an edited version of the artillery fix that may work better on an Intel i7 processor.

[Riitaoja]

I have been studying more on how the Hyper-Threading is handled on Intel i7 (and maybe Intel i3 too?) processors.

The logic looks like this from what I understand:

#1 = Physical core
#2 = Hyper Threaded core
#3 = Physical core
#4 = Hyper Threaded core
#5 = Physical core
#6 = Hyper Threaded core
#7 = Physical core
#8 = Hyper Threaded core

Now SPWAW needs to run on the last physical core for the artillery screen to work properly. And that core would be core #7 on an i7 processor if my logic here is correct.

So the binary value for core #7 would be 1000000 and that would translate into a AFFINITY value of 40.

The current Artillery Fix version 2 is a bit dumb in that it does not take Hyper Threading into account properly. It would see that Intel i7 processor has four (4) physical cores and that is correct. However it would then proceed to think that the game needs to start on core #4 which is incorrect for Intel i7...

[Alby]

ORIGINAL: Riitaoja

I have been studying more on how the Hyper-Threading is handled on Intel i7 (and maybe Intel i3 too?) processors.

The logic looks like this from what I understand:

#1 = Physical core
#2 = Hyper Threaded core
#3 = Physical core
#4 = Hyper Threaded core
#5 = Physical core
#6 = Hyper Threaded core
#7 = Physical core
#8 = Hyper Threaded core

Now SPWAW needs to run on the last physical core for the artillery screen to work properly. And that core would be core #7 on an i7 processor if my logic here is correct.

So the binary value for core #7 would be 1000000 and that would translate into a AFFINITY value of 40.

The current Artillery Fix version 2 is a bit dumb in that it does not take Hyper Threading into account properly. It would see that Intel i7 processor has four (4) physical cores and that is correct. However it would then proceed to think that the game needs to start on core #4 which is incorrect for Intel i7...

wow ^^^^
waaaaay over my head!
LOL

[Falcon1]

How about for an AMD Phenom II quad core?
I have minimal problems right now but any improvement would be welcome.

[Riitaoja]

ORIGINAL: Falcon1

How about for an AMD Phenom II quad core?
I have minimal problems right now but any improvement would be welcome.

Are you using the Artillery Fix Version 2 and have you made sure mech.exe has no compatibility options set?

If so what sort of problems are you experiencing still on the artillery screen?

[Falcon1]

Here is what is in the CMD file that I use with Windows 7:

taskkill /f /IM explorer.exe
start /B /WAIT /AFFINITY 2 mech.exe
Start explorer.exe

The game runs nearly perfect for me using this, on at least 4 different systems for me over the years, some with Intel and others with AMD.
The only issue is a very minor lag on the artillery screen.
I do not use any compatibility modes.
If there's any way to tweak the CMD file to copmpletely eliminate the artillery lag that would be great.

[Riitaoja]

ORIGINAL: Falcon1

Here is what is in the CMD file that I use with Windows 7:

taskkill /f /IM explorer.exe
start /B /WAIT /AFFINITY 2 mech.exe
Start explorer.exe

The game runs nearly perfect for me using this, on at least 4 different systems for me over the years, some with Intel and others with AMD.
The only issue is a very minor lag on the artillery screen.
I do not use any compatibility modes.
If there's any way to tweak the CMD file to copmpletely eliminate the artillery lag that would be great.

That particular CMD file is configured to work on a dual core processor. So if you have a quad core you will want to change that AFFINITY 2 to read AFFINITY 8.

[Riitaoja]

The point of Artillery fix version 2 was to automaticaly start SPWAW with the correct AFFINITY value depending on what type of cpu the user has.
However if you want to input the correct AFFINITY value for your cpu manualy the list of correct values is here:

CPU type ------> AFFINITY values:
2-core (dual)--> 2
3-core ---------> 4
4-core (quad)-> 8
6-core --------> 20
8-core --------> 80

[Riitaoja]

Made a small update to the fix. New version number is 2.1.

[sami heimola]

Thanks about new art patch Riitaoja[:)]. I installed and made a little test. I chose 105 mm battery (Germany) and went to art menu. I marked 3 targets (ok marking them is still slow IMHO but I noticed that pressing shift at same time it's bit "faster", some 10+ seconds than after installing 1st version). Btw, returning back from art menu last more than about 20-30 seconds (I tried with shift but no effect) at least. I checked that my mech.exe had not any compability thing "on" before test. So, you said that "The fix does not work for computers that have an Intel i7 processor." I have i5 so is it possible that patch will not work with it too?

[Riitaoja]

ORIGINAL: sami heimola

Thanks about new art patch Riitaoja[:)]. I installed and made a little test. I chose 105 mm battery (Germany) and went to art menu. I marked 3 targets (ok marking them is still slow IMHO but I noticed that pressing shift at same time it's bit "faster", some 10+ seconds than after installing 1st version). Btw, returning back from art menu last more than about 20-30 seconds (I tried with shift but no effect) at least. I checked that my mech.exe had not any compability thing "on" before test. So, you said that "The fix does not work for computers that have an Intel i7 processor." I have i5 so is it possible that patch will not work with it too?

I'm really baffled... It should work on an Intel i5.

Just to be perfectly clear you are always staring the game from the file SPWAW_Arty_FIX_v21.cmd right?

[condompete]

Hi I have an i5 and it's not working for me either. Mech.exe is clean, no compatibility or admin on it and I'm starting from your .cmd. I have also tried entering start /B /WAIT /AFFINITY 8 MECH.EXE at command prompt and it loads fine but still no joy with the arty screen. Maybe it's a win 10 thing? It's a real shame, I've just come back to SPWAW after years away but the arty screen kills it.

[sami heimola]

Riitaoja:yes. Hmm could this be Windows 10 thing too[8|]? Not just depending what kind of processor you have?
Anyway, I use artillery seldom so this is not big deal for me[;)]... But if there's some way to "speed up" art function in future, it's not bad thing[:'(].

Thanks about trying to fix this!

[Riitaoja]

I guess it could be a Windows 10 thing. I am still running on Windows 7.

Here is a test you could try out:

1. First start the game directly from mech.exe.
2. Then press Ctrl+Shift+Esc to get to the Windows task manager.
3. select the "details" tab.
4. scroll the list to mech.exe and right click on it.
5. now select "set affinity"
6. from the list make sure only the last CPU has a check mark on it. so for example on quad core i5 you would only check CPU 3 and leave the other boxes empty.
7. after setting the affinity on task manager go back to the game and see if the artillery sreen works.

Here is a tutorial for Windows 8 on how to set the affinity from the Task manager. Unfortunately I did not find instructions for Windows 10 but I'm hoping it is similar.

http://www.eightforums.com/tutorials/24 ... s-8-a.html




P.S. You can try and play around with different CPU's selected and see if it makes any difference.

[sami heimola]

Hmm I didn't found that from Windows 10[&:]... Can anybody confirm same thing?

[Riitaoja]

ORIGINAL: sami heimola

Hmm I didn't found that from Windows 10[&:]... Can anybody confirm same thing?

Maybe this simulated screenshot helps?

[sami heimola]

Ahh finally I got that affinity thing changed[:'(]... It took bit time from me[;)] I made same test and noticed that changing affinity changed nothing (what comes to delay between choosing/setting target:(... It still takes at least 1 minute/target and leaving art menu too.

[pepita17]

what a pity for this venerable game those arty issue ...[:(]

[Riitaoja]

Does the fix work for anyone on Windows 10???

What if you try different checkboxes for the Affinity like selecting CPU 1,2 & 3 and leaving CPU 0 unchecked?