Alright, it is that time again. I have rewritten parts of CloneTrooper1019’s Module3D about 4 times, each being either better and more efficient than the last. Unfortunately, as I didn’t plan to do this before uploading the last update to Module3D V4 (fix for odd aspect ratios like 10:1), this one is only more efficient. I am going to thank @Oseday for the idea on the implementation with this:
Well, turns out this is very true. But first, here is a comparison (red is V4 and blue is V5):
They look the same, and that is because I couldn’t figure out any improvements to rotations. So, performance is the concern with this. With no camera movement and the frames and offset aren’t being updated, no new calculations are done. For when the camera is moving, script utilization goes down by about 60% (0.5% to 1% in script performance vs 2.5% to 3.5%).
As the main math hasn’t changed, being as optimized as I could get it, it is a drop in replacement V4.
Module: Module3D V5 - Roblox