Chain CTDs

[Dragonlord]

I dont care what anyone says anymore, this mod is going downhill.
I was playing today on the RUS #1 server on sandblasted.
After playing for about 30 minutes I got a CTD, and after that it was dead impossible for me to play anymore.
I kept getting getting constant CTDs and every time it was with 5 minutes or less between each of them.
And its not the first time it happens either.
The number of times I have been able to play a full match, usually 60 minutes, without a CTD can be counted on 1 hand.

I'm dead sick of hearing evasive answers about this.
Why do the devs keep adding content instead of fixing this gamebreaking bug?
In all my years of gameplay and gametesting I have not once seen this kind of issue where the devs seem more interested in adding content than fixing gamebreaking bugs.

I have lost count of all the explanations, so called solutions and outright excuses around this issue.
I have tried all these so called solutions to the problem yet the issue remains a constant.
I have run defrags, tried disabling my firewall and AV, I have tried deleting the shacers folder I even installed a new HDD and reinstalled everything, yet the problem just gets worse.

I have heard talk about the port to wars, will probably solve the problem or at least make it better.
To those who says that, how do you know this?
If you can show me hard proof that this will help I can wait, if not, stop saying it.
You just give players a false hope which in the end will only postpone the inevitable, players will leave as it becomes unplayable.

I know its beta and that we are supposed to find bugs to fix, but this problem just gets worse with each new update of the mod.
I have been with this mod since 0.2.0, and from what I hear that is when the problem started and that it was not an issue with 0.1.0.
I'm not the only one that has seen an increase in CTDs since 0.2.0 and its just getting worse.

My suggestion to the devs are that they wait with adding more content until this problem is solved, or it will just get worse and in the end make the mod unplayable for the majority of the players.

I really want to play but the way things are now it can go days between each time I play and then I usually only play a single match as the CTDs are such a nuisance.

Dont come and tell me to try this and try that and tell me it might help, I already have tried that.
I have been through the troubleshooting guide and more multiple times with no change whatsoever.
I had to make me a list in addition to the troubleshooting guide as allot of players have added their own solutions that worked for them which I have tried in the hopes that it might work for me as well, but with no success whatsoever.

NOTE:
The culprits for the CTDs for me seems to be
Cryphysics.dll
Cryanimation.dll
Crysystem.dll

[Aidan]

Take a chill pill dude ... sheesh ! 

[KingLeerUK]

Unfortunately, I don't see any repro steps in your report.
 

Formal description of the BUG. State what you did or what happened during the incident. Be brief and concise, and please make sure that it is readable.

Repro Steps: (If possible write down all steps leading to the BUG itself.) ex.: Flamer Crashes Client
1. Player 2 Purchases a Flamer
2. Player 2 positions himself in front of the Flamer.
3. Player 1 shots Flamer at Player 2.
4. Player 2 CTD.

Repro: 5/5 (How many times were you able to repro the BUG)

Severity: 1-5 (Where 1 is the lowest and 5 the highest)

I am sorry that you are having so many frequent CTD, but without a way to reproduce them reliably in a test environment we have nothing to specifically target for a fix in the code.
 
We do know that there is a regular issue with the current Novacat animations, and it is causing some issues with CryAnimation.dll for some players.  However, as we have stated numerous times in the past, debugging the animation engine with the modSDK is guess and check at best.
 
So, back to bug reporting, can you be more specific about what was happening at the time the crashes occurred?
Where there any assets on screen?
What was the composition of your team?
Of the opposing team?
Do you crash more in the early game or late game?
What map?
What game mode?
How many players?
What was your ping to the server? (Russia is far)
Did you get any logs? Console errors being spammed?
Take a screenshot of the crash dialogue?
What sort of graphics card do you have?
What driver version?
What sort of system resources where in use?
Do you have any resource monitoring?
How much RAM was in use at the time?

[Dragonlord]

Unfortunately, I don't see any repro steps in your report.
 

Formal description of the BUG. State what you did or what happened during the incident. Be brief and concise, and please make sure that it is readable.

Repro Steps: (If possible write down all steps leading to the BUG itself.) ex.: Flamer Crashes Client
1. Player 2 Purchases a Flamer
2. Player 2 positions himself in front of the Flamer.
3. Player 1 shots Flamer at Player 2.
4. Player 2 CTD.

Repro: 5/5 (How many times were you able to repro the BUG)

Severity: 1-5 (Where 1 is the lowest and 5 the highest)

I am sorry that you are having so many frequent CTD, but without a way to reproduce them reliably in a test environment we have nothing to specifically target for a fix in the code.
 
We do know that there is a regular issue with the current Novacat animations, and it is causing some issues with CryAnimation.dll for some players.  However, as we have stated numerous times in the past, debugging the animation engine with the modSDK is guess and check at best.

I am unable to produce any repro steps, the crashes appear totally random to me.
It can be on any map with any asset at any given time anywhere on the map.
The novacat bug which has been posted before is the only thing I can say with absolute certainty is not the sole reason for the CTDs as it can happen  with none of them on the map.

So, back to bug reporting, can you be more specific about what was happening at the time the crashes occurred?
Where there any assets on screen?
What was the composition of your team?
Of the opposing team?
Do you crash more in the early game or late game?
What map?
What game mode?
How many players?
What was your ping to the server? (Russia is far)
Did you get any logs? Console errors being spammed?
Take a screenshot of the crash dialogue?
What sort of graphics card do you have?
What driver version?
What sort of system resources where in use?
Do you have any resource monitoring?
How much RAM was in use at the time?

There was 2 or 3 friendly mechs on my screen, dont know which ones as i rarely pay attention to what type of asset is on the screen unless its essential to my current situation.

I do not know the composition of either mine or the opposing team other than that we were the same number of players on each team, with 12 on each side.

When I crash is totally random, it can be any time between when the match starts and when it ends. I have to way to producing any repro steps and I have no idea what triggers it.

This particular time the map was sandblasted.
The mode was Solaris Arena.
And there was a total of 20-24 players at any given time during the time I played.

Russia may be far to you, but my ping to the Russian server was a steady 50-6ms, as I am in Norway the distance is fairly short.

I use a Geeforce GTS 250 graphics card.
Right now I'm running with the latest drivers, but have had the same issue running with older drivers as well.
As I said in my OP I have been through the troubleshooting guide and then some multiple times with no change.

The system resources I have running are what I usually have running.
I dont have a complete list, but I can mention my web browser Opera, my AV and firewall Norton.
At the time I had this happen today I have WMP running as well, bu before you say that it can the the reason, I can say I have tried without it as well with the same result.

Only system monitoring software I run are EVGA precision, which I use to monitor my GPU temp as it tends to go quite high when running MWLL.
Seen it go as high as 90 C, and thats with the computer case open.
I got me a new MB to get some more space between my GPU and sounds card, but hit a snag when I installed it and have yet to find a solution to it. It may be the MB is defect in which case I have to get it replaced.

I dont know how much RAM was in use when it happened this time, but the times I have monitored it, it has never gone above 3GB usage and I got 4 GB installed running with Win XP pro SP3.

I have lost count of the number of threads on this issue and so far from both my own experience and what I have heard from others the problem just keeps getting worse with each update of the mod.

[Dragonlord]

Take a chill pill dude ... sheesh ! 

No, not this time.
I would like to see you in my position having to endure multiple CTDs every time you wanna play, making in dead impossible to play.
There comes a point for everyone when enough is enough, and I for one have had it with these CTDs and all the failed attempts at getting around the problem from my end and what looks from my point of view to be someones seemingly disinterest in fixing a gamebreaking problem.

[Aidan]

Take a chill pill dude ... sheesh ! 

No, not this time.
I would like to see you in my position having to endure multiple CTDs every time you wanna play, making in dead impossible to play.
There comes a point for everyone when enough is enough, and I for one have had it with these CTDs and all the failed attempts at getting around the problem from my end and what looks from my point of view to be someones seemingly disinterest in fixing a gamebreaking problem.

Dude ... if your GPU is getting to 90 degrees C ... you have cooling problems! My GPU, ATI 5970, never gets above 38 degrees C.

Fix it !

[Dragonlord]

I find that hard to believe as its only when I play MWLL it gets that high, any other game I played regardless of resource demands I have never seen it go above 65.

And you say fix it, as if I had not tried.

Regardless of that I simply do not have any way to do anything about it, and I have done what I can with what I have.
Not because I dont want to but simply for the lack of resources to do anything about it.
Put into laymans terms, my economy these days are so tight I can barely make ends meet, and as such cant afford to do anything about my computer.

[Aidan]

I find that hard to believe as its only when I play MWLL it gets that high, any other game I played regardless of resource demands I have never seen it go above 65.

And you say fix it, as if I had not tried.

Regardless of that I simply do not have any way to do anything about it, and I have done what I can with what I have.
Not because I dont want to but simply for the lack of resources to do anything about it.
Put into laymans terms, my economy these days are so tight I can barely make ends meet, and as such cant afford to do anything about my computer.

Sounds to me like your rig is not up to snuff. So play another game and quit bitching at the devs because your computer won't do it.

[Dragonlord]

I find that hard to believe as its only when I play MWLL it gets that high, any other game I played regardless of resource demands I have never seen it go above 65.

And you say fix it, as if I had not tried.

Regardless of that I simply do not have any way to do anything about it, and I have done what I can with what I have.
Not because I dont want to but simply for the lack of resources to do anything about it.
Put into laymans terms, my economy these days are so tight I can barely make ends meet, and as such cant afford to do anything about my computer.

Sounds to me like your rig is not up to snuff. So play another game and quit bitching at the devs because your computer won't do it.

Since you seem to know everything about my computer why dont you come here and fix it, then I dont have to make posts like this.
As I said in my previous post, I have run games in this computer which has been more demanding on the system than MWLL and never seen anything even close to this level of issues.

My system specs:

Windows Version: Microsoft Windows XP Professional
Video card Name: NVIDIA GeForce GTS 250 1 GB RAM
Installed Memory: 4,00 GB
Hard Drive: 500GB HDD
Sound card: Sounds Blaster X-Fi Fatality

[KingLeerUK]

Three things stand out to me from your detailed post:
 
1. anti-virus software and CTD seem to hand-in-hand, I'm wondering if you would be willing to risk playing with your AV disabled and see if performance is different.
 
2. 90'C for a graphics card is WAY too hot, likely leading to some system instabilities.  If MWLL is the only game that is causing that then we probably need to do some profile[] testing to see what is pushing your GPU sub-system so hard.  I'm assuming you are playing with everything cranked to max.  I have a GTX285 and I usually lower my shadow detail to MEDIUM or LOW and see little in-game difference but give my GPU a bit of breathing room.
 
3. Running a PC with the case open is defeating natural airflow design, assuming you have proper chassis fans installed.
 
Also, Win XP 32-bit with PAE can "see" 4gb of system RAM, but will only ever allocate a maximum of 2gb of it to any single process.

[=KoS=toasterpastries]

Dragonlord, I have a very similar setup to yours, and my CTD situation is very similar also.
When it decides to CTD, it will keep doing so more frequently until I give up for a while.
I had an X-Fi card, and sound stuttering went away after I pulled that out, but no change to CTDs.

Mine is:
XP Pro SP3 v.3300
Core 2 Quad 2.6 @ 3.3
EVGA 680i mobo
2x GTS250's in SLI
4G 800mhz RAM @ 825mhz (2.5 visible by XP)
3x WD 1TB drives

No active antivir, no software firewall. I use MWB and manually scan everything I dl.
XP is gutted to 16 processes on startup. Unnecessary services are disabled as well.
I have run memtest86+, un/reinstalled Crysis and MWLL, turned my OC off, turned it back up, checked for any possible conflicts on my PC.
I also use the most current drivers, and EVGA Precision. My card temps top out at ~72.

Where there any assets on screen? Doesn't matter
What was the composition of your team? Doesn't matter. I've CTD'd alone in LAN games too.
Of the opposing team? Doesn't matter
Do you crash more in the early game or late game? Doesn't matter
What map? Mostly Thunder Rift, Clearcut, Extremity, and Inferno. Others have very few CTD's for me, as do custom maps.
What game mode? Doesn't matter
How many players? Generally more CTD's when 12+ players are connected.
What was your ping to the server? Usually between 70 and 120, I don't play anywhere where it's higher.
Did you get any logs? Console errors being spammed? Nothing console-wise, generally the CTD's do not generate a new game.log file.
Take a screenshot of the crash dialogue? Not yet, but here's some fun stuff from Event Viewer...
Faulting application crysis.exe, version 1.1.1.6156, faulting module cryphysics.dll, version 1.1.1.6156, fault address 0x000ddad8.
Faulting application crysis.exe, version 1.1.1.6156, faulting module cryanimation.dll, version 1.1.1.6156, fault address 0x0004db72.
Faulting application crysis.exe, version 1.1.1.6156, faulting module d3d9.dll, version 5.3.2600.3300, fault address 0x000a59c2.
Faulting application crysis.exe, version 1.1.1.6156, faulting module msvcr80.dll, version 8.0.50727.4053, fault address 0x0001500a.

What sort of graphics card do you have? 2xGTS250
What driver version? 258.96
What sort of system resources where in use? Nothing except for MWLL. I have tested running with and without TS3 on, no difference.
Do you have any resource monitoring? Yeah, checking task manager every couple minutes like an obsession.
How much RAM was in use at the time? Generally tough to say, as it happens when I'm playing, and I don't run around with r_displayinfo 1 on while I'm trying to play. Generally I see MWLL use from 900MB to 1.2G, depending on the map and # of players.

I do hands-on gaming PC building and maintenance for a living, and have applied everything I know into troubleshooting this issue, with no change. So please don't throw me noob solutions.

I run CCC pack at lvl 3, I've tested with every level of CCC, and the stock game settings with no change.

When the game works, it runs beautifully, so don't tell me my rig isn't up to snuff. A friend runs this mod on an 2006 iMac with a tenth of the CTD's I have.

I stick to Sandblasted, Mirage, and Marshes, they generally crash much less than the others. This may be coincidence but that is my observation.

I have also tested on Win7 x64, in 32-bit and 64-bit, DX10 and DX9, all of them were much worse, CTD's 2 minutes in.

It's hard to swallow this being an individual PC issue, as it's the only program on my PC that's ever crashed.
However, I would really love if this helps in any sort of way toward fixing it.

It's difficult to want to participate in a league where CTD=loss when this still an issue.

[Thani]

I also use a NVIDIA GeForce GTS 250 1 GB RAM and my temperature also tends to go around 90 degrees Celsius, and I have yet to have a single CTD.  I also have both Panda and Avast! running together.  Strange, I wonder how all these people seem to be having so many crashing issues, when I haven't encountered a single problem that wasn't the result of something silly I did.

[Aidan]

Three things stand out to me from your detailed post:
 
1. anti-virus software and CTD seem to hand-in-hand, I'm wondering if you would be willing to risk playing with your AV disabled and see if performance is different.
 
2. 90'C for a graphics card is WAY too hot, likely leading to some system instabilities.  If MWLL is the only game that is causing that then we probably need to do some profile[] testing to see what is pushing your GPU sub-system so hard.  I'm assuming you are playing with everything cranked to max.  I have a GTX285 and I usually lower my shadow detail to MEDIUM or LOW and see little in-game difference but give my GPU a bit of breathing room.
 
3. Running a PC with the case open is defeating natural airflow design, assuming you have proper chassis fans installed.
 
Also, Win XP 32-bit with PAE can "see" 4gb of system RAM, but will only ever allocate a maximum of 2gb of it to any single process.

Yea ... what he said ... this

Gear up or gear out. This game takes power!

[Dragonlord]

Take a screenshot of the crash dialogue? Not yet, but here's some fun stuff from Event Viewer...
Faulting application crysis.exe, version 1.1.1.6156, faulting module cryphysics.dll, version 1.1.1.6156, fault address 0x000ddad8.
Faulting application crysis.exe, version 1.1.1.6156, faulting module cryanimation.dll, version 1.1.1.6156, fault address 0x0004db72.
Faulting application crysis.exe, version 1.1.1.6156, faulting module d3d9.dll, version 5.3.2600.3300, fault address 0x000a59c2.
Faulting application crysis.exe, version 1.1.1.6156, faulting module msvcr80.dll, version 8.0.50727.4053, fault address 0x0001500a.

From what I can see those are the exact same files I have problems with.

It's hard to swallow this being an individual PC issue

I have lost count of the number of players who has come here on the forums complaining about this issue and the number of times the y have done so, and what is the response we get?
We are told to check out computers and that the issue is on our end, despite having produced error reports and other information supporting our claims that the problem is indeed the mod and not the computer its running on.

Stop blaming the problem on MY computer and fix the bug then we can talk.

[Aidan]

Take a screenshot of the crash dialogue? Not yet, but here's some fun stuff from Event Viewer...
Faulting application crysis.exe, version 1.1.1.6156, faulting module cryphysics.dll, version 1.1.1.6156, fault address 0x000ddad8.
Faulting application crysis.exe, version 1.1.1.6156, faulting module cryanimation.dll, version 1.1.1.6156, fault address 0x0004db72.
Faulting application crysis.exe, version 1.1.1.6156, faulting module d3d9.dll, version 5.3.2600.3300, fault address 0x000a59c2.
Faulting application crysis.exe, version 1.1.1.6156, faulting module msvcr80.dll, version 8.0.50727.4053, fault address 0x0001500a.

From what I can see those are the exact same files I have problems with.

It's hard to swallow this being an individual PC issue

I have lost count of the number of players who has come here on the forums complaining about this issue and the number of times the y have done so, and what is the response we get?
We are told to check out computers and that the issue is on our end, despite having produced error reports and other information supporting our claims that the problem is indeed the mod and not the computer its running on.

Stop blaming the problem on MY computer and fix the bug then we can talk.

Bullshit! Quite trying to play this game on a fookin' abacus !!!