3 Commando Brigade

Rainbow six siege

Anyone got it, thinking about getting it or used the free weekend they just did. Wondering whether to get it when the price comes down or not bother. Sounds like it's best in a team and we all know how randomers online play!


Sent from my iPhone using Tapatalk

Looks terrible to me. No proper planning stage, and gimmicky gadgets. Won't be a patch on the originals

Well I've not played any of the others so no expectations there. Wasn't gonna take it to seriously. Along with that I won't buy it at its current price more thinking is buy it if it came down in price.


Sent from my iPhone using Tapatalk

Is it likely to go on sale?


Sent from my iPhone using Tapatalk

25% and it still is pretty much at price other games have on the release. I consider checking the game out when it has way more content as it has now, or it is around 20€.

I would never pay £50 for a game. Well, Arma I would but I know how much value for money I get there.

RB6 Siege looks like a flash in the pan fad to me and echo others comments on price. £15-20 tops for a few piss about sessions whilst having a beer.

I played the closed beta of it, and it just looks like a quick money grab by Ubisoft. It just feels like it aimed at the younger market as it gets very repetitive very quickly.

Like Robbie said maybe a few matches whilst having a beer but not one of those games that you would play for hours.

Netcode Example:

That doesn't actually look like an issue with the netcode but an issue with the replay!

It seems like what's really happened is that the killer saw a solid hit because the victim's "hey, stop leaning" input/update hadn't yet reached him and/or the server. The server does some clever lag-compensation calculation and arrives at the correct result that the killer has successfully hit the victim. It then goes and sends the victim the "hey, fall over dead" command. This command arrives at the client sometime later at which point the player sees his character fall over dead.
There's usually a tiny bit of intentional "input lag" built into games to avoid the "hey, fall over dead" command arriving at a point where you e.g. ducked back behind cover but with bad internet connections, quick movements and a bit of 'luck' it cannot be avoided that every now and then you'll think of yourself as being safely behind cover just as your PC starts executing that "hey, fall over dead" command.

This is perfectly normal and in no way unfair -- hits are determined not by what the "victim" sees but by what the "killer" sees. (Or, because people love cheating, by what the server thinks the killer saw). Since your hits on other people are calculated the exact same way this is balanced and fair. And since the skill in most fps is in "moving a crosshair over a target" and not in "moving your body to dodge bullets", it's more important that the "attacker" view is correct than that the victim's view is correct.

The issue here seems to be that the re-play camera is showing the "wrong" view of the world. It's showing the view the victim's PC had when the kill actually happened but what it should really be showing is the view that the attacker had (or rather, the view that the server thinks the attacker had) when the kill happened. This would mean that you'd still fall over dead behind a wall but at least in the replay you'd see yourself get shot and go down as your attacker saw you get shot and go down.

Or just crappy netcode.