Bring v2.3 back to Opt-In Branch Please

[Bababooie]

To the CMs on here (I know Matthew is on at the moment so if you read this maybe you could field it) would it be possible to request that v2.3 is made available to the Opt-In branch again instead of the v2.2.1 public build?

[Matt Allen]

I'll fire a message off and see if that's possible, but no promises I'm afraid. Sometimes these things aren't as easy as they sound. :)

I'll report back once people start to show up at the office though.

[Bababooie]

Yep yep, thanks for the quick reply.

Like I said in another thread I made (about v2.3 being better than v2.2.1 :P ), there were two much appreciated fixes I approved of in v2.3, but they're gone again in this build. :/

ITERATION
*takes drink*

[vv [FuMM]]

That should be soon as it's about 8:30am in london.

[Danjal]

Originally posted by Matthew Allen:

I'll fire a message off and see if that's possible, but no promises I'm afraid. Sometimes these things aren't as easy as they sound. :)

I'll report back once people start to show up at the office though.

I'm sorry Matthew - but things actually ARE that easy.
Its called "don't overwrite existing builds but release them seperately".

Sounds like someone made a pretty big boo boo in the office by releasing and overwriting the opt-in branch with the 'public release'.
Which is rather shameful when you expect a certain degree of professionality from a games development company...
Do 22cans actually understand how the tools they're working with "work"?
Since this isn't the first time a mistake like this is made, its not strange that these acts of incompetency are being highlighted when it comes to the state of the game.


As a matter of fact, to the point where it is actually possible to retain SEVERAL backdating versions of the game up at once to be able for selection.
It should've been possible for 22cans to even have v1.3 still available in the version selection.
Now I'm not trying to be negative here - but someone messed up bigtime here.
Keeping proper backups of your older versions was the first thing I was told when I started my lessons on programming.

[Praesmeodymium]

Mission critical data should be backed up in more than 1 location on more than 1 media type...

[76561198135081759]

Hi everyone, just to let you know we've re-uploaded v2.2 (i.e. 2.3 opt-in 1) to the opt-in branch of Steam. Please be aware that playing this build may result in your existing save being lost, but I suppose that's always a risk when playing builds on the dev branch.

Hopefully that should prove to be an immediate fix for any framerate issues you've been experiencing, however we really, really do need you to send in your bug reports to {LINK REMOVED}http://Support.22cans.com so that we can track down and fix the cause of this issue.

[zayfard/TTV]

Originally posted by G.K. @ 22Cans:

Hi everyone, just to let you know we've re-uploaded v2.2 (i.e. 2.3 opt-in 1) to the opt-in branch of Steam. Please be aware that playing this build may result in your existing save being lost, but I suppose that's always a risk when playing builds on the dev branch.

Hopefully that should prove to be an immediate fix for any framerate issues you've been experiencing, however we really, really do need you to send in your bug reports to http://Support.22cans.com so that we can track down and fix the cause of this issue.

Realising, and excepting, that this is very early days for finding out but are there any initial ideas of what is causing this?

[76561198140223498]

Originally posted by zayfard:

Originally posted by G.K. @ 22Cans:

Hi everyone, just to let you know we've re-uploaded v2.2 (i.e. 2.3 opt-in 1) to the opt-in branch of Steam. Please be aware that playing this build may result in your existing save being lost, but I suppose that's always a risk when playing builds on the dev branch.

Hopefully that should prove to be an immediate fix for any framerate issues you've been experiencing, however we really, really do need you to send in your bug reports to {LINK REMOVED}http://Support.22cans.com so that we can track down and fix the cause of this issue.

Realising, and excepting, that this is very early days for finding out but are there any initial ideas of what is causing this?

Currently we're unsure and actually very surprised this issue arose for a number of reasons, firstly that both internal and external testing never reported the slightest drop of quality so we were unprepared for it to be an issue on the live version, and secondly since we had been doing some work designed to improve frame rate :P

As George said above we would hugely appreciate any additional information being submitted to support such as:

• Exact frame rates you're having to deal with
  
• Save files
  
• Verbose files
  
• And anything that comes to mind you think could be useful

Thank you again for your patience with this issue and hopefully we will have a fix out soon for the update :)

[Danjal]

Interesting... Numerous players are encountering the same issue and you haven't had it happen in-office?
You sure we have the same version you guys tested? Maybe a change got slipped in somewhere along the way or two versions got merged somehow?

Anywho, great to see that the opt-in branch is back again - perhaps try to retain a backlog of 2~3 versions in the future and have them cycle rather than just replacing the last version so that people aren't entirely boned when the game gets updated to a version with massive issues?
Looking forward to hearing about some hotfixes for issues like these!

[earl_parvisjam]

Originally posted by Danjal:

Interesting... Numerous players are encountering the same issue and you haven't had it happen in-office?
You sure we have the same version you guys tested? Maybe a change got slipped in somewhere along the way or two versions got merged somehow?

Anywho, great to see that the opt-in branch is back again - perhaps try to retain a backlog of 2~3 versions in the future and have them cycle rather than just replacing the last version so that people aren't entirely boned when the game gets updated to a version with massive issues?
Looking forward to hearing about some hotfixes for issues like these!

This makes me intensely curious just what version control they're using. I've worked with Subversion and Git. Both allow reverts to any previously pushed version. It's hard to imagine them using anything that wouldn't allow such since it's the primary purpose of revision control in the first place. Revision control doesn't ever "overwrite" anything when a push is made.

[76561198140223498]

Originally posted by Danjal:

Interesting... Numerous players are encountering the same issue and you haven't had it happen in-office?
You sure we have the same version you guys tested? Maybe a change got slipped in somewhere along the way or two versions got merged somehow?

Anywho, great to see that the opt-in branch is back again - perhaps try to retain a backlog of 2~3 versions in the future and have them cycle rather than just replacing the last version so that people aren't entirely boned when the game gets updated to a version with massive issues?
Looking forward to hearing about some hotfixes for issues like these!

I agree its incredibly bizarre, we have double checked the build numbers and confirmed it was the same build we have been testing solidly coming up to the update..i honestly have no idea why it reacted this like for the players but the team is working hard to give both you and us a better idea of why this happened :)

I'll pass on your suggestions to the relevant people but i believe we already have some notion for this being talked about, however that's not an official statement its just my personal belief from keeping an ear out and also a wish :P

Keep an eye out for the fixes since with a bit of luck they will be with you soon :)

[vv [FuMM]]

did you pass on my suggestion that they add the version numbers into the verbose file? :P

[76561198140223498]

STOP USING ME FOR YOUR PERSONAL GAIN VV! >.>

[Danjal]

Originally posted by SalmonQA22Cans:

STOP USING ME FOR YOUR PERSONAL GAIN VV! >.>

Isn't that your job here? To serve towards the betterment of this product, so that others will be assured of its quality? =P

[76561198140223498]

Originally posted by Danjal:

Originally posted by SalmonQA22Cans:

STOP USING ME FOR YOUR PERSONAL GAIN VV! >.>

Isn't that your job here? To serve towards the betterment of this product, so that others will be assured of its quality? =P

I...well you see...umm.....huh, well thats me put in my place i guess >.>