jan 17 update discussion

I was simply interested in seeing some discussion of the Jan. 17 source and CS:S updates.

I love de_tides for one thing. I'm really thankful for a tight
map. I'm sure noobs in the hallways will suck getting in the way,
but I believe there's a lot of good times potential in a map that is
amazing to look at in any case. CTs may have the advantage here,
though I'm unsure of that.

I've noticed there's still plenty of bull in terms of shots
registering. There seems to be even -more- cases of aim being
true but not getting a single hit on someone. Yet sometimes it
seems fine. I really felt the December 15 update changed things
for the better and the worse, and this update may have too. On
two occasions I watched myself die -before- the enemy fired his
gun. Now I know that's just a disparity in what the server is
telling my client or how my client rendered the sequence of play, but I
think it's bad form for CS:S at any rate. I'm sure the attacker
experienced the shot being fired before seeing me die.. because
he said so after I said something about it.

de_prodigy still drops to jerky framerate (on my Athlon 64 1.5GB RAM
Nvidia 6800 GT) in the bomb room. I don't think it would be like
that if Prodigy had been released before the changes made Dec. 15, as
there are other times when I drop frames now and never had
before. I was hoping this would get fixed. BTW, turned all
the graphics options low or off doesn't help. It's so crazy stuff
in the Dec. 15 update that I'm not such a great fan of. Any other
nvidia users experiencing this?

I don't have any experience with the CS:S bot..

What do you mad mappers think of de_tides? Will you do a full mappers critique for me?

Cheers