Yellow-Dog-Man
Provide a way to adjust the position (distance or near clip) of the desktop Shift-P camera
Is your feature request related to a problem? Please describe.
Using RenderMaterialOverride or RenderTransformOverride it's possible to adjust things so your avatar's hair does not appear in your first person view, without having to set a distant nearclip. Here's what my view looks like using RenderMaterialOverride.
However, if you specify UserView in RenderMaterialOverride, your hair still appears in a Shift-P photo.
Specifying a second RenderMaterialOverride for the Camera view will fix the problem with Shift-P, but then if you take a picture of yourself from the outside, you end up bald in camera previews (but not in the final image, curiously).
Describe the solution you'd like
- Provide a way to adjust the shift-P screenshots to go a bit further out from the user view, OR
- Make the shift-P screenshots use the UserView RenderOverrides (while Ctrl-P still uses Camera)
Describe alternatives you've considered
Horrible protoflux hacks which look for the user pressing shift-P and try to change the Render*Override configuration before the picture is taken....?
Additional Context
No response
Requesters
bd_
The distance of the finger camera can be adjusted in VR by moving your hands; in desktop you don't have that option.
This would be useful to me, my primary avatar has the front of the face taking up half my screen whenever I take screenshots with shift+p, making the camera not viable for most situations.
This is kind of a duplicate of/related to #1978 which was previously closed, but it would be interesting to see if anything has changed because I am still interested in this and my request too
I don't see why this couldn't just be added as a component defining an anchor or offset; the offset for the camera is something that really does need tuned for each individual avatar and adding a camera mode RTO would be undesirable in nearly every other circumstance where you may wish to take a picture.
I don't even understand the closing reason on that issue because none of the offered solutions apply to cameras?
