Pattern viewer for forum threads

[rowett]

There are still borders visible between triangular cells (forming a sort of rhombic tiling) even with cellborders disabled

True due to the vagaries of the browser's rendering. I'll have another go at some stage.

Hexagons also seem to intersect each other slightly with cellborders turned off

Ditto.

Just one more neighbourhood suggestion: how about a 15-cell neighbourhood that also includes these three cells at the very tips, giving a perfect triangle instead of a wonky hexagon?

Not planned.

[rowett]

There are still borders visible between triangular cells (forming a sort of rhombic tiling) even with cellborders disabled

This should be better now.

[muzik]

There are still borders visible between triangular cells (forming a sort of rhombic tiling) even with cellborders disabled

This should be better now.

Still faintly visible, but far better than before.

[muzik]

Will it be possible to determine cell border thickness?

[Ian07]

Could the "Ctrl+C to copy pattern" thing be put in a more obvious spot, perhaps by "Click to control" when you hover over the viewer? It's such a useful command (especially on the wiki) that it probably shouldn't be buried so far down in the help menu; it took me several months before I even bothered to try it out.

[muzik]

An idea I've had for a while: for rules with aliases, when the T counter in the bottom left is clicked, could the alias text link to the rule's Catagolue page?

[rowett]

Build 320 is now live on the Forums and LifeWiki

Please note: you will need to refresh your browser to use the new build (Ctrl-F5 on Chrome)

Enhancements since the last released build:

• support for Triangular neighbourhoods - examples
  • The following three neighbourhoods are supported:
    • Triangular (postfix L) with 12 neighbours (touching triangle edges and vertices)
      • neighbourhood digits are 0123456789XYZ where X, Y and Z represent 10, 11 and 12 respectively
    • Triangular Edges (postfix LE) with 3 neighbours (touching triangle edges)
      • neighbourhood digits are 0123
    • Triangular Vertices (postfix LV) with 9 neighbours (touching triangle vertices)
      • neighbourhood digits are 0123456789
  • Generations rules are supported
  • B0 emulation is supported
  • Bounded Grids are supported for Plane or Torus
    • width and height both must be even
    • other bounded grid types will come in a future build
  • At ZOOM levels >= 4 the cells will be displayed as triangles

    Code: Select all

    x = 8, y = 6, rule = B34/S34/10L:T100,50
    bo3bo$bo4bo$b2o4bo$2bo5bo$2bo5bo$3b2ob2o!
    [[ ZOOM 5.2 ]]

• cells can now be displayed with a border
  • new bottom-right menu button Border to toggle cell border display
  • hotkey Alt and "X" to toggle
  • new script command [[ CELLBORDERS ]] to turn cell borders on

    Code: Select all

    #C [[ CELLBORDERS ]]
    x = 71, y = 55, rule = B013568S01History
    2.2B2.B.4B$2.10B2.4B$.17B$.17B$.18B$4BA4BA10B$4B2AB3A9B$3B2A3BA9B$.4B
    ABA11B$2.17B2.4B$2.23B$2.23B$2.24B$3.24B$4.22B$4.21B$5.21B$5.21B2.4B$
    6.26B$6.26B$6.2B.24B$6.2B2.24B$11.22B$11.21B$12.21B$12.21B2.4B$13.26B
    $13.26B$13.2B.24B$13.2B2.24B$18.22B$18.21B$19.21B$19.21B$20.20B$20.
    20B13.3D2.5D3.3D$20.2B.18B11.D9.D2.D3.D$20.2B2.8BC4BC3B4.D5.D10.D6.D$
    25.7B2CB3C2B5.D5.D9.D7.D$25.6B2C3BC4B2.5D3.4D6.D6.D$26.7BCBC5B4.D5.D
    3.D4.D6.D$26.15B4.D5.D3.D4.D5.D$27.14B10.D3.D3.D5.D$27.13B12.3D4.D5.
    5D$27.2B.8B$27.2B$44.D14.D$44.D4.D9.D$44.D14.D$42.5D2.D3.3D3.D3.D3.3D
    $44.D4.D2.D3.D2.D2.D3.D3.D$44.D4.D2.D6.3D4.D$44.D4.D2.D6.D.D5.3D$44.D
    4.D2.D3.D2.D2.D7.D$44.D4.D3.3D3.D3.D3.3D!
    

Fixes since the last released build:

• step back was not working correctly every 50 generations
• drawing cells wasn't correctly updating the tile map

The updated hotkey map detailing the LifeViewer keyboard controls is here.

Comments, feedback, suggestions and bug reports welcome!

[Gamedziner]

Drawing on the triangular grid seems to act as if the triangles were squares.

[muzik]

The viewer seems to be scaling bordered hexagons a lot weirder and blobbier as of late.

Build 316: https://cdn.discordapp.com/attachments/ ... image0.png

Build 320: https://cdn.discordapp.com/attachments/ ... image1.png

[rowett]

Drawing on the triangular grid seems to act as if the triangles were squares.

True. The drawing routines don't know about triangles yet. It's also true for hexagons but less easy to spot because they're more square.

[toroidalet]

Non-totalistic rules whose strings end with t (as in 4t) are interpreted as triangular:

Code: Select all

x = 10, y = 3, rule = B3/S234t
o8bo$b2o6bo$2o7bo!

Code: Select all

x = 10, y = 3, rule = B3-c/S234t
o8bo$b2o6bo$2o7bo!

One solution to this would be to change the triangular rule suffix to "TR", meaning only badly formatted rulestrings will be parsed this way.
Also the lower pattern seems to be shifted when I open it.

[rowett]

Non-totalistic rules whose strings end with t (as in 4t) are interpreted as triangular:

Code: Select all

x = 10, y = 3, rule = B3/S234t
o8bo$b2o6bo$2o7bo!

Code: Select all

x = 10, y = 3, rule = B3-c/S234t
o8bo$b2o6bo$2o7bo!

One solution to this would be to change the triangular rule suffix to "TR", meaning only badly formatted rulestrings will be parsed this way.

Good catch! Unfortunately "TR" won't work either since both "t" and "r" are valid non-totalistic modifiers. It also means that "TE" needs changing since "e" is also a valid non-totalistic modifier.

I'll probably change the "T" to "L" (which is available) and so the three neighbourhoods will become:

• Triangular (postfix L) with 12 neighbours (touching triangle edges and vertices)
  neighbourhood digits are 0123456789XYZ where X, Y and Z represent 10, 11 and 12 respectively
• Triangular Edges (postfix LE) with 3 neighbours (touching triangle edges)
  neighbourhood digits are 0123
• Triangular Vertices (postfix LV) with 9 neighbours (touching triangle vertices)
  neighbourhood digits are 0123456789

[rowett]

Build 321 is now live on the Forums and LifeWiki

Please note: you will need to refresh your browser to use the new build (Ctrl-F5 on Chrome)

Fixes since the last released build:

• changed neighbourhood postfixes from T, TE, TV to L, LE, LV

The updated hotkey map detailing the LifeViewer keyboard controls is here.

Comments, feedback, suggestions and bug reports welcome!

[muzik]

Will LTL be able to support higher-range hexagonal neighbourhoods?

Code: Select all

x = 12, y = 18, rule = B/S0123456H
bo7b3o8b3o$bo9bo10bo$bo7b3o8b3o$bo7bo12bo$bo7b3o8b3o4$20b4o$9b3o8b5o$
2o7b4o7b6o$obo6b2ob2o6b3ob3o$b2o7b4o7b6o$11b3o8b5o$23b4o!

[rowett]

Build 322 is now live on the Forums and LifeWiki

Please note: you will need to refresh your browser to use the new build (Ctrl-F5 on Chrome)

Fixes since the last released build:

• improved hexagonal cell drawing
• fix for LV neighbourhood

The updated hotkey map detailing the LifeViewer keyboard controls is here.

Comments, feedback, suggestions and bug reports welcome!

[rowett]

Will LTL be able to support higher-range hexagonal neighbourhoods?

Not planned. Plus it doesn't support range 1 hexagonal.

[Gamedziner]

The triangles seem to flatten into squares when you zoom out far enough (~4.0x zoom)

[rowett]

The triangles seem to flatten into squares when you zoom out far enough (~4.0x zoom)

Actually they become squares below 4x zoom. It's the same for hexagons.
That's also the zoom limit for displaying grid lines (if enabled).

[muzik]

For alternating rules, capitalization of the rule name in the bottom-left menu seems to use the one provided in the rulename instead of what exists in the alias list:

Code: Select all

x = 2, y = 3, rule = Jelly
o$2o$o!

Code: Select all

x = 2, y = 3, rule = jelly
o$2o$o!

Other rule families seem to work normally.

[rowett]

For alternating rules, capitalization of the rule name in the bottom-left menu seems to use the one provided in the rulename instead of what exists in the alias list

Fixed in the next build, thanks.

[muzik]

Will lifeviewer be able to simulate multistate one-dimensional rules?
https://www.wolframalpha.com/input/?i=r ... 181,+k%3D3

[Hunting]

An old bug:

Code: Select all

x = 8, y = 32, rule = B3/S23:T8,0
4bo$3b3o3$3b3o$4bo4$4bo$4bo$2bo3bo$b3ob3o$b3ob3o$bobobobo$2b2ob2o$2b2o
b2o4$3b3o2$3bobo$4bo2$2o5bo2$2b5o4$8o!
#C [[ AUTOFIT ]]

And a new bug:

Code: Select all

x = 1, y = 1, rule = W18
o!

[muzik]

Idea I've had for a long while:

Instead of having defined aliases for Replicator-type rules of range n (e.g. Replicator R4, Fredkin R2), why not treat the rule names themselves as a form of rulestring?

A rulestring Replicator Rn would set both birth and survival transitions to all odd numbers 1 through (2n+1)²-2, and Fredkin Rn would set birth transitions to to all odd numbers 1 through (2n+1)² and survival transitions to all even numbers 0 through (2n+1)²-1.

This would be especially useful for higher-order replicator rules whose rulestrings may be too long to even fit into a forum post.

[fluffykitty]

All of those are just instances of the general family where a cell is set to the XOR of all cells in a certain neighborhood. Replicator uses an 8-cell neighborhood, Fredkin uses a 9-cell neighborhood, etc.

[muzik]

Will any uniform tilings such as r{6,3} ever be supported in the near future?