Why are there these line shaped holes in my raycasting model pixelator?

[dthecoolest]

@Ethanthegrand14

The problem that is causing this is rotating the model to scan another side

Ah good catch, maybe its more than just a rounding issue as well since I see this in your code

@Ethanthegrand14

	ModelToPixelate:SetPrimaryPartCFrame(CFrame.Angles(0, 0, math.rad(270)))

Since you are using SetPrimaryPartCFrame, I recognize that this method of rotating the model is real buggy, due to floating point issues as you have discovered.

@Ethanthegrand14

but round(0.050000005960464) will return 0

:SetPrimaryPartCFrame() gradually offsets component parts

I made an animated barrier thing that uses :SetPrimaryPartCFrame() to move portions of the barrier. Here is its progress over time: When I first open it up in run mode: [image] I minimized studio and left it alone for a while. A little short of an hour later and it’s turned into this: [image] Notice how some of the pieces are no longer connected. Leaving it for a day resulted in this: [image] Here is a picture that shows the individual models: [image] local interpolation = require(scri…

I remember there was a community resource which solves this problem but I can’t seem to find it now maybe later if so I’ll edit it.

Edit: Found it

[Obsolete] ModelMover - A simple solution to CFrame inaccuracies from repeated calls to SetPrimaryPartCFrame

ModelMover is obsolete. Do not use it for new work. It has been replaced by the native method PVInstance:PivotTo, which functions for both models and parts alike. For obvious reasons, this module is no longer supported. Introduction to ModelMover If you’ve made extensive use of Model:SetPrimaryPartCFrame you are no stranger to the inherent inaccuracies it can acquire over time. For instance, if I rotate a model by getting it’s PrimaryPart’s CFrame, modifying that, and then setting it to the n…

maybe this will help