im having the same issue with this too weird
found a fix!!!
apperantly it was an invisible part that had “CanCollide” off so I just added
params.RespectCanCollide = true
under the raycast that’s used to adjust the camera when it collides with something
it works for now but maybe this might help :3
1 Like
Hi all!
v2.3.0 (patches to some of the common issues reported recently) is now available on GitHub! Updates to the Roblox model itself will be here soon 
2 Likes
I haven’t tried this new version yet, but I noticed when playing in a live game the player can set the camera to whatever type they want. Is that one of the common issues reported that was fixed in this version?
Basically, in studio it works and shows the camera is set by developer but in a live game it gives them the option to change it.
In Studio Playtest:
In Live Game:
For some reason, at certain angles, it glitches my camera under the map.
Nevermind, it was just overlapping with another script
Is it possible to make it so the first person camera is in the position of the head?
Something like this:
robloxapp-20241111-0127306.wmv (1.1 MB)
Oh, and don’t forget to download For some reason, it’s requiring us to.
Hey there! I see this module has had quite useful updates recently and I’m really glad you fixed the common issues. I’ve had one problem for a while now. Let me describe it.
So basically when you add the offset, it seems that there are 2 separate CFrames, the offset and the origin, basically the host. When rotating it seems that origin still stays in the same position and it rotates the offset. So then it seems that the camera is rotating around a point and not at a point.
Here is a veryyy rough image I made.
When the player rotates, it rotates the origin, then the origin rotates the offset, making it seem like the camera is orbiting the origin. I just want it where the camera completely rotates at the origin or the origin cframe is updated to match the offset cframe.
Hey!
How you described the offset is intended behavior for CameraService. That’s how shift-lock views/mechanics are made in this context! I might add functionality for what you’re looking for as an additional property in a future release
If you’re seeking to have the camera rotate around a certain offset point, what I would recommend for now (if using CameraService) is:
- Create a transparent, non-collideable part that is welded/attached/connected in some way to your character by the desired offset you’d want (i.e. an invisible part 2 studs to the right)
- Set the camera’s host to that part specifically! (If you want to retain dynamic head/body motions, make sure this part is parented to the character model directly).
You could also fork the repo to handle that offset you’re looking for. Feel free to DM me if you need any help if you choose that route
Hope that helps!
1 Like
The solution that you provided has fixed my issue. Thank you so much and goodluck with the future updates your gonna make!
1 Like
This is a great module!
I just have one suggestion,
- Is it possible if you can create a function for add and subtract FOV? I have tried to add that myself but I get weird errors and bugs.
Thank you.
What do you mean by that in terms of functionality?
Sorry. My fault I was not clear in what I meant.
The type of functionality I meant was for it to be able to add a certain number to the FOV so that it would be more realistic and dynamic.
You could create a separate function for that, because for some reason I can’t figure it out 
.
Example:
local CAMERA_FOV_DEFAULT = 55
local CAMERA_FOV_SPRINTING = CAMERA_FOV_DEFAULT + 10
local CAMERA_FOV_CROUCHING = CAMERA_FOV_DEFAULT - 10
local function playCameraTween(targetFOV, duration)
TweenService:Create(Camera, TweenInfo.new(duration, Enum.EasingStyle.Quint), { FieldOfView = targetFOV }):Play()
end
UserInputService.InputBegan:Connect(function(input, gp)
if gp then return end
if input.KeyCode == Enum.KeyCode.LeftShift and not IsASprinting and Humanoid.MoveDirection.Magnitude > 0 then
IsASprinting = true
FireStates(true) -- Notify the server to start sprinting
Humanoid.WalkSpeed = 25
playCameraTween(CAMERA_FOV_SPRINTING, 0.5)
--playCameraTweenV2("add", CAMERA_FOV_SPRINTING)
end
end)
I mean instead of always getting the main FOV instead just add it onto the current FOV
This is what I used to do
TweenService:Create(Camera, TweenInfo.new(duration, Enum.EasingStyle.Quint), { FieldOfView = Camera.FieldOfView + targetFOV }):Play()
So is it possible if you can make it just add onto the current FOV and Subtract for the current FOV.
Please,
Thank you
Oh I just fixed it, thanks for your help though.
This is the function if you want to have this dynamic, realistic and unoverridden FOV functionality -
function CameraService:AddOrSubtractFOV(val: number, instant: boolean, AddOrSub : string)
AddOrSub = string.lower(AddOrSub)
--> Make sure that "val" is positive before doing anything
assert(type(val) == "number" and val > 0, "[CameraService] FieldOfView should be greater than 0.")
--> Set up FOV logic
if instant then
if AddOrSub == "add" then
cam.FieldOfView = cam.FieldOfView + val
else
cam.FieldOfView = cam.FieldOfView - val
end
else
if AddOrSub == "add" then
local tween = TweenService:Create(cam, TWEEN_INFO, {FieldOfView = cam.FieldOfView + val})
tween:Play()
tween.Completed:Wait()
tween:Destroy()
else
local tween = TweenService:Create(cam, TWEEN_INFO, {FieldOfView = cam.FieldOfView - val})
tween:Play()
tween.Completed:Wait()
tween:Destroy()
end
end
end
Do you know why everything is jittering and sometimes my head accessory appears?
R6 Localscript in StarterCharacterScripts:
local CameraService = require(game:GetService("ReplicatedStorage").CameraService)
local information = {
Smoothness = 0.1,
RotSmoothness = 0.1,
Wobble = 0,
CharacterVisibility = "Body",
MinZoom = 0,
MaxZoom = 0.001, --> To avoid running into math errors, make sure MaxZoom and MinZoom have a difference of at least 0.001.
Zoom = 0,
AlignChar = true,
Offset = CFrame.new(),
LockMouse = true,
BodyFollow = false,
}
CameraService:CreateNewCameraView("FPS", information)
CameraService:SetCameraView("FPS")
CameraService:ChangeFOV(90)
Unfortunately, I’ve yet to find a solution (if any) for the jitters on R6 avatars. New updates over the years on rendering, framerates, and avatars have unfortunately hurt CameraService’s support of it.
In your specific case, having no offset with body character visibility may mimic that effect. However, it could also be a byproduct of your Smoothness. 0.1 is really low. Perhaps try 0.35 and above?
I would suggest going fully first-person (without a body view) if insistent on using CameraService and changing Smoothness doesn’t work. Otherwise, I would suggest using an Offset, going to R15, or using your own system 
2 Likes
Just a question/clarification, is the plan here to eventually find a fix, then?
Unfortunately, I don’t have enough time on my end to see if there’s a patch
It’s my current belief based on past attempts to resolve the issue that fixing the R6 issues with CameraService would require an entire rewrite of how it works under-the-hood. When that happens is unknown.
However, if anyone is able to find a fix, they’re free to create a fork or a pull request!