Getting a weird error on a new project

[vitez_vaddiszno]

I'm new to Godot (if it matters, I have notable experience in Python and a little in C# and C++ as well, and I used to make some platformers in Game Maker Studio when I was 13 or so).

I'm following this tutorial: https://www.youtube.com/watch?v=S8lMTwSRoRg

and right when he runs the first instance of the program at 6:50, I already get an error:

E 0:00:00:0038 parse_mapping: Unrecognized input string "20f0" in mapping:
03000000790000000600000000000000,Sanwa Supply JY-P76USV,crc:20f0,a:b0,b:b1,back:b8,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,leftshoulder:b4,leftstick:b10,lefttrigger:b6,leftx:a0,lefty:a1,lefty:a1,rightshoulder:b5,rightstick:b11,righttrigger:b7,rightx:a2,righty:a4,start:b9,x:b2,y:b3,platform:Windows,
<C++ Error> Condition "true" is true. Continuing.
<C++ Source> core/input/input.cpp:1494 @ parse_mapping()

I have no idea how to interpret this. It looks like it has a problem with a USB controller that's plugged in, but even if I remove it, the error appears when running the project. I haven't even done anything other than what he did in the video: create a new project, make a 2D scene and rename the main node.

Does anyone have any idea what I may be missing? Thanks.

[umop-apisdn]

So... You're crashing when running a brand-new empty project?

I suspect a hardware issue, or perhaps a corrupted install.

[vitez_vaddiszno]

Originally posted by umop-apisdn:

So... You're crashing when running a brand-new empty project?

I suspect a hardware issue, or perhaps a corrupted install.

Not crashing - the empty gray scene appears fine in its new window, I just get this error in the log section and worry that it may cause problems down the line if I leave it unaddressed.
My PC is a few years old, but quite capable, and the install is fresh from Steam.

As I said, it looks like it detects some unrecognized input from my controller (judging from stuff like leftshoulder, leftstick, lefttrigger etc.) but I'm not even touching it when this happens.

[umop-apisdn]

Sounds like it could be a hardware issue... Unplug your controller, reboot, and see if it still does it. Having errors before you even get started isn't a good way to go; tracking down the source of the issue should be a high priority.

If the error goes away after you remove the controller, then the problem probably exists inside the controller. As sad as losing a favorite controller is, that's quite likely the best case scenario... moving forward from there starts getting into the motherboard and other expensive components.

[vitez_vaddiszno]

Originally posted by umop-apisdn:

Sounds like it could be a hardware issue... Unplug your controller, reboot, and see if it still does it. Having errors before you even get started isn't a good way to go; tracking down the source of the issue should be a high priority.

If the error goes away after you remove the controller, then the problem probably exists inside the controller. As sad as losing a favorite controller is, that's quite likely the best case scenario... moving forward from there starts getting into the motherboard and other expensive components.

Yep, I've done just that. unplugged, restarted pc, started the project again in godo. Got the same error. It's strange how I seem to be the first person this has happened. Well, I'll wait if maybe someone knows what the error message is referring to, as it seems to be my only lead.

This line in particular seems as if it's a piece of dryly written IT humor:
<C++ Error> Condition "true" is true. Continuing.

[umop-apisdn]

You might try a different version of Godot, to see if it's just a problem with the current Steam version? https://godotengine.org/download

My personal thought is that it's a bad USB port, but hardware is usually difficult to diagnose from a distance.

Since you mentioned being able to work with C++, I'll mention that you can view the Godot Engine source at https://github.com/godotengine/godot - the specific file the error mentions is located at https://github.com/godotengine/godot/blob/master/core/input/input.cpp and parse_mapping() starts at line 1438.

[vitez_vaddiszno]

Originally posted by umop-apisdn:

You might try a different version of Godot, to see if it's just a problem with the current Steam version? https://godotengine.org/download

My personal thought is that it's a bad USB port, but hardware is usually difficult to diagnose from a distance.

Since you mentioned being able to work with C++, I'll mention that you can view the Godot Engine source at https://github.com/godotengine/godot - the specific file the error mentions is located at https://github.com/godotengine/godot/blob/master/core/input/input.cpp and parse_mapping() starts at line 1438.

Looks like we've found the solution at the same time! I've since read a bunch of reddit and git threads where people were having the same issue, though with different input strings (mine was "20f0", theirs were different). The conclusion was also using the non-steam version, and indeed the error is absent there, though only in the normal version. The .NET versions retains the error. Thanks for the help anyways! Hope it gets fixed in the other versions.

[jagholin]

It is very strange to jump to hardware issue explanation, when the godot editor itself is full of bugs and issues like this

[umop-apisdn]

Originally posted by jagholin:

It is very strange to jump to hardware issue explanation, when the godot editor itself is full of bugs and issues like this

You're not wrong about the amount of bugs and weirdness generally present in the Godot Engine, but "I'm one of a very few people experiencing issues like this one" and "it seems to be connected to a physical peripheral" are both things that can indicate a hardware issue, rather than software.

Source: I've been slinging code since 1986, and turning a screwdriver since 1992.

[🇰🇵Burner🇰🇵]

I have gotten a similar looking error for the past year and a half, I just ignore it

[darek.niksa]

this bug is very common and for now I think It is not doing anything

[vitez_vaddiszno]

Originally posted by umop-apisdn:

Originally posted by jagholin:

It is very strange to jump to hardware issue explanation, when the godot editor itself is full of bugs and issues like this

You're not wrong about the amount of bugs and weirdness generally present in the Godot Engine, but "I'm one of a very few people experiencing issues like this one" and "it seems to be connected to a physical peripheral" are both things that can indicate a hardware issue, rather than software.

Source: I've been slinging code since 1986, and turning a screwdriver since 1992.

As it turned out, it was a software issue (the bugged Steam version) having an issue with my (flawlessly working) hardware, so while the logic is sound, things are not always what they seem.

[umop-apisdn]

Originally posted by vitez_vaddiszno:

As it turned out, it was a software issue (the bugged Steam version) having an issue with my (flawlessly working) hardware, so while the logic is sound, things are not always what they seem.

Ok, cool. How did you solve the issue?

[vitez_vaddiszno]

Originally posted by umop-apisdn:

Originally posted by vitez_vaddiszno:

As it turned out, it was a software issue (the bugged Steam version) having an issue with my (flawlessly working) hardware, so while the logic is sound, things are not always what they seem.

Ok, cool. How did you solve the issue?

By using the non-Steam version from the website.
(But I mean, I've already told you this in a reply on May 28th, so now I'm feeling a little derealization)

[umop-apisdn]

Originally posted by vitez_vaddiszno:

Originally posted by umop-apisdn:

Ok, cool. How did you solve the issue?

By using the non-Steam version from the website.
(But I mean, I've already told you this in a reply on May 28th, so now I'm feeling a little derealization)

Yeah, alright... but you realize you're the one who brought this back up, right?

[vitez_vaddiszno]

Originally posted by umop-apisdn:

Originally posted by vitez_vaddiszno:

By using the non-Steam version from the website.
(But I mean, I've already told you this in a reply on May 28th, so now I'm feeling a little derealization)

Yeah, alright... but you realize you're the one who brought this back up, right?

I just wanted to expand on your reply with additional info for anyone who may read the thread. Namely, that they should keep in mind that even if all signs point to a software having issues with a hardware, the problem may still lie in either the software or the hardware.