- Home /
'UniversalAdditionalCameraData' has been destroyed but you are still trying to access it.
using Unity 2022.1.1f1
using Universal Render Pipeline 13.1.8
I keep getting 999+ errors of this every time I exit play mode.
It only shows up while I'm not in play mode.
As soon as I go back into play mode it goes away and stops until I exit play mode again.
I can restart Unity and it'll go away until the next time I exit out of play mode.
If I delete my camera manually in the Editor before exiting play mode it doesn't show up that time.
I've tried deleting the camera and making a new one it still happens
My camera is spawned into the scene with the player at runtime
I cannot figure out what could be accessing my camera nonstop when it's not even play mode.
Does anybody know how to fix this? Thanks
I get the same in 2022.1. Completely unexplanable, started some say and I haven't changed anything about cameras. Must be a general bug, since I do not touch UniversalAdditionalCameraData at all.
It's also in the issue tracker already.
Answer by AaronBacon · Jun 03 at 12:47 AM
UniversalAdditionalCameraData is to do with the Universal Render Pipeline package, only things I can suggest is make sure all the cameras in the scene have the "UniversalAdditionalCameraData" Component on them, and if they do, perhaps check your URP package is up to date in the package manager.
Yup I made sure of all that. Something is still trying to access it even when it’s not in play mode. Not sure how to fix it though
I am seeing the same error using Cinemachine + 2d camera. My scripts are harmless and nothing is manipulating the camera. I think it's a a bug in 2022.1 but not sure yet what is causing it
Ok it seems to be related to hitting play while having a prefab opened in context. Breaks the editor about half the time. A workaround is to simply not play when you have an context-opened prefab
It was happening to me even when I wasn’t in prefab mode. It has to be a bug with 2022.. it somehow magically fixed itself on mine too, it’s not showing up anymore. Couldn’t really even figure out what was causing it