Glorian wrote: ↑Thu Aug 26, 2021 5:44 pm
Tesq did some research on Logonproblems and strange CPU behaviour:
1-FIX for: Stutter, freeze, crash while loading, crash while loading and click on loading screen
2-FIX for: lag while enemy blob fight you / use channeling
3-FIX for cpu multicore bug on old games:
4-FIX for fullscreen erros/ app crash:
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
fix 1) it is similar to "4gbpatch" i wrote on forum some years prior since it's about problems regarding xp era games problems. It's not a client bug in strict sense
basically from some week i had an increase chance to get crash when log in or out, /rel and closing the game:
i gave a look at my windows event register and i found error 0x00000005.
Digged a bit regarding old games/xp era and before i found multiple site which point into a nasty memory access error which is what i tried to track from a lot cuz for what i saw on warhamemr dawn of war 1 it had a similar problem but different fix.
It seems windows require most of the program to be write using some windows software criteria and when a program does not behave like windows want, a "background process nuke the application", that process is to make windows protect from harmfull programs such virus etc to what i understand
the name of the background process is called " Data Execution Prevention (DEP)" - under win7(till win 10)
it is possible to selective disable it for 32 bit program such as warhammer (so both war.exe and war64.exe can be added to exeptions) while for 64 bit application you need to use prompt and total disable it on the computer; since i also had show a problem with my amd gpu i currently testing it completly disable on the computer but i had tried and also the simple war.exe exeption and it does work
I can say for sure that the random crash when i was log in-out , do /rel, or closing client are gone for good, so while i reserve for future comment on client performance under zergy fight i can say 100% client is stable now (using the script for no combat log and using the borderless window, i gona try fullscreen from now on) No crash whatsoever ( it even apply the t1 de bolster faster when login into zone as side info..)
windows event handler/register dont give any more application errors now
to reach "DEP" user interface on win 7 pro : controll pannel-> system -> advanced option > "under performance" click on "option" (in win 10 is in a similar spot but im with 7 )
fix 2) it is what you may had experienced in city when is just 24 vs 24 and it is gpu related; to check if you gpu is wrong set up (especially in OC) restart client; when you loging on server martyr square and after conenct you need to observe when the voice " handshaking"happen if it take 2 second or more from handshaking to next voice then your gpu is not workign right with warhammer.
This is also the reason why after previously fix the borderless windowed is stable vs crash meanwhile full screen isn’t. Fullscreen is more all in all more subject to crash if your gpu is not optimized for warhammer.
The first pass is set your gpu to default from the overclock or any modification, then re try log in out if the handshaking take 1 sec or less or you dont see the animation fo the flames not freeze (the more fluid it go the better ) then the gpu is not well sycnro with the client behaviours
after that you need check what is the default/base clock speed and memory clock of the gpu; when that is done you need to progressivly increase em both in % and not see how much you can pump, if the syncro the base value the gpu will lag on warhammer.
NOTE: not all values work, my amd rx 550 bost till 15% work well but after with warhammer it became unstable, it also became unstable on other xp /7 era games such tw attila and DoW 1. (atm is set on 10% cuz seems heat and prolonged session had an impact aswell)
NOTE 2: if default values dont work try to toy with both clock and memory for about 10% of the values (exemple 1500 mhz →1650 mhz) and so on first on clock speed only and test then with memory only and test, when you find the value that dont make the handshaking voice lag you can start boost in %.
NOTE 3: full overclock but freeze on handshaking will work badder then default but with no freeze on handshaking
NOTE 4: auto overclock wont work since it gona push both clock speed and memory speed to the limit and it gona make gpu unstable for warhammer.
NOTE 5: check handshaking short after set manually the gpu values because test after a while will give a false freeze due the gpu being in idle clock so just test every time immediately (no need to freak eh), you can ignore any later freeze while handshaking when log in/out or after a client restart.
fix 3) write in search msconfig and press enter; inside the new tab on startup options click on advanced,
Now manually set the number of core that windows will use to the max value.
Now warhamemr will be assigned to whatever core is free instead being always link to the first one
fix 4)dont use borderless and use screen calibration for set gamma profile, full screen have a lot of problems and with the other fix windowed will perform better than full screen under any measurable values.
///////////////////////////////////////////////////////////////////////////////////////////////////
NOTE: all these changes are being tested by me personally over 1 week in which my cpu has been replaced aswell, from an a 6300 to a a4-760k on which i had passed from a 4.ghz with frequency increased frequency (from 100 to 103) into a 4.5 ghz with only increased multipler on cpu with base 100 cpu frequency.
I wrote this additional lines because stability for warhammer is better than raw power and also your gpus need NOT to be too fast than your cpu or it will bottleneck itself and lose some cycle for some ankward reasons.
(what is happening is that cpu will outrun the gpu and make photogram it cant use and freeze/ stutter.