Currently known issues with how LifeViewer renders and displays things.
The grid lines used to partition the grid in Margolus rules are not consistent in representing the partitioned regions.
It would be expected that either GRIDMAJOR would represent the "active" partitioning, or GRID would, but not interchangeably depending on the input pattern. The former would be preferable.
GRID used
GRIDMAJOR used
x = 1, y = 1, rule = M0,2,8,3,1,5,6,7,4,9,10,11,12,13,14,15
o!
#C [[ THUMBSIZE 2 THEME 6 GRID GRIDMAJOR 0 SUPPRESS THUMBLAUNCH ]]
#C [[ COLOR GRIDMAJOR Black GRIDMAJOR 2 THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]]
AutoFit can sometimes put the viewer at a very slightly different zoom level than the Fit Pattern button. This likely depends on the scale level of the viewer.
For example (on an iPad), with browser tabs shown, AutoFit zooms to 36.2, whereas Fit Pattern zooms to 36.0. With browser tabs not shown, AutoFit goes to 39.9, whereas Fit Pattern uses 40.0.
On a desktop computer, Fit Pattern goes to 37.0, whereas AutoFit goes to 37.3.
When toggling icons on and off, the positions of the major grid lines can be seen shifting in location.
To reproduce this you must manually switch to another theme with major grid lines such as MCell or Golly: even if a theme is explicitly specified in viewerconfig on the wiki, the actually applied theme will be a custom theme without major grid lines.
The Neighbor cell shader does not interact correctly with the edges of bounded grids.
In the following examples, Plane is correct, but Torus is not; the redness should be continuous in the latter.
Editing cells near the edge can make the redness continue to the very edge, however this will be reverted when stepping forward a generation. The redness will also incorrectly happen for Plane, despite the outside being functionally dead.
Editing cells at the very edge will also not cause cells on the other connected side of a torus to update as would be expected.
If the boundary colour is set to the same colour as the background colour, and stars are enabled, boundary hexagons and triangles will occlude the stars.
This does not affect boundary squares.
Zooming out beyond 4.0x, or enabling Use Rectangles, will cause the stars to correctly render.
Squares
Hexagons
Triangles
x = 1, y = 1, rule = B/S
!
#C [[ THUMBSIZE 2 THEME 6 GRID GRIDMAJOR 0 SUPPRESS THUMBLAUNCH ]]
#C [[ COLOR BACKGROUND 0 0 0 COLOR BOUNDARY 0 0 0 X 256 Y -256 STARS GRID OFF MAXGRIDSIZE 9 THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]]
Layered history cells are a different color in the general-range algorithm compared to the range-1 algorithm, even when using the same pattern and Theme.
For themes with no history, layers will appear where cells previously were in the general-range algorithm, even though this does not happen for the range-1 algorithm.
This is presumably caused by a lack of cell shader support in the general-range algorithm.
Help > Info > Cells will also imply the Basic shader is in use, even though this is implied not to be the case.
AutoFit can act less smooth than expected at some times: patterns can approach viewer edges causing a bouncing effect, and reaching a stopping generation will not smoothly transition the viewer to the target zoom value.[1]
The Neighbour shader causes visual bugs when used on the hexagonal and triangular grids.
It also uses the wrong colours and neighbour calculations when used on the two types of rectangular grid.
Support is planned,[2] but the current behaviour is still incorrect.
Transitioning from one theme to another appears to differ depending on the display refresh rate, rather than being constant as playback speed is. For example, the theme changes much faster on 144hz compared to 60hz.
In addition, rather than fading as cells do, the grid appears to change colour immediately.
x = 2, y = 4, rule = B2/S
o$bo$bo$o!
#C [[ THUMBSIZE 2 THEME 6 GRID GRIDMAJOR 0 SUPPRESS THUMBLAUNCH ]]
[[ THEME Blues X 10 AUTOSTART GPS 4 T 10 T 20 THEME Day LOOP 20 ]]