It is possible (and very easy) to go up and down ladders completely silently without crouching whilst moving up/down them

To do this you must move up the ladder absolutely dead on straight.



You can do so by using the side of the ladder as a wall to guide you straight up, or by simply aiming perfectly perpendicular to the ladder as you walk up.

If you have any slight sideways/diagonal movement on the ladder it will make the normal sounds.

Tested and confimed in both nuke and train with Redstar.

Knife Hit Detection
Since we were all excited for the new knifing animations we had quite a few rounds of knife fights, but the hit detection for knifing is too narrow. In other words, the cone of attack is extremely thin. It needs to be made into more of a melee style swipe, like cs1.x =)

Spectator Mode Bugs
Lets face it, a good deal of time playing CS is spent in First Person Spec.

In CSP theres some missing features:

1) Weapon Models have detached muzzle flashes.
2) No weapons show their View Punch (POV) Animations.
3) The reason I listed this in exploits is the lack of flashes in spec could be used to give additional info to remaining teammates over vent.

Proper Weapon Switching Speed
Weapon switching comparison:

UPDATE: It is possible to fire 4-5 bullets from the m4a1 in 1.6 before CSP can fire one.

For this test I timed the delay* between the moment you switch and the moment you can start firing in both CS 1.6 and CSPromod 1.04b. I tested all the weapons and I concluded that this delay is the same for all the weapons and combinations possible in CS 1.6
In CSPromod 1.04b, the Galil is the only weapon which fires quicker than all the other ones, it shouldn't.

Here are the results of my testing:

Counter-Strike 1.6

-delay*: 0.69/x/0.71 (in seconds) delay= 0.70 seconds

CSPromod 1.04b

-delay*: 0.98/x/1.02 (in seconds) delay= 1.0 seconds

__________________________________________________ _______________________________

Difference : 0.30 seconds

Once again this difference is significant in-game and must be tweaked.

Hi,
I did a lot of timing comparisons between CSP 1.04b and cs 1.6 weapons rate of fire (ROF)

Here are the results:

___________________________________________CSPromo d BETA 1.04

CSP ak47 rate of fire ( 30 bullets )

3.05
3.07
3.05
2.98
3.05
3.05
3.05
2.98
3.00
3.05
Result: 3.05 seconds

____________________________________________Counte r-Strike 1.6

CS 1.6 ak47 rate of fire ( 30 bullets )

2.85
2.85
2.90
2.90
2.90
2.87
2.90
2.90
2.85
2.90
Result: 2.90 seconds

Conclusion: Difference between 1.6 and csp: 0.15 seconds


___________________________________________CSPromo d BETA 1.04

CSP famas burst fire mode rate of fire ( 25 bullets )

5.50
5.46
5.46
5.51
5.50
5.51
5.50
5.50
5.50
5.50
Result: 5.50 seconds

____________________________________________Counte r-Strike 1.6

CS 1.6 famas burst fire mode rate of fire ( 25 bullets )

4.54
4.51
4.50
4.50
4.51
4.50
4.50
4.50
4.50
4.50
Result: 4.50 seconds

Conclusion: Difference between 1.6 and csp: 1.00 second


___________________________________________CSPromo d BETA 1.04

CSP knifing rate of fire for 10 hits (left click)

3.85
3.79
3.81
3.81
3.81
3.81
3.79
3.81
3.81
3.81
Result: 3.81 seconds

____________________________________________Counte r-Strike 1.6

CS 1.6 knifing rate of fire for 10 hits (left click)

3.42
3.39
3.40
3.42
3.40
3.37
3.40
3.42
3.40
3.39
3.43
3.42
3.42
3.40
3.40
Result: 3.40 seconds

Conclusion: Difference between 1.6 and csp: 0.41 second

Thanks for reading, those values are really important!

Anyway I have now tweaked every listed weapon to the max, any further differences are CPU/tickrate related.

When you throw a nade there's a delay between the moment you click on your mouse and the moment the nade is thrown*. I think you noticed that this delay (in csp 1.04) is a little bit too long in comparison of its behaviour in CS 1.6 , and it really affects the gameplay .

I did some testing, here are the results:

I timed the delay between the moment I clicked on my mouse (without keeping the button pressed) and the moment the nade was thrown.

Counter-Strike 1.6

-delay*: 0.48/x/0.52 (in seconds) delay= 0.50 seconds

CSPromod 1.04b

-delay*: 0.75/x/0.80 (in seconds) delay= 0.77 seconds

Difference : 0.27 seconds.

__________________________________________________ ___________________

After that, I threw the 4 nades one after the other:

Counter-Strike 1.6

Total time: 6.13 seconds

CSPromod 1.04b

Total time: 7.40 seconds

Difference: 1.27 seconds

As you can see there's a difference and it is significant in-game, that's why I think it should definitely be tweaked!

Weapon/Bomb Dropping or Passing
Is there anything that can be done about the Velocity/Speed/Strength with which weapons are dropped? Passing weapons to other players is impossible as of now.

In 1.6 you look at your own feet for a huge boost in distance. The amount of distance is inversely related to the amount of downward view angle. Although this may seem to not make sense, in buy freezetime in 1.6 you cannot jump or move, so its a perfect way to make long distance tosses of the bomb or weapons. Its a skill players must develop and gives the game added depth.

In CS:S the only way to make long distance tosses is by looking at the sky and making a running jump at the same time. Then the players momentum is applied to his jumping toss, but in CS:S you can't move in freezetime. So his mechanic is totally stupid and not well thought out, although in theory it seems to make more sense when you consider the physics involved and maybe realism.

In CSP we can jump in place during freezetime, so, in my opinion there's essentially two options here.

Treat weapon tossing the same as 1.6 with the downward via angle increasing velocity, or perhaps make it where the more of the sky you look at the greater the velocity and higher angle trajectory, but when I say that I mean the ability to actually reach far off spawns with it.

Either way the CS:S mechanic will not work, because a stationary player needs a way to toss his weapon or the bomb to far off spawned teammates for competitive play.

Lastly, the animations don't scale well above 60FPS at all. On my CRT I play @150hz/150fps and those weapon toss animations look like a flip book, even if I lower both to 101. With Vsync on they seem a bit smoother to me, but others have said they aren't noticing any difference.

* First off credits to:

d0ublethink (concept)
kc- (for testing-ish)
Majikk (My friend that did the 'nading while I recorded the data)
Maceman (Also helped with the 'nading)

What happened: I made a grenade testing map (small preview in image header) to test the maximum blast radius damages, and the damages of each. It's up to you devs or smart people to find out a mathematical function to apply this to the game :]

About the map: The map (for 1.6) consisted of markings on the floor in increments of 10 game units. Large bars represented 100 units. Grenades are placed throughout the map with functional buy zones and respawning health packs.

-------------------------------

Max Radius: 325 Units

The Information: NO ARMOR



0 Units (Direct) - 97 Damage
50 Units - 77 Damage
100 Units - 65 Damage
150 Units - 50 Damage
200 Units - 38 Damage
250 Units - 11 Damage
300 Units - 8 Damage
325 Units - 1 Damage

The Information: WITH ARMOR



0 Units (Direct) - 48 Damage, 25 Armor Damage
50 Units - 38 Damage, 20 Armor Damage
100 Units - 32 Damage, 17 Armor Damage
150 Units - 23 Damage, 12 Armor Damage
200 Units - 18 Damage, 10 Armor Damage
250 Units - 10 Damage, 6 Armor Damage
300 Units - 4 Damage, 3 Armor Damage
325 Units - 0 Damage, 1 Armor Damage

Same results with HEAD ARMOR as with just ARMOR.

-------------------------------