Page 7 of 20
Re: lifeviewer bug
Posted: October 5th, 2022, 9:03 pm
by mniemiec
I just noticed a bug only started happening yesterday. Every single pattern I bring up displays an overlay that says, "If there are no cells displayed, click on Help". Does anyone know why this is happening?
Re: lifeviewer bug
Posted: October 5th, 2022, 10:59 pm
by dvgrn
mniemiec wrote: ↑October 5th, 2022, 9:03 pm
I just noticed a bug only started happening yesterday. Every single pattern I bring up displays an overlay that says, "If there are no cells displayed, click on Help". Does anyone know why this is happening?
Yup, I believe that's not a bug, that's a feature -- i.e., a deliberate temporary change that Chris has made to LifeViewer, to get the message out to current users of LifeViewer in Chrome, about implementing
the workaround. Haven't heard specific plans, but it would seem to make sense to remove that message after a week or two, since it will be more in-the-way than useful after a while.
Re: lifeviewer bug
Posted: October 6th, 2022, 12:02 am
by rattlesnake
Code: Select all
x = 8, y = 3, rule = LifeHistory
C6.E$A6.A$C6.E!
The 2 blinkers are the same in generation 1 but diverge in generation 2.
Re: lifeviewer bug
Posted: October 6th, 2022, 4:37 am
by mniemiec
mniemiec wrote: ↑October 5th, 2022, 9:03 pm
I just noticed a bug only started happening yesterday. Every single pattern I bring up displays an overlay that says, "If there are no cells displayed, click on Help". Does anyone know why this is happening?
dvgrn wrote: ↑October 5th, 2022, 10:59 pm
Yup, I believe that's not a bug, that's a feature -- i.e., a deliberate temporary change that Chris has made to LifeViewer, to get the message out to current users of LifeViewer in Chrome, about implementing
the workaround. Haven't heard specific plans, but it would seem to make sense to remove that message after a week or two, since it will be more in-the-way than useful after a while.
I'm currently using Chrome Version 105.0.5195.127 (Official Build) (64-bit), and see no problems.
Re: lifeviewer bug
Posted: October 6th, 2022, 4:55 am
by rowett
mniemiec wrote: ↑October 6th, 2022, 4:37 am
I'm currently using Chrome Version 105.0.5195.127 (Official Build) (64-bit), and see no problems.
Which operating system are you using?
Re: lifeviewer bug
Posted: October 6th, 2022, 7:33 am
by dvgrn
mniemiec wrote: ↑October 6th, 2022, 4:37 am
I'm currently using Chrome Version 105.0.5195.127 (Official Build) (64-bit), and see no problems.
To clarify: you're using Chrome 105, you
don't have
Out-of-process 2D canvas rasterization set to Disabled in
chrome://flags, and you don't see a slowdown in patterns such as the
Exploratorium? I was seeing "reasonable" evolution rates for very small patterns before putting in the workaround, but the Exploratorium was running at multiple seconds per tick.
Re: lifeviewer bug
Posted: October 6th, 2022, 8:10 am
by rowett
dvgrn wrote: ↑October 6th, 2022, 7:33 am
mniemiec wrote: ↑October 6th, 2022, 4:37 am
I'm currently using Chrome Version 105.0.5195.127 (Official Build) (64-bit), and see no problems.
To clarify: you're using Chrome 105, you
don't have
Out-of-process 2D canvas rasterization set to Disabled in
chrome://flags, and you don't see a slowdown in patterns such as the
Exploratorium? I was seeing "reasonable" evolution rates for very small patterns before putting in the workaround, but the Exploratorium was running at multiple seconds per tick.
If he's on Linux then he won't be hitting either issue (no cells or slowdown), since
Out-of-process 2D canvas rasterization is Disabled by default on Linux.
I've amended the warning that LifeViewer displays on start so it only happens on Windows.
Re: lifeviewer bug
Posted: October 6th, 2022, 11:25 am
by rowett
rattlesnake wrote: ↑October 6th, 2022, 12:02 am
Code: Select all
x = 8, y = 3, rule = LifeHistory
C6.E$A6.A$C6.E!
The 2 blinkers are the same in generation 1 but diverge in generation 2.
LifeViewer's [R]History implementation differs slightly in that mark1 cells remain mark1 cells (after transitioning through markOff) rather than becoming mark2.
Re: lifeviewer bug
Posted: October 6th, 2022, 7:12 pm
by mniemiec
mniemiec wrote: ↑October 6th, 2022, 4:37 am
I'm currently using Chrome Version 105.0.5195.127 (Official Build) (64-bit), and see no problems.
dvgrn wrote: ↑October 6th, 2022, 7:33 am
To clarify: you're using Chrome 105, you
don't have
Out-of-process 2D canvas rasterization set to Disabled in
chrome://flags, and you don't see a slowdown in patterns such as the
Exploratorium? I was seeing "reasonable" evolution rates for very small patterns before putting in the workaround, but the Exploratorium was running at multiple seconds per tick.
I'm getting about 30 fps on that, when I drag the speed bar up to maximum x64.
Re: lifeviewer bug
Posted: October 9th, 2022, 3:00 am
by bibunsekibun
After looking at it for the first time in a while, it seems that LifeViewer can't load rle.
I can't seem to change the state of the cell.
Re: lifeviewer bug
Posted: October 9th, 2022, 5:59 am
by rowett
bibunsekibun wrote: ↑October 9th, 2022, 3:00 am
After looking at it for the first time in a while, it seems that LifeViewer can't load rle.
I can't seem to change the state of the cell.
I'll need some more details and an example of what you're trying to do.
Re: lifeviewer bug
Posted: October 9th, 2022, 6:24 am
by bibunsekibun
rowett wrote: ↑October 9th, 2022, 5:59 am
I'll need some more details and an example of what you're trying to do.
Apparently it was the influence of Out-of-process 2D canvas rasterization.

Re: lifeviewer bug
Posted: October 13th, 2022, 5:57 pm
by wirehead
[[ ]]'s require spaces around them to be picked up as commands. Is this intentional?
Code: Select all
x = 12, y = 18, rule = DeadlyEnemies
3.2B$3.2B6$.2B7.2B$.2B7.2B3$3A5.2B$2.A5.2B$3A3$.2B$.2B!
#C [[ZOOM 5.3 STOP 51]]
Code: Select all
x = 12, y = 18, rule = DeadlyEnemies
3.2B$3.2B6$.2B7.2B$.2B7.2B3$3A5.2B$2.A5.2B$3A3$.2B$.2B!
#C [[ ZOOM 5.3 STOP 51 ]]
(Noticed when I took a look at
this.)
Re: lifeviewer bug
Posted: October 13th, 2022, 6:16 pm
by dvgrn
wirehead wrote: ↑October 13th, 2022, 5:57 pm
[[ ]]'s require spaces around them to be picked up as commands. Is this intentional?
Yes, the spaces are part of the syntax.
Re: lifeviewer bug
Posted: October 15th, 2022, 1:45 pm
by confocaloid
Crossposting this from another thread - was anyone able to reproduce this? Is this due to presence of several large viewers on the linked page? I just attempted again opening the thread thread
Updated oscillator stamp collection (was: Re: Golly suggestions) in Firefox 105.0, and the same problem occurred.
Re: lifeviewer bug
Posted: November 5th, 2022, 9:20 pm
by wirehead
When I am editing a post I made with a rule that is <s>not yet recognized by LifeViewer</s> pasted at the end after the pattern (edit: whoops, I already had mentioned the rule elsewhere) and I copy cells and go to paste it in the text box, it pastes nothing. The x=NNN, y=NNN header is correct, but the body is just a single solitary !. And, no, my selection is not empty.
Re: lifeviewer bug
Posted: November 6th, 2022, 4:41 pm
by rowett
wirehead wrote: ↑November 5th, 2022, 9:20 pm
When I am editing a post I made with a rule that is <s>not yet recognized by LifeViewer</s> pasted at the end after the pattern (edit: whoops, I already had mentioned the rule elsewhere) and I copy cells and go to paste it in the text box, it pastes nothing. The x=NNN, y=NNN header is correct, but the body is just a single solitary !. And, no, my selection is not empty.
I can't reproduce this. Please post an example.
Re: lifeviewer bug
Posted: November 6th, 2022, 5:09 pm
by wirehead
rowett wrote: ↑November 6th, 2022, 4:41 pm
wirehead wrote: ↑November 5th, 2022, 9:20 pm
When I am editing a post I made with a rule that is <s>not yet recognized by LifeViewer</s> pasted at the end after the pattern (edit: whoops, I already had mentioned the rule elsewhere) and I copy cells and go to paste it in the text box, it pastes nothing. The x=NNN, y=NNN header is correct, but the body is just a single solitary !. And, no, my selection is not empty.
I can't reproduce this. Please post an example.
Ok, try this:
Code: Select all
x = 0, y = 0, rule = ruleforbug153180
AB.AB.AB!
@RULE ruleforbug153180
@TABLE
n_states:3
neighborhood:Moore
symmetries:permute
1,0,0,1,0,1,0,0,1,2
Hit reply on this post, click preview, scribble something, copy, and then try to paste it back into the code box.
Edit: somehow this doesn't seem to work. The rule table format looks okay, but somehow it says "test123: rule lookup failed 404." Maybe it has something to do with the rule being pasted in after the pattern
and being recognized in the wiki...
Re: lifeviewer bug
Posted: November 7th, 2022, 1:15 am
by rowett
wirehead wrote: ↑November 6th, 2022, 5:09 pm
Edit: somehow this doesn't seem to work. The rule table format looks okay, but somehow it says "test123: rule lookup failed 404." Maybe it has something to do with the rule being pasted in after the pattern
and being recognized in the wiki...
The rule table is invalid. There are not enough numbers on the final line of the definition.
Re: lifeviewer bug
Posted: November 7th, 2022, 2:23 pm
by wirehead
rowett wrote: ↑November 7th, 2022, 1:15 am
wirehead wrote: ↑November 6th, 2022, 5:09 pm
Edit: somehow this doesn't seem to work. The rule table format looks okay, but somehow it says "test123: rule lookup failed 404." Maybe it has something to do with the rule being pasted in after the pattern
and being recognized in the wiki...
The rule table is invalid. There are not enough numbers on the final line of the definition.
Fixed it now. I can't reproduce the bug either, at least with that example, so maybe it has something to do with the rule table being in two places (pasted at end
and the wiki) and LifeViewer gets confused.
Re: lifeviewer bug
Posted: November 7th, 2022, 3:22 pm
by rowett
wirehead wrote: ↑November 7th, 2022, 2:23 pm
Fixed it now. I can't reproduce the bug either, at least with that example, so maybe it has something to do with the rule table being in two places (pasted at end
and the wiki) and LifeViewer gets confused.
LifeViewer only goes to the Wiki if there isn't a valid rule in the comments.
Re: lifeviewer bug
Posted: November 7th, 2022, 4:51 pm
by wirehead
rowett wrote: ↑November 7th, 2022, 3:22 pm
wirehead wrote: ↑November 7th, 2022, 2:23 pm
Fixed it now. I can't reproduce the bug either, at least with that example, so maybe it has something to do with the rule table being in two places (pasted at end
and the wiki) and LifeViewer gets confused.
LifeViewer only goes to the Wiki if there isn't a valid rule in the comments.
Not sure what was going on, then. Must have been a cosmic ray.
Re: lifeviewer bug
Posted: November 29th, 2022, 7:54 pm
by rattlesnake
Code: Select all
x = 2, y = 2, rule B3/S23
2o$2o!
#C [[ RAINBOW ]]
Play, Alt-W, reset.
Re: lifeviewer bug
Posted: November 30th, 2022, 10:22 am
by rowett
rattlesnake wrote: ↑November 29th, 2022, 7:54 pm
Code: Select all
x = 2, y = 2, rule B3/S23
2o$2o!
#C [[ RAINBOW ]]
Play, Alt-W, reset.
Fixed, thanks for reporting!
Re: lifeviewer bug
Posted: November 30th, 2022, 5:00 pm
by AlbertArmStain
pressing "enter" on mac doesn't work