PlayerModule.CameraModule.TransparencyController:168: invalid argument #3 to 'clamp'

[mew903]

Yea tick still works, but it’s been removed from all official documentation IIRC so I’m assuming it’s deprecated in favor of the os time functions.

@YummyLava57

I assumed the issue was due to float precision because the only way this could happen is if lastUpdate was higher that tick()

That’s basically what I was trying to say but my thought here is that FPS unlockers cause either tick or that local module to go haywire. I’m basing my thought off of this post here:

Client tick() being far ahead of server tick() when FPS is unlocked?

So im making a remote cooldown script and client has to send its tick() to the server for comparison with its tick(). One of the checks is if the received tick() is not higher than server tick(). This is the result when im in studio (60 FPS): Client tick(), Server tick(), Server tick - Client tick [image] The difference is only 0.015 which is normal, and now in the game with unlocked FPS: Client tick(), Server tick(), Server tick - Client tick [image] The client tick() is over 3500 ahead …