Let us edit NearPlaneZ Camera Property - Parts getting clipped by camera

The Camera Instance’s NearPlaneZ property affects clipping when an object gets too close to the camera. This wouldn’t be a problem if the NearPlaneZ was something like -0.001 or something similar, but it’s actually -0.1.

That’s a large chunk of the Z axis you can play around with. Roblox should let us change it to improve our way of life, especially us who make FPS games with on screen viewmodels. One way to play around the limit is by scaling everything up by 10x but that’s not practical.

This is what happens when Roblox forces the NearPlaneZ to -0.1 instead of something more realistic like -0.005 or -0.001.

Please Roblox.

18 Likes

bump
im also having issues with vm clipping into the plane

1 Like

bump

making a fractal game similar to fractal block world, but scaling up/down is super limiting because of both the 2048 stud size limit and the 0.1 stud NearPlaneZ
if the NearPlaneZ was at something like 0.005 i could scale the player far smaller without issues. this makes the minimum player size far smaller, meaning i can lower the default player size and have the maximum player size be much larger relative to default without worrying about the size limit. this way, the player can scale up and down well over a dozen times before reaching engine limitations

I’m bumping this too, because there’s still no way to edit it.

I need this to be editable for my game. bump bump bump bump

Solution:

In Workspace set its Scale property to something larger than 1 and it’ll make the NearPlaneZ cutoff less significant and as a side effect it will also improve shadow fidelity.

image

i would not call changing the entire scale of your map a solution

2 Likes

It absolutely is a solution to this engine constraint

this is a feature request, it would be different if you were asking for help on how to achieve something similar, but thats not what this is. The actual solution would be getting whats requested, and so far that hasnt happened

staff wont look at this if it already is marked as completed, incorrectly giving it a “solution” helps no one

5 Likes

This is a solution to solve the problem of NearPlaneZ clipping, a workaround is still a solution.

a workaround is not a solution in this case, this is as good as me requesting shader support and marking the solution as reverse engineering studio and implementing it myself

2 Likes

I’m keeping it as a solution because it very much is one because it solved the need for this property. There’s nothing stopping you from resizing workspace, it’s as easy as editing one property.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.