Weird Camera.CFrame behaviour

[Mah_Bucket]

When will this be fixed? I rely heavily on camera interpolation for my game and the temporary fix that was posted did not fix the problem. If I have to delay the Halloween event I have planned because of this bug I’ll be very disappointed and upset.

[Alvin_Blox]

Yes, me as well. My YouTube viewers are very confused and as I can’t update the videos now that they’re up, many are complaining of the Poppercam issues. I don’t want it to cause them becoming angry, disliking the video and saying it doesn’t work.

[Revlayz]

How long is it going to take?

My game is having a hard time as my guns are broken.

[daireb]

I’m surprised this has been around for so long. My game isn’t the worst effected, but I still had to put in some hacky workarounds, but it is farcical that such a major bug has been active for so long. It is also effecting other games that I’m working on as well.
A lot of games are practically unplayable, and this is a huge problem. The bug has been around for 4 days now, and I understand that it’s been the weekend but there should at least have been a rollback.

[starchip12]

Any updates on this issue? It is happening for me too and I don’t really know any temporary fixes.

[AllYourBlox]

I think part of the problem is that we now have too many threads independently discussing this same issue (at least 5 that I can see). Discussion of the fix is in the main thread for the PlayerScripts release here:

New Player Scripts are coming (10.11.18), and how you can prepare

Next Thursday (10.11.2018), provided no blocking issues are uncovered during QA, we will be shipping the new structure of Roblox PlayerScripts. In response to some loss of functionality the first time we deployed the new scripts, the structure has changed in such a way that developers will still have access to things they were directly requiring some of our modules for, such as GetMoveVector() and Enable()/Disable() for controls. The new structure looks like this: [NewPlayerScriptsStructure] A…

In a nutshell, fixing this is not as simple as just a rollback. Now that there are games relying on the existence of these scripts, we can’t simply turn off the feature without complete breaking all of these games, in more than just a camera glitch way (any game waiting for the new module would never load). The immediate solutions available to the developer are in the very first post of the thread linked above. You can:

1. Install the old CameraScript (and all of its children) to StarterPlayerScripts and republish your game (the quickest fix).
2. Download the Pre-release 3 set of new playerscripts, which has this Poppercam issue fixed, and use those until the fix is live (at which point you’ll want to remove the forked scripts in order to get any other bug fixes that are in the final release). The fix itself is not in PopperCam or PopperCam_Classic, but in CameraModule:Update() where PopperCam’s Update function is called from.

I’m going to keep the Prelease PlayerScripts links in that thread up to date as any other issues are found, so that developers have this option of getting the fixes early when their games are impacted.

[CJ_Oyer]

This may be a dumb question but do you know where I can find a copy of the old CameraScript? Thanks!

[AllYourBlox]

Just click that link in my post you replied to, they are attached at the end of the first post in the “New PlayerScripts are coming” thread .

[Chrythm]

When this started happening, I started to get reports about falling through the floor and walking through walls as well as the cam problem. Could this have something to do with rthro or inner box collision?

[AllYourBlox]

The fix for this issue, Poppercam_Classic popping and disrupting custom cameras when cameraType is Scriptable, is now live. If you installed the old CameraScript in your game just to address this issue, you should be able to remove it now.