399 replies to this topic

[MischiefSC]

Updated my GTX 560 to the newest 314 drivers, rebooted.

Having HUD issues almost every single game. Missing IFF identification, minimap, strange crosshairs, associated problems.

1 in 5 matches it doesn't trigger the end screen; my mech just hangs there and I have to quit the match and my mech remains unavailable until it times out and releases it.

[Flying Fox 333]

I am getting two problems which prevent me from playing at the moment. A black screen after the maps loading screen and the inability to relaunch with the mech after the match is finished, as it stays "in-game" afterwards.

Was any error message provided with the crash, if so, which?
No

Where in the game or menus did the crash occur?
After the maps loading screen.

What steps had been taken prior to the crash occurring?
Play any online game mode.

Does the crash re-occur for you if repeating those same steps?
Yes. Tried different mechs with the same result.

What are your video settings, did you change them since last patch?
Have tried low across the board, but previously played with Game Detail at medium with no issues with the previous patch.

What are your System specs?

Intel Core 2 Duo E6850 3 GHz, AMD Radeon HD 5850 & 4GB RAM

I can provide the crashdump.dmp file if required. Just send me a message with the best way to send this to you.

Omicron.log

Spoiler

BackupNameAttachment=" Build(4418) 03 Apr 13 (12 45 04)" -- used by backup system
Log Started at 04/03/13 12:45:04
Running 32 bit version
Executable: I:\Program Files\Piranha Games\MechWarrior Online\Bin32\MWOClient.exe
FileVersion: 3.4.1.4418
ProductVersion: 3.4.1.4418
Using STLport C++ Standard Library implementation
Added MOD directory <engine> to CryPak
Executable Command Line: "I:\Program Files\Piranha Games\MechWarrior Online\Bin32\MWOClient.exe" flowthru
Total number of logical processors: 2
Number of available logical processors: 2
Total number of system cores: 2
Number of cores available to process: 2
Processor 0:
CPU: Intel Intel® Core™2 Duo CPU E6850 @ 3.00GHz
Family: 6, Model: 15, Stepping: 11
FPU: On-Chip
CPU Speed (estimated): 2.9 MHz
MMX: not present
SSE: present
3DNow!: not present
Serial number not present or disabled
Processor 1:
CPU: Intel Intel® Core™2 Duo CPU E6850 @ 3.00GHz
Family: 6, Model: 15, Stepping: 11
FPU: On-Chip
CPU Speed (estimated): 2.9 MHz
MMX: not present
SSE: present
3DNow!: not present
Serial number not present or disabled
[Error] Error: ConsoleVariableGroup 'sys_spec_environment' key 'e_TerrainLodRatio' is not missing in default
[Error] Error: ConsoleVariableGroup 'sys_spec_environment' key 'e_TerrainTextureLodRatio' is not missing in default
[Error] Error: ConsoleVariableGroup 'sys_spec_environment' key 'e_TerrainTextureLodRatio' is not missing in default
[Error] Error: ConsoleVariableGroup 'sys_spec_environment' key 'e_TerrainTextureStreamingPoolItemsNum' is not missing in default
[Error] Error: ConsoleVariableGroup 'sys_spec_environment' key 'sys_spec_Quality' is not missing in default
[Error] Error: ConsoleVariableGroup 'sys_spec_environment' key 'r_ssreflections' is not missing in default
[Error] Error: ConsoleVariableGroup 'sys_spec_environment' key 'e_TerrainTextureStreamingPoolItemsNum' is not missing in default
[Error] Error: ConsoleVariableGroup 'sys_spec_postprocessing' key 'r_UseEdgeAA' is not missing in default
Windows 7 64 bit SP 1 (build 6.1.7601)
System language: English
Windows Directory: "C:\Windows"
Prerequisites...
* Installation of KB940105 hotfix required: no! (either not needed or already installed)
Local time is 12:45:04 04/03/13, system running for 12 minutes
4096MB physical memory installed, 2442MB available, 4095MB virtual memory installed, 40 percent of memory in use
PageFile usage: 28MB, Working Set: 19MB, Peak PageFile usage: 28MB,
Current display mode is 1280x1024x32, (Unknown graphics card)
IBM enhanced (101/102-key) keyboard and 5+ button mouse installed
--------------------------------------------------------------------------------
Stream Engine Initialization
GameName: MechWarrior Online
BuildTime: Apr 1 2013 14:38:12
Windows Error Reporting is enabled setting exception handler
Font initialization
Physics initialization
Sound initialization
<Sound> Initializing AudioDevice now!
<Sound> Initialize FMOD with dynamic memory callbacks
<Sound> Starting to initialize Windows Audio Session API output!
<Sound> Drivers found: 3
<Sound> Available drivers:
1. Headphones (SoundMAX Integrated Digital HD Audio)
2. Speakers (SoundMAX Integrated Digital HD Audio)
3. SPDIF Interface (SoundMAX Integrated Digital HD Audio)
<Sound> FmodEx-AudioDevice: Now running on driver: Headphones (SoundMAX Integrated Digital HD Audio)
<Sound> Using speaker mode: FMOD_SPEAKERMODE_STEREO
<Sound> Initializing FMOD-EX now!
<Sound> Initialized FMOD-EX
<Sound> Available record drivers: 0 Microphone (SoundMAX Integrated Digital HD Audio) !
<Sound> Available record drivers: 1 Line In (SoundMAX Integrated Digital HD Audio) !
<Sound> Record config is set to autodetect using record driver 0
<Sound> Using FMOD version: 00044004 and internal 00044004!
<Sound> Initializing SoundSystem now!
Renderer initialization
used GeomInstancingThreshold is 2
Localized language content(english) not available or modified from the original installation.
Localized language content(english) not available or modified from the original installation.
Network initialization
[net] using iocp socket io management
network hostname: TD
ip:192.168.1.11
[Network Version]: RELEASE PURE CLIENT
MovieSystem initialization
Console initialization
Time initialization
Input initialization
AI initialization
Initializing Animation System
Initializing 3D Engine
Initializing default materials...
Script System Initialization
Entity system initialization
Initializing AI System
[PlayerProfiles] Login of user 'Tim' successful.
[PlayerProfiles] Found 2 profiles.
Profile 0 : 'Flying Fox 333'
Profile 1 : 'default'
[GameProfiles]: Successfully activated profile 'Flying Fox 333' for user 'Tim'
Patch Complete Received
Patch Complete Received
Patch Complete Received
Patch Complete Received
============================ Loading level mechlab ============================
[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]
======== mechlab is loaded in 4.6 sec ========
sv_gamerules = TrainingGrounds []
============================ Loading level forestcolony_snow ============================
UnLoadLevel End: 0.4 sec
Initializing default materials...
CGameRules::OnClientEnteredGame: Client has entered the game.
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetName
[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]
======== forestcolony_snow is loaded in 19.8 sec ========
CHAT SYSTEM- Flying Fox 333 to No Pilot:
killed
CHAT SYSTEM- Flying Fox 333 to No Pilot:
killed
CHAT SYSTEM- Flying Fox 333 to No Pilot:
killed
CHAT SYSTEM- Flying Fox 333 to No Pilot:
killed
CHAT SYSTEM- Flying Fox 333 to No Pilot:
killed
CHAT SYSTEM- Flying Fox 333 to No Pilot:
killed
CHAT SYSTEM- Flying Fox 333 to No Pilot:
killed
CHAT SYSTEM- Flying Fox 333 to No Pilot:
killed
UnLoadLevel End: 0.5 sec
sv_gamerules = mechlab []
============================ Loading level mechlab ============================
Initializing default materials...
[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]
======== mechlab is loaded in 5.0 sec ========
UnLoadLevel End: 0.4 sec
Game rules class: Assault
Level forestcolony_snow does not support Assault gamerules.
============================ PrepareLevel forestcolony_snow ============================
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] locomotion-group not found: animations/mechs/jagermech/lmg_files/flight_fs_1.lmg
[Error] locomotion-group not found: animations/mechs/jagermech/lmg_files/flight_take_off_ltf.lmg
[Error] locomotion-group not found: animations/mechs/jagermech/lmg_files/flight_fs_1_fp.lmg
[Error] locomotion-group not found: animations/mechs/jagermech/lmg_files/flight_take_off_ltf_fp.lmg
[Error] Runaway thread
[Error] Runaway thread
[Error] Runaway thread
[Error] Runaway thread
[Error] Runaway thread
UnLoadLevel End: 0.2 sec
Ammo Pool Statistics:
homingrocket: 0
waypointrocket: 0
[Error] Runaway thread
[Error] Runaway thread
System Shutdown
[Error] Runaway thread
WER: Running CryEngine Exception Handler
WER: Creating Crash Dump
WER: Attempting to load DBGHELP.DLL
WER: DBGHELP.DLL Located
WER: Creating Crash Dump File
WER: Crash Dump File Created writing dump data
Saved dump file to 'user\crashdump.dmp'

Edited by Flying Fox 333, 02 April 2013 - 09:01 PM.

[Hallas]

End game not finishing; no Cbills or XP credit.

Random freezing/crashing to desktop

Edited by Hallas, 02 April 2013 - 09:09 PM.

[MagZi]

I'm having an issue where I'm unable to drop in my Atlas, I've been able to Drop with my Fang. But when I attempt with my Atlas it just goes to a black screen.

[Nirilus]

1. Multiple matches - when match is over, never get the last screen. Action stops, but nothing happens. (Smoke and stuff is still animated in background.) Have to escape to exit match and server holds my mech presumably for the full 15 minutes?

2. Press Tab to see stats, and the boxes are empty (happened one match so far)

3. Night vision goes off randomly (One match, impacted multiple players)

4.

• 
  
• Was any error message provided with the crash, if so, which? No
  
• Where in the game or menus did the crash occur? During Gameplay, and in the in match stats screen
  
• What steps had been taken prior to the crash occurring? No Crash.
  
• Does the crash re-occur for you if repeating those same steps? NA
  
• What are your video settings, did you change them since last patch? No changes
  
• What are your System specs? (You can include them in a [spoiler] GTX 680 core i5 3750k 8gb ram pc1600 motherboard - gigabyte u77 something[ /spoiler])

[Tanimaga]

Issues after patching today..

Takes 5 minutes or so to enter a match. When the match begins, it was already been 5 minutes into an active one.

After being destroyed, hangs on the "You have been destroyed" screen without any option to view match or exit.

Training Grounds option works fine, but fails to show speed tweek on my mechs. My 150kph Raven is 136kph.

[Rhae]

Since patching, everytime I start a match the screen goes black and the only way to get out of it is to alt-tab and force close the program.

Never had this issue prior to the patch today.

[Graxas]

Rhae, on 02 April 2013 - 09:29 PM, said:

Since patching, everytime I start a match the screen goes black and the only way to get out of it is to alt-tab and force close the program.

Never had this issue prior to the patch today.

Same Issue - tried upating video drivers, updating Direct X, uninstall then reinstall MWO, changing video settings to play in a window or on high instead of very high and still getting the issue. Have been able to play 1 match out of the last 15 launches.

[Corvus Antaka]

getting more and/lots of hardlocks, screen just randomly freezes for seemingly no reason, ctrl-alt-del only way to resolve, no dmp generated.

[Dr Killinger]

Already mailed support about it and provided coious amounts of data for them, but I'm also having the black screen bug. Map loads, and I get a black screen and lots of internet activity until I kill the process. It loaded into a match once, but after around3 minutes of blackscreen.

Windows 8
i5-760 @ 3.8GHz
GTX470 @ 750MHz/1750MHz on diver version 314.22 WHQL
8GB DDR3
2meg ADSL line

I played all weekend, and had 2 matches just before the patch dropped, and had changed literally nothing, not even drivers, so it's all on the patch.

[Tanimaga]

Pretty much useless until the issues are resolved. Even rolling back the patch would be nice until the bugs are worked out.

[pudge131]

Taron, on 02 April 2013 - 12:04 PM, said:

Never ending matches

Match is over, no ending screen, mech is blocked sind 10 minutes now.

ANd you dont earn the CBills or experience from that match either!

[Nutlink]

Crashing back to the Home tab quite often now. Never had this issue before. I have my CPU OC'd but I dropped it back down to stock settings to test it out, and it still happened. Tried it out on my laptop and backup rig as well, same thing. It's just crashing a lot, as in roughly 40% of the matches. It usually happens in the middle of the round too, not at the beginning, and it doesn't matter which map it is. Current nVidia drivers are 314.22 on Windows 8 for 2 of my machines (GTX 680 and GT555m), and 13.3 beta for the 5870 on Windows 7.

[Tanimaga]

Anyone else do a fresh install, and see if it cleared the problems?

[Xerkran]

My issues till now:

5 Times Crash to Desktop without any Error-message after 3-5min ingame, 2x frozen minimap (always looking and walking to top) and 1x no HUD.

System:
2500K@3,2Mhz, GTX560Ti, 8GB RAM, all Drivers up to date.

[Cyk0]

I have gotten: FRead did not read expected number of byte from file, only 128 of 0 bytes read

And a crash each time I have tried to launch so far.

Dual Ati Radeon HD 5700...

Edited by Cyk0, 02 April 2013 - 10:47 PM.

[Jaxass]

Worst stability yet, I used to crash rarely now me and all my friends crash once every 30-40 minutes of play

[Igchy]

- When start the match got black screen every time ,got to press alt+tab to get back into the match which is already start for 1 minute.

- Crash to desktop no error message during a match.

- Have not change any setting since last patch.

-My spec ram 4 GB / Ati HD 5770 (driver 13.3) /Intel 750@2067 Ghz / My ping 300 + - 10

I understand this is a beta ,its not strange that these things happen every patch.Keep up the good work PGI.love this game

[Grus]

in game turning after a target and crashed to desktop. river city night.

how am i supposed to get my KD back up over 6 with all these crashes? lol

Edited by Grus, 02 April 2013 - 10:51 PM.

[Bruce Adders]

Zealander, on 02 April 2013 - 12:43 PM, said:

I can login and launch; the map screen then loads showing me what map is loading, then black screen and endless nothingness...
Using Vista 64 Premium SP2, GEFORCE GTX 650Ti (driver 314.22), Direct x 11.0
(FYI I wasn't getting any crashes or glitches at all with the last patch)

Me too - this patch has made loading into a battle ok, my mechs is there and getting shot up, but all I have is silence and black screen ad infinitum. Guess I'll try again tomorrow and hope the patch is fixed. Once again, a shame about wasting my premium account time.