Enabling/Disabling PlayerController vs the whole Player Object

Hi, I am just curious…
Is there a difference between disabling/enabling a object component to disabling/enabling the whole object? Because my solution to the challenge was to disable the player object with player.SetActive(false); (and then later enabled it with true). With this the CinematicControlRemover is not dependant on the RPG.Control namespace.

Disabling the player object will turn off the renderers (well, really all the scripts) on the player, so the player won’t be visible in the cinematic. That’s not necessarily wrong, it can be a good design choice. Disabling the PlayerController only makes it so that clicking won’t work for the player till it’s restored.

Ah… did not notice the player wont be visible because he was not visible in the cutscene even before disabling him.

Thanx for the answer

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.

Privacy & Terms