lifeviewer bug

[ENORMOUS_NAME]

try to change the step size to exactly sixty

Code: Select all

x=0, y=0, rule=B3/S23
o!

[Saka]

What's wrong? I don't see anything wrong (Mobile, google chrome 85.0.4183.127). The cell just dies.

[bubblegum]

What's wrong? I don't see anything wrong (Mobile, google chrome 85.0.4183.127). The cell just dies.

He means that the generation stays at the generation it died once.
A bit more: Afterwards, Space becomes the same as Tab while B/Backspace remains fine.

[ENORMOUS_NAME]

wait wuttt


i fullscreened it and it worked i changed step size to 60

ok nvm for the bug

also 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

[rowett]

also 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

It's not a bug. When stepping LifeViewer stops as soon as the pattern dies.

[bubblegum]

also 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

It's not a bug. When stepping LifeViewer stops as soon as the pattern dies.

Well that's just terrible design.

[MathAndCode]

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

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]

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.

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]

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)

That's probably due to rounding to the nearest pixel, which is not a bug that's specific to LifeViewer.

[EvinZL]

I'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:

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!

The cell in front of the lwss won't be born, while if the lwss is put anywhere else it will work

This also seems to happen in inbredlife for any pattern at a certain location

[dvgrn]

I'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:

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!

The cell in front of the lwss won't be born, while if the lwss is put anywhere else it will work

This also seems to happen in inbredlife for any pattern at a certain location

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).

I'd guess that the added LWSS is just over the edge of a new 16x16 region that didn't exist before the LWSS was edited in.

[rowett]

I've found another lifeviewer bug

This has been fixed. Thanks for reporting!

[EvinZL]

When copying, lifeviewer swaps B3/S23 for Conway's Life, making clipboard patterns unusable

[rowett]

When copying, lifeviewer swaps B3/S23 for Conway's Life, making clipboard patterns unusable

Fixed, thanks.

[ENORMOUS_NAME]

ok new bug


go here viewtopic.php?f=11&t=390#p2261 and click on the third lifeviewer window
run 2 gens and delete everything
click the tab thing at the bottom left
it will still say 1 alive

[rowett]

run 2 gens and delete everything
click the tab thing at the bottom left
it will still say 1 alive

Fixed, thanks for reporting!

[MathAndCode]

go here viewtopic.php?f=11&t=390#p2261 and click on the third lifeviewer window

How about this?
Do 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.



Edit: Here's another bug: Again going to the third LifeViewer window in the same linked post, turn the grid on, place a gray cell at (8, 11), go to generation 10, remove the gray cell at (8, 11) and add a gray cell at (9, 8) (Either order seems to work.), then place the "reset" button. One of the changes made at generation 10 but not the other will remain. (Specifically, gray cells will exist at both (8, 11) and (9, 8). Again, other generations and coordinates probably work.

[goldenratio]

Do 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.

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]

In 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).

[bubblegum]

In 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).

Unable to reproduce.

Also, LifeViewer bugs (by custom) go in the LifeViewer thread.

[rowett]

In 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).

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.

[Schiaparelliorbust]

Code: Select all

x = 46, y = 47, rule = B3/S23
18$15b2o$15b2o4$23b3o$23bo2bo$24b3o7$21b2o$20bo2bo$21b2o!

Go to generation 645 and place a cell like this:

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!

The duoplet dies and comes back to life.
I couldn't repeat it myself though.

[goldenratio]

The duoplet dies and comes back to life.
I couldn't repeat it myself though.

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.

If you can't repeat it it's probably just a glitch and not possible to fix.

Requesting this thread to be locked, so any further bugs can be posted where they're supposed to go (in the lifeviewer thread).

[EvinZL]

If you open a LifeHistory pattern, and draw in state-3 over state-2 cells, and then udo, the cells should revert to state-3, but instead they become state-4.

[rowett]

If you open a LifeHistory pattern, and draw in state-3 over state-2 cells, and then udo, the cells should revert to state-3, but instead they become state-4.

Thanks for reporting! It's on the backlog.