So what is the culprit for all these CTDs?

[Dragonlord]

I just wonder, could the reason for these CTDs be memory or FPS related?
I have noticed that on clearcut and frostbite I tend to get a string of CTDs whenever I try to rejoin the server after a CTD.
I get on to the server, but before I can select a team I get another CTS, and my FPS must be below 1 as it can take several seconds for the camerea to react to my mouse movements.

Whenever I get a CTD, I never have any problems with sound, graphics or anything else that might indicate that a CTD is imminent.
Only thing that indicates a CTD is that my computer sometimes starts reading off my crysis disc.
From what I undertstand I should not even need the disc, but I cannot launch MWLL unless I have the disc in my drive. If I dont have it in it will ask me to put it in.

[Dragonlord]

Now I'm pissed off.
I ave found out why I sometimes get a loss in rank after a CTD.
Playing on Inferno today I had 3 CTDs, the 3rd not 10 minutes after the 2nd.

But whats worse, I noticed that for each CTD I lost a kill.
Thats right, After the 1st CTD, I had 1 kill after clearly remembering having 2 before.
I then go no to kill a BA, and then fight a mech.
During the fight with the mech I get my 3rd CTD, when I come back in I noticed I have been reduced in rank from Point Commander to Warrior.
Looking at the scoreboard I see I only have 1 kill again, where as I had 2 before the CTD.

I can live with the CTDs, but the loss in score and rank is not fun.
I have a hard enough time getting kills and points as it is without me losing it becuase of CTDs.
Punishing players with suicide counts for a CTD?

[zephoid]

what are your computer stats. i get a CTD about every 5th or 6th full game. and i run my computer overclocked in just about any way possible. This is probably due it a graphics driver problem if it is related to fps

[Dragonlord]

Not sure what you mean by computer stats.
My system specs are:

Intel core 2 duo E7500 @ 2.93 GHZ
4 GB RAm
250GB HDD
Geeforce GTS 250 1 GB RAM
Sound blaster X-Fi Fatality sound card
Win XP Pro SP3

I run the whole system on default values, no overclocking.
Dunno much about drivers.

But as I said, I can handle the CTD if it was not for the fact that I seem to loose kills, points and ranks each time I CTD just as when you suicide or kill a teammate.
I get the feeling I'm being punished for issues that are out of my control.

[zephoid]

I honestly have my doubts about the efectiveness of it, but I can give it a try.
Done it before and the effect of it has been minimal at best.

I actually had a similar problem to this in another game. When i was playing bf2 a lot this drove me insane. For me, it was the graphics driver. even though i had the newest driver, my card HATED it. anything besides the old 160.02 drivers or older and it would spaz ane CTD. i have a nice picture of a blackhawk where every pixel is a different color that i particularly like. anyways, try and find an older driver and try it.

I can also recommend removing the sound card entirely and trying. sound cards can really screw your system.  It doesnt have to have an error before the CTD, the CTD may be the error and it just crashes right away.

[Dragonlord]

I have no idea what Video driver I have.
The info I can find about it says 6.14.11.9562

As for my sound card, I havent tried removing that yet.
I havent got the drivers for my onboard sound card installed, and have to find out what the sound card are to find the right drivers for it.

But my personal opinion is that if the game crashes because of what hardware I have installed in my computer, then the game is flawed.
I have never in all my years fo gaming seen any game/mod whatsoever have this serious an issue with crashes, beta or not.
And its getting worse for every new release, not better which says alot about the development.

This is beta, we are supposed to test the mod tofind problems, when problems are found they shoud be fixed, instead there is added more and more content with more bugs and issues which I belive is the main reason for all these crashes.
I would not be surprised if the reason for the crashes was some coflicts in the code or something, but I'm no expert at this and this is pure speculation on my part.

And Frankly, I'm tired of constantly hearing that its my hardware thats something wrong with.
If it was my hadware then the problem would not be so widespread.
Every single match I play I hear at least 4-5 ppl complainng about CTDs and whats worse, its not the same ppl each time either.

When I get a CTD, I have to wait 5-10 minutes to enter the match again on some maps, or I just keep getting CTDs.
Its as if one CTD is causing more, like a domino effect.
And any money I may have had saved up are lost, and I start with the current rank minimum money even if I had more when I crashed.

[zephoid]

some people get a lot of CTDs, others none. therefore it is not the mod itself causing the problems. its the hardware and driver interaction with crysis that are causing the CTD. stop blaming the mod.

Personally i have had 2 CTD in about 200+ games of MWLL, both were due to server crashes and thats probably a problem with crysis net code.

It is either a bad install of Crysis, the mod, or your hardware thats the problem. you may not want to hear it, but thats the truth.

[NSallaNuto]

some people get a lot of CTDs, others none. therefore it is not the mod itself causing the problems

Simply not true, problems started with version 0.2.0 while 0.1.1 WAS FINE and never crashed, so the problem is not just the Crysis engine. Something happened in 0.2.0 and has not been addressed yet in 0.3.2.

[zephoid]

as i have stated, i do not have CTDs on a regular basis at all. i run this mod on 2 computers (both nvidia) and neither have any problems. therefore it has to be hardware related. as i said it is probably hardware and driver interaction with the game engine causing the problems rather than the mod. the mod may be using a custom resource that doesnt interact well with a certain part of the engine and that is possibly causing problems with the driver in turn (seems possible, but unlikely), but if your getting CTDs every 15mins it has to be hardware related. Either that or a bad download/mod install. or even a bad crysis install.

[NSallaNuto]

So, how do you explain that version 0.1.1 does not crash? same hardware, same drivers, same Crysis engine.

The only changed item is the mod version, plain Crysis does not crash nor other games do.

And note that those are "clean" CTDs, driver problems usually result in blue screens or system instability and this is not the case, after a CTD I can relaunch the game immediately.

Another element is that the same problem happens to a lot of people with very different setups.

[Dragonlord]

I was never around for 0.1.x so cant speak for that, but I have noticed a significant increase in the number of CTDs since 0.2.0

During 0.2.0 I usually got a CTD once maybe every 3 matches or so, and never had problems getting back in.
Since the release of 0.3.0 and subsequently 0.3.1 and 0.3.2 the CTD have become so frequent I get 2-3 of them each match, little depending on the length of the matches, and on some maps I get CTDs again when I try to rejoin like a domino effect.

I have done no changes whatsoever to my hardware or drivers since 0.2.0, so how do you explain that the CTDs are related to my hardware and drivers and they just become more frequent with each subsequent release/hotfix of the mod.
That to me suggests that there are something with the mod that causes a conflict with my computer and thus the CTD, and as I said above, its like a domino effect that just keeps growing..

Now my HDD has been starting to act up in the last week or two, and as such I have ordered a new one as I think it something happend to it or it could just have gotten old, I had it for over 2 years.
That HDD will arrive in a couple days, I'll then do a clean install and see what happens.

NOTE:
Just so you dont come here and tell me that its my HDD thats the reason for my CTDs
I have had that HDD installed in my computer for 2 years and never had problems with it before now, and my computer is turned on 24/7.

Also I have never had anywhere near this kind of problem with any game before whatsoever be it beta or not, and I have been playing games and using computers since before the days before the x86 computers.
Hell I even remember the days when DOS was the OS for computers and windows didnt even exist.
Sure I do have the occasional game that tend to crash for some reason, but I'm talking 1 or 2 games a year which each has maybe 5 crashes each in the same timespan.

I'm tried of being told all the time that its my hardware or drivers there is a problem with.
Your reasoning are flawed, since all computers are different.
Everyone uses different hardware and not everyone uses the newest drivers.
Some say the newest drivers solve the problem, others again say they have to use older drivers
If it was driver/hardware related, how come its caused by different combinations of drivers/hardware?
And again as some say, if 0.1.x was fine and the problem started with 0.2.0 how can the problem be on my end?

If you ask me the problem is not so specific as being only related to the players hardware/drivers, instead the problem is caused by a combination of factors in which these are a part of it, but not the sole reason as everyone seems to be so eager to claim.
I'm no expert, and dont know anything about code or programming, heck I couldnt even figure out the editing of the code in the actionmapper.xml file back when we did that, so I have no idea what other factors might be related to this problem.

[SquareSphere }12thVR{]

So did you try to reformat yet?  The only time i crashed was back during 0.1.x when i tried running 32bits.  Since then I've been running 64bit and have had zero problems

Also, having your computer on 24/7 is not a good indicator of computer health.  Even massive web servers for popular sites have to be rebooted every now and again for maintenance.

[CannedMeat]

There's a known issue to do with the Novacat that seems to cause a lot of crashes. Often just coming into view of one will cause you to crash. At times where people don't buy it for whatever reason, I only crash once every two or three maps, which is still quite a lot though compared with other games. I used to get frustrated because the game always crashed just as I finally could afford a good mech 

Everyone I've talked to in game crashes from time to time. I don't really believe these people who say they never have crashed. I wouldn't put too much effort in to trying to fix it on your end, save for making sure your drivers and directx are all up to date.

Once they fix the Novacat bug, it should be pretty bearable assuming your rank is properly saved when you rejoin.

[Dragonlord]

Square, no I have not reformatted yet and I do no intend to.
There is no reason for me doing it anymore.
As I said in my previous reply, I'm getting a hew HDD in a couple days which will replace my current one.
Doing all that now and then again in a couple days is just a waste of my time.

[cocoajin]

It'll likly take a couple of days to defrag it anyway.  These HDs are so big now a days, but the defrag programs have never adapted to do the job faster.