About every battle I get into someone disconnects. I having the same problem where I get in a match and I get booted from the game. Many times is when I'm running around or about to cap a base. Anybody having the same problem and any ideas why this is going on. Any ideas on how to fix this problem? I doubt the people are quitting from the game, but the game is just kicking them.


The Relentless Disconnect?
Started by 277787, Feb 22 2013 11:57 PM
6 replies to this topic
#1
Posted 22 February 2013 - 11:57 PM
#2
Posted 23 February 2013 - 04:59 AM
Check your crash dumps for clues about why you're disconnencting.
#3
Posted 23 February 2013 - 11:33 AM
Redshift2k5, on 23 February 2013 - 04:59 AM, said:
Check your crash dumps for clues about why you're disconnencting.
How do I check "crash dumps"? I'm having the same problem since the latest patch. Before maybe 1 in 10 matches it would freeze up, now it seems it's every 2 out of 3 matches. Not playable...
#4
Posted 23 February 2013 - 11:40 AM
Somewhere in your game folder. I believe under users, but otherwise possibly in the actual game folder.
Typically this file is over 400 megabytes and is called something along the lines of crashdump.dump
This file can be opened partially with notepad. I haven't had a crash in ages, so yeah..
Typically this file is over 400 megabytes and is called something along the lines of crashdump.dump
This file can be opened partially with notepad. I haven't had a crash in ages, so yeah..
#5
Posted 23 February 2013 - 12:52 PM
I too have been experiencing this, I ran very stable until the last patch. I will also attempt to check my crash dumps.
#6
Posted 23 February 2013 - 01:00 PM
Well the logs appear to be in the C:\Games\Piranha Games\MechWarrior Online\LogBackups directory, I sorteb by date an looked at the last few.
Mine has been referencing graphical glitches:
============================ PrepareLevel forestcolony ============================
Initializing default materials...
[Error] Runaway thread
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'objects/environments/skyboxes/forestcolony_clouddome_a.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/forestcolony_clouddome_a.dds]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/laser_beam_1x4_lop0.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/laser_beam_1x4_lop0.dds]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/ppc_beam_b.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/ppc_beam_b.dds]
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetName
======== forestcolony is loaded in 8.5 sec ========
I am curious as to what you are seeing [color="#b27204"]277787[/color].
Mine has been referencing graphical glitches:
============================ PrepareLevel forestcolony ============================
Initializing default materials...
[Error] Runaway thread
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'objects/environments/skyboxes/forestcolony_clouddome_a.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/forestcolony_clouddome_a.dds]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/laser_beam_1x4_lop0.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/laser_beam_1x4_lop0.dds]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/ppc_beam_b.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/ppc_beam_b.dds]
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetName
======== forestcolony is loaded in 8.5 sec ========
I am curious as to what you are seeing [color="#b27204"]277787[/color].
#7
Posted 23 February 2013 - 08:38 PM
Hm. Clearly that's an easier method. With the omicron name and such I never thought to look at them. I've just looked at the dump file I found at one point -- admittedly long after the fact, and found numerous references to errors.
Welp, there we have it.
LogBackup, sort by date, and take a peek.
Welp, there we have it.
LogBackup, sort by date, and take a peek.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users