Another Developer Chat Thursday Feb. 16th at 19:00 GMT

Started by beta_helix

beta_helix Staff Lv 1

Today's Developer Chat focused mostly on current issues with the client, you can read the transcript from the chat here: http://fold.it/portal/chats , so we will have another Developer Chat next Thursday at 11am PDT (19:00 GMT).

If you cannot make it to the chat at that time, please post your questions in the comments to this news post and we will address all of them during the next chat.

Today the Foldit team went through many of the highly-voted feedbacks and hopefully they will be resolved soon (as soon as we solve the client problems). If you would like to help us diagnose exactly what is wrong with the current clients, please join the Contest we have created for this: http://fold.it/portal/node/991787#comment-15649 .

Thank you for your patience and we hope to be able to talk to most of you next Thursday (especially those of you who were in distant time zones).

spmm Lv 1

First thanks for taking the time to chat to us all.

May I suggest that, as we as players are unable to estimate the effort involved in any one 'fix', or the impact it may have, we could take an approach of prioritising fixes in batches leading up to CASP.

It is also difficult for us to estimate the effort involved in transferring fixes from alpha to beta to main.

It seems to be(?) problematic to do smaller more frequent iterative fixes, say one a month if necessary, for example fast track tutorial and high priority bug fixes, which may have a high impact on new folders (and the rest of us in trying to help out in chat) and we tend to have updates which are a very big mixed bag, often with associated complex issues which do not emerge immediately.

So a suggested priority order to set us up for CASP would be:

1 scoring/rebuild problems insofar as possible.

2 - tutorial, housekeeping, and language issues fast track any remaining which can be dealt with in a sprint so newcomers and people without English as a first language can play.

1 and 2 could be swapped depending on the degree of difficultly of 1

3 - Cookbook, tools (reset defaults) and other display issues that can be fixed in a Cookbook, tools and game display sprint, some of these may be in the fix mix already but these issues really do have a big impact on folders.

4 - Lua and other script issues - not new requests, just clearing any bug backlog so we have happy coders and reliable scripts.

I would think that those items, just doing fixes, and any overwhelmingly supported enhancements that can fit in the appropriate batch, will take us up to April-May, ie three or four sprints plus time to load and test through beta and main.

The advantage in doing the code fixes last is that the coders will be able to confidently work with the preceeding fixes and prepare detailed requirements for any remaining issues.

Anything not fitting into these groups would not get tackled before CASP unless there is a separate resource available to atttend to it, in particular doing anything which is not directly beneficial at the CASP foldface.

Cheers spmm

Wildcat777 Lv 1

Steps how to get the error:

1.Join to Contest "Freestyle Design 40"
2.Check if CI=1
3.Change the 40 loop segments to helix
4.Start Tweak / Straighten out Structure
5.Stay as long on the Straighten out Structure Button (ball) until you reach score = -999999.999
6.You see the result in the first picture down
7.Stay now as long until the helix get fine
8.You see the result in the second picture down

My opinion is:

There is any plus/minus problem (+x/-x or +y/-y or +z/-z) or any problem with a plan orientation (triangle={a,b,c} or triangle={a,c,b} variable b and c are mixed)

It seemes like the helix has to go through a mirrored plan to get nice.

Good luck to fix this error
Peter