Jump to content

[Bug]Kicked To Mechlab


18 replies to this topic

#1 Notick

    Member

  • PipPipPip
  • 67 posts
  • LocationAvon, IN

Posted 27 January 2013 - 08:04 PM

I've been rather impervious to most of the crash bugs my entire tenure here. I'll rarely ever crash with the typical bugs (Black Screen, Hud Bug, Yellow Screen, ETC...)

However, lately I'll randomly drop in the middle of a match, and get kicked into the MechLab almost as if the game has crashed. The game itself doesn't crash, however. It just removes me from the game giving an in-game "NoTick has Disconnected' message to those still in game. It's happening quite frequently. (Almost every other game)

This started after last Patch. There's no rhyme or reason to it - so I have no obvious feedback to what's causing it. I have deleted the Shaders folder, as well as deleted the info within the OmnicronOnline file. I'll post if it's noticeably helped or not.

Edited by Notick, 04 February 2013 - 07:26 PM.


#2 Notick

    Member

  • PipPipPip
  • 67 posts
  • LocationAvon, IN

Posted 29 January 2013 - 02:04 PM

The steps I've taken did not help with this problem. The outcome when the bug happens looks exactly the same as if I've hit "Quit Match" from the Escape menu. The game closes into the 'Mechlab.

#3 sycocys

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Moderate Giver
  • Moderate Giver
  • 7,641 posts

Posted 29 January 2013 - 04:35 PM

I know it's a pain, but can you try a full re-install to see if something in the patch itself got kinked on it's way to you?

#4 Darkrook

    Member

  • PipPip
  • 43 posts

Posted 29 January 2013 - 06:32 PM

I'm getting the same crash, i never crashed before last patch. I didn't change anything either. Its random and can start 10 seconds into match, or I can be in it for 10 minutes.

#5 Febrosian R Gillingham

    Member

  • PipPipPipPipPip
  • Little Helper
  • 122 posts

Posted 30 January 2013 - 12:04 AM

Also had this bug, randomly after the latest patch. It seems to be getting worse now though - I've been dropped from each of my last 5 matches at various times. Very annoying. Will try a full reinstall soon

#6 Notick

    Member

  • PipPipPip
  • 67 posts
  • LocationAvon, IN

Posted 31 January 2013 - 01:34 PM

Things I have done, but hasn't helped/repaired the issue:

-100% reinstall client. (Fully removed - even went through the Registry's and deleted everything).
-I have deleted the Shaders folder, as well as deleted the info within the OmnicronOnline file.
-Retro'd my nVidia drivers from 310 to previous.
-re-installed 310 drivers after previous step failed
-fully driver-scrubbed PC then reinstalled 310 nVidia drivers
-after previous failed, installed new Beta 313 drivers from nVidia (Which are supposed to help with CryEngine) to no avail

#7 ElmoWithAGun

    Member

  • PipPipPipPipPip
  • 164 posts
  • Location123 Sesame Street

Posted 31 January 2013 - 01:54 PM

My friend was having this issue and a simply restarting his computer seemed to have fixed it for him.

#8 Notick

    Member

  • PipPipPip
  • 67 posts
  • LocationAvon, IN

Posted 31 January 2013 - 02:01 PM

My PC is shutdown every evening. This hasn't remedied the issue at all for me.

#9 ElmoWithAGun

    Member

  • PipPipPipPipPip
  • 164 posts
  • Location123 Sesame Street

Posted 31 January 2013 - 02:06 PM

Reproduce the problem and check if there is anything that was printed in your Omicron.log file right before you're kicked back to the mechlab. The log file is pretty easy to follow.

#10 Notick

    Member

  • PipPipPip
  • 67 posts
  • LocationAvon, IN

Posted 31 January 2013 - 10:11 PM

It has happened over 14 times in the past hour. I've rebooted the computer, reset the client, done all the previously listed steps, and nothing is helping. The Omicron or OmicronOnline file reveals nothing of value...

Every match it was happening in was an 8-man. They were always in random instances. I would be in a match for some time before I randomly get disconnected. Or, it would happen almost immediately after the new power-up sequence.

I'm at an utter loss.

Edited by Notick, 31 January 2013 - 10:13 PM.


#11 Notick

    Member

  • PipPipPip
  • 67 posts
  • LocationAvon, IN

Posted 01 February 2013 - 05:36 PM

Had an interesting event happen today... Rather than getting into a game, and then randomly kicked to Mechlab per usual, I hit 'Launch' and the game didn't even log me in at all - it did, though, keep my Mech in-game even though I never actually got put into the game client.

Muy strange

#12 Darkrook

    Member

  • PipPip
  • 43 posts

Posted 03 February 2013 - 12:24 PM

Not sure if it will help, but i turned off AA , and i haven't had this crash in 2 days. Not sure if PGI fixed, or turning this off actually worked. Anyways its worth a shot if you havent tried it yet. Good Luck

#13 ChaosGrinder

    Member

  • PipPipPipPipPipPipPip
  • Elite Founder
  • Elite Founder
  • 881 posts
  • LocationNew Eden

Posted 03 February 2013 - 12:36 PM

I get that bug too. I get kicked back to mechlab without warning in the middle of the fight, all since last patch. I´ve done everything but nothing helped.

#14 ayezred

    Member

  • PipPip
  • Elite Founder
  • Elite Founder
  • 41 posts
  • LocationWhat?, Dunno.

Posted 03 February 2013 - 01:53 PM

I have the same issue.

#15 Notick

    Member

  • PipPipPip
  • 67 posts
  • LocationAvon, IN

Posted 03 February 2013 - 05:33 PM

I believe I found the verbage for the problem we're expereincing.

In my Omicron file, it says:

============================ PrepareLevel rivercity ============================
Initializing default materials...
[Error] Runaway thread
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetName
======== rivercity is loaded in 16.8 sec ========
CGameClientChannel::Release
could not free all buffers from CDevBufferMan!
UnLoadLevel End: 0.4 sec
	sv_gamerules = mechlab []
============================ Loading level mechlab ============================
Initializing default materials...
======== mechlab is loaded in 3.9 sec ========


The 'could not free all buffers from CDevBufferMan!' line leads directly into an 'unload' of the level, then kicking back into the MechLab.

Edited by Notick, 03 February 2013 - 05:35 PM.


#16 RapierE01

    Member

  • PipPipPipPipPipPipPipPip
  • 1,576 posts
  • LocationEden

Posted 04 February 2013 - 01:29 AM

i had the same problem after starting a match. The Loading screen apears and the all got black. 3 Mins later i was back in my Mech Hangar and the Mech wasnt in battle.

I solved the Problem during restarting my Wireless Spot. Since this it works

#17 Dunkelbunter

    Member

  • PipPip
  • 47 posts

Posted 04 February 2013 - 02:09 AM

I had send all my data files (dxdiag, omicron, chrashdump and the omicron backup) to PGI.
I waiting for answer.

What had i do:
- reinstall the game
- upgrade nvidia driver
- downgrade invidia driver
- testing another wifi-card
- reinstall teamspeak
- change the channels at my router
- upgrade the wifi driver

On my notebook i had testing 10 games and i had no crashes.
But with the desktop pc i had only trouble after the last patch.

#18 Notick

    Member

  • PipPipPip
  • 67 posts
  • LocationAvon, IN

Posted 04 February 2013 - 07:24 PM

Similar story with myself. I've sent in all the requested files by the PGI support person, and added a later addendum explaining my own findings within the Omicron file.

I only utilize my hand-built Desktop which is connected via direct Cat-6 cable to the router. I've never had this issue before the patch - and honestly, After the thousands of games I've played, I've had maybe 10 total of the 'black screen' bugs, and maybe 15 instances of the '4fps' bug. This is the only bug that's actually been 100% detrimental to my play.

I can not drop at all without the game dropping back to MechLab. It's a 100% rate now, not just periodic instances.

Edited by Notick, 04 February 2013 - 07:27 PM.


#19 Antony Weiner

    Member

  • PipPipPipPipPipPip
  • 344 posts
  • LocationEast Coast U.S.

Posted 04 February 2013 - 11:41 PM

I had this happen to me 3 times in a row in 8 man games.

The most frustrating bug I've encountered so far.

Terrible bug.





6 user(s) are reading this topic

0 members, 6 guests, 0 anonymous users