Dual Core Bug is back (Negative Delta TIMER) & FIX

[Judas]

The dual core bugs are back, and wow, is more annoying then ever before, crashing and giving mostly negative delta timers but also general protection faults like mad.... at times it won't even let you fire up the game and log in..

Anyways. However, a temp fix ~>

run the lineage2, when the update window appears... hit CTRL+ALT+DELETE and bring up the task manager.

Go to processes and click on the LINEAGE2.exe, right click it and select AFFINITY. Within the choices to check, UNCHECK ONE of the cores, preferably the cpu 1 (leaving CPU 0 checked)... hit ok, exit the task manager, and hit START on the lineage2 window.

Symptoms:

Lineage2 crashing randomly and or instantly with general Protection fault or Negative Delta timer errors. First crash is usually random and if the computer is NOT restarted, the game has a high chance of crashing instantly while trying to log into the specific server.

Symptoms after fix is in place:

Game preformance improves significantly, roughly a 25%-50% boost in overall preformance and stability has been seen on 3 dual core system currently running the game. Instant Crashing doesn't happen and i've only had the game crash once on one of the machines within a 4 hour timespan.

This fix also seems to be helpful for the current Official Lineage2, clearing up nearly all crashes being seen. However full server error messages and disconnections and overall major lag is still seen.

<~ Still only able to play PTS

[Oranj2]

sorry but its you. no problems whatsoever here with c4.

[Judas]

no it's not me..... :p

i've proven it as i'm getting a few reports from various people

[Box_of_Fox]

You misunderstand, PvrJudas-- what he means is "Oh its not happening to me so therefore it can't be happening to anyone else but PvrJudas" :D ;)

[Judas]

[ QUOTE ]
You misunderstand, PvrJudas-- what he means is "Oh its not happening to me so therefore it can't be happening to anyone else but PvrJudas" :D ;)

[/ QUOTE ]

yeah..... i see that quite often from him....

[Oranj2]

well it isnt. dual core runs fine. try the ms patch with the /usepmtimer switch in startup. i run 2 clients, each client uses a cpu.

[SethofAlmarak]

Seriously, I haven't experienced the horror stories some users describe, never had an issue with the game except accepted, "normal" bugs related to game code, never to hardware. I've nevere had any trouble with GG, never had crashes outside of the ocassional disconnection, and most video crashes are to blame on a less than stellar radeon 9600 128 MB when attempting to run the gam eon max graphics with 4x AA. Not saying they can't happen since every PC is a world in itself; every user has a different configuration, installed application etc.

but I'm afraid to upgrade if this is what's awaiting me :3

[Judas]

[ QUOTE ]
well it isnt. dual core runs fine. try the ms patch with the /usepmtimer switch in startup. i run 2 clients, each client uses a cpu.

[/ QUOTE ]

Congrats, i know how to do that to... but i'm refering to a bug that generally 95% of other users out there trying to play but crashing constantly don't know how to fix or do....

Your arrogants is quite astounding though.

[ElfD3vil]

I don't know what it is but I always have a problem with this. I try to run 2 Clients or even 1 Client and I Crit Error everytime I try to do some of the following what would seem simple tasks.

Alt-Tab
Alt-Enter (Window Mode for 2 Clients)
Resizing Window Mode
Changing Resolution Going from Window Mode to Full Screen.

It never ever fails to Crit Error when I do those Functions.. As for the set affinity that someone Suggested I can't.. I wasn't able to on Window Xp Pro and Windows Xp Pro x64bit. I get a Error Can't Set Affinity but every other Game will let me or Program. So why does this problem happen only in Lineage 2? Unreal Tournament doesn't do this and its the same game Engine.

ElfD3vil

[Judas]

[ QUOTE ]
I don't know what it is but I always have a problem with this. I try to run 2 Clients or even 1 Client and I Crit Error everytime I try to do some of the following what would seem simple tasks.

Alt-Tab
Alt-Enter (Window Mode for 2 Clients)
Resizing Window Mode
Changing Resolution Going from Window Mode to Full Screen.

It never ever fails to Crit Error when I do those Functions.. As for the set affinity that someone Suggested I can't.. I wasn't able to on Window Xp Pro and Windows Xp Pro x64bit. I get a Error Can't Set Affinity but every other Game will let me or Program. So why does this problem happen only in Lineage 2? Unreal Tournament doesn't do this and its the same game Engine.

ElfD3vil

[/ QUOTE ]

You must set affinity before fully loading the game

what you do is bring up the linage2 update window.. then sett the affinity for it.. it's a parent program so it'll transfer the affinity setting to the daught program which is the game fully loaded..

[Baladre]

AMD Athlon x2 4400+/Asus A8N-E Rev2/OCZ 2gb @ 2-3-2-5/ATI x1900XTX PCI-Ex/OCZ PowerStream 600/Windows XP x64 Pro SP1

Omg, what a computer!

[Judas]

[ QUOTE ]
AMD Athlon x2 4400+/Asus A8N-E Rev2/OCZ 2gb @ 2-3-2-5/ATI x1900XTX PCI-Ex/OCZ PowerStream 600/Windows XP x64 Pro SP1

Omg, what a computer!

[/ QUOTE ]

if my signature would be aloud to be longer... i'd show more off.... but that isn't possible..

i'm load balancing 2 of the faster connections i can get.... :)

like i've said before, it's my business to have various machines...... this is but one.... my main....

[Oranj2]

Its probably xp x64. Try L2 in 32bit XP.

[Oranj2]

btw setting affinity of lineageii.exe wont affect l2.exe.
and you cant change l2.exe cos of gameguard.

[DeathBecomesYou]

I run a P4 Dual core and havent experienced these issues yet /gulp ....I am however running 32bit XP.

[Judas]

[ QUOTE ]
btw setting affinity of lineageii.exe wont affect l2.exe.
and you cant change l2.exe cos of gameguard.

[/ QUOTE ]

WRONG....

Lineage2.exe is a parent program, when it is started, the affinity is auto. Both cpu's are loaded (saposedly)...

L2.exe is a daughter program, meaning the lineage2.exe executes l2.exe, all previous commands and settings are then transferred.

You wouldn't be able to add commands to the lineage2.exe shortcut and have them still work when you fully load l2.exe if your "theory" was correct...

My one intel dual core rig is experiencing issues....