Page 1 of 1

### Viewer Generations Bug

Posted: May 15th, 2019, 5:38 pm
From Sandbox thread Polyominoes:
fluffykitty wrote:Improved to 117:

Code: Select all

``````x = 35, y = 8, rule = //6
3.2A6.B\$.5A3.5B2.2C.2C2.D2.2D2.2E.2E\$6A3.4B3.2C.C3.4D3.5E\$7A3.3B4.3C
4.3D4.3E\$.6A3.4B3.4C3.4D2.5E\$.5A3.5B2.2C.2C2.5D2.2E.2E\$2.2A6.2B13.D\$
25.D!
``````
All of the shapes advance twice on the first generation, rather than only once.

### Re: Viewer Generations Bug

Posted: May 15th, 2019, 9:32 pm
Gamedziner wrote:From Sandbox thread Polyominoes:
fluffykitty wrote:Improved to 117:

Code: Select all

``````x = 35, y = 8, rule = 7//6
3.2A6.B\$.5A3.5B2.2C.2C2.D2.2D2.2E.2E\$6A3.4B3.2C.C3.4D3.5E\$7A3.3B4.3C
4.3D4.3E\$.6A3.4B3.4C3.4D2.5E\$.5A3.5B2.2C.2C2.5D2.2E.2E\$2.2A6.2B13.D\$
25.D!
``````
All of the shapes advance twice on the first generation, rather than only once.
Seems to be triggered when all live cells die. (In the quote it happens on G2 instead of G1 because of the rule change)

### Re: Viewer Generations Bug

Posted: May 16th, 2019, 12:13 am
This has been fixed and will be in the next released build. Test case is here. Thanks for reporting!

### Re: Viewer Generations Bug

Posted: May 16th, 2019, 6:55 am
One more bug: Drawing state 1 draws state 5 on certain points, while also drawing state 1 two cells to the left. For the previous patterns, at least, this seems to occur on all cells with coordinates (1+16m,3+16n), where m and n are both integers.

### Re: Viewer Generations Bug

Posted: May 16th, 2019, 8:56 am
Nice catch! This has been fixed and will be in the next released build.