No Such Frame: Sprite 1-2-3

WitherWither A Bugged Life Join Date: 2002-12-24 Member: 11513Members, NS1 Playtester, Contributor, Constellation
in Tech Support
<div class="IPBDescription">Read? :)</div> About 30% of the times I join a server and open my console just as I join, I get about 5000 lines that say

"No such frame: Sprite 1"

Up to sprite 2 and sprite 3, I have *no* clue what it means but it lags me and my choke goes up like mad, I searched the tech support forum on no such frame and on frame, but I didn't find anything.

Can anyone help me out? I tried reinstalling.. <!--emo&:angry:--><img src='http://www.unknownworlds.com/forums/html/emoticons/mad.gif' border='0' style='vertical-align:middle' alt='mad.gif'><!--endemo-->

Thanks.
Off Topic Disagree Agree Awesome

Comments

  • FlayraFlayra Game Director, Unknown Worlds Entertainment San Francisco Join Date: 2002-01-22 Member: 3Super Administrators, NS2 Developer, Subnautica Developer
    This is a harmless error, so don't worry about it while we fix it.
    Off Topic Disagree Agree Awesome
  • wrongwaygobackwrongwaygoback Join Date: 2003-03-02 Member: 14237Members
    Will this be fixed soon, as it makes the game (at least for me) unplayable?
    Off Topic Disagree Agree Awesome
  • KaMiKaZe1KaMiKaZe1 Join Date: 2002-11-18 Member: 9196Members
    I get this as well, but I've never seen it affect gameplay in any way. Is your choke high only when this occurs, or is your choke always high? If it's always high, read the following snippet from <a href='http://rentals.nuclearfallout.net/rent.php?content=faq-lag' target='_blank'>http://rentals.nuclearfallout.net/rent.php...content=faq-lag</a>. It should fix any problems you are having with choke and unexplainable lag.

    <!--QuoteBegin--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->
    There are three main settings to look at on the client-side. These are rate, cl_updaterate, and cl_cmdrate.

    rate determines the speed, in bytes per second, that your client allows itself and the server to interact at. This setting is needed because your client has no idea how fast your connection is, and it doesn't know how to find out. The rate setting tells it the maximum speed at which it can transfer data. If it is set too high, your connection may not be able to handle it, and you will get packetloss; if it is set too low, choke and latency will increase, possibly making your game stutter or lag. Half-life is generally able to compensate for choke fairly well, as long as there is not much of it; however, when choke gets too high (over 100), it has to start dropping packets (and we all know how bad packetloss is!). I recommend a rate of 8000 or 10000, since most broadband connections can easily handle it (try 10000 first).

    cl_updaterate determines how many updates per second the client will accept when it is interacting with the server. A higher value can make gameplay more smooth, although it often makes your ping appear higher due to the added latencies on both ends from extra calculations involved. I recommend a cl_updaterate of 40, which I have found balances ping and smoothness fairly well. Feel free to try higher and lower values. A value too high can cause choke if your machine or your connection can't handle all the packets!

    cl_cmdrate relates to how many commands your client sends to the server per second. I usually recommend that users set their cl_cmdrate cvar to the same value as cl_updaterate. <!--QuoteEnd--></td></tr></table><span class='postcolor'><!--QuoteEEnd-->
    Off Topic Disagree Agree Awesome
Sign In or Register to comment.