Looks like I’m working for you and you found the module I’m using.
You changed the map to the workspace, meaning you declare every part or model as a static model.
To get around this:
Define the static model(s).
Render all moving objects continuously (for example if you’ve a racing game, karts).
I’m not guaranteeing that my solution is perfect. I haven’t tested it and so will test things out with the module.
This is the old version, and my new work is much better.
I recommend you switch to using this one instead. It gives you way more control over how things are rendered.
If you have questions on it, or need help with the setup, feel free to DM me!
@marketmanager1@chrisopdemobiel
Edit: Rewrote this demo file to use the new handler system!
Security Camera System.rbxl (848.3 KB) Note: This is uploaded with the module in it, and is therefore an outdated version of the module. The newer versions are backwards compatible, so just switching to the updated edition will still run in this example. If you plan on taking the module, I suggest you take the latest version of the module instead of copying the file out of this example.
This is the same map (I added balls rolling around for demo), but the code went from hundreds of lines to just 41!
Hey BoatBomber, is there a way to use more cameras and more screens? Because I tried changing it but every time I do it send all cameras screens to the same screen and glitched the view of it, could you help me making it so I can use more then 5 cameras and each a own screen?
I’m trying to use this as a mirror. So when a player looks or moves to the left, the reflection will as well instead of moving to the right. Any advice on how to do so? I can’t exactly figure it out.
Just duplicate the surface guis (make sure to adorn the main part ofc), and also duplicate the main script and edit it according to its exact parameters.
You can delete the line that teleports them to the screen, that was added to the demo so that players end up in the demo area. This has also been asked before, if you scroll up.
Blindly copy pasting demos without reading the code is a bad idea.
Slight problem, for some reason. whenever a part gets added or a character gets added, it registers, however when a part/character is removed or deleted. it stays on the camera until you refresh your character. is there any other way to make it so the part gets removed? By the way, sorry for refreshing an old post.
This would have been better if we used Region3/OverlapParams to show parts close to the camera rather than rendering the whole workspace. This is wayy more performant, but i guess this is old now.
Umm hey i found a bug where when a object is deleted it dosnt dissapear but stays there and appears to be anchored but on the client side it is gone but the camera shows different!