Code: Select all
x=0, y=0, rule=B3/S23
o!
Code: Select all
x=0, y=0, rule=B3/S23
o!
Code: Select all
x = 12, y = 5, rule = Symbiosis
10.B$10.A$3A6.A.A$A.A7.A$A.A7.B!
Code: Select all
x = 10, y = 13, rule = Symbiosis
BA$.A$2.B2$3.B$3.A$3.A$2.B2A2.2A$4.A2.A.A$.B2A3.A$2.A$2.A$2.B!
He means that the generation stays at the generation it died once.
anythingsonata wrote:July 2nd, 2020, 8:33 pmconwaylife signatures are amazing[citation needed]
Code: Select all
x = 12, y = 5, rule = Symbiosis
10.B$10.A$3A6.A.A$A.A7.A$A.A7.B!
Code: Select all
x = 10, y = 13, rule = Symbiosis
BA$.A$2.B2$3.B$3.A$3.A$2.B2A2.2A$4.A2.A.A$.B2A3.A$2.A$2.A$2.B!
It's not a bug. When stepping LifeViewer stops as soon as the pattern dies.ENORMOUS_NAME wrote: ↑September 25th, 2020, 8:36 amalso yeah another bug: no matter what step size you use it first just goes one generation and then the cell dies instead of the step size you chose
Well that's just terrible design.rowett wrote: ↑September 25th, 2020, 8:46 amIt's not a bug. When stepping LifeViewer stops as soon as the pattern dies.ENORMOUS_NAME wrote: ↑September 25th, 2020, 8:36 amalso yeah another bug: no matter what step size you use it first just goes one generation and then the cell dies instead of the step size you chose
anythingsonata wrote:July 2nd, 2020, 8:33 pmconwaylife signatures are amazing[citation needed]
Half of that happened for me, but instead of stopping at generation 1, it went to generation 1 then continued with step size 60. When I stopped it, it was at generation 3361, which is equal to 56×60+1.ENORMOUS_NAME wrote: ↑September 25th, 2020, 8:36 amno matter what step size you use it first just goes one generation and then the cell dies instead of the step size you chose
yeah that's what I meant, and the original bug was that if your browser window was too small you couldn't set it to certain step sizes by dragging the slider around, but you could with the + and -. (technically = and - but whatever)MathAndCode wrote: ↑September 30th, 2020, 4:47 pmHalf of that happened for me, but instead of stopping at generation 1, it went to generation 1 then continued with step size 60. When I stopped it, it was at generation 3361, which is equal to 56×60+1.
Code: Select all
x = 12, y = 5, rule = Symbiosis
10.B$10.A$3A6.A.A$A.A7.A$A.A7.B!
Code: Select all
x = 10, y = 13, rule = Symbiosis
BA$.A$2.B2$3.B$3.A$3.A$2.B2A2.2A$4.A2.A.A$.B2A3.A$2.A$2.A$2.B!
That's probably due to rounding to the nearest pixel, which is not a bug that's specific to LifeViewer.ENORMOUS_NAME wrote: ↑September 30th, 2020, 5:35 pmthe original bug was that if your browser window was too small you couldn't set it to certain step sizes by dragging the slider around, but you could with the + and -. (technically = and - but whatever)
Code: Select all
x = 7, y = 9, rule = inbredLife
4.3A$3.A2.A$6.A$6.A$3.A.A2$3A$2.A$.A!
I was able to duplicate this by following the directions, with this rake. The "farthest glider" is the easternmost one. The cell that doesn't turn on when it should is at (129, 29).EvinZL wrote: ↑December 1st, 2020, 2:58 pmI've found another lifeviewer bug. If you take the rake pattern in the inbredLife thread, run it for 400 generations, and then put an LWSS so that the lwss and the farthest glider form this:The cell in front of the lwss won't be born, while if the lwss is put anywhere else it will workCode: Select all
x = 7, y = 9, rule = inbredLife 4.3A$3.A2.A$6.A$6.A$3.A.A2$3A$2.A$.A!
This also seems to happen in inbredlife for any pattern at a certain location
This has been fixed. Thanks for reporting!
Code: Select all
x = 12, y = 5, rule = Symbiosis
10.B$10.A$3A6.A.A$A.A7.A$A.A7.B!
Code: Select all
x = 10, y = 13, rule = Symbiosis
BA$.A$2.B2$3.B$3.A$3.A$2.B2A2.2A$4.A2.A.A$.B2A3.A$2.A$2.A$2.B!
Fixed, thanks for reporting!ENORMOUS_NAME wrote: ↑January 2nd, 2021, 10:19 pmrun 2 gens and delete everything
click the tab thing at the bottom left
it will still say 1 alive
How about this?ENORMOUS_NAME wrote: ↑January 2nd, 2021, 10:19 pmgo here viewtopic.php?f=11&t=390#p2261 and click on the third lifeviewer window
Probably because LifeViewer doesn't treat blue or grey cells as on cells. For example, scribble something using history cells and then select all, no selection is made.MathAndCode wrote: ↑January 2nd, 2021, 11:40 pmDo to that same pattern, run it for 42 generations (Other numbers probably also work.), select the cells from (2, 4) to (5, 7) (Other ranges probably also work.), then click the "clear cells outside selection" button. Some blue and gray cells are still present. I suspect that the program doesn't bother clearing cells outside what it thinks is the bounding box, which is only around all of the live cells. Probably relatedly, pressing the "select all cells" button (again, at generation 42) results in a box that contains all of the live cells but not all of the blue and gray cells.
Unable to reproduce.MathAndCode wrote: ↑January 6th, 2021, 11:07 pmIn LifeViewer, changing the rule from Conway's Life to B3S23 pulls up the theme menu without a button to close it (although if one clicks the button to pull up the help menu, a back button appears).
anythingsonata wrote:July 2nd, 2020, 8:33 pmconwaylife signatures are amazing[citation needed]
I can't reproduce this. In general if it's not possible to provide a repeatable set of steps or a pattern that shows the problem it's unlikely I'll be able to fix it.MathAndCode wrote: ↑January 6th, 2021, 11:07 pmIn LifeViewer, changing the rule from Conway's Life to B3S23 pulls up the theme menu without a button to close it (although if one clicks the button to pull up the help menu, a back button appears).
Code: Select all
x = 46, y = 47, rule = B3/S23
18$15b2o$15b2o4$23b3o$23bo2bo$24b3o7$21b2o$20bo2bo$21b2o!
Code: Select all
x = 18, y = 19, rule = LifeHistory
10$7.2A$6.A2.A$6.A2.A$7.2A.2A$9.A2.A$9.A2.A$10.2A$11.C!
Schiaparelliorbust wrote: ↑January 14th, 2021, 12:25 pmThe duoplet dies and comes back to life.
I couldn't repeat it myself though.
If you can't repeat it it's probably just a glitch and not possible to fix.rowett wrote: In general if it's not possible to provide a repeatable set of steps or a pattern that shows the problem it's unlikely I'll be able to fix it.
Thanks for reporting! It's on the backlog.