3D FPS Tutorial from the engine documentation, keyboard problem

green-baron

am trying to run the part one https://docs.godotengine.org/en/stable/tutorials/3d/fps_tutorial/part_one.html. Mouse movement works, but there's no response to keyboard movement or jump. Have i forgtten to wire up something in the projekt settings or some such (Linux) ?

TwistedTwigleg

In the project settings, what actions do you have setup? Probably the input mappings either got lost on import or something.

green-baron

"movement_forward" is set to key W and Up and the other three to A,S,D and Left, Down, Right respectively. "Movement_jump" is set to Space, and the others I haven't had yet.

In order to be sure i cut & pasted the player script from the link without any changes, switched to Testing_Area and run it.

TwistedTwigleg

Hmm, maybe something is broken with the project then. It wouldn't surprise me, it's a couple years old at this point. Which version of Godot are you using?

green-baron

3.2.1 stable official.

And may I say, keyboard cooperates with GLFW in my own tinkering with a render "framework".

No problem, i'll look around for more tutorials.

TwistedTwigleg

@"Green Baron" said: 3.2.1 stable official.

And may I say, keyboard cooperates with GLFW in my own tinkering with a render "framework".

No problem, i'll look around for more tutorials.

Hmm, I dunno, to be honest. Sorry! It might be something is messed up with the tutorial.

green-baron

@TwistedTwigleg: The problem appears to be in the engine, not in your tutorial (phew) :-)

I had the same problems with another turial (gamefromscratch), where they use is_key_pressed() instead of is_action_pressed(), and still the keyboard was unrepsonsive .... in most cases. But once it worked and i couldn't reproduce it ... until I found out that switching to another application and back again enabled keyboard acceptance. Looks like the window has no focus initially or some such ?

3.2.1 is already history, maybe this is fixed in newer versions, then.

Just as a sidenote, I may have posted this in the wrong subforum, as it is not related to 3D alone ...

TwistedTwigleg

@"Green Baron" said: @TwistedTwigleg: The problem appears to be in the engine, not in your tutorial (phew) :-)

I had the same problems with another turial (gamefromscratch), where they use is_key_pressed() instead of is_action_pressed(), and still the keyboard was unrepsonsive .... in most cases. But once it worked and i couldn't reproduce it ... until I found out that switching to another application and back again enabled keyboard acceptance. Looks like the window has no focus initially or some such ?

3.2.1 is already history, maybe this is fixed in newer versions, then.

Well, I’m glad it’s not the tutorial! Shame it appears to be an engine bug though, as those are (generally) harder to fix. I’d check to see if the latest version of Godot shows the issue, and if it does, maybe open an issue on GitHub if one does not exist.

Just as a sidenote, I may have posted this in the wrong subforum, as it is not related to 3D alone ...

I’ll move it to general support.

green-baron

It might be that my problem is related/identical to an issue reported on the Tutorial's github repository, where a user reports that his character doesn't move. Just sayin'.

It is well tutorial with a lot of insight. But now I got a new problem, I am sorry @TwistedTwigleg .

I reached the end of part 2 and started with part 3. At the start, two scenes are introduced, space and ruins. They have nodes for ceiling/floor/walls, but at least the floor doesn't "hold", the player and other bodies like cubes fall through. There are a bunch warnings (e.g.: "return value discarded" and "unused argument", probably just cosmetics I suppose) but also errors of type "rocover from penetration" in Player.gd in function process_movement, the line

vel = move_and_slide(vel, Vector3(0, 1, 0), 0.05, 4, deg2rad(MAX_SLOPE_ANGLE))

Edit: ok, I found out that assigning the mesh library Space_Level_Mesh_Lib.tres to the floor_and_cailing node fixed the fall through for the player. Doing the same for the Walls fixes the rest, also the bounciness. The level plays nicely, then. So I think that fixes the issue, and the errors have disappeared. I love it when errors disappear :-)

Nice level. I like the atmosphere :-)

Cheers

Megalomaniak

Changes to the collision object in the new engine version have likely broken things and assignments would have to be updated in the example files if I had to wager a guess.

green-baron

I see. I assume you're talking about the upcoming 4.x engine ? Because the tutorial now works as expected, I am still on 3.2.1 for now and for learning ...

Megalomaniak

4.0 more than likely will see changes yes, but I'm saying somewhere in the 3.2 release cycle there might have been a change causing scenes from some earlier version to lose collision assignments. Or maybe the version the example scenes were created in didn't have such a way of assigning them at all.

TL;DR being that the example files might just need to be updated.

TwistedTwigleg

Yeah, the included zip files need updating. I made a pull request for this, but because the plan for the documentation seems to be moving tutorials out (or at least long ones), it probably won’t be merged. As far as I can tell, only the GridMap nodes were needing updating though. Everything else seemed to be okay when I was testing.

Edit: To fix the grid maps, you just need to re-export and reassign the GridMap MeshLibrary to the Gridmap. Then collisions and the meshes should work :)

green-baron

Yes, only the two gridmap nodes. Thanks guys, sorry to be a bother.

Megalomaniak

Hmm? No bother. It's what the forum is for.

TwistedTwigleg

Yeah, that's what the forums are here for, so no reason to apologize! It's all good :smile: