search

sampad1370 / lidgren-network-gen3

Automatically exported from code.google.com/p/lidgren-network-gen3
0 stars 0 forks source link

Messages being read with no output #157

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. NetServer.Start()
2. Read Debug, Error, Warning, and VerboseDebug
3. Output the above messages

What is the expected output? What do you see instead?
Socket bound to x.x.x.x:port true/false.
Network thread started.

What version of the product are you using? On what operating system?
5/07/2013, gen3, Win8

Please provide any additional information below.
In past version messages will be sent detailing the startup of the NetServer 
and Client.  In the version listed above this does not happen.  This applies to 
all message types, including Data, StatusChange, etc.

Original issue reported on code.google.com by rcg2...@moc.edu on 19 Oct 2013 at 7:13

GoogleCodeExporter commented 9 years ago 
Are you building Release? These messages only appear in Debug builds

Original comment by lidg...@gmail.com on 13 Jan 2014 at 8:07

GoogleCodeExporter commented 9 years ago

Original comment by lidg...@gmail.com on 23 Jan 2014 at 9:34

GoogleCodeExporter commented 9 years ago 
Yes, I built for release.  A prior revision still showed these messages in both 
release and debug.  I'd prefer to have the option of whether or not to showing 
Debug, VerboseDebug, and Warning messages in both build types.

Original comment by rcg2...@moc.edu on 24 Jan 2014 at 7:45

GoogleCodeExporter commented 9 years ago 
For performance reasons; Debug and Verbose message aren't generated in Release. 
You can easily make local changes tho - just remove [Conditional("DEBUG")] from 
LogDebug in NetPeer.Logging.cs

Original comment by lidg...@gmail.com on 24 Jan 2014 at 7:59