ConwayLife.com

Posted: **July 31st, 2025, 2:28 pm**

Here is a bug I found with LifeViewer Pro:

#C Spaceship collection from FWKnightship
x = 791, y = 218, rule = SoManyShips2
350.B$305.B15.B7.B19.B.B37.B.B3.BAB3.BAB3.BAB28.4A28.4A25.B.B$297.BAB
4.B.B6.B.B4.B.B5.B.B4.BAB4.BAB11.BAB5.BAB22.B.B3.ABA3.ABA3.ABA28.A2BA
28.A2BA26.B$297.ABA5.A8.B6.A5.3B5.ABA4.ABA5.A5.ABA5.ABA23.A5.B6.A4.B29.
B2.B28.B2.B26.A$312.A.A6.B7.B13.B6.B6.B32.B10.A2B4.B91.A$335.B7.B6.B6.
B6.B.B41.B63.2A25.B.B$343.B6.B6.B50.B63.2A25.B.B$343.B6.B6.B50.B30.2A
31.2B25.B.B$343.B6.B6.B6.A.A40.B.B28.4A31.B26.B27.4A$337.B5.B6.B6.B49.
B.B28.A2BA31.B54.B2.B$298.B.B6.2A8.2A17.B.B4.B6.B6.B7.B23.B.B5.B.B7.B
.B117.2A2B2A30.2A8.2A8.2A$299.B6.4A6.4A6.4A5.3B5.B6.B6.B31.B.B6.B9.A30.
A88.B2.B30.4A6.4A6.4A$297.A.A.A5.2B7.4B5.2A2B2A6.B5.B6.B6.B6.B.B23.A7.
B9.B29.2A32.B55.4A$316.B2.B5.6B12.B6.B6.B38.B.2B38.2B121.A4.A4.A4.A4.
A4.A$325.B4.B5.2A5.B6.B6.B31.3A7.B38.2B121.A.2A.A4.A.2A.A4.A.2A.A$336.
2A5.B6.B6.B6.A.A23.BA5.2B137.2A23.BA2.AB4.BA2.AB4.BA2.AB$336.2B5.B6.B
6.B33.B5.BA129.4A4.2A24.4A6.4A6.4A37.A.A.A6.A.A.A$315.B9.B17.B6.B6.B7.
B162.B2.B3.4B24.2A8.2A8.2A29.B.B5.6A5.7A29.B.B25.B.B11.B.B13.B.B38.B.
B13.B.B$302.4A8.B.B7.B.B15.B.B4.B.B4.A170.2A2B2A.AB2.BA75.B6.6B5.7B30.
B27.B13.B15.B40.B15.B$225.A74.3A2B3A7.3B5.3B6.B10.A6.A5.2A170.B2.B3.4B
33.A2.A39.B6.B10.B5.B29.B.B5.B.B17.B.B11.B.B5.B.B5.B.B38.B.B5.B.B5.B.
B$223.BA73.3A6B2A6.B9.B5.B.B16.B5.2B170.4A4.2A139.B.B39.B.B54.B.B$223.
A.A72.A3B4.3B8.A4.B9.A23.2B178.2A45.2A30.B62.B41.B56.B$3.A294.2B8.B273.
4A83.B.B6.B11.B.B4.B.B11.B.B6.B6.B.B38.B.B6.B6.B.B$.BA329.A249.4B84.B
6.B.B11.B6.B13.B6.B.B6.B40.B6.B.B6.B$.A.A327.2A249.B2.B83.B.B5.B.B11.
B5.B.B11.B.B5.B.B5.B.B38.B.B5.B.B5.B.B$A.2A327.2B357.B.B$331.2B$613.B
3.B2$530.B141.A41.B11.B44.B11.B$528.2BAB142.BA22.B15.B11.B44.B11.B$528.
B.A5.2A139.A16.2A2B.2B15.2B5.2B48.2B5.2B$531.A4.2A140.B13.A2.A2.B$51.
B.B8.B.B8.B.B452.AB2A2.5B154.2A.B3.B$51.B10.B10.B454.5A.2B2.BA152.3A$
62.A10.B36.2A418.AB.A.4B$59.B.B8.B.3B34.3A32.BAB16.2A364.3B4.2A$59.B10.
B38.3A32.AB16.3A371.2A178.2B5.2B48.2B5.2B$147.A8.2AB3.3A545.B.B15.B.B
36.B.B$114.2A39.2A.B552.B17.B38.B$113.A41.A3.A7.2A541.B.B15.B.B36.B.B
$113.A41.2B.2A6.A361.A5.A2B$53.A7.A95.3A6.A361.BAB6.B$52.2A6.2A6.3A456.
B.BA2.2A.B173.B.B3.2B5.2B3.B.B36.B.B3.2B5.2B$52.A.A5.A.A5.A464.ABAB174.
B17.B38.B$69.B2A463.A174.B.B15.B.B36.B.B$62.B3$780.2B6$780.2B$774.B.B
$775.B10.B$774.B.B8.B.B3$774.B.B3.2B3.B.B$775.B10.B$774.B.B4$17.3A$17.
A.AB763.A3B$17.2A766.A.A$18.B764.B2.A$785.B$64.AB75.B.B$64.A75.A2BAB$
62.AB.A.A30.A40.2B2.B$62.BA.A31.2A41.B2.2B$60.2A3.B30.2A.A31.3A5.BA2B
A96.3A$60.B.2A2B32.AB31.3A6.B.B98.3A$131.2A3.B105.3A$62.A72.B107.2A$134.
B14.B.B89.B3A$133.B3.2A9.A2BAB89.A$136.3A8.2B2.B$136.3A9.B2.2B$147.BA
2BA$145.B2.B.B$142.A2B$144.B$141.B2.A$141.AB9$295.A.A4.A.A4.A.A29.3A5.
B.B5.B$295.3A4.3A4.3A28.5A6.B6.B25.B.B$295.B6.3B4.B30.5B5.2A5.B26.B.B
$342.B14.B26.A.A29.B.B8.B.B$309.2A38.B.B32.ABA29.B.B8.B.B$309.2B45.2A
58.B.B8.B.B$309.2B45.2B27.A31.B10.B31.B.B$356.2B25.2A.2A73.B70.A.A$460.
B.B31.B9.A26.BA.AB$296.A6.A155.2A.2A30.B8.3A25.B3.B$74.A220.ABA4.ABA187.
ABABA33.2BA.A2B45.A.A.A12.A4.A90.A32.B$41.AB30.A.A219.BAB4.BAB155.3B30.
3A5.A.ABA.A22.2B3.2B27.BA.A.AB9.2B2A.2A2B9.A.A2.A.A8.A4.A34.2A7.A29.B
A.AB29.B.B$39.A.2A30.ABA219.B.B4.B.B155.B.B30.3A34.B5.B26.B2.3A2.B8.B
.A.B.A.B9.B.B2.B.B7.A.A2.A.A32.3A6.A.A27.B.B.B.B29.B$38.2A.2B30.BA220.
ABA4.ABA120.A.A64.2A.2A6.A.A57.B2A3.2AB8.B2.3A2.B9.3B2.3B7.3B2.3B34.A
6.3B30.A31.B.B29.B$73.2B39.B310.3A64.B3.B6.3B57.BA.B.B.AB8.B3.A3.B9.B
.B2.B.B7.BAB2.BAB41.BAB62.B.B28.B.B$37.2AB32.ABAB37.B36.2AB150.A121.3B
135.B2.A.A2.B8.B7.B9.2AB2.B2A7.B.B2.B.B41.3B30.A32.B29.B.B28.A$37.BAB
33.A40.B33.2B2A411.B7.B8.B7.B9.BAB2.BAB6.2A2B2.2B2A40.B.B30.A62.A.A27.
A.A$114.A33.B4.A409.B7.B8.B7.B26.B2.B43.ABA63.B59.3B$115.AB30.2A43.BA
369.B2.3A2.B8.B7.B11.B2.B11.A2BA139.ABA27.BAB$147.2A2.A37.BA.B2A368.2B
.3A.2B8.B7.B10.BA2.AB9.B4.B108.B59.3B$147.B40.B.2B.A371.A.A.A10.B7.B10.
A.2B.A9.2B2.2B168.B.B$149.A38.AB.BA372.A.A.A10.B7.B9.A.B2AB.A7.3A2.3A
167.B.B$189.2B.A374.A31.B4.B8.A.4B.A167.B.B$187.2B.2AB373.A.A8.3A9.3A
7.A.2A.A11.2A170.3B$187.3A387.2BA9.A2B8.B2.B184.B.B$188.A378.B9.3B9.3B
7.2A2.2A9.A4.A168.ABA$599.2B2.2B9.B.2A.B$614.2B2.2B$600.B2.B12.2B$600.
B2.B11.B2.B$597.A.A4.A.A7.2B2.2B$597.3A4.3A7.A.2B.A$597.3B4.3B8.B2.B2$
615.B2.B$615.4B$615.B2.B$615.4A35$302.A$295.A.A3.A.A$295.3A2.2A.2A$328.
BAB$296.A30.BABAB$327.A3BA4.BAB31.2A90.A.A$329.A6.ABA30.B.2A$329.A7.A
31.B.B88.AB.B.BA$329.A39.B2.A$337.A32.2B28.B29.B4.B25.A.B.A$337.A61.B
.B27.B6.B24.AB.BA23.B$329.A99.B6.B25.A.A23.B.B50.A7.A41.B$328.3A69.B26.
B3.B2.B3.B24.B23.2B.2B21.5B23.A7.A39.B3.B64.B.B$328.BAB68.3A60.B.B23.
3B22.BA.AB22.2AB2.A2.B2A39.ABA$399.BAB61.B23.B.A.B21.5B23.BA2.B2.AB29.
B.B6.B.B.B.B63.B.B$463.A25.A24.ABA23.B2.BA.AB2.B27.5B6.A3.A28.B.B34.B
$463.A24.B.B24.A24.3B.3B.3B26.ABA.ABA39.B35.B$463.A76.3B2.A2.3B27.BA.
AB38.2A.2A32.A.A57.2A$463.A24.B.B87.2B.2B6.A3.A27.BA.AB30.B.3B.B56.2A
$488.BAB97.B.B.B.B26.BA.AB29.3A.B.3A52.B3.A$463.B24.3A99.ABA29.B.B30.
2A2.B2.2A51.BA$488.A.A87.2B.2B6.B3.B62.2BA.A2B54.AB$489.B25.B62.BA.AB
.3A4.B65.B.B.B51.A3.B$515.B61.ABA.AB.A.A126.2A$515.A62.5B.2A128.2A$512.
B2.A2.B60.B.B$513.2B.2B$515.A$514.A.A7$684.B20.A$704.A.A.A$703.A.2A$704.
2A.A7.3A$706.2A7.A.A$704.A9.B3A$714.2B$713.B$712.B$710.2B$708.3AB$708.
A.A$708.3A!

If you load this pattern into LifeViewer Pro and then save it and press View, the entire pattern disappears after 1 generation.

Posted: **July 31st, 2025, 3:22 pm**

What is LifeViewer Pro?

Posted: **August 1st, 2025, 12:00 am**

R2INT wrote: July 31st, 2025, 2:28 pm If you load this pattern into LifeViewer Pro and then save it and press View, the entire pattern disappears after 1 generation.

Fixed in build 1313. Thanks for reporting!

Resu wrote: July 31st, 2025, 3:22 pm What is LifeViewer Pro?

LifeViewer Pro is a faster version of LifeViewer. It's currently in Alpha testing.

Posted: **August 2nd, 2025, 6:36 am**

Given recent changes relating to pattern collisions with the outer boundary, would it also make sense to stop pattern identification if KILLGLIDERS interferes with its evolution? It wasn't mentioned here but the same logic applies.

The only actual issue I've found is this - I don't know if fixing it would be easier, since I use Identify on uncapped guns often to get the period and generate maps and such:

Code: Select all

#C bounding box height 19
x = 33, y = 14, rule = B3/S23
2o5b2o$2o5b2o2$4b2o$4b2o5$22b2ob2o$21bo5bo$21bo6bo2b2o$21b3o3bo3b2o$
26bo!
[[ AUTOIDENTIFY KILLGLIDERS ]]

Code: Select all

#C bounding box height 21
x = 33, y = 14, rule = R1,C2,S2-3,B3
2o5b2o$2o5b2o2$4b2o$4b2o5$22b2ob2o$21bo5bo$21bo6bo2b2o$21b3o3bo3b2o$
26bo!
[[ AUTOIDENTIFY KILLGLIDERS ]]

A more clear reproduction case of a previously reported bug: history trail cells are created here, despite the basic shader being in use, despite trail cells like these being something that should never be able to come into existence outside of the Cell Age shader.

Code: Select all

x = 6, y = 6, rule = B3/S23
2o$2obo$4bo$bo$2bob2o$4b2o!
[[ X -4 PASTEMODE XOR PASTET EVERY 2 PASTE 6o$6o$6o$6o$6o$6o! -10 0 PASTE 6o$6o$6o$6o$6o$6o! -10 0 GRID SHADER Basic ]]

It also creates insta-die cells in the Rainbow and Neighbour Count shader settings:

Code: Select all

x = 6, y = 6, rule = B3/S23
2o$2obo$4bo$bo$2bob2o$4b2o!
[[ X -4 PASTEMODE XOR PASTET EVERY 2 PASTE 6o$6o$6o$6o$6o$6o! -10 0 PASTE 6o$6o$6o$6o$6o$6o! -10 0 GRID SHADER Rainbow ]]

Code: Select all

x = 6, y = 6, rule = B3/S23
2o$2obo$4bo$bo$2bob2o$4b2o!
[[ X -4 PASTEMODE XOR PASTET EVERY 2 PASTE 6o$6o$6o$6o$6o$6o! -10 0 PASTE 6o$6o$6o$6o$6o$6o! -10 0 GRID SHADER Neighbour ]]

Is this specific case of integer overflow worth paying any attention to? The max supported value is 1073741824, whereas overflow happens at exactly twice that. I don't know if there's a way to check if a value is above 2147483647 and block it from being processed before it loops around, and give the standard "argument out of range" with the value actually specified.

Code: Select all

x = 1, y = 1, rule = B/S0
o!
[[ SHADER Basic STARTFROM 4294967295 SHOWGENSTATS SHOWTIMING EXTENDEDTIMING ]]

Posted: **August 4th, 2025, 7:48 pm**

rowett wrote: August 1st, 2025, 12:00 am
R2INT wrote: July 31st, 2025, 2:28 pm If you load this pattern into LifeViewer Pro and then save it and press View, the entire pattern disappears after 1 generation.
Fixed in build 1313. Thanks for reporting!

I assume this is a Pro exclusive release? Neither conwaylife.com nor lazyslug.com have a LifeViewer Standard build 1313 available.

Posted: **August 5th, 2025, 8:07 am**

Me, on esolangs wiki wrote: I need to vent a little…
I was in the middle of compiling an oscillator stamp collection for B3/S23-a5, and I got to period 12. Then I accidentally saved a selection instead of the whole thing, and then I lost what must be hours of progress…
All this was done on a LifeViewer website tab, so I didn’t even have any way to salvage it, like I could have if I did it elsewhere. I hope I can convince Rowett to do something to prevent future accidents like this. The last saved version I had anywhere was up to period 4 only…
Is this because of my carelessness alone?

:Ɛ (no, not 3:)

I have two possible suggestions that could prevent this from happening again.

The first is the easiest: make it so that if you currently have a selection and you save, it still saves the entire pattern.

The second is harder, but likely worth it. Make it so that the last few (3 is a good amount) patterns saved in that LifeViewer instance are saved internally, and can be recovered.

Posted: **August 5th, 2025, 8:18 am**

hotcrystal0 wrote: August 5th, 2025, 8:07 am The second is harder, but likely worth it. Make it so that the last few (3 is a good amount) patterns saved in that LifeViewer instance are saved internally, and can be recovered.

If it is saved, is it going to be saved for one person only, and how will that person be identified?

Posted: **August 5th, 2025, 8:32 am**

Resu wrote: August 5th, 2025, 8:18 am If it is saved, is it going to be saved for one person only, and how will that person be identified?

It’s intended to be saved locally.

Posted: **August 5th, 2025, 9:25 am**

3. You can add accounts to LifeViewer to allow for online backup of save data (patterns (required) + comments (optional) + scripts (optional)). (likely the hardest solution)

Posted: **August 7th, 2025, 12:48 pm**

The bug from LifeViewer Pro still exists:

Code: Select all

x = 110, y = 120, rule = SoManyShips2
5.B$5.B3$7.A$6.AB9.2B6.2B$7.A13.A$20.ABA$5.B$5.B8$21.B$21.B$4.ABA$5.A
13.A$2B6.2B9.BA$19.A8$20.ABA$20.BAB21$20.ABA$20.BAB$64.BA42.BA$13.2B49.
AB42.AB$64.BA42.BA18$20.ABA$20.BAB21$20.ABA20.B$20.BAB20.B3$86.BA20.B
A$13.2B12.2B6.2B49.AB20.AB$86.BA20.BA2$43.B$43.B3$31.B$31.B3$39.2B6.2B
4$31.B$31.B$20.ABA$20.BAB!

Wiew the pattern.
Switch to SoManyShips3.
Switch back to SoManyShips2.

The result: a higher-range multistate INT rule that explodes with state 66, even though the rule only has 3 states. Attempting to copy and paste within the pattern results in a 'Could not decode system clipboard' message.

Here is the RLE you get after saving:

Code: Select all

x = 128, y = 128, rule = SoManyShips2
48undefined$48undefined$48undefined$14undefined2.32undefined$14undefined
2.32undefined$14undefined.33undefined$48undefined$48undefined$16undefined
.9undefined3.5undefined3.11undefined$15undefined2.9undefined2.6undefined
2.12undefined$15undefined2.13undefined2.16undefined$14undefined2.13undefined
3.16undefined$14undefined2.14undefined.17undefined$14undefined.33undefined
$48undefined$48undefined$32undefined$32undefined$32undefined$32undefined
$30undefined$30undefined$14undefined2.14undefined.undefined$13undefined
3.16undefined$9undefined3.undefined.undefined2undefined3.8undefined2.
2undefined$9undefined2.6undefined2.9undefined2.2undefined$28undefined
.3undefined$32undefined$32undefined$32undefined$32undefined$32undefined
$16.32undefined$16.14undefined2.16undefined$16.13undefined3.16undefined
$16.13undefined.undefined.16undefined$16.32undefined$16.32undefined$16.
32undefined$16.32undefined$16.32undefined$16.32undefined$16.32undefined
$16.32undefined$16.32undefined$16.32undefined$16.32undefined$16.32undefined
$16.32undefined16.16undefined32.16undefined$16.32undefined16.16undefined
32.16undefined$16.32undefined16.16undefined32.16undefined$16.32undefined
16.16undefined32.16undefined$16.32undefined16.16undefined32.16undefined
$16.32undefined16.16undefined32.16undefined$16.32undefined16.16undefined
32.16undefined$16.14undefined2.16undefined16.16undefined32.16undefined
$16.13undefined3.16undefined16.16undefined32.16undefined$16.13undefined
.undefined.16undefined16.9undefined2.5undefined32.5undefined2.9undefined
$16.6undefined3.23undefined16.9undefined2.5undefined32.5undefined2.9undefined
$16.6undefined2.24undefined16.9undefined2.5undefined32.5undefined2.9undefined
$16.32undefined16.9undefined2.5undefined32.5undefined2.9undefined$16.
32undefined16.16undefined32.16undefined$16.32undefined16.16undefined32.
16undefined$16.32undefined16.16undefined32.16undefined$16.32undefined
$16.32undefined$16.32undefined$16.32undefined$16.32undefined$16.32undefined
$16.32undefined$16.32undefined$16.32undefined$16.32undefined$16.32undefined
$16.32undefined$16.32undefined$16.14undefined2.16undefined$16.13undefined
3.16undefined$16.13undefined.undefined.16undefined$16.32undefined$16.
32undefined$16.32undefined$16.32undefined$16.32undefined$16.32undefined
$16.32undefined$16.32undefined$16.32undefined$16.32undefined$16.32undefined
$16.32undefined$16.32undefined$16.32undefined$16.32undefined$16.32undefined
$16.48undefined16.48undefined$16.48undefined16.48undefined$16.48undefined
16.48undefined$16.14undefined2.20undefined2.10undefined16.48undefined
$16.13undefined3.20undefined2.10undefined16.48undefined$16.13undefined
.undefined.20undefined.11undefined16.48undefined$16.48undefined16.48undefined
$16.48undefined16.15undefined2.20undefined2.9undefined$16.6undefined3.
11undefined3.5undefined3.17undefined16.15undefined2.20undefined2.9undefined
$16.6undefined2.12undefined2.6undefined2.18undefined16.15undefined2.20undefined
2.9undefined$16.48undefined16.15undefined2.20undefined2.9undefined$16.
36undefined2.10undefined16.48undefined$16.36undefined2.10undefined16.
48undefined$16.36undefined.11undefined16.48undefined$16.48undefined16.
48undefined$16.24undefined2.22undefined16.48undefined$16.24undefined2.
22undefined$16.24undefined.23undefined$16.48undefined$16.32undefined3.
5undefined3.5undefined$16.32undefined2.6undefined2.6undefined$16.48undefined
$16.48undefined$16.24undefined2.22undefined$16.24undefined2.22undefined
$16.14undefined2.8undefined.23undefined$16.13undefined3.32undefined$16.
13undefined.undefined.32undefined$16.48undefined$16.48undefined$16.48undefined
$16.48undefined!

Viewing the pattern again after saving with a state-1 cell results in total death.

Posted: **August 8th, 2025, 8:07 am**

hotcrystal0 wrote: August 5th, 2025, 8:07 am
Me, on esolangs wiki wrote: I was in the middle of compiling an oscillator stamp collection for B3/S23-a5, and I got to period 12. Then I accidentally saved a selection instead of the whole thing, and then I lost what must be hours of progress…

...make it so that if you currently have a selection and you save, it still saves the entire pattern.

This is implemented in build 1315.

Posted: **August 8th, 2025, 8:08 am**

R2INT wrote: August 7th, 2025, 12:48 pm The bug from LifeViewer Pro still exists:

Fixed in build 1315. Thanks for reporting!

Posted: **August 8th, 2025, 11:15 am**

muzik wrote: August 2nd, 2025, 6:36 am Given recent changes relating to pattern collisions with the outer boundary, would it also make sense to stop pattern identification if KILLGLIDERS interferes with its evolution?

The only actual issue I've found is this - I don't know if fixing it would be easier, since I use Identify on uncapped guns often to get the period and generate maps and such

If it's an issue then I would disable Identify entirely when KILLGLIDERS is specified. If the current functionality is useful then I don't mind keeping it.

muzik wrote: August 2nd, 2025, 6:36 am A more clear reproduction case of a previously reported bug: history trail cells are created here, despite the basic shader being in use, despite trail cells like these being something that should never be able to come into existence outside of the Cell Age shader.

Fixed in build 1316, thanks!

muzik wrote: August 2nd, 2025, 6:36 am Is this specific case of integer overflow worth paying any attention to?

Also fixed.

Posted: **August 8th, 2025, 6:14 pm**

rowett wrote: August 8th, 2025, 11:15 am
muzik wrote: August 2nd, 2025, 6:36 am A more clear reproduction case of a previously reported bug: history trail cells are created here, despite the basic shader being in use, despite trail cells like these being something that should never be able to come into existence outside of the Cell Age shader.
Fixed in build 1316, thanks!

Fix confirmed, but there still appears to be this edge case:

Code: Select all

x = 6, y = 6, rule = B3/S23
2o$2obo$4bo$bo$2bob2o$4b2o!
[[ X -4 PASTEMODE XOR PASTET EVERY 2 PASTE 6o$6o$6o$6o$6o$6o! -10 0 PASTE 6o$6o$6o$6o$6o$6o! -10 0 GRID THEME Mono LAYERS 10 ]]

Code: Select all

x = 6, y = 6, rule = B3/S23
2o$2obo$4bo$bo$2bob2o$4b2o!
[[ X -4 PASTEMODE XOR PASTET EVERY 2 PASTE 6o$6o$6o$6o$6o$6o! -10 0 PASTE 6o$6o$6o$6o$6o$6o! -10 0 GRID SHADER Basic LAYERS 10 ]]

The second works correctly, but the first has some higher layered cells in a block on the left for some reason, even though "THEME Mono" should make this impossible. Note how these only appear as a result of PASTE and can never come from evolution.

Posted: **August 12th, 2025, 9:38 am**

Also reiterating this Pro discrepancy on that topic:

Code: Select all

x = 5, y = 4, rule = B3/S23
o2bo$4bo$o3bo$b4o!
[[ HISTORYSTATES 0 GRID LAYERS 10 AUTOSTART TRACK 1/2 0 ZOOM 8 ]]

In the current standard engine there is (correctly) no history trail left, but in the WASM engine there (incorrectly) is, as indicated by the taller layers.

Posted: **August 12th, 2025, 4:23 pm**

muzik wrote: August 8th, 2025, 6:14 pm ...there still appears to be this edge case

Fixed, thanks.

muzik wrote: August 12th, 2025, 9:38 am Also reiterating this Pro discrepancy on that topic:

In the current standard engine there is (correctly) no history trail left, but in the WASM engine there (incorrectly) is, as indicated by the taller layers.

I'm aware. It's only visible with Layers so low priority to fix.

Posted: **August 13th, 2025, 8:00 am**

Some more investigation into another extremely minor previously-reported layering/history cell case:

HISTORYSTATES 0:

Code: Select all

x = 3, y = 4, rule = B2/S
o$2bo$2bo$o!
[[ HISTORYSTATES 0 GRID LAYERS 10 AUTOSTART TRACK 1 0 ZOOM 16 COLOR DEAD Lime COLOR DEADRAMP Green GPS 4 ]]

Code: Select all

x = 3, y = 4, rule = R1,C2,S,B2
o$2bo$2bo$o!
[[ HISTORYSTATES 0 GRID LAYERS 10 AUTOSTART TRACK 1 0 ZOOM 16 COLOR DEAD Lime COLOR DEADRAMP Green GPS 4 ]]

Expected: Alive 64 -> Dead 0
Actual: Alive 64 -> Dead 0

HISTORYSTATES 1:

Code: Select all

x = 3, y = 4, rule = B2/S
o$2bo$2bo$o!
[[ HISTORYSTATES 1 GRID LAYERS 10 AUTOSTART TRACK 1 0 ZOOM 16 COLOR DEAD Lime COLOR DEADRAMP Green GPS 4 ]]

Code: Select all

x = 3, y = 4, rule = R1,C2,S,B2
o$2bo$2bo$o!
[[ HISTORYSTATES 1 GRID LAYERS 10 AUTOSTART TRACK 1 0 ZOOM 16 COLOR DEAD Lime COLOR DEADRAMP Green GPS 4 ]]

Expected: Alive 64 -> Dead 1
Actual: Alive 64 -> Dead 63 -> Dead 62 -> Dead 1

HISTORYSTATES 2:

Code: Select all

x = 3, y = 4, rule = B2/S
o$2bo$2bo$o!
[[ HISTORYSTATES 2 GRID LAYERS 10 AUTOSTART TRACK 1 0 ZOOM 16 COLOR DEAD Lime COLOR DEADRAMP Green GPS 4 ]]

Code: Select all

x = 3, y = 4, rule = R1,C2,S,B2
o$2bo$2bo$o!
[[ HISTORYSTATES 2 GRID LAYERS 10 AUTOSTART TRACK 1 0 ZOOM 16 COLOR DEAD Lime COLOR DEADRAMP Green GPS 4 ]]

Expected: Alive 64 -> Dead 63 -> Dead 1
Actual: Alive 64 -> Dead 63 -> Dead 62 -> Dead 61 -> Dead 1

HISTORYSTATES 3:

Code: Select all

x = 3, y = 4, rule = B2/S
o$2bo$2bo$o!
[[ HISTORYSTATES 3 GRID LAYERS 10 AUTOSTART TRACK 1 0 ZOOM 16 COLOR DEAD Lime COLOR DEADRAMP Green GPS 4 ]]

Code: Select all

x = 3, y = 4, rule = R1,C2,S,B2
o$2bo$2bo$o!
[[ HISTORYSTATES 3 GRID LAYERS 10 AUTOSTART TRACK 1 0 ZOOM 16 COLOR DEAD Lime COLOR DEADRAMP Green GPS 4 ]]

Expected: Alive 64 -> Dead 63 -> Dead 62 -> Dead 1
Actual: Alive 64 -> Dead 63 -> Dead 62 -> Dead 61 -> Dead 60 -> Dead 1

In all cases above 0 and sufficiently below the default, there are generally two more history states than there should be, having the same colour as Dead 1 but not actually being that state.

Posted: **August 14th, 2025, 9:33 am**

confocaloid wrote: September 26th, 2024, 3:15 am p398 mod199 diagonal 3c/199 push-spaceship, glider+block recollision
Code: Select all
x = 13, y = 16, rule = B3-ck4eq5aij6ei7e/S23-cky4t5n8
bo$2bo$3o12$11b2o$11b2o!
#C [[ ZOOM 8 THEME MCell GRID TRACKLOOP 398 6/398 6/398 ]]

This viewer is causing errors from non-existent commands and HTML code of unknown origin that seem to get interpreted as commands in chrome on iOS 18.6.
The error only seems to happen on that post, not a quote.

Posted: **August 18th, 2025, 7:19 am**

The largest possible bounded grid size is 16352 (via MAXGRIDSIZE 14); anything larger than this will cause an error.

Code: Select all

x = 3, y = 3, rule = B3/S23:P16352
o$obo$2o!
[[ MAXGRIDSIZE 14 SHADER Basic ]]

However, for some reason, any value from 16353 to 16379 inclusive is still considered "acceptable" in that we get a SHOW IN VIEWER link rather than SHOW PATTERN ERROR, even though from my testing you can never get a bounded grid of this size.

Code: Select all

x = 3, y = 3, rule = B3/S23:P16353
o$obo$2o!
[[ MAXGRIDSIZE 14 SHADER Basic ]]

Code: Select all

x = 3, y = 3, rule = B3/S23:P16379
o$obo$2o!
[[ MAXGRIDSIZE 14 SHADER Basic ]]

Code: Select all

x = 3, y = 3, rule = B3/S23:P16380
o$obo$2o!
[[ MAXGRIDSIZE 14 SHADER Basic ]]

For the general-range algorithm the upper limit appears to be 16377:

Code: Select all

x = 3, y = 3, rule = R1,C2,S2-3,B3:P16377
o$obo$2o!
[[ MAXGRIDSIZE 14 SHADER Basic ]]

Code: Select all

x = 3, y = 3, rule = R1,C2,S2-3,B3:P16378
o$obo$2o!
[[ MAXGRIDSIZE 14 SHADER Basic ]]

This seems to indicate that, at the very least, bounded grid sizes 16378 and 16379 should also produce SHOW PATTERN ERROR links. Is it even possible to validate bounded grid size before loading the pattern, and provide such an error sooner?

I also want to know if the old error message that indicates the maximum possible bounded grid size for the specified rule could be returned since this would be useful in cases like these.

Posted: **August 18th, 2025, 9:32 am**

muzik wrote: August 18th, 2025, 7:19 am
Code: Select all
x = 3, y = 3, rule = R1,C2,S2-3,B3
o$obo$2o!
[[ SHADER Basic ]]

Why is it not using the basic shader?

Posted: **August 19th, 2025, 3:02 am**

Resu wrote: August 18th, 2025, 9:32 am Why is it not using the basic shader?

Because Shaders are only supported for the range 1 algo (and ignored for others).

Posted: **August 28th, 2025, 5:13 am**

Is snow simulation tied to refresh rate? It seems to fall easily twice as fast on 144hz compared to 60hz. (Also not sure if "New pattern" should be displayed via NOGUI, since there isn't exactly a way to make it not new.)

Code: Select all

x = 1, y = 1, rule = B/S
!
[[ SNOW NOGUI ]]

The following arrangement of escaping gliders is not killed at all even though it should be (removing any one of these gliders will eventually kill the rest of them):

Code: Select all

x = 116, y = 90, rule = B3/S23
113b2o$113bobo$113bo5$80b2o$79b2o$81bo71$34bo$33b2o$33bobo5$2o$obo$o!
[[ KILLGLIDERS ]]

Three of the bounded grid edges are covered by history cells, but the top one is not, even though with this pattern you'd expect all of them to be treated the same. (Perhaps only living cells should appear on top of grid boundaries, and history states should appear underneath instead?)

Code: Select all

x = 1, y = 4, rule = M0,4,8,3,1,10,6,7,2,9,5,11,12,13,14,15:T256,254
o3$o!
[[ ZOOM -4 STARTFROM 32512 ]]

Posted: **August 28th, 2025, 12:54 pm**

muzik wrote: August 28th, 2025, 5:13 am Three of the bounded grid edges are covered by history cells, but the top one is not, even though with this pattern you'd expect all of them to be treated the same. (Perhaps only living cells should appear on top of grid boundaries, and history states should appear underneath instead?)

This appears to merely be an artifact of being zoomed out - it's the same whether you run the pattern manually or let it go to that generation, but zooming further in reveals the edges are not actually covered.

Posted: **August 28th, 2025, 6:26 pm**

rabbit wrote: August 28th, 2025, 12:54 pm This appears to merely be an artifact of being zoomed out - it's the same whether you run the pattern manually or let it go to that generation, but zooming further in reveals the edges are not actually covered.

It's indeed an artifact, but could been fixed by simply making the boundary cells display over history, or make history unable to go beyond bounds.

Posted: **August 30th, 2025, 11:21 am**

When identifying some hexagonal oscillators which are sufficiently large that the grid can't be displayed on the period/frequency map, every group of two rows is sequentially shifted rightward. This is a reasonable approach if you're very zoomed out, but for cases like the following where there's only just barely not enough room to show it with the grid (in fact, in this case, whether the grid is shown or not depends on whether the browser tabs are displayed) it looks displeasingly rough and asymmetric. Compare how smooth the left side looks versus how rough the right side is, despite them in actuality being equivalent in shape on the actual hexagonal grid:

Code: Select all

x = 15, y = 23, rule = B2o3-o4-m56/S2m3o4-o56H
b2o$o3bo$b4o$2bobo$3b2o14$10b2o$10bobo$10b4o$10bo3bo$12b2o!
[[ AUTOIDENTIFY THEME Red ]]

: IMG_0961.jpeg (285.69 KiB) Viewed 671 times

Was thinking of a way to make this look better and I came up with the following solution. Take the map, the way it exists on a normal square grid:

Code: Select all

x = 37, y = 45, rule = B/S0123HT
7bo$7b2o$bo4b5o4bo$4ob8ob4o$19o$20o$b19o$b20o$2b19o$3b18o$3b19o$3b20o
$4b19o$5b18o$5b19o$5b20o$b29o$32o$33o$34o$b33o$b34o$2b33o$2b34o$3b33o
$3b34o$4b33o$5b32o$7b29o$12b20o$13b19o$14b18o$14b19o$14b20o$15b19o$16b
18o$16b19o$16b20o$17b19o$17b20o$18b19o$19b4ob8ob4o$21bo4b5o4bo$28b2o$
29bo!

Code: Select all

x = 37, y = 45, rule = B/S01234V
7bo$7b2o$bo4b5o4bo$4ob8ob4o$19o$20o$b19o$b20o$2b19o$3b18o$3b19o$3b20o
$4b19o$5b18o$5b19o$5b20o$b29o$32o$33o$34o$b33o$b34o$2b33o$2b34o$3b33o
$3b34o$4b33o$5b32o$7b29o$12b20o$13b19o$14b18o$14b19o$14b20o$15b19o$16b
18o$16b19o$16b20o$17b19o$17b20o$18b19o$19b4ob8ob4o$21bo4b5o4bo$28b2o$
29bo!

Insert a gap between each column:

Code: Select all

x = 73, y = 45, rule = B/S01234V
14bo$14bobo$2bo9bobobobobo9bo$obobobo3bobobobobobobobo3bobobobo$obobo
bobobobobobobobobobobobobobobobo$obobobobobobobobobobobobobobobobobob
obo$2bobobobobobobobobobobobobobobobobobobo$2bobobobobobobobobobobobo
bobobobobobobobo$4bobobobobobobobobobobobobobobobobobobo$6bobobobobob
obobobobobobobobobobobobo$6bobobobobobobobobobobobobobobobobobobo$6bo
bobobobobobobobobobobobobobobobobobobo$8bobobobobobobobobobobobobobob
obobobobo$10bobobobobobobobobobobobobobobobobobo$10bobobobobobobobobo
bobobobobobobobobobo$10bobobobobobobobobobobobobobobobobobobobo$2bobo
bobobobobobobobobobobobobobobobobobobobobobobobobobobo$obobobobobobob
obobobobobobobobobobobobobobobobobobobobobobobobo$obobobobobobobobobo
bobobobobobobobobobobobobobobobobobobobobobobo$obobobobobobobobobobob
obobobobobobobobobobobobobobobobobobobobobobo$2bobobobobobobobobobobo
bobobobobobobobobobobobobobobobobobobobobobo$2bobobobobobobobobobobob
obobobobobobobobobobobobobobobobobobobobobobo$4bobobobobobobobobobobo
bobobobobobobobobobobobobobobobobobobobobobo$4bobobobobobobobobobobob
obobobobobobobobobobobobobobobobobobobobobobo$6bobobobobobobobobobobo
bobobobobobobobobobobobobobobobobobobobobobo$6bobobobobobobobobobobob
obobobobobobobobobobobobobobobobobobobobobobo$8bobobobobobobobobobobo
bobobobobobobobobobobobobobobobobobobobobobo$10bobobobobobobobobobobo
bobobobobobobobobobobobobobobobobobobobobo$14bobobobobobobobobobobobo
bobobobobobobobobobobobobobobobobo$24bobobobobobobobobobobobobobobobo
bobobobo$26bobobobobobobobobobobobobobobobobobobo$28bobobobobobobobob
obobobobobobobobobo$28bobobobobobobobobobobobobobobobobobobo$28bobobo
bobobobobobobobobobobobobobobobobo$30bobobobobobobobobobobobobobobobo
bobobo$32bobobobobobobobobobobobobobobobobobo$32bobobobobobobobobobob
obobobobobobobobo$32bobobobobobobobobobobobobobobobobobobobo$34bobobo
bobobobobobobobobobobobobobobobo$34bobobobobobobobobobobobobobobobobo
bobobo$36bobobobobobobobobobobobobobobobobobobo$38bobobobo3bobobobobo
bobobo3bobobobo$42bo9bobobobobo9bo$56bobo$58bo!

Starting from the top, shift everything over by one cell to the right:

Code: Select all

x = 67, y = 45, rule = B/S01234V
33bo$32bobo$19bo9bobobobobo9bo$16bobobobo3bobobobobobobobo3bobobobo$15b
obobobobobobobobobobobobobobobobobobo$14bobobobobobobobobobobobobobob
obobobobobo$15bobobobobobobobobobobobobobobobobobobo$14bobobobobobobo
bobobobobobobobobobobobobo$15bobobobobobobobobobobobobobobobobobobo$16b
obobobobobobobobobobobobobobobobobo$15bobobobobobobobobobobobobobobob
obobobo$14bobobobobobobobobobobobobobobobobobobobo$15bobobobobobobobo
bobobobobobobobobobobo$16bobobobobobobobobobobobobobobobobobo$15bobob
obobobobobobobobobobobobobobobobo$14bobobobobobobobobobobobobobobobob
obobobo$5bobobobobobobobobobobobobobobobobobobobobobobobobobobobobo$2b
obobobobobobobobobobobobobobobobobobobobobobobobobobobobobobobo$bobob
obobobobobobobobobobobobobobobobobobobobobobobobobobobobobobo$obobobo
bobobobobobobobobobobobobobobobobobobobobobobobobobobobobobo$bobobobo
bobobobobobobobobobobobobobobobobobobobobobobobobobobobobo$obobobobob
obobobobobobobobobobobobobobobobobobobobobobobobobobobobo$bobobobobob
obobobobobobobobobobobobobobobobobobobobobobobobobobobo$obobobobobobo
bobobobobobobobobobobobobobobobobobobobobobobobobobobo$bobobobobobobo
bobobobobobobobobobobobobobobobobobobobobobobobobobo$obobobobobobobob
obobobobobobobobobobobobobobobobobobobobobobobobobo$bobobobobobobobob
obobobobobobobobobobobobobobobobobobobobobobobobo$2bobobobobobobobobo
bobobobobobobobobobobobobobobobobobobobobobobo$5bobobobobobobobobobob
obobobobobobobobobobobobobobobobobobo$14bobobobobobobobobobobobobobob
obobobobobo$15bobobobobobobobobobobobobobobobobobobo$16bobobobobobobo
bobobobobobobobobobobo$15bobobobobobobobobobobobobobobobobobobo$14bob
obobobobobobobobobobobobobobobobobobo$15bobobobobobobobobobobobobobob
obobobobo$16bobobobobobobobobobobobobobobobobobo$15bobobobobobobobobo
bobobobobobobobobobo$14bobobobobobobobobobobobobobobobobobobobo$15bob
obobobobobobobobobobobobobobobobobo$14bobobobobobobobobobobobobobobob
obobobobo$15bobobobobobobobobobobobobobobobobobobo$16bobobobo3bobobob
obobobobo3bobobobo$19bo9bobobobobo9bo$32bobo$33bo!

Then create a copy of the map shifted orthogonally by one cell:

Code: Select all

x = 68, y = 45, rule = B/S01234V
33b2o$32b4o$19b2o8b10o8b2o$16b8o2b16o2b8o$15b38o$14b40o$15b38o$14b40o
$15b38o$16b36o$15b38o$14b40o$15b38o$16b36o$15b38o$14b40o$5b58o$2b64o$
b66o$68o$b66o$68o$b66o$68o$b66o$68o$b66o$2b64o$5b58o$14b40o$15b38o$16b
36o$15b38o$14b40o$15b38o$16b36o$15b38o$14b40o$15b38o$14b40o$15b38o$16b
8o2b16o2b8o$19b2o8b10o8b2o$32b4o$33b2o!

What we have now is a period map where each oscillator cell is represented by two pixels, and cells are in the natural staggered brickwall order you'd expect of the hexagonal grid. Obviously this is very stretched, but the solution is simple: when displaying it in LifeViewer, you'd just squish it inwards by a factor of 2, like is done to vertically stretch triangular-grid period maps, using a scaling method that doesn't introduce blur. The results, at least to my understanding, should look far better at scales like this. (Wouldn't surprise me if this has been thought of already before, though.)

ConwayLife.com

Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads