ConwayLife.com

Forums for Conway's Game of Life
https://conwaylife.com/forums/

lifeviewer bug

https://conwaylife.com/forums/viewtopic.php?t=4742

Page 28 of 32

Re: LifeViewer bug on mobile devices

Posted: May 11th, 2025, 9:54 pm
by b-engine
b-engine wrote: April 4th, 2024, 2:19 am
I'm going to name this "no drag bug".

This bug seems to disappear after some time - usually few minutes, but I don't have patience to do so.

@rowett
The reason you can't replicate the bug seems like due to faster internet connection speed - LifeViewer seems to load touchscreen controls after SHOW IN VIEWER appears.

Re: lifeviewer bug

Posted: May 17th, 2025, 6:15 am
by pifricted
b-engine wrote: May 11th, 2025, 9:54 pm "no drag bug".
This seems only happens on mobile phones.

Seems LifeViewer doesn’t think you’re dragging in the viewer after you click other places.

Click the window many times may work.

Re: LifeViewer bug on mobile devices

Posted: May 26th, 2025, 5:42 am
by b-engine
b-engine wrote: March 7th, 2025, 6:05 pm
I've confirmed that this "no drag bug" happens on any Android devices with only touchscreens. There may be something wrong with the touch controls.

Re: LifeViewer bug on mobile devices

Posted: June 17th, 2025, 5:45 pm
by b-engine
b-engine wrote: May 26th, 2025, 5:42 am
b-engine wrote: March 7th, 2025, 6:05 pm
I've confirmed that this "no drag bug" happens on any Android devices with only touchscreens. There may be something wrong with the touch controls.
Maybe this is due to LifeViewer mistaking touch input for mouse input.

EDIT:
PiSpaceships wrote: March 27th, 2025, 4:19 pm Sometimes LifeViewer blocks so nothing can be did except zooming. It often occurs on my ebook reader but it once occured in Opera on my phone.
Maybe this is the no drag bug that I encounter often. In such situation there's nothing much to do expect zooming.

Re: lifeviewer bug

Posted: July 1st, 2025, 9:00 am
by Citation needed
Citation needed wrote: July 1st, 2025, 8:59 am Here is a caterer in JvN29.

Code: Select all

x = 15, y = 28, rule = JvN29
3.LK$3.LJL3K$3.LJL2.J$3.LNL2.J$3.PNP2.J$3.PNP2.N2.L3K$3.PJP2.N2.P2.J$
3.LJP2.J2.P2.J$3.LJL2.J2.P2.J$3.LJL2.J2.L2.N$3.LJL2.J2.L2.J$3.LJL2.J2.
L2.N$2.ILJP2KJLKL2.J$2.IPJ2IMNPNK2.N$L2KMJLKOL5IJ$L.JOKLIJL2K$P.2LJIP
JLIJ$P.ILNOLJ2IJ$P4.JLJ$L4.JLJ$L4.JLN$L4.NPJ$L4.JPJ$L4.JPJ$2IMIMJPN$6.
PJ$6.LJ$6.IJ!
[[ COLOR 13 255 255 255 COLOR 14 255 255 255 COLOR 15 255 255 255 COLOR 16 255 255 255 ]]
[[ STEP 10 NOTHROTTLE ]]
"NOTHROTTLE" does not seem to be working as expected.

Re: lifeviewer bug

Posted: July 1st, 2025, 9:13 am
by muzik
Citation needed wrote: July 1st, 2025, 9:00 am"NOTHROTTLE" does not seem to be working as expected.
What is Settings > Advanced > Refresh Rate set to? It seems to work fine if set to 60, but if set to Auto or 144 we don't visit exclusively every tenth generation. Or is the issue something else?

Re: lifeviewer bug

Posted: July 7th, 2025, 10:29 am
by rowett
Citation needed wrote: July 1st, 2025, 9:00 am "NOTHROTTLE" does not seem to be working as expected.
This is probably because you are expecting 10x to mean 10 generations every frame. This is only true if your monitor refreshes at 60Hz.

In order to be consistent across different refresh rate monitors LifeViewer considers that 1x means 60 generations per second and that 10x means 600 generations per second.

If you have a 60Hz monitor and are at 10x then you will see the T value increment by 10 generations every frame (600 generations displayed at 60Hz is 600/60 = 10 per frame).

However, if you have a 75Hz monitor and are at 10x then you will see the T value increment by 8 generations every frame (600 generations displayed at 75Hz is 600/75 = 8 per frame).

Re: lifeviewer bug

Posted: July 16th, 2025, 5:46 pm
by b-engine
The elements of LifeViewer seems to flicker or disappear when I move the camera, making it very nearly unusable. This seems to happen every time, no matter how I reload or visit different sites.

Re: lifeviewer bug

Posted: July 17th, 2025, 8:31 am
by rowett
b-engine wrote: July 16th, 2025, 5:46 pm The elements of LifeViewer seems to flicker or disappear when I move the camera, making it very nearly unusable. This seems to happen every time, no matter how I reload or visit different sites.
I'll need to know:
  • Version of LifeViewer (e.g. Standard build 1312)
  • Device you are using (e.g. Laptop)
  • Operating system (e.g. Windows 11)
  • Browser (e.g. Chrome Version 138.0.7204.101 (Official Build) (64-bit))
  • Pattern and set of steps that reproduces the problem

Re: lifeviewer bug

Posted: July 17th, 2025, 5:50 pm
by b-engine
rowett wrote: July 17th, 2025, 8:31 am
Apparently the bug fixed itself after a few moments.

EDIT: it came back again.
Only those elements that has something below moved or them clicked would temporarily display for a frame. Maybe it misidentified my device as e-ink device?

EDIT 2: turning on Render Quality seems to fix the issue.

EDIT 3:
Using Chrome 136.0.7103.125 on Android 15. Don't know the exact device specs. Just open the viewer would reproduce the bug.

Re: lifeviewer bug

Posted: July 21st, 2025, 6:18 pm
by b-engine
b-engine wrote: July 17th, 2025, 5:50 pm
rowett wrote: July 17th, 2025, 8:31 am
Seems like the bug only happen in one device.
"Fixed" because I switched to another device.

Re: lifeviewer bug

Posted: July 23rd, 2025, 8:55 pm
by b-engine
A bug of gliders killer affects the evolution of Likda:

Code: Select all

x = 9, y = 15, rule = B3/S23
bo$obo$bo8$8bo$6bobo$5b2obo2$4b3o!
[[ AUTOSTART ]]

Code: Select all

x = 9, y = 15, rule = B3/S23
bo$obo$bo8$8bo$6bobo$5b2obo2$4b3o!
[[ KILLGLIDERS AUTOSTART ]]

Re: lifeviewer bug

Posted: August 4th, 2025, 6:39 pm
by b-engine
Cross posting this complaint:
LuveelVoom wrote: July 30th, 2025, 5:55 pm …
I'm really, really pissed at the weird copy bug that seems to haunt Lifeviewer. It makes it really hard to assemble pattern collections and I don't have time right now to learn Golly's controls.
…

Re: lifeviewer bug

Posted: August 4th, 2025, 7:11 pm
by rowett
b-engine wrote: August 4th, 2025, 6:39 pm Cross posting this complaint:
LuveelVoom wrote: July 30th, 2025, 5:55 pm …
I'm really, really pissed at the weird copy bug that seems to haunt Lifeviewer. It makes it really hard to assemble pattern collections and I don't have time right now to learn Golly's controls.
…
I'll need details: what is the copy bug? Some steps to reproduce it. Browser, device, LifeViewer build etc.

Re: lifeviewer bug

Posted: August 4th, 2025, 7:50 pm
by LuveelVoom
I'm fairly sure it's an OS issue. On both MacOS and ChromeOS, copy-pasting something into the viewer from your external clipboard is very inconsistent.

Also, sometimes, on every device I've used (so probably a LV issue), very rarely, undoing after copy/paste/move operations will corrupt the region you were interacting with.

Re: lifeviewer bug

Posted: August 5th, 2025, 12:43 am
by rowett
LuveelVoom wrote: August 4th, 2025, 7:50 pm I'm fairly sure it's an OS issue. On both MacOS and ChromeOS, copy-pasting something into the viewer from your external clipboard is very inconsistent.

Also, sometimes, on every device I've used (so probably a LV issue), very rarely, undoing after copy/paste/move operations will corrupt the region you were interacting with.
Thanks. I'll need some repeatable steps that reproduce the problem.

Re: lifeviewer bug

Posted: August 5th, 2025, 5:05 pm
by tommyaweosme
rowett wrote: August 5th, 2025, 12:43 am -quote snip-
Thanks. I'll need some repeatable steps that reproduce the problem.
a2adl5.gif
a2adl5.gif (2.26 MiB) Viewed 6633 times
✎a higher quality gif is coming as soon as my parents approve ezgif✎

✎they approved it so here is the higher quality gif✎
ezgif-5a9858a7a3cd30.gif
ezgif-5a9858a7a3cd30.gif (2.15 MiB) Viewed 6627 times

Re: lifeviewer bug

Posted: August 5th, 2025, 5:18 pm
by LuveelVoom
For me it is the same as the above gif except that there is just no option to paste.

Re: lifeviewer bug

Posted: August 6th, 2025, 5:47 pm
by rowett
tommyaweosme wrote: August 5th, 2025, 5:05 pm ✎a higher quality gif is coming as soon as my parents approve ezgif✎
Fixed in build 1314.

Re: lifeviewer bug

Posted: August 20th, 2025, 5:18 pm
by Anivec
LifeViewer seems to save the entire pattern on the grid rather than the selected portion, unlike Golly. This might be seen as a nuisance, but it becomes more problematic for breaking up one large collection into smaller, separate RLEs.

Re: lifeviewer bug

Posted: August 20th, 2025, 5:52 pm
by b-engine
Anivec wrote: August 20th, 2025, 5:18 pm LifeViewer seems to save the entire pattern on the grid rather than the selected portion, unlike Golly. This might be seen as a nuisance, but it becomes more problematic for breaking up one large collection into smaller, separate RLEs.
On the other hand, saving only the selection could cause loss of search results or other patterns, which is also a problem.

Maybe add a toggle into Settings > Clipboard?

Re: lifeviewer bug

Posted: August 21st, 2025, 10:37 am
by rowett
b-engine wrote: August 20th, 2025, 5:52 pm
Anivec wrote: August 20th, 2025, 5:18 pm LifeViewer seems to save the entire pattern on the grid rather than the selected portion, unlike Golly. This might be seen as a nuisance, but it becomes more problematic for breaking up one large collection into smaller, separate RLEs.
On the other hand, saving only the selection could cause loss of search results or other patterns, which is also a problem.
As it stands Pattern>Save Pattern will always save the entire pattern. This was requested to avoid accidently saving a selection instead of the full pattern.

If you want just the selection then use Edit>Copy and it will be in the clipboard.

Re: lifeviewer bug

Posted: August 29th, 2025, 1:53 am
by pifricted
pifricted wrote: August 29th, 2025, 1:51 am

Code: Select all

x = 1, y = 1, rule = B3578/S345678|B8/S3456-c7e8
!
[[ RANDOMIZE ZOOM -1 STEP 4 ]]
Why Zoom = 1 when I view it?

Re: lifeviewer bug

Posted: August 29th, 2025, 4:13 am
by rowett
pifricted wrote: August 29th, 2025, 1:53 am Why Zoom = 1 when I view it?
Because ZOOM 1 and ZOOM -1 are the same.

Re: lifeviewer bug

Posted: September 9th, 2025, 4:21 am
by muzik
Had this object identifying since the start of this month:

Code: Select all

x = 8, y = 8, rule = M0,1,2,3,4,5,6,13,8,9,10,7,12,14,11,15:P10
2b4obo$4ob3o$4ob2o$o4b3o$o3b4o$5ob2o$3ob3o$o3bob2o!
[[ MAXGRIDSIZE 9 THEME Mono SHADER Basic SHOWGENSTATS SHOWTIMING EXTENDEDTIMING ]]
It kept going until I woke up this morning, where I noticed that it had finally stopped identifying at generation 217232803617, without giving any actual results.

Code: Select all

x = 11, y = 11, rule = M0,1,2,3,4,5,6,13,8,9,10,7,12,14,11,15
2$5b4o$2b4ob3o$2b2ob5o$3bo2bo2bo$3bo2b4o$2b8o$3b2ob4o$2b2o3bobo!

Code: Select all

#C Identify Snapshot
#CXRLE Gen=217152025216
#I -2147483648|232368910|1396686913|655370|16384122
#I -2147483648|-659061010|1725337440|655370|16384122
#I -2147483648|26182244|2418820369|655370|16384122
#I -2147483648|26182244|3919325816|655370|16384122
#I -2147483648|1232394278|429070511|655370|16384122
#I -2147483648|48690790|2335335936|655370|16384122
#I -2147483648|-1990690372|3135069041|655370|16384122
#I -2147483648|48690790|3421283733|655370|16384122
#I -2147483648|2000279260|652451718|655370|16384122
#I -2147483648|232368910|896107886|655370|16384122
#I -2147483648|-1599738108|1144596297|655370|16384122
#I -2147483648|-659061010|2658883287|655370|16384122
#I -2147483648|-1929701576|4209511341|655370|16384122
#I -2147483647|-369467493|3765709591|655370|16384122
#I -2147483647|-369467493|2501204198|655370|16384122
#I -2147483647|-1857911159|3615053057|655370|16384122
#I -2147483646|1015379780|4191852209|655370|16384122
#I -2147483646|1106824874|96813745|655370|16384122
#I -2147483646|449159036|1304711027|655370|16384122
#I -2147483646|-648505082|2545645941|655370|16384122
#I -2147483646|1106824874|3139496218|655370|16384122
#I -2147483645|-338237721|130794055|655370|16384122
#I -2147483645|-338237721|3139568916|655370|16384122
#I -2147483645|-2119495543|14545911|655370|16384122
#I -2147483645|1068954751|477700353|655370|16384122
#I -2147483645|-1313408387|3209928694|655370|16384122
#I -2147483645|-1313408387|3794660971|655370|16384122
#I -2147483644|-116937516|1838364972|655370|16384122
#I -2147483643|935137849|510549114|655370|16384122
#I -2147483643|1340822207|3319004854|655370|16384122
#I -2147483642|1622495266|3976633395|655370|16384122
#I -2147483642|-2085046080|464268796|655370|16384122
#I -2147483642|1336417844|1059170303|655370|16384122
#I -2147483642|458358466|1581137086|655370|16384122
#I -2147483642|-2085046080|3181560649|655370|16384122
#I -2147483642|-1771449824|3883635857|655370|16384122
#I -2147483642|-1734835128|1400982089|655370|16384122
#I -2147483642|686938388|2914226652|655370|16384122
#I -2147483641|-1953625079|3866904350|655370|16384122
#I -2147483641|1484099201|344330297|655370|16384122
#I -2147483641|-1428701679|723820179|655370|16384122
#I -2147483641|1474423023|2925495447|655370|16384122
#I -2147483641|-1657730735|980006288|655370|16384122
#I -2147483640|-1542879924|3370262218|655370|16384122
#I -2147483640|-1542879924|4285048669|655370|16384122
#I -2147483639|1865085461|3017903698|655370|16384122
#I -2147483639|2101363961|3080504130|655370|16384122
#I -2147483639|610991375|1404322624|655370|16384122
#I -2147483639|115387907|139110120|655370|16384122
#I -2147483639|2101363961|710837383|655370|16384122
#I -2147483639|-1930822697|1821083324|655370|16384122
#I -2147483639|1375315825|1995362443|655370|16384122
#I -2147483638|-686707600|2764648708|655370|16384122
#I -2147483638|-2098355482|1980425314|655370|16384122
#I -2147483638|-665308464|3881890658|655370|16384122
#I -2147483638|-665308464|3888343395|655370|16384122
#I -2147483637|2119663519|2951599138|655370|16384122
#I -2147483636|-268527490|4081651358|655370|16384122
#I -2147483636|-409669254|4283966088|655370|16384122
#I -2147483636|-1913562482|2155456636|655370|16384122
#I -2147483636|599340030|2672252182|655370|16384122
#I -2147483636|-409669254|1615045791|655370|16384122
#I -2147483636|512718024|924844055|655370|16384122
#I -2147483635|291724229|2762902008|655370|16384122
#I -2147483635|505112027|3887235354|655370|16384122
#I -2147483635|505112027|1050379527|655370|16384122
#I -2147483635|437141259|1275596531|655370|16384122
#I -2147483634|-116220202|1019098699|655370|16384122
#I -2147483634|-536789674|2362330217|655370|16384122
#I -2147483634|-1890402188|3571767787|655370|16384122
#I -2147483633|-787772675|1714996496|655370|16384122
#I -2147483633|-1039184213|1918021692|655370|16384122
#I -2147483633|-787772675|2279879335|655370|16384122
#I -2147483633|-730915345|2346167089|655370|16384122
#I -2147483633|-596653435|508394220|655370|16384122
#I -2147483633|-2082675879|248737722|655370|16384122
#I -2147483633|-1984928447|2279067587|655370|16384122
#I -2147483526|1590451274|2396533984|655370|16384122
#I -2147483264|-2102984370|2401232615|655370|16384122
#I -2147481361|-1855483519|2403184211|655370|16384122
#I -2147469614|-728296042|2403509162|655370|16384122
#I -2147453510|-935352668|2403582905|655370|16384122
#I -2147417182|-557277438|2403621624|655370|16384122
#I -2147174599|-685175211|2403648326|655370|16384122
#I -2146597964|-1643708638|2403655398|655370|16384122
#I -2146429452|-1172890822|2403656619|655370|16384122
#I -2143758974|213256542|2403657600|655370|16384122
#I -2142490185|-2121993577|2403658163|655370|16384122
#I -2141447423|-539693629|2403658716|655370|16384122
#I -2131306548|1464882988|2403659272|655370|16384122
#I -2129887073|-2094866557|2403659323|655370|16384122
#I -2108339842|-1157802446|2403659511|655370|16384122
#I -2100108671|1554613633|2403659552|655370|16384122
#I -2098216182|-1868871888|2403659632|655370|16384122
#I -2097948350|1970988096|2403660252|655370|16384122
#I -2096514420|-659060102|2403660265|655370|16384122
#I -2059919835|-1004900841|2403660398|655370|16384122
#I -1979065278|-364691424|2403660403|655370|16384122
#I -1958948220|2077273800|2403660410|655370|16384122
#I -826904542|-270721264|2403660414|655370|16384122
#I -310250137|145696685|2403660416|655370|16384122
#I -848368312
#C [[ AUTOIDENTIFY ]]
x = 8, y = 8, rule = M0,1,2,3,4,5,6,13,8,9,10,7,12,14,11,15:P10,10
2b6o$3o2b3o$3obob2o$2o3b2o$2o2b2obo$2ob3obo$b3o2b2o$2o2b4o!
[[ MAXGRIDSIZE 9 THEME Mono SHADER Basic SHOWGENSTATS SHOWTIMING EXTENDEDTIMING ]]
No idea if I've hit some sort of upper time limit in Identify, or something else ended up happening.

Would I be correct in saying the upper period bound is [population] choose [number of cells in envelope]?
All times are UTC-04:00
Page 28 of 32

Powered by phpBB® Forum Software © phpBB Limited