Hey guys,
Around February 27th Roblox updated their CameraModule script which (to my knowledge) added an FFlag to their camera system (the PlayerModule script that is inserted into PlayerScripts). This update broke one of my custom CameraScripts that relied on requiring the CameraModule scripts and due to the Roblox update returned a nil value. I “fixed” the problem by forking the CameraModule script and adding the updated version in StarterPlayerScripts. I then added the PlayerModule script that housed the changes into StarterPlayerScripts in order to replace the older version that had the FFlag. The changes I made are below:
local cameraApi = {}
--[[if FFlagUserRemoveTheCameraApi then
return cameraApi
else]]--
return cameraModuleObject
--end
As you can see, I commented out the code that would return a nil value. This fixed the problem, until I realized that these changes did not apply on mobile or the Windows Store version. On mobile and on the Windows Store version of Roblox, the localscript (which is also in StarterPlayerScripts) that required the CameraModule returned a nil value, indicating that it was likely still using the updated version of Roblox’s script which did not have the changes made above. However, when I used the browser version of Roblox, the changes were applied and the localscript worked fine. To check, the same tests were made on a mobile phone and Windows laptop that belonged to a friend of mine and the same results were reported. Is there something I have to do separately to account for mobile and Windows Store users? Or is this a problem on my end?
Thanks in advance. 