pwnSource is where players and developers come together
This website is updated regularly. Features here are under construction and will constantly be improving.
Please share your Feedback with us and the Community, or you can Contact Us privately
Counter-Strike: Global Offensive
New Interp Bug should be removed
Ticket Status Category Type Severity Version Created
1236 Closed Achievements and Stats Defect Poor Experience 2013-02-11 05:34:01
Ticket Priority
  • 52
  • 0
  • 1

Written By jope 3097 Hits Last Updated 2013-10-02 01:11:22

Steps to Reproduce the Problem:

New CS:GO Interp bug after the old one was fixed.

1. If you write cl_updaterate +128 and cl_cmdrate +128 in your config or console you will have new interp bug.

Expected or Desired Behavior:

If you use the two commands you will be able to play with that interp bug.
You make headshots while you are not shooting on the head hitbox. You will have a ping of (1) on league servers. But it is also possible to set the ping with that interp bug that nobody will be able to see the difference and you ping stay normal.

If anybody want to see it just watch my short clip on youtube i made last night:

Additional Relevant Information that could be helpful to address this issue:

i really hoped it will be fixed soon by valve with a new update and people will not be able to play in leagues with that bug too.
As example:

Thanks for listen.

If anybody want to post it on steamforums just give me a credit.

best regards,


you moderate pwnSource tickets

The Community maintains the accuracy and quality of ticket information.
Please update tickets as things change, keep pwnSource up to date and organized!

DISCUSSION: debate game mechanics, balance, etc.

QUESTION & ANSWER HELP EXCHANGE: ask great questions, get great answers

FEATURE REQUESTS: propose your own ideas and solutions

DEFECT REPORT: alert developers of specific issues

OPEN: this is the default status when a ticket is created

IN PROGRESS: when Developers acknlowedge the issue, or power users propose solutions

VERIFYING: a solution has been found, and needs to be confirmed by other users

CLOSED: the ticket has reached its end of life

DUPLICATE: there is a better written version of this ticket

UNCLEAR: this ticket has insufficient detail

LOW, WISHLIST Tickets do not impact the gameplay directly

POOR EXPERIENCE Tickets are used to describe the quality of the gameplay

BLOCKS GAMEPLAY Tickets describe conditions that render the game unplayable

Ticket Changes
Comment Popularity, Appreciation, and Reputation
User Appreciation and Reputation
    • 1
    • 0
    • 0
      • micronn
      • 41
      • 0
    Ahh, thats why I can't kill people in proper head because they are playing all with +128 without a strange ping in scoreboard.

    It needs to be fixed in Wednesday!
    • 1
    • 0
    • 0
      • cs_c0de
      • 121
      • 0
    I have run in to this exact bug a few times here recently and it makes it very hard to play against.

    I would think that it should be fairly easy to set certain variables to only accept numerical values.

    Besides, if most of these netcode settings are smart enough to auto-adjust themselves to the correct values as long as the max value is entered, then there seems to me to be no reason for these variables to be changed by the end user.

    Maybe one solution is to lock off these variables (cl_updaterate and cl_cmdrate) and set them to a max value of 128.
    • 0
    • 0
    • 0
      • aikanaro
      • 2
      • 1
    It's easy to tell who uses +128 rates because their ping on the server (only in tablescore) is 1 or 5. After checking ping in console u will get his real ping to the server and if it's not 10m or less then he is using +128 rates.
    • 1
    • 0
    • 0
      • enro-griffins-del1ve
      • 0
      • 0

    pls push the steam thread!
    • 0
    • 0
    • 0
      • deepii
      • 48
      • 10
    Update 2/13/13:
    * Fixed an interpolation exploit with bogus update rates.