This page serves as an archive of known issues with LifeViewer which cannot be fixed due to limitations of the hardware and/or browser LifeViewer is being run on.
The period map generated by Identify can sometimes appear blurry.
This only occurs when "Scale" (see Help > Info) is at a non-integer value.
This occurs when the bounding box of the oscillator in question is not large enough for the "no grid, but with a thick border" period map style to be used, but is too thick for the "with a grid" style to be displayed without being slightly rescaled, introducing undesirable blurring.
On hexagonal and triangular grids, cells of the exact same or similar colors directly adjacent to each other may render small gaps between each other, which are most visible for non-integer zoom levels.
These may be incredibly subtle depending on the hardware and software used - it may be advisable to take a screenshot and paste it into an image editor and flood fill in order to reveal these borders.
hexagons
triangles
x = 11, y = 11, rule = //3H
6A$A5BA$AB4ABA$ABA3BABA$ABAB2ABABA$ABABABABABA$.ABAB2ABABA$2.ABA3BABA
$3.AB4ABA$4.A5BA$5.6A!
#C [[ THUMBSIZE 2 THEME 6 GRID GRIDMAJOR 0 SUPPRESS THUMBLAUNCH ]]
#C [[ ZOOM 15.8 GRID OFF COLOR 1 Red COLOR 2 Red THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]]
Oscillators with a sufficiently large bounding box will not have a period map generated.
This is due to a limitation of maximum image size on various Mobile devices (typically 4096x4096).
LifeViewer acts as though one has been generated, however nothing is actually displayed when trying to view it, This is distinct for cases where LifeViewer intentionally does not display strict volatility information, such as when it would take too much memory, for unsupported rulespaces or for spaceships.