How to rotate the Phantom 3d Camera left and right for tank controls for existing player character #227
-
|
Hi, I'm a bit new to Godot 4.2 and was trying out the Phantom Camera 3D but I was wondering how would I apply the 3d rotation of the Phantom camera to the player's left and right input as well as have the player be the center of the aforementioned rotation? |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 23 replies
-
|
If you've got an image or video example then it might help figure out an ideal solution, but I'm guessing you are looking for some sort of orbit camera position, where pressing left / right rotates the camera around the player? |
Beta Was this translation helpful? Give feedback.
-
|
Nothing immediately obvious springs to mind when seeing that, but a couple of things to check:
|
Beta Was this translation helpful? Give feedback.
-
|
I believe it's the former since the camera does rotates when the player moves though rotation of the camera has changed within the editor to have it face the player's back within a certain angle. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for the delayed response. I'm guessing it's a case of then applying a specific position and angle every time the character goes between the different areas (land and air). So that there is a hard-coded position and perspective being applied, so you control exactly how it should behave, rather than the system guessing what the intent should be. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, sorry for the late reply I've tried to get the camera to rotate to the mouse similarly to the Third person example but the mouse isn't as responsive as I hoped. For context the I set up the both the main and phantom camera as Export Variables. |
Beta Was this translation helpful? Give feedback.
-
|
It's a bit difficult to debug and validate from a single script alone as many other factors could play into it like physics collisions, other scripts etc. |
Beta Was this translation helpful? Give feedback.
-
|
What's a MRP?
…On Wed, Apr 10, 2024 at 5:06 AM Marcus Skov ***@***.***> wrote:
It's a bit difficult to debug and validate from a single script alone as
many other factors could play into it like physics collisions, other
scripts etc.
If you're able to share a MRP where that script is being used, don't worry
about the environment or model, then that would make it a lot easier.
—
Reply to this email directly, view it on GitHub
<#227 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGVEAO4OWXKS3DUOTU4UTNTY4T6J5AVCNFSM6AAAAABEFNYWOOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TANRYGUYTG>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Minimal Reproducible Project |
Beta Was this translation helpful? Give feedback.
-
|
Voltitan_vol3_MRP.zip
<https://drive.google.com/file/d/1JGF4NAsWYDGy2yepQTeYDUI0X6hGUqXg/view?usp=drive_web>
…On Wed, Apr 10, 2024 at 2:22 PM Marcus Skov ***@***.***> wrote:
Minimal Reproducible Project
—
Reply to this email directly, view it on GitHub
<#227 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGVEAO4WZ7ELABCKG4NU3M3Y4V7NBAVCNFSM6AAAAABEFNYWOOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TANZUG44DC>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Voltitan_vol3_mrp.zip
<https://drive.google.com/file/d/1zP8B81vbdqCDFqQktHtIBcmadSnqih6W/view?usp=drive_web>
Sorry the other folder was having some dependency issues here's another
folder. The Minimal Scene is the Test2 scene from the Level folder and can
be played by running the project
…On Wed, Apr 10, 2024 at 2:22 PM Marcus Skov ***@***.***> wrote:
Minimal Reproducible Project
—
Reply to this email directly, view it on GitHub
<#227 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGVEAO4WZ7ELABCKG4NU3M3Y4V7NBAVCNFSM6AAAAABEFNYWOOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TANZUG44DC>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing this! It seems to be account restricted though? At least, can't seem to open the link without a Google account. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry about that, fixed the permissions
Voltitan_vol3_mrp.7z
<https://drive.google.com/file/d/1eWan7JqNpN93MSmM6cDOzSlPWndIOEeY/view?usp=drive_web>
…On Thu, Apr 11, 2024 at 5:48 AM Marcus Skov ***@***.***> wrote:
Thanks for sharing this!
It seems to be account restricted though? At least, can't seem to open the
link without a Google account.
—
Reply to this email directly, view it on GitHub
<#227 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGVEAO2CWCBIZJB4BCPGAJ3Y4ZL7RAVCNFSM6AAAAABEFNYWOOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TAOBRG4ZTA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
That link works! rec.mp4 |
Beta Was this translation helpful? Give feedback.
-
|
It turns out the camera responds to the mouse input when I switched the unhandled input function the _input function event instead. |
Beta Was this translation helpful? Give feedback.
-
|
If |
Beta Was this translation helpful? Give feedback.
-
|
The function that captured the input would be the get_input(delta) function from the player's script since that function handles the player's controls on land. |
Beta Was this translation helpful? Give feedback.
-
|
The level scene in question is the test2 scene within the Level folder. The player's behavior earlier was before I attempted to have the camera use the mouse inputs like the 3rd person controller example scene. I was having trouble having the phantom camera respond to the mouse inputs.
…On Fri, Apr 12, 2024, 6:21 AM Marcus Skov ***@***.***> wrote:
That link works!
So opened up the project and the scene you mentioned, but I am a bit lost
as to how it works. It looks and behaves differently than the video you
shared earlier and am not sure where to start?
https://github.com/ramokz/phantom-camera/assets/5159399/efb1b7a3-3849-41f2-bc01-5ebf5295cdd6
—
Reply to this email directly, view it on GitHub
<#227 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGVEAO2HMOM2RT235VN2O5DY46YUFAVCNFSM6AAAAABEFNYWOOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TAOJUGMYDS>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Are you still having issues then? Since I'm not entirely sure what I should be looking for in the project files. |
Beta Was this translation helpful? Give feedback.
-
|
The player within the Test2 scenes is the one with the problem with the unhandled inputs as well as the one using the third person phantom camera. So far the camera still responds to the _input function rather than the unhandled input. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, got distracted with the recent release and getting fixes in. Would suggest creating a new scene / project that only has the bare minimum setup for the controls and camera. That way, you can start isolating the possible variables that cause the issue. To the previous comment, it's highly likely that something else is overtaking the input controls, but it's difficult to spot what that might be with so much going on. That's also the intent behind MRP (minimal reproducible project), where only the essentials are present to avoid conflicting logic that larger projects contain. It is also helpful for others who are unfamiliar with a project by not having to debug larger codebases that might be interfering, and instead just focus on a specific issue. |
Beta Was this translation helpful? Give feedback.
-
|
The Inputs themselves are actually handled by the get_input function that's
called through the physics_process function of the player(VolTitan) script.
I think that might also be a factor for the issue with the unhandled input
not responding to the mouse.
…On Thu, May 9, 2024, 6:09 AM Marcus Skov ***@***.***> wrote:
Sorry, got distracted with the recent release and getting fixes in.
I had a look again, but it's a bit difficult to figure out what might be
causing it, as a lot of things are happening in the project / scripts.
Would suggest creating a new scene / project that only has the bare
minimum setup for the controls and camera. That way, you can start
isolating the possible variables that cause the issue. To the previous
comment, it's highly likely that something else is overtaking the input
controls, but it's difficult to spot what that might be with so much going
on.
That's also the intent behind MRP (minimal reproducible project), where
only the essentials are present to avoid conflicting logic that larger
projects contain. It is also helpful for others who are unfamiliar with a
project by not having to debug larger codebases that might be interfering,
and instead just focus on a specific issue.
—
Reply to this email directly, view it on GitHub
<#227 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGVEAO4QS4LV5ASTIOXO3FDZBNDNPAVCNFSM6AAAAABEFNYWOOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TGNRXGA2DC>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Here's new MRP that isolates the clutter.
Voltitan_vol3_mrp2.zip
<https://drive.google.com/file/d/1SjfvGAm5_tZtLFeLhU5ngIkC4LZ2xqBp/view?usp=drive_web>
…On Thu, May 9, 2024 at 6:09 AM Marcus Skov ***@***.***> wrote:
Sorry, got distracted with the recent release and getting fixes in.
I had a look again, but it's a bit difficult to figure out what might be
causing it, as a lot of things are happening in the project / scripts.
Would suggest creating a new scene / project that only has the bare
minimum setup for the controls and camera. That way, you can start
isolating the possible variables that cause the issue. To the previous
comment, it's highly likely that something else is overtaking the input
controls, but it's difficult to spot what that might be with so much going
on.
That's also the intent behind MRP (minimal reproducible project), where
only the essentials are present to avoid conflicting logic that larger
projects contain. It is also helpful for others who are unfamiliar with a
project by not having to debug larger codebases that might be interfering,
and instead just focus on a specific issue.
—
Reply to this email directly, view it on GitHub
<#227 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGVEAO4QS4LV5ASTIOXO3FDZBNDNPAVCNFSM6AAAAABEFNYWOOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TGNRXGA2DC>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Am not sure which file to open? Opening the project triggers an error for a Beta scene, and the only scenes that are open by default are the addon's Third-Person example scene and Think the issue you're facing here is more of a general Godot input conflict rather than something specific to the addon. I, personally, prefer to help out if it's related to Phantom Camera specifically — in particular when it's on a more complicated project such as yours. As mentioned earlier, if the For some more context about MRP, the intent behind a minimal reproducible project (MRP), is that it only contains a single scene with just the content to get the basic behaviour working and to highlight what isn't working. Meaning, no additional script, no assets or fancy stuff in general. It's so that there's no conflicting logic that's interfering, but also so that the issue reporter can potentially self-identify the issue by isolating the problem to as few lines of code as possible. E.g. an addon specific function doesn't work correctly or an error being triggered when toggling something on or off. |
Beta Was this translation helpful? Give feedback.
-
|
The beta scene is the mrp scene with just the player and the the phantom cameras and main camera. But I was wondering for an already established player character do I need to use the Unhandled_Input to use the phantom camera? The player's inputs are handled by the get_input(delta) function. The camera still works when using the _input(event) instead of unhandled_input |
Beta Was this translation helpful? Give feedback.
-
|
Sure, but the Beta scene is still throwing an error when trying to open it: To answer your question, you ought to be using My point in the previous post is that the addon itself isn't the underlying issue, but rather that there's a conflicting input in the other scripts in the project/scene(s). So the help request that I'm hearing isn't specific to the project, but rather an input management issue for a particular project. Something, I think, is more appropriate in a general Godot forum, as technically anyone would be able to help |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the suggestion, and the Phantom camera responds with the unhandled_input within the player's controller it turns out its the control nodes within the level's scene that are interfering with the mouse's input. |
Beta Was this translation helpful? Give feedback.
-
|
On Wed, May 15, 2024 at 12:13 PM DaShawn Jones ***@***.***>
wrote:
… Here's new MRP that isolates the clutter.
Voltitan_vol3_mrp2.zip
<https://drive.google.com/file/d/1SjfvGAm5_tZtLFeLhU5ngIkC4LZ2xqBp/view?usp=drive_web>
On Thu, May 9, 2024 at 6:09 AM Marcus Skov ***@***.***>
wrote:
> Sorry, got distracted with the recent release and getting fixes in.
> I had a look again, but it's a bit difficult to figure out what might be
> causing it, as a lot of things are happening in the project / scripts.
>
> Would suggest creating a new scene / project that only has the bare
> minimum setup for the controls and camera. That way, you can start
> isolating the possible variables that cause the issue. To the previous
> comment, it's highly likely that something else is overtaking the input
> controls, but it's difficult to spot what that might be with so much going
> on.
>
> That's also the intent behind MRP (minimal reproducible project), where
> only the essentials are present to avoid conflicting logic that larger
> projects contain. It is also helpful for others who are unfamiliar with a
> project by not having to debug larger codebases that might be interfering,
> and instead just focus on a specific issue.
>
> —
> Reply to this email directly, view it on GitHub
> <#227 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BGVEAO4QS4LV5ASTIOXO3FDZBNDNPAVCNFSM6AAAAABEFNYWOOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TGNRXGA2DC>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Beta Was this translation helpful? Give feedback.
Sure, but the Beta scene is still throwing an error when trying to open it:
To answer your question, you ought to be using
_unhandled_inputfor gameplay related inputs. Like its name implies, it only triggers when something else doesn't catch inputs. E.g. if you have a pause menu open, you probably don't want the playable character, and PCams, to be controllable at that point. Godot covers that in more detail on this page.My point in the previous post is that the addon itself isn't the underlying issue, but rather that there's a conflicting input in the other scripts in the project/scene(s). So the help request that I'm hearing isn't specific to the project, but rather an input manageme…