Post bugs here

[Stuffe]

Please report your bug here:
https://turingcomplete.game/report_bug

Thanks!

[Emrys]

@earl217

I just realized that this game doesn't really have a problem with the number of colors in the wires, but rather a massive problem with the inability to adequately label its circuits. I'm currently in the process of building a 16-bit computer with the "Logism Evolution" program and want to transfer what I've already learned from this game to it, but after about a year I'm having a hard time getting back into this game because it's not clear right away is what I made some logic circuit like this for. In "Logisim" everything is labeled much better and despite the few colors there are, I find my way around there better because I can describe or label something in every place. The integrated circuits, which you create yourself and can then incorporate into your circuits as components, are also easier to handle in box form than in this game, where the IC usually always ends up in impractical, cloud-like shapes. With "Logism" all the entrances and exits are described and I don't have to constantly look in somewhere to see what I've done something for. That's why a lot of colors aren't necessary. You also have the option to work with tunnels in order to have fewer wires on the screen that cross others.

I think this is an important point for improvement.

[MegaIng]

@Emrys In TC, you can name your IO components, which will be displayed in the bottom panel, and you can add a description that will be added right next to it. You can also shape your component pretty easily by placing filler components.

[Emrys]

Messaggio originale di MegaIng:

@Emrys In TC, you can name your IO components, which will be displayed in the bottom panel, and you can add a description that will be added right next to it. You can also shape your component pretty easily by placing filler components.

Yes, but the larger the IC is, the smaller the font at the bottom of the bottom panel becomes, until you can no longer read it at all. Therefore it is partially unusable for me. In Logism I can always easily read the labels in the workspace without having to click anything.
I can also place text anywhere in the circuit at any time to make comments. Designing the shape of an IC in this game didn't work well in my opinion, at least at the time, so I just left it as suggested by the game. But I have the same problem with Logisim. But since the design suggested by the program is ideal for me (box shape), I can just leave it there and the connections are also perfectly arranged on the sides.

[Seb]

I can move the (supposed to be locked) red elements when I move it along with another element. It feels like cheating !

[Ryan]

i don't know if this counts as a bug or not, but when panning the screen the components jump around visually and don't track perfectly with the actual grid as it appears on screen. it's as if the camera movement inertia effect is different from the actual camera velocity which makes it hard to work when moving around a lot since you have to wait for the camera to stop moving after every movement

[citizenslave]

Was there ever a resolution for set_input? It's still buggy for me but I may be using it incorrectly. When I use it the first time in a program it seems to work fine (more or less, sometimes I have to open the code editor first just to jank it), but on subsequent calls it seems to take a tick to "catch up" in a way that doesn't occur if I read the data from a switched constant using the same two leads.

[Ryan]

is there a way to search this bug tracker? i'd be amazed if this hasn't been brought up yet: i'm completely unable to copy/paste text in the code window. ctrl+c just deletes all highlighted code, and there is no undo. ctrl+v does nothing (besides delete highlighted text as well) no matter what's on the clipboard.

[MegaIng]

Messaggio originale di citizenslave:

Was there ever a resolution for set_input?

No, still broken.

[MegaIng]

Messaggio originale di Ryan:

is there a way to search this bug tracker? i'd be amazed if this hasn't been brought up yet: i'm completely unable to copy/paste text in the code window. ctrl+c just deletes all highlighted code, and there is no undo. ctrl+v does nothing (besides delete highlighted text as well) no matter what's on the clipboard.

This is somehow a bug specific to your setup, copy paste does work generally.

[Juan Fernadez]

How to recover from below pls?
//Qte//
Turing Complete 0.1059 Beta on Windows
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
at: ObjectDB::cleanup (core\object.cpp:2064) - ObjectDB instances leaked at exit (run with --verbose for details).
//Uqte//

[MegaIng]

Messaggio originale di Juan Fernadez:

How to recover from below pls?
//Qte//
Turing Complete 0.1059 Beta on Windows
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
at: ObjectDB::cleanup (core\object.cpp:2064) - ObjectDB instances leaked at exit (run with --verbose for details).
//Uqte//

That's not an issue, that's completely normal log content.

[citizenslave]

Messaggio originale di MegaIng:

Messaggio originale di citizenslave:

Was there ever a resolution for set_input?

No, still broken.

Ok. I can live with that just using a switched constant to pretend or some more elaborate mechanism if I need tests with different (programmed) inputs. I mostly just needed to know for 100% sure if set_input was broken, my code was, or my architecture. Was struggling to find anything up-to-date or describing my exact issue to validate that.

Thanks.

[Juan Fernadez]

Messaggio originale di MegaIng:

Messaggio originale di Juan Fernadez:

How to recover from below pls?
//Qte//
Turing Complete 0.1059 Beta on Windows
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
at: ObjectDB::cleanup (core\object.cpp:2064) - ObjectDB instances leaked at exit (run with --verbose for details).
//Uqte//

That's not an issue, that's completely normal log content.

After that, when I enter "condition", I/O is missing forever, I can not improve my design better. It doesn't run without I/O. How to fix pls?

[Juan Fernadez]

Then bug in "level - conditions" asf:
There is a red warning bar in the bottom, saying
"This save is from an obsolete version of this level. Create and load a new schematic in the schematic menu"

meanwhile there aren't 8-bit-inputs and output anymore, thus I can't run.

I didn't see any version update y/day.

Just a crack down - restart computer - Run Turing Complete - level conditions - bug

[Juan Fernadez]

Not fixed after uninst and reinst.
Other levels seems normal, only the "conditions" where my computer restarted, there4 I show you the debug file to find solution.