lifeviewer bug

[rowett]

It kept going until I woke up this morning, where I noticed that it had finally stopped identifying at generation 217232803617, without giving any actual results.

No idea if I've hit some sort of upper time limit in Identify, or something else ended up happening.

Analysis:

• There's no time limit.
• The generation number 217232803617 is well within range (Javascript integers can go up to 2^53 and that's around 2^38).
• The buffer was 80% full at the last snapshot.
• Identify stops without results if a) the buffer gets full or b) the pattern dies

From that I suspect the buffer got full. In which case it will have displayed a notification which likely was gone by the time you checked.

Side note: LifeViewer doesn't currently load the Identify snapshot. That's on the backlog.

[R2INT]

For some reason, when I reset a pattern on my laptop, it does not let me interact with LifeViewer until after the message saying 'Reset' closes.

[b-engine]

This may be a graphical issue.

Screenshot_20250912-061358.png (42.12 KiB) Viewed 5832 times

Maybe draw the grid lines behind cells?

[qqd]

The versions of LifeHistory that are implemented in LifeViewer and Golly are different, and according to the article on the rule, only Golly implements it correctly. Run the following pattern (turn off any blue light filters beforehand):

Code: Select all

x = 15, y = 54, rule = LifeHistory
C2.C6.D2.D$4.C9.D$C3.C5.D3.D$.4C6.4D7$E2.E6.D2.D$4.E9.D$E3.E5.D3.D$.
4E6.4D7$C2.C6.C2.C$4.C9.C$C3.C5.C3.C$.4C6.4C7$E2.E6.C2.C$4.E9.C$E3.E
5.C3.C$.4E6.4C7$C2.C6.E2.E$4.C9.E$C3.C5.E3.E$.4C6.4E7$E2.E6.E2.E$4.E
9.E$E3.E5.E3.E$.4E6.4E!
[[ STOP 20 ]]

According to the article, state 5 (yellow) is treated as a live cell and will convert to state 4 (red) in the next generation. More importantly, it has no birth conditions and can therefore never appear in the evolution of a pattern whiteout any state 5 cells.

However, in the demo above, the last two rows evolve an LWSS made completely of state 5 cells, even though they were all in state 4 in generation 10. Apparently state 4 cells which were state 5 cells at a previous point in time evolve into state 5 cells rather than state 3 (white) cells as they should as demonstrated in the other rows. Fortunately, Golly does not experience this issue, but it makes me wonder how this bug could possibly happen with only 1 red state.

[muzik]

However, in the demo above, the last two rows evolve an LWSS made completely of state 5 cells, even though they were all in state 4 in generation 10. Apparently state 4 cells which were state 5 cells at a previous point in time evolve into state 5 cells rather than state 3 (white) cells as they should as demonstrated in the other rows. Fortunately, Golly does not experience this issue, but it makes me wonder how this bug could possibly happen with only 1 red state.

This has been pointed out a handful of times es before, but the current behaviour is intentional: viewtopic.php?p=195406#p195406

[Citation needed]

Newly uploaded rules don't seem to work on "lazyslug.com".

Code: Select all

x = 0, y = 0, rule = ColourisedLife47s
GpDoQpNpJ Nb!
[[ ICONS ]]

[rowett]

Newly uploaded rules don't seem to work on "lazyslug.com".

Fixed, thanks!

[Citation needed]

Newly uploaded rules don't seem to work on "lazyslug.com".

Fixed, thanks!

Unfortunately, OCA permalinks stopped working.

http://lazyslug.com/?rule=b2-as12

[rowett]

Unfortunately, OCA permalinks stopped working.

http://lazyslug.com/?rule=b2-as12

They work fine:
http://lazyslug.com/?rle=3o$o$bo!&rule=b2-as12


See Edit 2 here.
Basically rule, name and viewerconfig are ignored if rle is not present.

[b-engine]

The pop-up viewer flashes when scrolling.


On Firefox 143.0 (Build #2016113383), 62b30a28e7a4110ced2411d4b81bcb1256839616

GV: 143.0-20250908174027
AS: 143.0
OS: Android 9

[jayden678910]

Rule table just doesn’t work.

Code: Select all

x = 1, y = 1, rule = thingy
!
@RULE thingy
@TABLE
n_states:4
neighborhood:Moore
symmetries:rotate4reflect
var a = {0,1}
var b = a
var c = a
var d = a
var e = a
var f = a
var g = a
var h = a
var a1 = {0,3}
var b1 = a1
var c1 = a1
var d1 = a1
var e1 = a1
var f1 = a1
var g1 = a1
var h1 = a1
var a0 = {0,1,2,3)
var b0 = a0
var c0 = a0
var d0 = a0
var e0 = a0
var f0 = a0
var g0 = a0
var h0 = a0
0, 2,b,c,d,e,f,g,h, 1
# Death
1,a0,b0,c0,d0,e0,f0,g0,h0,0
@COLORS
1 255 0 0
2 255 128 0
3 180 0 255

[rowett]

Rule table just doesn’t work.

Code: Select all

var a0 = {0,1,2,3)

The quoted line has ) rather than }.

[jayden678910]

Rule table just doesn’t work.

Code: Select all

var a0 = {0,1,2,3)

The quoted line has ) rather than }.

thanks

[b-engine]

Maximizing the viewer causes buttons to overlap:

Screenshot_20251016-060121.png (22.37 KiB) Viewed 5479 times

[b-engine]

Now maximizing the viewer causes it to expand beyond bounds and render the maximize button as well as half of the UI inaccessible:

Screenshot_20251022-183307.png (11.25 KiB) Viewed 5433 times

[WRAPboi]

I pressed the reset button, and my patterns disappeared.
this happened with any ships that had been copied on to lifeviewer, i deleted it, reconstructed it myself, pressed play, reset, and it all disappeared.

[b-engine]

I pressed the reset button, and my patterns disappeared.

If you had drawn patterns after the 0th tick, resetting would remove the patterns. That's intentional [Citation needed].

[muzik]

The whole point of Theme Golly is to duplicate what Golly does.

This differs significantly:

Code: Select all

x = 19, y = 34, rule = LifeHistory
F22$9.D$7.D.D6.2E$7.3D5.2E$7.D8.2E$17.E7$18.F!
[[ THEME Golly
ZOOM 11 GPS 20 AUTOSTART
T 0 PAUSE 1
T 20 PAUSE 1
GPS 40 LOOP 200 ]]

Color definitions needed to make this accurate:

Code: Select all

x = 19, y = 34, rule = LifeHistory
F22$9.D$7.D.D6.2E$7.3D5.2E$7.D8.2E$17.E7$18.F!
[[ THEME Golly COLOR MARK1 192 255 192 COLOR ALIVE 0 255 0 COLOR ALIVERAMP 0 255 0 COLOR DEAD 0 0 128 COLOR DEADRAMP 0 0 128
ZOOM 11 GPS 20 AUTOSTART
T 0 PAUSE 1
T 20 PAUSE 1
GPS 40 LOOP 200 ]]

[rowett]

This differs significantly:

Fixed in build 1343.

[LWSSONHWSSONLWSS]

This is from the trolls thread. Sometimes when you rewind the pattern, it follows a completely different sequence.
That is the problem with PASTE commands.

Code: Select all

 x = 10, y = 10, rule = B3/S23
5bobo$b2o2bobo$3o3bobo2$2bo6bo2$6b2obo$6b2o$6bo2bo$7b2o!




























































































































































































































































[[ PASTEMODE XOR PASTET EVERY 7 1 PASTEDELTA -1 0 PASTE oobb$bboo$oboo$boob! 0 1 ]]
[[ STARTFROM 1 ]]
[[ SHADER BASIC ]]

[Chris857]

This is from the trolls thread. Sometimes when you rewind the pattern, it follows a completely different sequence.
That is the problem with PASTE commands.

I see issues when running it out somewhere 50-100 gen and rewinding.

[rowett]

This is from the trolls thread. Sometimes when you rewind the pattern, it follows a completely different sequence.
That is the problem with PASTE commands.

Fixed in build 1345.

[b-engine]

Now maximizing the viewer causes it to expand beyond bounds and render the maximize button as well as half of the UI inaccessible: Screenshot_20251022-183307.png

Bringing this back up because it's annoying me especially since I could easily mistap the maximize button.

[LuveelVoom]

New versions of lifeviewer seem to have a bug where the selection box's first corner is sticky: it will always be at the same spot even when you try to recreate the selection box somewhere else using the mouse or a touchscreen, unless you remove the entire selection box using the "remove selection" button. This is extremely annoying.

[rowett]

New versions of lifeviewer seem to have a bug where the selection box's first corner is sticky: it will always be at the same spot even when you try to recreate the selection box somewhere else using the mouse or a touchscreen

I can't reproduce this. It works fine for me on Windows desktop (Chrome) and iPhone (Safari). Please let me know which device and browser you are using?