Aller au contenu

Photo

[Error report] Extreme graphics stalls MP


  • Veuillez vous connecter pour répondre
Aucune réponse à ce sujet

#1
BioSpirit

BioSpirit
  • Members
  • 261 messages
I was getting some extreme and unusual graphics lagg/stalls during a multiplayer game and I noticed an anomaly in the log. The game was having about 10'000 rendering threads. That's not normal. I wasn't the host.

EDIT: Also the startup time was unusually long. It took about 30-40 seconds. The other players were already moved into the other side of the map and I was in a middle of the enemies when the game finally started.

########### Level cleanup took: 0.149757 seconds
########### Finished persistent loading MPLobby: 0.710833 seconds
The thread 'Win32 Thread' (0xfd4) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xfe4) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x11cc) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x580) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x13b0) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x960) has exited with code 0 (0x0).
The thread 'RenderingThread' (0x410) has exited with code 0 (0x0).
The thread 'RenderingThread' (0x10b4) has exited with code 0 (0x0).
The thread 'RenderingThread' (0x113c) has exited with code 0 (0x0).
The thread 'RenderingThread' (0xad4) has exited with code 0 (0x0).
--- Snip ---
The thread 'RenderingThread' (0x2248) has exited with code 0 (0x0).
The thread 'RenderingThread' (0x224c) has exited with code 0 (0x0).
The thread 'RenderingThread' (0x2250) has exited with code 0 (0x0).
The thread 'RenderingThread' (0x2254) has exited with code 0 (0x0).
The thread 'RenderingThread' (0x2258) has exited with code 0 (0x0).
The thread 'RenderingThread' (0x225c) has exited with code 0 (0x0).
--- Snip ---
The thread 'RenderingThread' (0xa094) has exited with code 0 (0x0).
The thread 'RenderingThread' (0xa098) has exited with code 0 (0x0).
The thread 'RenderingThread' (0xa09c) has exited with code 0 (0x0).
The thread 'RenderingThread' (0xa0a0) has exited with code 0 (0x0).
The thread 'RenderingThread' (0xa0a4) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x12c4) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x12cc) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x308) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x9c8) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xffc) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xa0e0) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xba4) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1140) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x12f4) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x13bc) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xde0) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x730) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xbd0) has exited with code 0 (0x0).
########### Level cleanup took: 0.328035 seconds
First-chance exception at 0x7464b9bc in MassEffect3.exe: Microsoft C++ exception: wchar_t at memory location 0x0201e324..
First-chance exception at 0x7464b9bc in MassEffect3.exe: Microsoft C++ exception: wchar_t at memory location 0x0201e420..
First-chance exception at 0x7464b9bc in MassEffect3.exe: Microsoft C++ exception: wchar_t at memory location 0x0201bd7c..
########### Finished persistent loading entrymenu: 2.176967 seconds

Modifié par BioSpirit, 15 avril 2012 - 08:14 .