### Re: Lifeviewer Bugs

Posted:

**August 1st, 2024, 6:08 am**Page **19** of **19**

Posted: **August 1st, 2024, 6:08 am**

Posted: **August 1st, 2024, 6:09 am**

The glider should turn red gradually, but an error message came up.

Code: Select all

```
x = 5, y = 5, rule = ColourisedLife27s
3o$o$bo!
[[ T 1 COLOR 1 0 0 255 ]]
[[ T 100 COLOR 1 255 0 0 ]]
```

Posted: **August 1st, 2024, 6:31 am**

I already answered this in another thread.Citation needed wrote: ↑August 1st, 2024, 6:09 amThe glider should turn red gradually, but an error message came up.Code: Select all

`x = 5, y = 5, rule = ColourisedLife27s 3o$o$bo! [[ T 1 COLOR 1 0 0 255 ]] [[ T 100 COLOR 1 255 0 0 ]]`

Posted: **August 1st, 2024, 8:11 am**

Will this bug be fixed in the future?Citation needed wrote: ↑August 1st, 2024, 6:09 amThe glider should turn red gradually, but an error message came up.Code: Select all

`x = 5, y = 5, rule = ColourisedLife27s 3o$o$bo! [[ T 1 COLOR 1 0 0 255 ]] [[ T 100 COLOR 1 255 0 0 ]]`

If so, it would be an excellent feature.

Posted: **August 4th, 2024, 5:27 pm**

I'll put it on the backlog. It's not high priority so it may be a long time before it's added.

Posted: **August 5th, 2024, 12:16 am**

And LifeViewer can't laod ruletables:

(edit:But this work?)
When T=0, some [R]History cells look like this:

(edit:But this work?)

Code: Select all

```
x = 1, y = 1, rule = HMtest
!
@RULE HMtest
@TABLE
n_states:7
neighborhood:hexagonal
symmetries:none
var a={0,1,2,3,4,5,6}
var s=a
var d=a
var f=a
var g=a
var h=a
#m birth
1,a,s,6,5,d,f,5
2,4,6,a,s,d,f,6
3,a,s,d,f,5,4,4
#m die
4,a,s,3,5,d,f,2
5,1,6,a,s,d,f,3
6,a,s,d,f,2,4,1
#else m sur...
1,a,s,d,f,g,h,2
2,a,s,d,f,g,h,3
3,a,s,d,f,g,h,1
4,a,s,d,f,g,h,5
5,a,s,d,f,g,h,6
6,a,s,d,f,g,h,4
@COLORS
0 0 0 0
1 127 127 127
2 74 74 74
3 74 74 74
4 0 255 0
5 0 205 0
6 0 155 0
```

Posted: **August 5th, 2024, 1:20 am**

Posted: **August 6th, 2024, 12:34 am**

In build 1185, when selecting some area, future events can depend on the direction in which the selection was performed. The expected behaviour is that the direction of performing a selection should not affect any future events.

- Select the state-3 Herschel by a movement diagonally from top-left to bottom-right, then press Ctrl+Space to advance selection by one tick. It works.
- Select the state-3 Herschel by a movement diagonally from bottom-right to top-left, then press Ctrl+Space to advance selection by one tick. It fails with "No live cells to select".
- Select the state-3 Herschel by a movement diagonally from bottom-left to top-right, then press Ctrl+Space to advance selection by one tick. It fails with "No live cells to select".
- Select the state-3 Herschel by a movement diagonally from top-right to bottom-left, then press Ctrl+Space to advance selection by one tick. It fails with "No live cells to select".

confocaloid wrote: ↑August 6th, 2024, 12:27 am[...]Code: Select all

`x = 55, y = 57, rule = LifeHistory 8.D3.D.D3.D2.3D3.3D2.5D3.D4.3D5.D$8.2D2.D.D3.D.D3.D.D7.D4.2D3.D3.D3. 2D$8.D.D.D.D3.D5.D.D7.D5.D3.D3.D2.D.D$8.D2.2D.D.D.D4.D2.4D4.D5.D4.3D 2.D2.D$8.D3.D.D.D.D3.D3.D3.D3.D5.D3.D3.D.5D$8.D3.D.2D.2D2.D4.D3.D3.D 5.D3.D3.D4.D$8.D3.D.D3.D.5D2.3D4.D4.3D3.3D5.D5$4B$.4B$2.4B$3.4B$4.4B$ 5.4B$6.4B$7.4B$8.4B7.A$9.4B6.3A$10.4B8.A$11.4B6.2A$12.4B5.6B12.A$13. 4B6.5B9.3A$14.4B4.7B7.A9.2A$15.4B2.8B7.2A8.A.A$16.14B2.2B.3B3.2A5.A$ 17.21B.BA.AB3.2A.2A$13.2A3.22B2A2B2.B.A.A$14.A4.25B.3A2.A$14.A.AB.23B .BAB2.2A$15.2A22B4.B4A$16.17B.4B5.B.B.A$18.19B7.2A.A.A$9.A10.16B9.A2. 2A$9.3A8.15B8.A.A$12.A7.14B9.2A$11.2A3.B3.13B$11.8B.12B$13.18B$13.17B $12.17B$10.18B$8.19B$8.2BC15B$7.3BCBC4B.9B$8.2B3C4B2.7B$7.5BC4B4.5B$ 6.10B3.5B$5.4B10.2A$5.3B12.A$3.4B10.3A$3.2A12.A$4.A$.3A$.A!`

Posted: **August 6th, 2024, 5:01 am**

Fixed in build 1186. Thanks for reporting!confocaloid wrote: ↑August 6th, 2024, 12:34 amIn build 1185, when selecting some area, future events can depend on the direction in which the selection was performed.

Posted: **August 10th, 2024, 2:15 pm**

Some icons are not showing up.

Posted: **August 12th, 2024, 7:58 pm**

Codd suddenly stopped working. Also, I kept getting signed out of LifeWiki just now.

**EDIT:** It worked on the phone.

Posted: **August 13th, 2024, 4:15 am**

Which browser and device are you using?

Posted: **August 13th, 2024, 4:16 am**

It's probably related to the "general errors" that have been appearing on the forums recently.Citation needed wrote: ↑August 12th, 2024, 7:58 pmCodd suddenly stopped working. Also, I kept getting signed out of LifeWiki just now.

Posted: **August 20th, 2024, 7:55 pm**

Crossposting what appears to be a LifeViewer bug (build 1191).

The rulestring "R2,C2,S,B0,2-3,8,NW0101010001000001000101010" appears to be translated into an alternating CA:
which doesn't match how the strobing CA with B0 but not Smax is supposed to work, and doesn't match how it works in Golly 4.3.

Changing to use custom neighbourhood (N@) instead of weighted neighbourhood also changes evolution of the patterns in LifeViewer build 1191.

The rulestring "R2,C2,S,B0,2-3,8,NW0101010001000001000101010" appears to be translated into an alternating CA:

Code: Select all

`R2,C0,S1,6-7,B,N@54422a|R2,C0,S1-8,B1,4-7,N@54422a`

Changing to use custom neighbourhood (N@) instead of weighted neighbourhood also changes evolution of the patterns in LifeViewer build 1191.

CARuler wrote: ↑August 20th, 2024, 6:46 pmThis is the best rule of its kind that I could find:Edit:Code: Select all

`x = 255, y = 186, rule = R2,C2,S,B0,2-3,8,NW0101010001000001000101010 [...]`

oscillator:Edit2:Code: Select all

`x = 3, y = 4, rule = R2,C2,S,B0,2-3,8,NW0101010001000001000101010 o$2bo$o$2bo!`

this rule certainly has engineering potentialCode: Select all

`x = 5, y = 4, rule = R2,C2,S,B0,2-3,8,NW0101010001000001000101010 o3bo$bo2$4bo!`

confocaloid wrote: ↑August 20th, 2024, 6:59 pm[...] When evolving the original pattern in LifeViewer build 1191, I believe the following rules areactuallyfollowed:

- for odd generations, use B14567/S12345678;
- for even generations, use B/S167.
TL,DR: so far it seems to be a LifeViewer bug. When fixed, the rulestring you specified will no longer be interpreted to refer to the same cellular automaton, and the patterns will no longer work the same way. It seems like your CA can be equivalently defined in the following way:Code: Select all

`x = 60, y = 60, rule = R2,C0,S1,6-7,B,N@54422a|R2,C0,S1-8,B1,4-7,N@54422a 20bo3bo10bo3bo2$21bo16bo6$20bo18bo12$o7bo42bo7bo$2bo54bo3$o58bo11$o58b o3$2bo54bo$o7bo42bo7bo12$20bo18bo6$21bo16bo2$20bo3bo10bo3bo!`

Code: Select all

`R2,C0,S1,6-7,B,N@54422a|R2,C0,S1-8,B1,4-7,N@54422a`

Posted: **August 24th, 2024, 4:02 pm**

In case fixing this appears to be too complicated at the moment, could you please temporarily disable support for CA with both B0 and weighted neighbourhood (NW), until this is corrected? The reason is that people are unknowingly posting patterns which rely on an incorrect interpretation of a rulestring with B0 and NW.confocaloid wrote: ↑August 20th, 2024, 7:55 pmCrossposting what appears to be a LifeViewer bug (build 1191).

The rulestring "R2,C2,S,B0,2-3,8,NW0101010001000001000101010" appears to be translated into an alternating CA:which doesn't match how the strobing CA with B0 but not Smax is supposed to work, and doesn't match how it works in Golly 4.3.Code: Select all

`R2,C0,S1,6-7,B,N@54422a|R2,C0,S1-8,B1,4-7,N@54422a`

[...]

Posted: **August 25th, 2024, 1:10 am**

Can you disable emulation on B0 NW rules? They will only work on bounded grids.confocaloid wrote: ↑August 24th, 2024, 4:02 pmIn case fixing this appears to be too complicated at the moment, could you please temporarily disable support for CA with both B0 and weighted neighbourhood (NW), until this is corrected? The reason is that people are unknowingly posting patterns which rely on an incorrect interpretation of a rulestring with B0 and NW.confocaloid wrote: ↑August 20th, 2024, 7:55 pmCrossposting what appears to be a LifeViewer bug (build 1191).

The rulestring "R2,C2,S,B0,2-3,8,NW0101010001000001000101010" appears to be translated into an alternating CA:which doesn't match how the strobing CA with B0 but not Smax is supposed to work, and doesn't match how it works in Golly 4.3.Code: Select all

`R2,C0,S1,6-7,B,N@54422a|R2,C0,S1-8,B1,4-7,N@54422a`

[...]

Posted: **August 26th, 2024, 4:06 am**

Done.confocaloid wrote: ↑August 24th, 2024, 4:02 pmcould you please temporarily disable support for CA with both B0 and weighted neighbourhood (NW), until this is corrected?

Posted: **August 26th, 2024, 5:03 am**

Can rowett allow B0 NW rules on finite grids (confocaloid wrote: ↑August 20th, 2024, 7:55 pmCrossposting what appears to be a LifeViewer bug (build 1191).

The rulestring "R2,C2,S,B0,2-3,8,NW0101010001000001000101010" appears to be translated into an alternating CA:which doesn't match how the strobing CA with B0 but not Smax is supposed to work, and doesn't match how it works in Golly 4.3.Code: Select all

`R2,C0,S1,6-7,B,N@54422a|R2,C0,S1-8,B1,4-7,N@54422a`

Changing to use custom neighbourhood (N@) instead of weighted neighbourhood also changes evolution of the patterns in LifeViewer build 1191.

CARuler wrote: ↑August 20th, 2024, 6:46 pmThis is the best rule of its kind that I could find:Edit:Code: Select all

`x = 255, y = 186, rule = R2,C2,S,B0,2-3,8,NW0101010001000001000101010 [...]`

oscillator:Edit2:Code: Select all

`x = 3, y = 4, rule = R2,C2,S,B0,2-3,8,NW0101010001000001000101010 o$2bo$o$2bo!`

this rule certainly has engineering potentialCode: Select all

`x = 5, y = 4, rule = R2,C2,S,B0,2-3,8,NW0101010001000001000101010 o3bo$bo2$4bo!`

confocaloid wrote: ↑August 20th, 2024, 6:59 pm[...] When evolving the original pattern in LifeViewer build 1191, I believe the following rules areactuallyfollowed:

- for odd generations, use B14567/S12345678;
- for even generations, use B/S167.
TL,DR: so far it seems to be a LifeViewer bug. When fixed, the rulestring you specified will no longer be interpreted to refer to the same cellular automaton, and the patterns will no longer work the same way. It seems like your CA can be equivalently defined in the following way:Code: Select all

`x = 60, y = 60, rule = R2,C0,S1,6-7,B,N@54422a|R2,C0,S1-8,B1,4-7,N@54422a 20bo3bo10bo3bo2$21bo16bo6$20bo18bo12$o7bo42bo7bo$2bo54bo3$o58bo11$o58b o3$2bo54bo$o7bo42bo7bo12$20bo18bo6$21bo16bo2$20bo3bo10bo3bo!`

Code: Select all

`R2,C0,S1,6-7,B,N@54422a|R2,C0,S1-8,B1,4-7,N@54422a`

Posted: **August 26th, 2024, 5:20 am**

Why are you repeatedly posting unnecessary ridiculously long quotes, followed by short replies?

This case in particular is ridiculous, because you're basically directing at me questions that only the developer and maintainer of LifeViewer can possibly answer.

@unname4798 I will likely silently report any further posts from you that contain unnecessary overly long quotes, as violations of the forum rule that says that unnecessarily long/nested quotes should be avoided.

Posted: **August 26th, 2024, 7:35 am**

Can rowett allow B0 NW rules on a finite grid (without emulation)?

Posted: **August 26th, 2024, 3:30 pm**

Probably not. I don't like the strobing.unname4798 wrote: ↑August 26th, 2024, 7:35 amCan rowett allow B0 NW rules on a finite grid (without emulation)?

Posted: **August 27th, 2024, 1:49 am**

???

Code: Select all

```
# [[ SQUARECELLS ICONS ]]
x = 41, y = 32, rule = H3LLcircuit
2.BA.AB.2B3AB2AB3.B.A3.3BAB2.A.B.A$B4.A2B.B2.AB2.BA2B.BAB.A.B2A4.A.2B
.AB$4.BA3.A.AB.A5.A.A2.2BAB2.4A.2A2.B$A.AB.A.B4A.ABAB.4A.BAB2.A.A3BA2.
A2B$2B3.3A2B.B3.2BA.2A.3B2.ABA.2A.B.BA3B$B3.B.B2.AB2.B2.B4.B2A.B2.B.B
.2B2.B3.A$B2.B2A.B2.B.2B2.2B.A.2A.B2.A2B3.B2.B$BA.A6.B.B8.2B3.B.AB.3A
2.A2.2A$3A2.B3.B3.A.A.2A3.2BA2.3A.AB.3A.2B$A2.A.2B.2B.A.A.BA2.2A.A3.B
4A2B.B2.AB$A2.A.2B.2A.B.BA2.A.BAB2.B2A2.AB5.B2.BA$AB.A.B.BA4.A.B3.B4.
A.B.2A.2BA.A.2A2B$B.BA.A3.BAB2.2A.A2.A.B.A2B2.BA.3A.2ABA$B2A.AB.A.2B2A
2B.A3.B.BA2.2A2.AB.AB4.A$2A.A.A2.A.BABAB.2BA2B.B4.B.A3.AB.2AB.A$4B.B6.
2AB.2B.2BA2.A.A.B3.2B2.B2.B$4B2A2.A2.A2.B.BA2BA3.A3.ABA3.B.A3.B$AB7.B
.A2.A2.BAB.2A3.B2.B2.A2.2A3.B$2.3A.A.2B.A6.A4.AB.2B5.B.2B2.2B$A2B.A.A
B4.AB2.B3.B.2B.2A2.B.2AB5.2A$AB.5B.2B2.B.A3.A.A5.B.BA.2A.2AB$4.BA6.2B
2.B4.A.B.BAB.B2AB3.2ABAB$.3B2.A3BAB.ABA.2A.A2B.2A.BA.B2A2.BABA2B$4.BA
B2.A3.B2.AB2.AB.AB4.B2.A2.AB.2A$2B2AB.9A5.B7.A2BA3BA2.BAB$2AB.A3.B.A.
B5.2A.A3.B2.A3.2B.A2.BA$.A.A.A2B.2B.2AB.B2A.B2ABA3.A3.B.A.A2.A$3.A9.B
A2.A3B3.2A2.BA.B2A6.B$.BA2.B2A.3A.A3.A.2B2.A2.A.A.A2.B6.A$.3B.BA.BA4.
4B.2B.A5.A.A.2B4.2B$B3.A2.B.A.2B5.A2.A.2A2B.3BA.B3.A$.2B4.A.A2B3.BAB2A
.A.B2.B.BA.B2A.B3AB!
```

Posted: **August 27th, 2024, 3:16 am**

Posted: **August 31st, 2024, 5:48 am**

An additional complication with B0 NW is that B0 is not necessarily limited to strobing background. The NW... format allows to specify negative weights of neighbours. There can be two or more alive neighbours in neighbourhood positions whose weights add to zero (e.g. one alive neighbour in position weighted +1, one alive neighbour in a position weighted -1, and no other alive neighbours). Any such configuration would query the same birth condition (B0).

I don't know how much is explored re: CA with negatively-weighted neighbours, though.

I don't know how much is explored re: CA with negatively-weighted neighbours, though.

confocaloid wrote: ↑August 31st, 2024, 5:32 amWhat are known explored CA with negatively-weighted neighbours?

The NW... neighbourhood format allows to specify negative weights ("[...] The hexadecimal representation has the MSB as the sign bit [...]"). However, there seems to be little evidence of people actually using that feature.