-
Notifications
You must be signed in to change notification settings - Fork 384
Base Layer explanation and adding user's intention #44
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
base: main
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -14,33 +14,38 @@ This article includes instructions for implementing this functionality either wi | |||||
Learn more about [layers and cameras](https://wiki.gdevelop.io/gdevelop5/interface/scene-editor/layers-and-cameras/#cameras) and [how to keep UI objects on screen](/gdevelop5/tutorials/keep-ui-on-screen). | ||||||
|
||||||
|
||||||
## Follow an object smoothly | ||||||
## Follow a character smoothly | ||||||
|
||||||
Adding the **Smooth Camera** [behavior](https://wiki.gdevelop.io/gdevelop5/behaviors#adding_a_behavior_to_an_object) to the character make the camera follow it automatically. The **Move camera closer** action can still be used to avoid a 1-frame delay. | ||||||
Add the **Smooth Camera** [behavior](https://wiki.gdevelop.io/gdevelop5/behaviors#adding_a_behavior_to_an_object) to the object *(remember to [install it first](https://wiki.gdevelop.io/gdevelop5/extensions/search/) from the Extension catalog)*. The **Smooth Camera's** parameters such as "catch up" and "speed" can be modified to personalize the smoothness of the camera. | ||||||
|
||||||
!!! tip | ||||||
|
||||||
Learn [how to install new extensions](/gdevelop5/extensions/search) by following a step-by-step guide. | ||||||
Make sure that the character, enemies and platforms on the project are placed on the "Base Layer" on the layer panel. If the issue persist, ask the community on the [forum](https://forum.gdevelop.io/t/camera-not-following-character/45356). | ||||||
|
Make sure that the character, enemies and platforms on the project are placed on the "Base Layer" on the layer panel. If the issue persist, ask the community on the [forum](https://forum.gdevelop.io/t/camera-not-following-character/45356). | |
Make sure that the character, enemies and platforms on the project are placed on the "Base Layer" on the layer panel. If the issue persists, ask the community on the [forum](https://forum.gdevelop.io/t/camera-not-following-character/45356). |
LuniMoon marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an important part of the actual solution. It should not be too far in the doc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I trust you're right.
Tho, I read the article as someone which issue is simple (a basic, beginner's issue): I wanted to follow a single character, with a single camera, and because I come from design (we're very methodical and organised with layers) I had multiple layers with objects (background, base layer, foreground).
So, after learning that all i needed to do was to place my platform (on background) on the base layer along with my character, my issue was fixed. So, the information of knowing how to move several layers together wasn't valuable for me. That's why I moved it to the bottom (true, I've been reading with my use case in mind, so I'm ignorant of others).
I'm starting to be afraid that the article might be failing to resolve the issue (and the reason why we're doing documentation efforts): users struggle to self-diagnose the issue they're experiencing, and feel they have to "guess" from the (so perceived) isolated answers on the web.
I do wonder if the structure of the article should be:
- Which extension to use, and how to install it (done on the first chunk)
- Why are layers a camera, and how do they work? (I tried to address this on the tooltip)
Ending the article here could theorically cover the basics but as we've observed, there can be different intentions on this single title (I wonder if they should be H2 on the article), such as...
- Simply following a platformer object (keeping it simple on the base layer)
- Following an object, but having other stuff in other layers (how can the know if they should use the extension "copy camera possition" or "Move several layers together"?) - (user from the forum wanting to do this)
- Switching cameras between several objects (user from the forum wanting to do this)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Why are layers a camera, and how do they work? (I tried to address this on the tooltip)
This is the role of this other page:
- Simply following a platformer object (keeping it simple on the base layer)
Using only one layer is not a simple solution, it's a just bad solution.
Some platforms and decorations need to be behind the player. If they are on the same layer, new platforms will be added on top of the player. The creator will need to change the z-order of the character each time there is something new and setting the player a big z-order won't cut it because new instances will always be the maxiumum z-order + 1.
Even for a very basic game, not using layers is a ticket to an UX hell.
- Switching cameras between several objects (user from the forum wanting to do this)
It can be a new section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. I know the existence of the Layers and Cameras wiki (it's included in one of the tooltips).
As for the layers, I see what you're saying: for changing Z positioning, I'd like to eventually merge layers with instances.
But for layer usage, like I said, I am very methodical with my layers, so I did separate them on my project as follows: backgrounds, base layer (in which I had my platform) character, and foreground. I had my character in my "character" layer, not on "base layer". After some help from y'all, I moved my character to the "base layer" but not the platform in which it was standing (which caused my character to float in the middle of the scene). My problem was there.
Tristan did suggested adding an extension called "copy camera position" (or something like that) but: 1. I got annoyed that I had to add yet another extension (I wonder if this is what a user meant by "relying too much on extensions"), 2. I didn't understand why I had to copy other camera's possitions.
So, maybe the solution is partially there: instead of giving them a "fake solution" (keeping most of the graphics on the base layer), pointing them to the "proper solution" -> creating a link to another article on why and how to copy camera position to follow a single camera. 🤷
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. I know the existence of the Layers and Cameras wiki (it's included in one of the tooltips). As for the layers, I see what you're saying: for changing Z positioning, I'd like to eventually merge layers with instances. But for layer usage, like I said, I am very methodical with my layers, so I did separate them on my project as follows: backgrounds, base layer (in which I had my platform) character, and foreground. I had my character in my "character" layer, not on "base layer". After some help from y'all, I moved my character to the "base layer" but not the platform in which it was standing (which caused my character to float in the middle of the scene). My problem was there.
This advice was to give you the shortest way to have something that works. It's fine to give this advice to someone that is lost as a temporary solution. It's not fine in an official documentation.
Tristan did suggested adding an extension called "copy camera position" (or something like that) but: 1. I got annoyed that I had to add yet another extension (I wonder if this is what a user meant by "relying too much on extensions"), 2. I didn't understand why I had to copy other camera's positions.
Layers can be copied just like this, but Tristan's extension make it easier to do. I think it's better in an extension because it avoids to have a lot of actions that almost do the same thing directly in the engine (which could be overwhelming for beginners).
So, maybe the solution is partially there: instead of giving them a "fake solution" (keeping most of the graphics on the base layer), pointing them to the "proper solution" -> creating a link to another article on why and how to copy camera position to follow a single camera. 🤷
The existing page has a section for this "Move several layers together".
D8H marked this conversation as resolved.
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To configure the camera to center on an object, go to the [event sheet](https://wiki.gdevelop.io/gdevelop5/events) and **add an Action** *(no need to set a Condition)* called **"Center the camera on an object"**. | |
To configure the camera to center on an object, go to the [event sheet](/gdevelop5/events) and **add an Action** *(no need to set a Condition)* called **"Center the camera on an object"**. |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original title was "Move several layers together". The new one doesn't mean the same thing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't.
The title of the article says "follow an object with a camera", so I wondered if "follow several objects together" wouldn't be better and closer to the original intention, to let the reader know what they'll achieve (instead of how to do it?).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't. The title of the article says "follow an object with a camera", so I wondered if "follow several objects together" wouldn't be better and closer to the original intention, to let the reader know what they'll achieve (instead of how to do it?).
It explains how to make several layer cameras follow 1 object (as if layers were glue together).
Making 2 cameras follow 2 objects is something else and would required a split screen.
Uh oh!
There was an error while loading. Please reload this page.