Page 15 of 32
Re: lifeviewer bug
Posted: February 28th, 2024, 4:15 am
by H. H. P. M. P. Cole
rowett wrote: February 28th, 2024, 3:57 am
H. H. P. M. P. Cole wrote: February 28th, 2024, 3:40 am
Have a try copy-pasting this pattern in lazyslug.com:
If lazyslug.com correctly works it should produce a p8 oscillator in the middle (which it correctly does, on the forums' built-in viewer). However, it doesn't, and instead the soup dies out after 1 generation. Can someone please fix the bug?
Fixed, thanks for reporting!
Doesn't work for me though. What do I have to do?
Re: lifeviewer bug
Posted: February 28th, 2024, 4:22 am
by confocaloid
You may need to hard refresh your browser to make sure you have the latest version (rather than a version that was cached on an earlier visit).
Re: lifeviewer bug
Posted: March 4th, 2024, 1:28 am
by b-engine
(Not sure if there's a more appropriate thread there, so I put it here)
LifeViewer displays Golly theme like this:
Code: Select all
x = 2, y = 2, rule = /2/3
BA$BA!
#C [[ THEME GOLLY ]]
However the actual Golly theme have red and yellow swapped (thus the gradients between them).
EDIT:
If you turn on HQ rendering & stars then you'll see this:

- Screenshot 2024-03-05 150948.png (55.75 KiB) Viewed 7682 times
Then zoom out until you see this:

- Screenshot 2024-03-05 151001.png (19.83 KiB) Viewed 7682 times
Re: lifeviewer bug
Posted: March 5th, 2024, 9:33 am
by rowett
b-engine wrote: March 4th, 2024, 1:28 am
However the actual Golly theme have red and yellow swapped (thus the gradients between them).
Fixed, thanks for reporting!
b-engine wrote: March 4th, 2024, 1:28 am
If you turn on HQ rendering & stars then you'll see this
Fixed, thanks!
Re: lifeviewer bug
Posted: March 7th, 2024, 1:12 am
by b-engine
(I don't know it there's a more appropriate thread for this, so I posted it here)
Saw this while browsing the forum:

- CODE: SELECT ALL / SHOW IN VIEWER / SHOW PATTERN ERROR
- Screenshot 2024-03-07 130542.png (4.01 KiB) Viewed 7595 times
Re: lifeviewer bug
Posted: March 7th, 2024, 3:07 am
by rowett
b-engine wrote: March 7th, 2024, 1:12 am
(I don't know it there's a more appropriate thread for this, so I posted it here)
Saw this while browsing the forum:
Screenshot 2024-03-07 130542.png
Please post a link to the pattern. Does it always happen? What error is provided if you click on "SHOW PATTERN ERROR"?
Re: lifeviewer bug
Posted: March 7th, 2024, 3:16 am
by muzik
rowett wrote: March 5th, 2024, 9:33 am
b-engine wrote: March 4th, 2024, 1:28 am
However the actual Golly theme have red and yellow swapped (thus the gradients between them).
Fixed, thanks for reporting!
Probably worth pointing out that this change also affects higher-range Generations rules, which is the opposite of what Golly does (in this case it was correct before):
Code: Select all
x = 30, y = 12, rule = R2,C4,S3,B4
2$4.B.C.B$2.2A.C.C.2A$.AB2C3.2CBA$ABC7.CBA$ABC7.CBA$.AB2C3.2CBA$2.2A.
C.C.2A$4.B.C.B!
[[ THEME Golly ]]
Personally I think the Golly theme should be kept as yellow-to-red; Andrew himself
has stated that red-to-yellow was a mistake and that yellow-to-red is a superior choice, particularly on a dark background.
I assume it isn't possible to have a theme default to red-to-yellow for range-1 and yellow-to-red for general-range?
Re: lifeviewer bug
Posted: March 7th, 2024, 4:56 am
by rowett
muzik wrote: March 7th, 2024, 3:16 am
Probably worth pointing out that this change also affects higher-range Generations rules, which is the opposite of what Golly does
Fixed, thanks!
The whole point of Theme Golly is to duplicate what Golly does. I also agree with Andrew which is why the Generations Theme in LifeViewer differs from Golly and is yellow-to-red.
Re: lifeviewer bug
Posted: March 7th, 2024, 3:09 pm
by muzik
rowett wrote: March 7th, 2024, 4:56 am
muzik wrote: March 7th, 2024, 3:16 am
Probably worth pointing out that this change also affects higher-range Generations rules, which is the opposite of what Golly does
Fixed, thanks!
In this case would it also be possible for the Golly Theme to display 2-state higher-range patterns in the same way (yellow instead of white)?
Code: Select all
x = 9, y = 10, rule = R5,C0,S33-57,B34-45
3b3o$b6o$b7o$8o$9o$obo2b4o$o4b4o$2o3b4o$b2o2b3o$2b4o!
[[ THEME Golly ]]
The Golly theme for higher-range rules also appears to be leaving a trail of history cells behind now, which is not the case in the actual program nor for range-1.
Re: lifeviewer bug
Posted: March 10th, 2024, 12:07 am
by confocaloid
rowett wrote: March 7th, 2024, 3:07 am
b-engine wrote: March 7th, 2024, 1:12 am
(I don't know it there's a more appropriate thread for this, so I posted it here)
Saw this while browsing the forum:
Screenshot 2024-03-07 130542.png
Please post a link to the pattern. Does it always happen? What error is provided if you click on "SHOW PATTERN ERROR"?
I don't know if this is the same pattern, but I currently observe the same behaviour for several patterns posted on the same page of the thread:
viewtopic.php?p=42350#p42350
viewtopic.php?p=42370#p42370
viewtopic.php?p=42373#p42373
viewtopic.php?p=42385#p42385
viewtopic.php?p=42388#p42388
viewtopic.php?p=42399#p42399
viewtopic.php?p=42400#p42400
Clicking "Show in viewer" appears to show the pattern, but I did not check extensively if it works correctly. Clicking "Show pattern error" shows "DeadlyEnemies - Unsupported rule name".
edit: LifeViewer build 1125
Re: lifeviewer bug
Posted: March 14th, 2024, 11:43 am
by rowett
muzik wrote: March 7th, 2024, 3:09 pm
In this case would it also be possible for the Golly Theme to display 2-state higher-range patterns in the same way (yellow instead of white)?
Yes, done.
muzik wrote: March 7th, 2024, 3:09 pm
The Golly theme for higher-range rules also appears to be leaving a trail of history cells behind now, which is not the case in the actual program nor for range-1.
Fixed, thanks!
Re: lifeviewer bug
Posted: March 14th, 2024, 11:44 am
by rowett
confocaloid wrote: March 10th, 2024, 12:07 am
rowett wrote: March 7th, 2024, 3:07 am
b-engine wrote: March 7th, 2024, 1:12 am
(I don't know it there's a more appropriate thread for this, so I posted it here)
Saw this while browsing the forum:
Screenshot 2024-03-07 130542.png
Please post a link to the pattern. Does it always happen? What error is provided if you click on "SHOW PATTERN ERROR"?
I don't know if this is the same pattern, but I currently observe the same behaviour for several patterns posted on the same page of the thread:
viewtopic.php?p=42350#p42350
Fixed, thanks!
Re: lifeviewer bug
Posted: March 16th, 2024, 5:56 am
by b-engine
In [R]Investigator there're two buttons that overlaps when you select a pattern:
Code: Select all
x = 1, y = 1, rule = B3/S23Investigator
!
However it doesn't happens in [R]History and [R]Super:
Code: Select all
x = 1, y = 1, rule = B3/S23History
!
Code: Select all
x = 1, y = 1, rule = B3/S23Super
!
Re: lifeviewer bug
Posted: March 23rd, 2024, 10:32 pm
by b-engine
What does the white cells even do? The rule (Ignorance) has only 3 states and the white cells doesn't include in the cell states.

- screenshot (47).png (8.73 KiB) Viewed 7313 times
Switch the rule to Ignorance to see the white cells:
Code: Select all
x = 11, y = 3, rule = B3/S23Investigator
.A3.B3.E$A3.B3.E$3A.3B.3E!
Code: Select all
x = 11, y = 3, rule = Ignorance
.A3.B3.E$A3.B3.E$3A.3B.3E!
Also you can switch the rule to Ignorance but the "SHOW PATTERN ERROR" says that Ignorance isn't supported rule name.
Re: lifeviewer bug
Posted: March 24th, 2024, 7:05 am
by squareroot12621
b-engine wrote: March 23rd, 2024, 10:32 pm
What does the white cells even do? The rule (Ignorance) has only 3 states and the white cells doesn't include in the cell states.
screenshot (47).png
Switch the rule to Ignorance to see the white cells:
Code: Select all
x = 11, y = 3, rule = B3/S23Investigator
.A3.B3.E$A3.B3.E$3A.3B.3E!
Code: Select all
x = 11, y = 3, rule = Ignorance
.A3.B3.E$A3.B3.E$3A.3B.3E!
Also you can switch the rule to Ignorance but the "SHOW PATTERN ERROR" says that Ignorance isn't supported rule name.
The white cells are state 5 from StateInvestigator. LifeViewer doesn't know how to convert a state-5 cell into a rule with only 3 states, so it just…doesn't. (I
am surprised it doesn't throw an error, though.)
Re: lifeviewer bug
Posted: March 24th, 2024, 7:14 am
by b-engine
squareroot12621 wrote: March 24th, 2024, 7:05 am
The white cells are state 5 from StateInvestigator. LifeViewer doesn't know how to convert a state-5 cell into a rule with only 3 states, so it just…doesn't. (I
am surprised it doesn't throw an error, though.)
When I click on the white cells it literally says it's state 5 cell.

- See the bottom left corner.
- Screenshot_2024-03-24-19-12-49-10_40deb401b9ffe8e1df2f1cc5ba480b12.jpg (93.27 KiB) Viewed 7289 times
Surprisingly the state 5 cells do work.
lifeviewer does not seem to be able to play at 50x speed on my computer
Posted: March 31st, 2024, 12:41 am
by eRroR_6o6
Code: Select all
x = 0, y = 0, rule = B/S012345678
!
try to set this to 50x speed.
When I try it it either plays at 49x speed or 51x speed
Is this a bug or does it just not work on my MacOS Catalina?
Edit: it also seems you can't set it to 62x either
Re: lifeviewer does not seem to be able to play at 50x speed on my computer
Posted: March 31st, 2024, 12:53 am
by b-engine
You can use + and - keys to set the playback speed precisely, regardless of OS.

- This is in LifeViewer help
- Screenshot_2024-03-31-12-53-31-43_40deb401b9ffe8e1df2f1cc5ba480b12.jpg (26.86 KiB) Viewed 7263 times
Re: lifeviewer does not seem to be able to play at 50x speed on my computer
Posted: March 31st, 2024, 2:39 am
by eRroR_6o6
b-engine wrote: March 31st, 2024, 12:53 am
You can use + and - keys to set the playback speed precisely, regardless of OS.Screenshot_2024-03-31-12-53-31-43_40deb401b9ffe8e1df2f1cc5ba480b12.jpg
ok then
it's just that the slider doesn't really go to 50x speed
Re: lifeviewer does not seem to be able to play at 50x speed on my computer
Posted: March 31st, 2024, 2:51 am
by b-engine
eRroR_6o6 wrote: March 31st, 2024, 2:39 am
ok then
it's just that the slider doesn't really go to 50x speed
The shortcut keys are used to get around the problem. However, the problem is still in touchscreen devices.
Next time make LifeViewer bug reports like this in LifeViewer bugs thread.
Re: lifeviewer does not seem to be able to play at 50x speed on my computer
Posted: March 31st, 2024, 10:48 am
by eRroR_6o6
b-engine wrote: March 31st, 2024, 2:51 am
eRroR_6o6 wrote: March 31st, 2024, 2:39 am
ok then
it's just that the slider doesn't really go to 50x speed
The shortcut keys are used to get around the problem. However, the problem is still in touchscreen devices.
Next time make LifeViewer bug reports like this in LifeViewer bugs thread.
oh i didn't know there was a lifeviewer bug thread
Re: lifeviewer bug
Posted: April 3rd, 2024, 10:08 am
by rowett
b-engine wrote: March 16th, 2024, 5:56 am
In [R]Investigator there're two buttons that overlap when you select a pattern:
Fixed, thanks for reporting!
Re: lifeviewer bug
Posted: April 3rd, 2024, 10:10 am
by rowett
b-engine wrote: March 23rd, 2024, 10:32 pm
What does the white cells even do? The rule (Ignorance) has only 3 states and the white cells doesn't include in the cell states.
Also you can switch the rule to Ignorance but the "SHOW PATTERN ERROR" says that Ignorance isn't supported rule name.
Fixed, thanks. You'll now get an error message if you have invalid states in the pattern.
Re: lifeviewer does not seem to be able to play at 50x speed on my computer
Posted: April 3rd, 2024, 12:36 pm
by rowett
eRroR_6o6 wrote: March 31st, 2024, 12:41 am
try to set this to 50x speed.
When I try it it either plays at 49x speed or 51x speed
If the display is too small then there will be a few speeds that can't be selected.
If you really want 50x you could use the script command
[[ STEP 50 ]] in the pattern.
Code: Select all
#C [[ STEP 50 ]]
x = 0, y = 0, rule = B/S012345678
!
Re: LifeViewer bug
Posted: April 3rd, 2024, 5:46 pm
by b-engine
This is a big problem for weighted HROT rules.
b-engine wrote: April 3rd, 2024, 5:42 pm
There's seems a bug here:
Code: Select all
x = 0, y = 0, rule = R2,C2,S2-3,B3,136,NW8888881118810188111888888
5o$5o$2ob2o$5o$5o!
There're 136 neighbors in the weighted neighborhood, but LifeViewer says the maximum neighbors a cell can have is 8.