-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect information on editing creating scenes and instances #10503
Comments
The ball scene is a |
When Following through the guide I downloaded the Instancing_starter.zip, extracted and imported it, all is fine till getting to the Editing scenes and Instances section I double-click ball.tscn, select the ball not and in the inspector it's a CollisonShape2D which doesn't have physicsMateral property to expand. Unlike in the guide. Hope that makes sense, really confused me when I went through the guide and just ended up skipping it. |
That's not the node, you need to select the root of the scene called |
OOOHHHHHH I get it now! I do think that maybe some rewording might be needed for the line: No doubt I'm not the first idiot to just select the ball in the scene viewfinder. Many thanks |
Your Godot version:
4.3
Issue description:
Incorrect information on editing creating scenes and instances
The guide shows the ball as a RigidBody2D when in the instancing_starter.zip. the ball is a CollisionShape2D.
URL to the documentation page:
https://docs.godotengine.org/en/stable/getting_started/step_by_step/instancing.html#editing-scenes-and-instances
If you know how to fix the issue you are reporting please
consider opening a pull request. We provide a tutorial on
using git here: https://docs.godotengine.org/en/stable/community/contributing/pr_workflow.html,
writing documentation at https://docs.godotengine.org/en/stable/community/contributing/docs_writing_guidelines.html
and contributing to the class reference here: https://docs.godotengine.org/en/stable/community/contributing/updating_the_class_reference.html
The text was updated successfully, but these errors were encountered: