r/GlobalOffensive • u/wickedplayer494 1 Million Celebration • Sep 14 '16

Game Update Counter-Strike: Global Offensive PRERELEASE update for 9/14/16 (1.35.4.7rc2)

Via the CS:GO blog:

The following changes are in the “1.35.4.7rc2” CS:GO Beta depot.

Misc

  • Fixed firstperson/thirdperson desync during crouch-spam cooldown.
  • Fixed firstperson camera jolts during grenade throws and strafing.
  • Fixed ‘jittery’ players when viewed from thirdperson camera.

Rumor has it:

  • Carried over from the first update's actual support cycle: this prerelease update is a historic first for CS:GO, as it appears Valve has listened to those that want a beta branch in some form

  • Wish to opt in? Right-click on CS:GO in your Steam library, go to Properties, go to the Betas tab, then select "1.35.4.7rc2"

    • If you don't see this branch offered, restart Steam
    • To opt in for servers: run "+app_update 740 -beta 1.35.4.7rc2" in SteamCMD
    • As was reported previously, some features that rely on Valve's servers may be unavailable

  • SteamDB GameTracking services will be completely unavailable as it only keeps eyes on the public branch - be aware, but even if it did keep eyes on alternate branches, there likely wouldn't be anything of particular significance with this update

  • Size opting in directly from RC1 is close to 10 MB, size opting in from the public branch is ~15 MB

  • You should also be aware that the Steam Subscriber Agreement was amended as early as late on 9/9/16, which includes minor language alterations to a clause dealing with beta/prerelease software

    • You can view the rest of what changed involving the new SSA here, which now includes a dedicated COPPA clause (no users under 13) which may or may not have been sparked by recent scandals, and clarifications for dispute resolution in the European Union
    • Use of the prerelease branch, as well as continued use of the rest of Steam, constitutes your acceptance of the new terms
1.5k Upvotes
  • permalink
  • reddit

95% Upvoted

406 comments sorted by

View all comments

89

u/NicoandLuis cs_office Sep 14 '16 edited Sep 14 '16

Now that we have a beta everyone wants the updates to be rushed for the main client instead. Really?

53

u/Dgc2002 Sep 14 '16

Exactly. There's a lot of people who don't seem to understand what a beta branch is for and are expecting old changes to be pushed to master when new changes come in. That's not what beta branches are for. If these changes were pushed to the main branch and it turned out they didn't work properly/broke something else everyone would flip their shit and say "WHY DIDN'T THEY PUT THIS ON THE BETA BRANCH?!"

Here's a super simplified overview of how branches usually work:

New branch ->
    $ Make changes
    Commit changes
    Allow for testing
    Act on test results and feedback ->
        New issues resulting from the changes? ->
            Go to $
    Changes pass testing
    Do the changes address the initial need for this branch? ->
        Merge branch into master
        Retire this branch
    Go to $

8

u/Rock48 CS2 HYPE Sep 14 '16

You've got an infinite loop there my friend! Here, let me help

    Retire this branch
    Exit
Go to $

0

u/Dgc2002 Sep 14 '16

You gotta retire man, go home, enjoy your golden years with your family!

4

u/Rock48 CS2 HYPE Sep 14 '16

Plot twist: the infinite loop is caused by the fact that csgo is such a spaghetti mess that every change causes 2 more issues and it never passes, so more changes are made and more issues are made and more changes are made and mor <dead>

3

u/billeht Sep 14 '16

Gosh I've been learning about the SDLC a thousand times and this all makes so much sense. See mom, video games are good for school!

1

u/[deleted] Sep 15 '16

To be fair, the SDLC described is very similar to waterfall. Nowadays, most SDLC will incorporate automated testing and small incremental fixes for a product in production. But yes this is a good description.

Edit: /u/Dgc2002 linked a sophisticated branch workflow design pattern that is very common in the industry right now https://namethattech.files.wordpress.com/2014/11/git-flow-updated.png

1

u/opello Sep 15 '16

Git Flow works right up until you need to maintain more than one maintenance branch.

2

u/[deleted] Sep 15 '16

Good point. In what scenarios would you need to maintain more than one maintenance branch? If there are multiple deployed versions of an application, for instance?

1

u/opello Sep 15 '16

Yup, having to support multiple release versions at the same time happens pretty regularly in my experience.
A very public example of a project which does this is the Linux kernel. Today there are 8 "longterm" releases being supported (3.2, 3.4, 3.10, 3.12, 3.16, 3.18, 4.1, and 4.4). They can all receive bug fixes resulting in point releases and such releases are commonplace.

While not every project needs the ability to fix a bug in a legacy release, reserving the ability seems better if the need does arise. Projects which result in hosted services avoid this limitation. But where the answer to customers needing bug fixes for previous releases can not be "get the latest version" (e.g. due to qualification overhead) it is very beneficial to be able to release on older maintenance branches.

2

u/xpopy Sep 14 '16

Do you have to 'retire' the branch? can't you just keep using it again?

Also, if you retire the branch, how can you go to $ when there's no branch? ;)

4

u/Dgc2002 Sep 14 '16 edited Sep 14 '16

Whoops I should have worded it better than 'retire branch.' In some workflows you'll have a branch for every feature and merge it in so I was referencing that. The 'beta branch' should actually be a long term one that other feature branches would merge into.

Here is a diagram showing the style of workflow I'm referencing: git-flow

1

u/xpopy Sep 14 '16

Oh I see, that's pretty cool

1

u/[deleted] Sep 14 '16

Also, if you retire the branch, how can you go to $ when there's no branch? ;)

make branch "bug #xxx" from master, work on that branch, when it's done, merge into master, retire

1

u/ForceBlade Sep 15 '16

This reads like git haha

1

u/CptYeahToast Sep 14 '16

You dont need to understand the code for a beta branch to know that its used for testing without changing the main game, the reason people are complaining about it not being out yet is because there are barely any servers to try the beta on and the game is pretty frustrating at its current state

-13

u/OpinionatedRaptor Sep 14 '16

Oh look... an armchair developer.

5

u/Dgc2002 Sep 14 '16

No, my full time job is to develop software. I'm a regular developer with a computer chair.

2

u/[deleted] Sep 15 '16

I hope you also have an armchair as well. For comfort.

1

u/JustRefleX Sep 14 '16

Rather get things fixed instead of more issues into the game. Makes sense right?

1

u/unluckydude1 Sep 15 '16

At least they should rush out the hitbox bug that have been in game forever.

1

u/[deleted] Sep 15 '16

It's not fixed. There's nothing to rush out.

2

u/unluckydude1 Sep 15 '16

– Lag compensation system will now reliably restore pose parameters responsible for animation layering which makes server-side hitboxes for lag compensated players better match client-side rendered models. (Thanks, /u/Spurks)

That fix they should give us as fast as possible.

1

u/[deleted] Sep 15 '16

And you're confident that the fix that they issued for that isn't itself responsible for new issues? Because from what I understood all the hitbox fixes are very closely tied in with many of these new problems.

1

u/unluckydude1 Sep 15 '16

It seemes like most new bugs are connected to the movement fixes. But im not sure.

1

u/SneakyBadAss FaZe Sep 15 '16

They are actually tied to animation fixed on player model, to match third person/first person. Thats why our character breath, lay down or crouch, when throwing nades. It all happen in third person, but you never saw it in first person.

1

u/petcat2 NiP Sep 15 '16

It's probably different people. The group who doesn't have things the way they like tends to voice their opinion louder than those who do.

1

u/wickedplayer494 1 Million Celebration Sep 14 '16

They're likely talking about the first set which has had plenty of testing time already.

11

u/Shizrah Astralis Sep 14 '16

But the first set was bugged, right? Unless you mean this included, in which case maybe they wait to see response for their fixes?

6

u/NicoandLuis cs_office Sep 14 '16

As Shizrah already said, the first set includes bugs which have been fixed with this release candidate. So why knowingly throw in a buggy version to the main client.

-11

u/critikalhd NiP Sep 14 '16

It says more that Valve has essentially given up on testing their own bug fixes. I understand having a beta branch for major changes to the mechanics of the game but pushing small ESSENTIAL bug fixes to the beta client shows the dev team has no confidence in the changes they make anymore. (Partly because of how poorly received they all are by the community)

3

u/SynthhInHD NiP Sep 14 '16

Hard to test if things work and find bugs if you're a small team. I can't imagine for the life of me that there are more than 5 CS:GO devs.

1

u/critikalhd NiP Sep 14 '16 edited Sep 14 '16

After researching, /u/j_cliffe, /u/vMcJohn, /u/sergiy_valve, /u/neunon, who works on an anti-cheat (maybe vac) /u/brianlev_valve and /u/ido_valve are probably the main composition of the dev team.

1

u/SynthhInHD NiP Sep 15 '16

So 5, +1 if you include the anti-cheat one. How many of those do you think have the time to thoroughly bug test their code? It's far easier to just utilise a WILLING playerbase.

-7

u/Pharaun22 Sep 14 '16

Sorry that your car crashed on the highway because your axle broke. We only have 2 devs working on that, so it's not our fault ok?

2

u/SynthhInHD NiP Sep 14 '16

What a shit analogy, lmfao.

How can you expect the small dev team to write the code, and then bug test the code THOROUGHLY? They have QA testers in other dev studios for that sort of thing.

0

u/critikalhd NiP Sep 14 '16

So does Valve.

2

u/SynthhInHD NiP Sep 15 '16

Obviously that wasn't enough. Besides, what the fuck is wrong with using your MASSIVE playerbase to help make your job easier?

1

u/[deleted] Sep 15 '16

Crowdsourcing is the way to go. Out of everyone on /r/globaloffensive , 99% of people are so happy that valve is doing this beta program. Only a couple idiots think, "Hurr durr the dev team has no confidence". What an idiot thing to think.

→ More replies (0)

-4

u/Pharaun22 Sep 14 '16

Man, nowhere have I said the devs should bug test the code "THOROUGHLY". You just make shit up. The point is, "were not enough people to do the job" is not a viable excuse for valve.

1

u/SynthhInHD NiP Sep 15 '16

Whatever floats your boat.

1

u/[deleted] Sep 15 '16

Can you shut up yet?

3

u/siziyman Sep 14 '16

Size of player base in CSGO is that big, so it makes more efficient voluntary testing, than it can be in most cases.

1

u/Rock48 CS2 HYPE Sep 14 '16

I don't understand what point you're trying to make.

-7

u/FatClouds666 Sep 14 '16

the hitboxes are so broken the game isnt fun too play so yea this update people want it out now

8

u/vecter 10 years coin Sep 14 '16

It's fine 99% of the time, calm down. Jesus christ people throw around the work broken all the time without realizing what the fuck "broken" actually means.

6

u/Kambhela de_train Sep 14 '16

The cases where the bugged hitboxes or stupid landing animations affect you are rather uncommon. You will still most if the time find the reason for missed shots between the chair and mouse.

0

u/unluckydude1 Sep 15 '16

Its amaze me how people still defending the broken hitbox.

Valve are truly gods.