getting_started/first_3d_game/01.game_setup

[giscus[bot]]

getting_started/first_3d_game/01.game_setup

In this first part, we're going to set up the game area. Let's get started by importing the start assets and setting up the game scene. We've prepared a Godot project with the 3D models and sounds ...

https://docs.godotengine.org/en/stable/getting_started/first_3d_game/01.game_setup.html

[Wadahell]

I had to turn the blue arc for it to light floor, so watch out for that

[stefangorneanu97]

Technically, both work, bcause they're the axes of a sphere.

[ThatChapThere]

Not really. If the light is pointing along an axis rotating that axis will do nothing. It will usually be either red or blue that works, not both.

[BryceDMonaco]

It would be nice to provide assets that are already made for 4.x to skip the conversion step.

[vmorris]

I actually liked going through the conversion as I've never done it before.

[ChadAMiller]

I wouldn't mind a conversion step except I literally cannot get it to work in 4.4. It just crashes.

[firevenus]

I think it is better to let the user know how much exact number should the light rotation on XYZ should be. I had a hard time to find which should I drag and finally I made it by dragging the slide of XYZ axis, then light the Gound up.

[damienjoldersma]

I agree too, I appreciate how they did that for the Ground / CollisionShape3D / MeshInstance3D. Anyways here is what I set the Transform settings for the DirectionalLight3D too:

Position (xyz): 0.0, 12.0, 0.0
Rotation (xyz): 270.0, 0.0, 0.0

[EchJetzt445]

Fair point, but i think this is also to get Familiar with the Enginge, and with Movement and the DirectionalLight, so i kinda also appreciate the learning experience

[Erhannis]

I'm confused why the root node is a plain node rather than 3d. Shouldn't a 3d scene start with a Node3d? The "Create Root Node" dialog even labels it "3D Scene".

[Calinou]

A plain node doesn't have a position/rotation/scale, which avoids scenarios where you accidentally move it around. I suppose you could still use a Node3D and lock it in the editor as an alternative.

[Erhannis]

I would also argue that it's less composable: if you wanted to, say, place a room scene into a larger city scene, if the room's root node doesn't have a transform then (according to my brief tests) you can't move it around.

[ElectricZax]

Keep in mind that this is a most basic tutorial for people that have no idea what they're doing. And for you to throw them in a 'larger city scene'... let's just say it doesn't look like a basic thing to me.

[RobbiewOnline]

At this stage when I run the project it doesn't render anything like what I can see in the preview, but I suspect it's because no camera has been added to the scene yet.

It would be nice if before proceeding you could run the project and see it at runtime for confidence before moving on.

[cgmartin]

I was interested in previewing here, too, for the same reasons. I jumped ahead to set up the camera.

With only a single lit MeshInstance3D at this step there isn't much to visually reference. You can end up with a purely white screen in the preview, depending on position/rotation of the camera, which could be confusing to some. Having a more detailed 3d player in the later section may have been the reason for adding the camera in a later step.

Though, getting introduced to the camera/preview as soon as possible in the tutorial seems best IMO - it is very valuable dev feedback for each step in the process. Perhaps consider moving the camera/preview instructions immediately after adding the player 3d model (and prior to setting up the player input actions).

[eddienoon]

Would I be able to make the mesh a child of the collision node itself or is that frowned upon? I am completely new to game dev and don't know many of the typical "rules" that would be used when designing a level.

[ElectricZax]

Same here (being new). I think you should stick to the tutorial. Learn the steps and bit by bit you will expand your knowledge bit by bit.

Regarding your question - it is loigcal that if it is a child - it is part of the main Collision and Mesh are on the same level, because they overlap. If they are not on the same level, but have parent/child relationship, then this could to problems.

[Catloo-Juan]

I set both the collitionshape3D and MeshInstance3D to 100 x 4 x 100 m but the MeshIntace appears way smaller than the collitionShape3D it stresses me out, also i the ground still looks grey and the player doesents interacts with it (it falls)