Bug 5017 - 'netchan queue is not proberly initialized in SV_Netchan_TransmitNextFragment' bug
Status: RESOLVED WORKSFORME
Alias: None
Product: ioquake3
Classification: Unclassified
Component: Misc
Version: 1.36
Hardware: PC Windows Vista
: P3 major
Assignee: Zachary J. Slater
QA Contact: ioquake3 bugzilla mailing list
URL:
Depends on:
Blocks:
 
Reported: 2011-05-26 04:57 EDT by yasir
Modified: 2011-06-21 10:20:38 EDT
2 users (show)

See Also:


Description yasir 2011-05-26 04:57:34 EDT 
Project: ioquake3.org
Version: SVN (don't know the number. But, I synched it today.)
Platform: Windows Vista
Bug: 'netchan queue is not proberly initialized in SV_Netchan_TransmitNextFragment'
1. I downloaded the source from ioquake3.org.
2. Updated the source code using TortoiseSVN.
3. Used Visual Studio 2008 Pro Ed to compile the Game.
4. Create a XXX.cfg file:
sv_maxclients 32
map q3dm1
addbot XXX (this line was written 24 times)
.
.
5. Used a batch file to launch the Game:
ioquake3.exe +exec XXX.cfg
6. Double-clicked the batch file.

The Game launches, the faces of the bots appears, then the camera goes into the map as if the Game is about to start. Then, it crashes with:
'netchan queue is not proberly initialized in SV_Netchan_TransmitNextFragment' on screen.

I hope it helped,
Yasir
Comment 1 Thilo Schulz 2011-05-26 06:39:30 EDT 
Please try to find out which SVN version introduced that bug.
Comment 2 yasir 2011-05-26 10:25:13 EDT 
(In reply to comment #1)
> Please try to find out which SVN version introduced that bug.

I wasn't sure what SVN version was. But, after some googling, I reinstalled TortoiseSVN, and did a Checkout. At the end of the Checkout, it said "Completed At revision 2000".
If that isn't what you meant, could you kindly tell me what I should look for instead?
Comment 3 yasir 2011-05-26 10:44:17 EDT 
(In reply to comment #1)
> Please try to find out which SVN version introduced that bug.

Just in case, this installer version is TortoiseSVN-1.6.15.21042-x64-svn-1.6.16.
Comment 4 Thilo Schulz 2011-05-27 05:49:46 EDT 
Yes, that revision number. I want you to downgrade to older revisions, you can do that using Tortoise SVN, I'm sure you'll figure out how. Compile those, and find out which svn revision introduced this bug.
Start off with something like 1900, if it works, try 1950 if it doesnt work try 1925 and so on. That's called "bisecting" .. and generally helps pinpoint the error. I don't have an MSVC build environment on me right now, that's why I need some help tracking this down.
Comment 5 yasir 2011-05-30 04:31:17 EDT 
(In reply to comment #4)
> Yes, that revision number. I want you to downgrade to older revisions, you can
> do that using Tortoise SVN, I'm sure you'll figure out how. Compile those, and
> find out which svn revision introduced this bug.
> Start off with something like 1900, if it works, try 1950 if it doesnt work try
> 1925 and so on. That's called "bisecting" .. and generally helps pinpoint the
> error. I don't have an MSVC build environment on me right now, that's why I
> need some help tracking this down.

I downgraded to several times all the way to 1800. But, none worked. I searched the net for any reports and found this:
http://icculus.org/pipermail/quake3-bugzilla/2009-September/001213.html

It said that in 1596 it was fixed. I used that one, and still didn't work.
Then, I found this:
https://bugzilla.icculus.org/show_bug.cgi?id=3418

I tried out the fix myself. And, it worked.
What I want to say is that it seems the fix to this bug isn't included in any of the revisions.
Comment 6 Thilo Schulz 2011-06-21 10:16:28 EDT 
I'm sorry, I cannot reproduce this bug. I compiled under Visual Studio 2010. Also, the fix suggested by Timbo IS in current SVN.
Comment 7 Tim Angus 2011-06-21 10:20:38 EDT 
That wasn't actually my suggestion in bug #3418; I just C&Ped an email from the list into the bug report.