«ActivateCameraController did not select a module» warn message

[16Thunderstorm]

Hello!

I have been having this problem recently:

First off I wanna say that:
Yes my CameraType is Scriptable
CameraSubject changes

When I encountered this issue I was confused since I didn’t modify any scripts relating to cameras.
This issue came out of nowhere.

Does anyone know what to do to fix it? Should we

:Destroy() The module script or
Is there anything else to do to fix this issue.

[16Thunderstorm]

I’m pretty sure I’m not the only one having this problem since this came out of nowhere.

[JackscarIitt (Jackscarlett)]

I mean this is pretty much a common bug

"ActivateCameraController did not select a module" warning in "CameraModule.lua"

This warning seems to have started to appear recently. In my case, it always appears when I activate a free camera in my game. Studio does not indicate a traceback. Clicking on the warning, it shows this line inside the module “CameraModule.lua”: C:\Program Files (x86)\Roblox\Versions\version-096c60fcfa5e4ca2\ExtraContent\scripts\PlayerScripts\StarterPlayerScripts_NewStructure\PlayerModule.module\CameraModule.lua [image]

[WARN] "ActivateCameraController did not select a module."

I have the same issue, this is how i patch the problem Try that workspace.CurrentCamera.CameraType = Enum.CameraType.Scriptable workspace.Camera.CameraType = Enum.CameraType.Custom wait() workspace.Camera.CameraType = Enum.CameraType.Scriptable workspace.Camera.CFrame = CFrame.new(-59.414, 20.361, -37.535) Also don’t use “Scriptable” use Enum.CameraType.Scriptable

Camera script bug

Recently, I have been encountering an error that goes along the lines of: 18:33:02.360 - ActivateCameraController did not select a module. I have no idea what to do about this. I have verified that this is not one of my scripts (it is a core script), and this happens on both the Roblox client and in Studio. The error is triggered when I try to change the camera’s CFrame, like so: local camera = workspace.CurrentCamera camera.CFrame = newCFrame I have printed the camera’s type before the li…

A simple work-around would be is just to add a simple wait() before you change your camera properties, my guess is cause the camera is still loading which is why it’s resulting in that error

[16Thunderstorm]

I’ll try that and come back with an answer.

[Nogalo]

did you manage to fix this issue with the wait?

[16Thunderstorm]

Not really, that’s weird I maybe did something wrong. Maybe bc there’s scripts that change the CameraType to Attach.

[16Thunderstorm]

An update. I still have that issue, which is dropping frames for my game sometimes. I’ll share the code soon. @Nogalo @JackscarIitt. Should I just add wait() itself without adding anything else or make it wait for something. I’ll share the « start up » code (just setting the CameraSubject to the first part for the beggining).

[16Thunderstorm]

I’ll try also to add wait for when we change CameraSubjects.

[Nogalo]

I resolved my issue by not making the camera scriptable. Just left it at custom and it works fine because the character is not spawned yet. I have a loading screen when you enter which spins the camera around 1 point in the middle and i thought i needed to make it scriptable to make spin but nope works fine without it.

[16Thunderstorm]

That won’t fit much in my game (A FNAF fan game)

[16Thunderstorm]

Overall this bug is very annoying.

[LeandroCZBr (pog)]

Make this:

repeat 
  wait()
  Camera.CameraType = Enum.CameraType.Scriptable
until Camera.CameraType == Enum.CameraType.Scriptable

Hope it helped