Will Godot miss lines if you try run too many things at once?

OofStatement

I think it's any line with
parentScript.current_word=parentScript.L_letter+parentScript.M_letter

Earliest this appears is line 96.

I think removing the yield commands might have fixed the problem. If I run the program when my phone isn't plugged into the laptop, the error doesn't seem to appear (at least not yet). It's only when the phone is plugged in that I get the error message. Not sure why that is.

OofStatement

I spoke too soon.

I think the error happened again when the phone wasn't plugged in. I say "I think" because I couldn't get any outputs to see if it was the same error. The tiles lit up but kept scrolling instead of disappearing. When the phone is plugged in, the game will freeze instead.

That said, I had to play the game a lot longer before the error happened.

xyz

OofStatement This certainly has nothing to do with "running too many things at once". The engine will not skip any of your code just because there's "too much" of it. That's not how things work. Besides, running a couple dozen objects is nothing for modern engines, far far from "too much".

You have some bugs/entanglements in code flow, logic or timing. If you ask people to help you with debugging - post a MRP. It's nigh on impossible to debug from random screenshots.

As a general advice, get into habit of zeroing in on bugs by using excessive printing, breakpoints and asserts. If a bug is extremely annoying, persistent and/or behaves totally random, it often pays off to spend some time to isolate it into minimal environment that it still can live in, by stripping a copy of the the project bit by bit. The bug's nature often becomes apparent in the process.

Toxe

xyz As a general advice, get into habit of zeroing in on bugs by using excessive printing, breakpoints and asserts.

+1 for getting into the habit of using asserts. They are extremely useful yet not utilized enough.

OofStatement

What's an MRP? I'm not entirely familiar with the lingo around coding.

xyz

OofStatement What's an MRP? I'm not entirely familiar with the lingo around coding.

It stands for Minimal Reproducible Project/Example.
Also here are some useful guidelines for making MRPs.

DaveTheCoder

OofStatement What's an MRP?

xyz explained what the abbreviation means, and provided links that go into more explanation.

The point is that if you're trying to study a bug in someone else's code, it's desirable to look at a project that's as small and simple as possible. Dealing with numerous scenes, nodes and scripts that are unrelated to the bug makes it much harder.

Sometimes the process of creating the MRP will help you find the bug yourself.

OofStatement

I tried making a version with only four buttons, but couldn't reproduce the error.

I added this after line 94 and it seems to have fixed the problem.

var timer = Timer.new()
	add_child(timer)
	timer.wait_time=0.01  
	timer.one_shot = true  
	timer.start()
	timer.connect('timeout', self, '_on_Timer_timeout')

I put everything after line 96 into the _on_Timer_timeout function.

« Previous Page