actually a bit more difficult than i expected to get this working the way i wanted in godot versus unity. in unity i could just set a texture to be where a camera outputs to. in godot if you want a camera to output somewhere else, it needs to be a child of a subviewport node. and a subviewport node is not a child of the "node3d" node, meaning it does not inherit attributes like a 3d transform, so if you had a first person camera on your character that turns left and right, that camera can no longer inherit the transform from the parent object, and you have to update its position in code, perhaps having another 3d node be the placeholder. then you have to assign these textures at runtime too, which also works oddly in godot because I can't have two scripts access each other's data easily, you need to use a method to send data(a "signal"). (& had to do this twice for the facecam..)
Trans Mermaid
- she/mer
Tired lesbian barely able to do much outside of survive work.
in reply to @slitherpunk's post:
Oh hell yeah, love a facecam for the player character! If it’s ok to ask, how’re you getting the second camera projecting onto the screen?
It's a little complicated but I go over that in my other post here:
https://cohost.org/slitherpunk/post/4532493-actually-a-bit-more
in reply to @slitherpunk's post:
There's a node you can use called RemoteTransform3D that automatically assigns its transform to another node. You could potentially set that up to move your camera. Also, there's a ViewportTexture which you can set up (though it requires a special "local to scene" flag on itself and its parent material) which you can point to your viewport to set your texture automatically. Maybe those could help a bit?
🤷 i've already got this working as is, i feel like i don't want to fiddle around in that hierarchy too much more getting messy with even more nodes if i don't have to