hello,

since fcpu >=v4.4.1 i get by clicking on fcpi in editor the following error :

Die Mod fCPU: Programmierbarer Kombinator (0.4.42) hat einen Fehler verursacht, der nicht behoben werden kann.
Bitte informiere den Autor der Mod über diesen Fehler.

Error while running event fcpu::fcpu-open (ID 227)
LuaGuiElement API call when LuaGuiElement was invalid.
stack traceback:
[C]: in function 'newindex'
__fcpu/src/gui/main.lua:282: in function 'GuiWidgetVisible'
fcpu/src/gui/main.lua:309: in function 'GuiWidgetOpen'
fcpu/src/gui/base.lua:161: in function <fcpu/src/gui/base.lua:150>

after that, the editor is closing automatically ?! if c reate a new editor scenario and place a new fcpu in it i can click on the fcpu without an error. strange.

tenim

I've now downgraded to v0.4.39 and it's working again. Could it be that it's due to the crowdin.com integration and that the URL is sometimes unavailable? When it wasn't working, the line number parameter in the mod settings always showed “unknown key...”.

tenim

This is quite a rare event. Most likely, your fCPU was saved at the moment of destruction.
Should be fixed in fCPU v0.4.43

thanks for the quick fix. it works now. but if i click on the button "insert signal type in code" now i get this error

Error while running event fcpu::on_gui_click (ID 1)
fcpu/src/gui/main.lua:629: bad argument #1 of 3 to 'match' (string expected, got table)
stack traceback:
[C]: in function 'match'
fcpu/src/gui/main.lua:629: in function 'proc'
fcpu/src/gui/base.lua:89: in function 'handler'
fcpu/3rdparty/flib061/gui.lua:390: in function <fcpu/3rdparty/flib061/gui.lua:376>

The last bug looks like magic. It’s hard to imagine what could have happened to create such an conditions.

Do you have the possibility to send a save (%appdata%\Factorio\saves for windows) ?

ok, have created a forum post with the save attached:

https://forums.factorio.com/viewtopic.php?t=132059

Should be fixed in v0.4.46 , please try it

the error still occoured in v0.4.47 but i have found a solution: have created a blueprint of the scenario without the fcpu and pasted it in a
fresh created new scenario. then placed fcpu and connected again to the other stuff. and now it works. possible a early error has corrupted some of the data somewhere in the file and now its resetted. I used to switch the CPU on and off excessively in the FCPU GUI to get the signals out of the lines and played around a lot with the other control buttons. Maybe there was an unfortunate combination of circumstances...

Anyway, it works now. :-)