Godot terminology guide plus my suggestion

cloa513

I am always tripped by Godot Jargon- people think I am saying one thing rather another. Could people try to use G in front all Godot Jargon especially Gscene, Gsprite.? Just another thread said GODOT can't share between scenes whereas unless you have one of anything it is very difficult with only Gscene.

cybereality

I'm not sure that is a good idea.

cloa513

Please explain. I am happy to listen to real argument-just reply to what I wrote.

DaveTheCoder

I doubt that many people would like that idea.

You could post a poll on the Godot Reddit and see what kind of response you get.

Calinou

I don't think adding a prefix to all Godot-specific concepts makes sense. It's not going to reduce confusion and won't improve SEO either. If you have difficulty understanding those concepts, I suggest re-reading the documentation from the beginning.

cybereality

@cloa513 said: Please explain. I am happy to listen to real argument-just reply to what I wrote. What you are saying doesn't really make sense. We are on the Godot Forum, clearly everything we are talking about is related to Godot. A Scene is called a Scene, because the creators of the engine designed it that way. It does not help clarity to call it something else other than it's real name. What would Gscene accomplish? We know we are talking about Godot already (as I said, we are on the Godot Forum) and if you look in the documentation, or search for tutorials, it is called "Scene". So making up your own names is confusing (both to yourself and anyone you are talking to). Better to just spend some time and actually learn the engine and what the names are called so you understand.

cloa513

Sorry people don't know we talking about Scene in Godot forum because we talk about games at the same time. If this forum was explicitly pure technical forum and then you have problem that technical languages don't enough words (GODOT speak does not enough words) to talk only in them. Other terms like Node are nowhere near as confusing because they are rather uncommon.

Megalomaniak

Most game engines - even most realtime 3D engines in general have some concept of a scene-graph/scene-tree. I don't see whats so confusing about that.

cloa513

@Megalomaniak said: Most game engines - even most realtime 3D engines in general have some concept of a scene-graph/scene-tree. I don't see whats so confusing about that.

Doesn't make it smart terminology- bad for every beginner. By the way you say concept not jargon- what do other engines call it- Unity calls objects equivalents Prefabs which is way better. I am not saying poor choice of jargon is in any way unique to GODOT. Other problematic stuff is that people to Sprite, Texture and Image as the same thing- if that's true why have three terms for the one thing. That instantiating (not a problematic term as it rather uncommon in English) is referred three ways including instantiation

cybereality

Sprite, Texture, and Image are not the same thing. I think you are just confused.

cloa513

@cybereality said: Sprite, Texture, and Image are not the same thing. I think you are just confused.

You please clarify- Definitely what others have written.

cybereality

So a Sprite is a 2D graphic that can move. Like Mario in a platforming game. It can have an Image attached (or multiple Images in the case of animation) but it is not just an Image. A Sprite can have other properties like a position, or a rotation, or scale, etc. Texture and Image are related but not the same. And Image is like a photograph, a JPG or PNG on your computer. A Texture is a data structure that can hold Image data, typically something that resides in video memory on a graphics card. You could then apply the Texture to a 3D model so you could see it on the screen. So the Texture is created from the Image, and they may represent the same thing, but technically they are not the same.

Megalomaniak

Similar to pictures and their relation to pixels there is the concept of a texture and it consists of texels. Whats the difference? A picture is an image mapped directly to the screen/output display. A texture is mapped to a digital surface that can itself be transformed.

cloa513

@cybereality said: So a Sprite is a 2D graphic that can move. Like Mario in a platforming game. It can have an Image attached (or multiple Images in the case of animation) but it is not just an Image. A Sprite can have other properties like a position, or a rotation, or scale, etc. Texture and Image are related but not the same. And Image is like a photograph, a JPG or PNG on your computer. A Texture is a data structure that can hold Image data, typically something that resides in video memory on a graphics card. You could then apply the Texture to a 3D model so you could see it on the screen. So the Texture is created from the Image, and they may represent the same thing, but technically they are not the same.

All well and good but really you need to explain in terms of GODOT,

cybereality

That is in relation to Godot. And these are general game programming and computer graphics concepts. Godot did not invent them.

cloa513

Sorry but I want to as used in Godot- specific terminology. Scene does not mean the same in Unity as it does in GODOT. It is pretty useless to refer to generic terms. Every engine has its quirks. Node does not exist as a specific entity in Unity rather as a generic term.

Megalomaniak

@cloa513 said: Scene does not mean the same in Unity as it does in GODOT.
It sure does. Just because godot is more capable in terms of what can be done with scenes and how they are constructed doesn't change the meaning or the fundamental concept.

DaveTheCoder

The term "scene" is a little confusing in Godot, because it can mean different things. It could refer to a node and its descendants, it could refer to a scene file (.tscn), or it could be used more generically to refer to a visual display. The context has to be used to distinguish among the different meanings. But I don't know if introducing more terminology would be helpful.

cloa513

@Megalomaniak said:

@cloa513 said: Scene does not mean the same in Unity as it does in GODOT.
It sure does. Just because godot is more capable in terms of what can be done with scenes and how they are constructed doesn't change the meaning or the fundamental concept.

This is not a question of fundamental concept or general meaning. Specific usage in GDScript or GODOT engine is the question.

Megalomaniak

Well in that case, similar to every other engine godot only has 1 "scene" thing and that is the scenegraph. tscn is just a file holding data about nodes that can be instanced into the scenegraph and thats it. The scene graph is the only real scene and it always holds/includes: 1 "root" viewport that rest of your scene data/nodes would live under(i.e. what you composite in the editor) and it has as siblings all your autoloads/globals.

BTW. a tscn file is also known as a PackedScene. So there you go, Scene specifically still refers to exactly the same thing it does in unity or unreal and what you want to have a specific term for has it - a PackedScene.