Connectivity Hotfix!
#61
Posted 25 April 2013 - 11:29 AM
#62
Posted 25 April 2013 - 12:18 PM
After I reinstalled the game and my first attempt that ended I a new and exciting crash things had gone quite nicely (Aside from my lack of skill that I won't blame PGI for.)
But just now the game crashed again, without comment or fair warning.
Round just started, no "All systems nominal" yet >>wham<< desktop.
So I guess the reinstall didn't help much.
But it was worth a try and at least I got a clean Installation now.
That something at least.
#63
Posted 25 April 2013 - 03:29 PM
8 man drops:
8 out of 10 games 1-2 pilots crashed to desktop
10 out of 10 games at least 1 pilot had no hud and/or no map,usualy 2 and up to 4 suffered this bug PER MATCH!
usage of repair tool has no effect on propability of crash or bug.
our team was so pissed that after 10 matches we simply gave up to play at all. several ppl stated that they wont start the game again bevore they see a anouncement for hotfix for the hotfix for a barly existing problem(rubberbanding was not a problem for us since month)
#64
Posted 25 April 2013 - 03:43 PM
Niko Snow, on 24 April 2013 - 10:07 AM, said:
- Desync and/or
- Rubberbanding,
Since the patch the rubberbanding/Desync has stoped, ran through Prime Time CST with no issues. thanks for the fix
#65
Posted 25 April 2013 - 05:00 PM
#66
Posted 25 April 2013 - 06:06 PM
Game just hung during the start up sequence.
Edit: and another, two matches later.
Edit: And a bunch of crashes to desktop which I have never had happen before.
Edited by Pater Mors, 26 April 2013 - 12:41 AM.
#67
Posted 25 April 2013 - 06:50 PM
#68
Posted 25 April 2013 - 07:38 PM
#69
Posted 25 April 2013 - 07:49 PM
#70
Posted 25 April 2013 - 08:00 PM
Edited by jay35, 25 April 2013 - 08:05 PM.
#71
Posted 26 April 2013 - 12:04 AM
BUT i have big issues now with hit detection. Especially on fast or jumping lights, which are near impossible to get a hit registered with now. My lasers for example hit on the mech and let it glow, the paperdoll though shows nothing and the hit is not registered.
I also frequently CTD now or face hard crashes (which i have to manually reboot after) that i never faced before. No crash dump, no logs, nothing...
#72
Posted 26 April 2013 - 01:04 AM
#73
Posted 26 April 2013 - 01:16 AM
#74
Posted 26 April 2013 - 02:56 AM
I'm still taking a break from it, I'll check back in from time to time but you're ruined any chance of my purchasing MC for some time. I'll play occasional games here and there but I won't have play sessions lasting 3-4 hours anymore and I sure as hell won't be recommending MWO to people until the game comes out of beta at the earliest.
The worst part is that despite the fact that as far as I could tell at least 15-30% of your players couldn't play and yet you still ran events like nothing was wrong. You guys need to start actively communicating with your community, or start handing out compensation every time you cause issues like this. 15MC a week would be a good compensation, it's enough for a single flush... let's face it, that's how we feel you've been treating our issues.
#75
Posted 26 April 2013 - 04:10 AM
Before patch had very little issue with the game and only the occasional no mini map hud bug
Also somethings gone wonky with lights again Stats from previous night where with large lasers 95% hit rate 80% damage after patch 19% damage.
Took 3 of us constantly hitting (from all our point of view) 1 raven which we finally managed to leg and then even when legged took a combined 8 alphas to finally kill.
Previous night I was killing ravens with relative ease post the patch in every game vs a raven it took nearly all my ammo to make them orange in a dedicated light hunting mech and config
#76
Posted 26 April 2013 - 07:54 AM
this is something that has happened since the latest april patch. and has not been resolved by the hotfix.
never had rubberbanding. i guess this would be called a desync issue?
Edited by Tennex, 26 April 2013 - 07:56 AM.
#77
Posted 26 April 2013 - 07:53 PM
#78
Posted 26 April 2013 - 08:06 PM
edit: it also happens sometimes in the middle of a drop
I only mention this because I have not had CTD issues in the game for some months now.
Has anyone else seen this trend?
Edited by Kin3ticX, 26 April 2013 - 08:30 PM.
#79
Posted 27 April 2013 - 01:49 AM
#80
Posted 27 April 2013 - 10:40 AM
OmicronOnline[ELogLevel_Error]: [Apr 27 2013 17:39:33 MWOClient.exe ERROR]: Failed to decode incoming packet. Message will be dropped: type=HUB2C::StackContainerListSuccess
Apparently the server sends bad packets as well - it's honestly getting outrageous!
Also nice:
OmicronOnline[ELogLevel_Debug]: Received OnPushNotification: a_Result=EResult_NoSession
OmicronOnline[ELogLevel_Debug]: Performing COmicronOnlineAgent::SendNotification
OmicronOnline[ELogLevel_Debug]: Received OnPushNotification: a_Result=EResult_NoSession
OmicronOnline[ELogLevel_Debug]: Performing COmicronOnlineAgent::SendNotification
OmicronOnline[ELogLevel_Debug]: Received OnPushNotification: a_Result=EResult_NoSession
OmicronOnline[ELogLevel_Debug]: Performing COmicronOnlineAgent::SendNotification
OmicronOnline[ELogLevel_Debug]: Performing COmicronOnlineAgent::SendRetrieveInventoryList
OmicronOnline[ELogLevel_Debug]: Received OnPushNotification: a_Result=EResult_NoSession
OmicronOnline[ELogLevel_Debug]: Received OnPushNotification: a_Result=EResult_NoSession
OmicronOnline[ELogLevel_Debug]: Received OnPushNotification: a_Result=EResult_NoSession
Or just this one:
======== mechlab is loaded in 9.8 sec ========
[Error] Runaway thread
[Error] Runaway thread
[Error] Runaway thread
[Error] Runaway thread
[Error] Runaway thread
UnLoadLevel End: 0.1 sec
Ammo Pool Statistics:
bullet: 18
homingrocket: 0
waypointrocket: 0
javelin: 0
narc: 0
[Error] Runaway thread
[Error] Runaway thread
System Shutdown
[Error] Runaway thread
DXInput Shutdown
Maybe this?
======== mechlab is loaded in 7.9 sec ========
CAccountMgr::OnRetrieveFriendList: Unhandled callback error: EResult_Timeout
The list goes on and on...
The funny part about it though is the fact that 70% of the "Session lost" errors occur when it tries to load my mechs in the mechbay now. The 30% left are CTDs once a game started telling me "Session lost". It's as if it cannot load the mech you selected for the game...database problem?
Edited by Sturmwind, 27 April 2013 - 10:49 AM.
9 user(s) are reading this topic
0 members, 9 guests, 0 anonymous users