I can't get my game to react to keyboard presses

This is a READ-ONLY snapshot of the Godot Community Forums when TwistedTwigleg was the owner, which is hosted for archival reasons only. The current Godot Community Forums can be found here.

Some links may point to external websites, including the current Godot Community Forums. These websites are not associated with TwistedTwigleg.

I can't get my game to react to keyboard presses

legionnaire

I an absolute noobie so I have been doing some YouTube tutorials I can follow them fine until I have to use keyboard input. I do everything exactly as stated in the tutorial but when when I run the node everything is fine until I try to move the character. it just won't move at all using the key input. it does not respond to any key press.

I tried to follow different tutorials and is the same with all. it just won't respond to keyboard inputs. I don't know if this helps but I am using a 2015 MacBook Air.

my Script

extends Area2D


export var speed = 400.0

func _process(delta):
	var direction = Vector2.ZERO
	
	if Input.is_action_pressed("move_right"):
		direction.x += 1
		
	if Input.is_action_pressed("move_left"):
		direction.x -= 1
	
	if Input.is_action_pressed("move_up"):
		direction.y -= 1
	if Input.is_action_pressed("move_down"):
		direction.y += 1
	
	if direction.length() > 1:
		direction.normalize()
	self.position += direction * speed * delta

cybereality

Did you setup those actions in the input map? You have click Project Settings, then the Input tab, and enter all those names for the actions and their keys.

legionnaire

yes I did. I created those names in the project settings-> input and I assigned It the keys a s d w.

cybereality

I see that your script is on an Area2D. You probably want it to be on a Node2D, and have 2 child nodes, the Area2D and a Sprite (for your graphics). You can alternatively made the parent node a KinematicBody2D if you need physics, but the code will need to change. Try to get it working with a Node2D first before you add physics. So add a new node Node2D and then drag the Area2D and your Sprite as children of that. Remove the script and re-add it to the parent (the Node2D) and then edit the script so at the top is says "extends Node2D". I believe that will work.

legionnaire

@cybereality: Thanks. I figured it out!!! It was really a noobie mistake. when I created the script for the player y did not create it as a node to the player so it wasn't attached to it. I am assuming it was because it didn't have any direct link to the player scene that caused the problem. now everything is fine after like 5hrs of trying to figure it out. Thank you very much for your assistance.

Erich_L

Don't forget to share what you've made after you get a good grip on the engine <3

newmodels

yes, the script has to be attached to a node in the scene tree. Godot goes down the scene tree and runs _process and other functions.

legionnaire

@Erich_L said: Don't forget to share what you've made after you get a good grip on the engine <3

I will! if I ever get past the frustration of trying to learn all this stuff. It seems overwhelming for my slow learning brain.

legionnaire

" Cannot get class 'FontData'. "

does anybody know what this mean? I keep getting this error when I try to run my latest iteration of the code but I am not using text or fonts in the test code or scripts.

cybereality

If you double click on the error, it should bring you to the code that is causing the problem.

legionnaire

it doesn't point to any error it just highlife a single word depending on where I click

legionnaire

at the time I think there is a bug with Godot. I thought I had it all figured out but apparently not. I am following a tutorial by GDQuest on YouTube. it a basic 2d platform game. I create a player, I insert a graphics block I set the collision and create two scripts one is the player script and the other is the actor script I set up this script code:

extends KinematicBody2D
class_name Actor

func _physics_process(delta: float) -> void:
	var velocity: = Vector2(300,0)
	move_and_slide(velocity)

and it works fine. it moves the block right

but when I modify the code to this:

extends KinematicBody2D
class_name Actor

var gravity := 3000.0
var velocity := Vector2.ZERO

func _physics_process(delta: float) -> void:
	velocity.y = gravity * delta
	move_and_slide(velocity)

the block is suppose to move down but it just stand still as if the scene froze and worst is that no matter what I do, if I replace it back to the previous code and run it the code does exactly as with this las code. the demo scene just seems to freeze. The block just won't move at all.

this thing has me stomp

Did I mention I am on a 2015 MacBook Air?

Calinou

As reported in the GitHub issue, this is not a bug within Godot. See the comments there.

legionnaire

@Calinou said: As reported in the GitHub issue, this is not a bug within Godot. See the comments there.

you are assuming I am an idiot or something and I am starting to wonder whether I am as well. cause when I create the original script as below: ` extends KinematicBody2D class_name Actor

func _physics_process(delta: float) -> void: var velocity: = Vector2(300,0) move_and_slide(velocity)

` it works fine. it moves a sprite to the right at a constant speed but when I modify it and run it, it doesn't work anymore. If I return the script to the code above it still doesn't work anymore. it just displays the sprite in it's original fixed position (NO MOTION).

have you tried it on a MacBook Air? I suspect the issue is with the Mac build.

@Calinou the challenge now is that you closed the issue, how am I supposed to challenge the decision. It's also not nice to just assume without even an attempt to look into it. I hope that's not how you treat all the new comers in to this engine.

Megalomaniak

Your velocity is 0 on x since you are assigning it as such initially and not modifying it, and you aren't iterating(adding or subtracting) to/from the Y velocity either so it's a constant value of 3000 * delta.

for starters make line 8:

    velocity.y += gravity * delta

instead of:

    velocity.y = gravity * delta

legionnaire

@Megalomaniak the thing is that I have started this project several times. If I just follow the instructions from the tutorial up to the more advanced example the code runs fine. but if I follow the tutorial from the simple example execute the scene and then move to the more advanced instruction set it just freezes and no matter what I do, I can't get the sprite to move after that. I am following the example from this tutorial on you tube

the tutorial starts at 2:19 I do exactly as it says but can't get it to work in the same manner. it just freezes.

legionnaire

@Calinou

Well it does seem to be a bug with the Mac build of the editor. I tried it in a windows build and it works fine. it's just the Mac build that gives me the headaches and since the Mac is my preferred programming system, if this isn't addressed I might not stick with this much longer.

... I just wish you were a bit more patient with the newbies. stuff like this is what I believe keep people from sticking with GoDot.

cybereality

I'm not sure what the precise issue is, but I can send you an example that works. I've been using Godot for over 2 years, and it works fine. There are certainly bugs in the engine, as with any complex software product, but this AFAIK is not one of them.

Especially when starting out as a beginner, you should assume your code is wrong, not that there is a bug in the engine, or a driver issue, or some OS problem. While that is certainly possible, and I've seen it in my experience, it should be the last line of thinking. Almost always you have made a mistake because you are not experienced in a particular tool and programming language. And there is nothing wrong with that, we all start somewhere.

cybereality

Here is an example project you can play with. https://drive.google.com/file/d/1T2VDMFr3petdbGj1vsd2vnwMgGm6K73-/view?usp=sharing

legionnaire

@cybereality Thanks but I don't need to try it. The guy from the tutorial has the complete tutorial files and when I run them, they ran fine. its when I go through the process of creating the game and modifying the files that cause the problem. are you using the Mac version of the editor? cause that's where the problem seem to be.