Topic changed: why do I CTHL all the time ?

[Vampress]

I should have explained' date=' these missions results aren't lost - they're just not displayed to you in your AAR. They are logged on our databases (and should be in CSR if delayed slightly).[/quote']

which no one actually cares about...

I'll give up the results from my mission IF I don't have the game crash because of the results pending bug...

people are complaining because if you get that results pending your going to have to relog into the game...and often it's more then 1 time you have to do it because it won't let you log back in right away.

It's endemic now...I get it all the time. I find people...most people get it in game now also ALL THE TIME.

NO ONE(maybe a few stat brats would) actually cares if the mission results are LOST...it's getting kicked out of the game everyone is steamed about.

[shrimps]

Anything that kicks me out of the game.

CTHL, CTD, results pending bug, etc.

all these have forced me to stop playing almost entirely.

I get CTHL almost every hour and results pending bug every 15 or so missions. OH and of course the game likes to throw in a CTD in between the two just for good measure.

Then I have to relog in multiple times because about every 3rd time I log in everything is locked. So yeah, it's bad.

[speed68]

That's enough of that' date=' Negative Nelly.[/quote']

That's it, you tell em!

{edit} Don't do that Jonesz, MM is hungry, and she likes ketchup!

btw....I like mustard better!

Edited November 18, 2009 by speed68

[retterkl]

Are the fact that the server thing the newsletter is running on and the mission results pending due to a lost connection to a server anything to do with eachother, or did Darkvex run around CRS headquaters unplugging lots of irrelevant devices?

[MOTORMOUTH]

Nope, nothing to do with forums or the website occupy the same servers as the game or other DB stuff.

[retterkl]

Nope' date=' nothing to do with forums or the website occupy the same servers as the game or other DB stuff.[/quote']

So who has been sabotaging the servers then? Newsletter going down, forums pooping out, mission results pending, lots of blank tiles appearing now.... seems rather coincidental.

Although I assume this is the stuff that you guys would usually be working on fixes for in normal business hours if it weren't for 1.31.

[MOTORMOUTH]

The newsletter issue is a completely unrelated software issue that we haven't nailed down yet. We're working on a complete wipe and reload of that and the mailing DB and a clean reload to hopefully sort that out.

The other stuff is out of my realm, but I did send out an email to our coders to see if there was anything blatantly fuxxored.

Nothing has been found so far. But they'll keep looking.

[monsjoex]

I should have explained' date=' these missions results aren't lost - they're just not displayed to you in your AAR. They are logged on our databases (and should be in CSR if delayed slightly).[/quote']

I know, but the bug now makes you CTHL, wich is very annoying.

[popeye0]

Have to agree with the "mission pending" bug. Its the one that might make me quit all together.

Nothing worse than defending a cp or spawning in to and going to look in the cp for the radio and getting shot, then knowing that an ei is capping but you have just got "the bug from hell" and cant do anything about it. Then have to reload twice to get back in.

I haven't played much in the past week and I am loosing interest in the map.

[viruses]

I won't mind if 1.32 was a Naval patch or maybe a bomber strategic patch. (Licks his chops for some B24, Ju88, Lancaster) or... maybe subs... landing craft!! Damn... I'm getting myself too excited..

[lure]

CRS need to change ISP for the game servers. I bet many CTHL and similar bugs are due to the ISP used.

Since a few month back the company hosting CRS "Primary Network" is blocking traffic from the part of the Internet I'm on. I can only play over the "Secondary Network" and that seems to struggle badly with server load. If there is any kind of population on the servers I get 50-70% packetloss. It's soon two weeks since I last bothered launching the game at all. I just do the occasional trace to the BE servers a few times each week to see if the network is open or not. If I was not a builder I probably would have canceled my sub by now.

[ZEBBEEE]

none of the above. 1.32 needs to be abotu 1 thing and ONLY 1 thing. the only thing that matters is an overhaul of the game play system to make combat better

don't worry, 1.32 will be about that.

[alfheim]

If it's a choice between CRS providing excellent connection to the game, or the new game features in 1.31, they better go with the former.

How many new players will it cost them if they release 1.31 with these terrible and unacceptable connection issues?

[Greni]

Change & test network route in your game settings with and without SSE , it helps a lot of people with CTHL problems and stop the spam please .

Thank you.

[lure]

Change & test network route in your game settings with and without SSE , it helps a lot of people with CTHL problems and stop the spam please .

Thank you.

Somewhere down the line CRS will have to decide if they want to keep using the crappy ISP they're on now.

Some of us don't even have access to both network routes and are left with whatever performance there is on the "backup" route.

traceroute to 66.28.6.226 (66.28.6.226), 30 hops max, 60 byte packets

1 192.168.1.1 (192.168.1.1) 0.321 ms 0.220 ms 0.484 ms

...

10 ti3001b300-ae0-0.ti.telenor.net (146.172.105.70) 27.011 ms 27.545 ms 29.108 ms

11 te4-8.ccr01.sto01.atlas.cogentco.com (130.117.15.53) 30.678 ms !X * *

CogentCo is blocking traffic even when the target IP is inside their own networks.

[nordmin1]

BLOO;

I have to call you your comment that the "mission results pending" is connection related.

This was NEVER an issue prior to 1.30 - there is a code change that has caused this. OR there has been a change in the servers at CRS (os or otherwise) that is causing the error.

More significantly - the error is increasing in frequency. SO - if it is a connection error, you have a switch that is packing it in, or a server that's about to take a dump.

If you cruise side during an average evening, you will hear HUNDREDS of reports of MRP crashes.

This should get a top billing priority with your bug fixers.

n1

[dotsie]

Signed.

Dont try put these issues on us CRS. I play plenty of online games with little or no connection issues.

[veubiah]

The mission results pending issue is connection related in as much as the connection seems to get lost when control is being transferred between hosts at the end of the mission. There are no identifiable network issues to the server network boundary when this happens

[errah]

I mean a patch to clean up some of the most annoying an long-standing issues? They're not a major thing by themselves, but they add up to death by a thousand cuts.

Stuff like :

* "Mission Results Pending" bug

* Grey "Enter World" button bug

* Reticules for the churchill tanks hull gunners

* The white flickering lines on the churchill III's gunsight

* The silly climb on the flak-30 when it fires

* The collider on the 109's nose so it doesn't sink into the airfield

* Making the ATR's manually reload

* Fixing the mouse issues on vista and windows 7

Stuff like that, I'm sure there are a million other things people have ideas for.

and add the 5/10 min CTD bug for ATI users with Catalyst 9.8/9.11 pls

[kroni]

every day i get this farking * "mission results pending" bug

i get it almost every mission!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

death to the bug!

DEATH TO ALL BUGS

I get it right in the most inconvienient of times all day everyday

Edited December 3, 2009 by Kroni

[geeezer]

Had 4 consecutive CTHL seconds after starting to move on the first spawn of the log on. Lost 2 LMGs and two 232s.

Before the second two events I tried resetting my router and internet connection [powered down] and restarted the computer.

No clue if in game or my internet provider [Comcast] is having a bad day. Other internet applications appear to be ok.