Page 1 of 1
[Latest stable] "The scenario level caused a non-recoverable error" Factoriopedia - "Quality factoriopedia"
Posted: Sun Jan 11, 2026 2:54 pm
by reduke
Mods: Quality + elevated rails
When loading Factoriopedia and choosing the tooltip called "Quality factoriopedia", the demo window crashes when the mouse clicks the Assembling Machine.

- qualfact.png (426.48 KiB) Viewed 257 times
Re: [Latest stable] "The scenario level caused a non-recoverable error" Factoriopedia - "Quality factoriopedia"
Posted: Sun Jan 25, 2026 3:00 pm
by reduke
I have just noticed that this has been moved to technical help when to me it is very clearly a bug. Note that it is still reproducible.
Can someone please move it back, or provide an explanation for the move?
Thank you.
Re: [Latest stable] "The scenario level caused a non-recoverable error" Factoriopedia - "Quality factoriopedia"
Posted: Sun Jan 25, 2026 3:20 pm
by boskid
Factoriopedia simulations are not pre-recorded, they are running live with your control settings. It looks like you changed the "open factoriopedia" binding from "Alt + Left-click" into "Control + Alt + Left-click". In that state if you try clicking the assembler a different binding will take priority, a "Ping a map location". Because of that the simulation tries to simulate "control + alt + left-click" and the factoriopedia window does not open because a ping is placed instead.
Assuming this is a bug, a fix would be to make the simulation ignore your controls and work regardless of conflicts. That could be seen as misadvertising because tip would say "press X to open factoriopedia" while for you it would not work and this could also be considered bug. If you want this moved to Bug reports, i can move this to Duplicates (
116465).
Re: [Latest stable] "The scenario level caused a non-recoverable error" Factoriopedia - "Quality factoriopedia"
Posted: Sun Jan 25, 2026 4:01 pm
by reduke
Thanks for the explanation.
I would consider it as a bug as changing key bindings shouldn't result in an error in my opinion.
I would suggest the fix for this to be that the tip should present your current bindings, while the in-window behaviour should show what the makers intended, irrespective of bindings.
Feel free to merge as suggested.