Conquest Mode on server

Nice one Wipers, I will try and keep everyone updated with any updates and workarounds for the patch.

For what I have been able to determine although I have had no official work yet is this

The CTD is caused by Nvidia and ATI latest drivers.

Please delete your cache in the My DocumentsBattlefield 2142mods folder and the file icontent.cache. This may help some and NVIDIA driver version 91.31 is confirmed to run with out crashing after clearing your cache. Please roll back to version 92.91

However I will try to get an official workaround today

@Wipers wrote:

I’m using Nvidia 84.xx drivers and I got CTD’d after a Titan map last night (the only one I played). I flushed the cache before putting on the patch too. Also had a CTD in the middle of a normal conquest map.

Can’t help thinking that DICE/EA are barking up the wrong tree thinking this is a drivers issue….

Yeah me too, but I am willing to go along with it at the moment until it is proved otherwise. Suffice to say I am a little miffed with this is putting it extremely mildly 👿

@=XDC=sPUNKer wrote:

By the way Lammie. When the frell is EA going to take a small moment of their time to go over the leader board and take note of the over exagerated teamwork scores, at least the the top 100 whose favorite vehicle seems to be the transport helis and if its not that then it looks like they are the Jesus of ressuplies. So many blatant stat padders in the top 100 it makes EA look bad. (even if they already do! 😛 )
how about they also make some tickertape news to warn those people that their stats will beb wiped to prevent future tards.
Sorry for rantig but when I look at these leader boards and I see a teamwork score of almost 50000 and that transport heli as their fave vehicle its just so blatantly obvious and these guys are getting away with it
http://battlefield.ea.com/battlefield/bf2142/Leaderboards.aspx?Lang=us&PID=&SrchName=&Profiles=
choose one with stats intact and check details. then look at ressuplies or heals or repair or other teamwork scores and they dont tally. Or if it aint that then theres something else fishy like the amount of times on only one particular map

Yeah the wheels at EA Customer Services turn slowly though although they have already reset over 100 accounts. The problem is that this issue is so widespread now that as quick as they reset 1 account another 10 enter the leader boards.

With the latest patch this is a thing of the past this has actually been fixed, however I’m wondering by fixing this they may have inadvertently caused the CTD’s at the end of the round. Although still not sure what is causing this problem.

I played on another Multiplay server last night running Titan and experienced no problems at all. The only thing different I have it seems from the majority is the Nvidia Driver that came with BF2 installed as all the other later drivers from Nvidia caused me problems both in BF2 and 2142.

So I actually do not understand where the root cause of the problem is. I would suspect it is client side though from all the posts I have seen over the various forums today (and there are lots of very unhappy people at the moment) is that whilst players are all being kicked from the servers at the end of round sequence on Titan, the servers are staying up, changing and loading the map rotations without any percieved issues.

I genuinely believe this is a clientside issue but not sure about the video driver route currently being explored. However time will tell over the next day or so wether this is the underlying issue or not.

In the meantime Conquest FTW!!!!

@LeGIt wrote:

I’m voting it’s multiplay again. Even with all your server fuckuos before the patch, every other server out there was fine. May even be to do with the clanforge setup itself, methinks.

Not sure what you getting at there mate – I played on both XDC and another Multiplay server last night with no problems whatsoever.

@Lammie wrote:

Ok the latest update I have is that this does indeed appear to be a serverside issue with Titan Maps.

I shall not gloat 🙄 😛
on another note ..come to think of it. it was working on the servers with one round of each so…good going Sherlock 😉

Since the maps load so quickly, I vote for setting to a single round per map. At least worth a try.

@Lammie wrote:

Ok the latest update I have is that this does indeed appear to be a serverside issue with Titan Maps.

The apparent workaround for this is to only run Titan Maps for a single round, so as suspected this is not a driver specific/related issue.

May be worth loading a couple of Titan maps on the Server to prove or disprove this theory?

£100 says its a by product of the ability to get the titan survival pin getting *cough* fixed 😆