ValveSoftware / source-sdk-2013

The 2013 edition of the Source SDK
https://developer.valvesoftware.com/wiki/SDK2013_GettingStarted
Other
3.77k stars 2k forks source link

Console prints messages out of order with Multicore Rendering enabled #57

Closed essbuh closed 11 years ago

essbuh commented 11 years ago

With Multicore Rendering enabled, the console can occasionally print messages out of order.

For example:

] find client "cl_ent_absbox" "cl_ent_bbox" client client cheat cheat

  • Displays the client's absbox for the entity under the crosshair.
  • Displays the client's bounding box for the entity under the crosshair. "cl_ent_rbox" client cheat
  • Displays the client's render box for the entity under the crosshair.
  • Find and list all client entities with classnames that contain the specified substring. Format: cl_find_ent

"cl_find_ent" "cl_find_ent_index" client client cheat cheat

  • Display data for clientside entity matching specified index. Format: cl_find_ent_index

] status hostname: Half-Life 2 Deathmatch version : 1.0.7.0/24 5337 insecure udp/ip : 192.168.1.5:27015 (public ip: X.X.X.X) map : nmo_broadway at: 682 x, -396 y, 137 z

4 "essbuh" (...) 05:23 14 0 active loopback

players : 1 (16 max)

userid name uniqueid connected ping loss state adr

] status hostname: Half-Life 2 Deathmatch version : 1.0.7.0/24 5337 insecure udp/ip : 192.168.1.5:27015 (public ip: X.X.X.X) map : nmo_broadway at: 682 x, -396 y, 137 z players : 1 (16 max)

4 "essbuh" (...) 05:24 14 0 active loopback

userid name uniqueid connected ping loss state adr

This does not seem to happen with multicore rendering disabled.

AnAkkk commented 11 years ago

Shouldn't this be posted in Source-1-Games instead? I've reported this issue back in 2009 and it was only fixed in L4D/L4D2. This is what I've been told for OB engine:

I'm looking at it.  It isn't an easy fix - the code that fixed it wasn't a bug fix for this but a rewrite of some low level logging systems.  I'll see if there is something simpler we can do to address it but we can't use the l4d code.
saul commented 11 years ago

I think it'd get more attention here Anakin, it's pretty ridiculous that the console managed to get this broken in the first place.

Worst case scenario, multi-threading should be removed from the logging system as it's clearly broken.

JoeLudwig commented 11 years ago

Unfortunately this is still beyond the scope of what we're fixing in the Orange Box codebase.