Question RenderTargetHandle has been removed and gives an error to replace with RTHandle, breaking change

Hi,

I recently installed 2023.1 latest version and seems all image effects on URP are 100% broken

RenderTargetHandle has been removed and gives an error to replace with RTHandle, which is far from trivial and gives like a 100+ more errors after a simple replacement

Is this something that is in Beta only, or will propagate to the final releases ?

I mean such a change will destroy every single of my projects for months or years to fix, is this something that was indented or we can expect that RenderTargetHandle will function normally as in Unity 2022 in the final release of Unity 2023 after the Beta ?

This is such a massive change that may mean weeks or months of work to recover the broken projects.

Thanks

 

RenderTargetHandle has been marked as obsolete since 2022.1, so I think they removed it this time (1 year later).

 

Sure, i dont use 2022 so would not know, as is not LTS yet, but the question still remains why remove it and break everything.

In any case, i managed to port to the new system, the only thing i miss is how to do the frame clean up function, as seems is no longer possible to do checks for renderer there, because RenderTextureHandler.CameraTarget is missing

 

Agree that removing obsolete features in second version is a good idea, so that people can have time to fix them before the LTS released.

Maybe Unity thinks people should remove these obsolete features within a year of the warning message.

 

Indeed probably they have something in mind, but with the state of Unity currently working on non LTS is very tricky, so they should consider only remove features that had warnings in a widely used LTS version imo as a general rule, so make sure people actually know about them.

I generally also work by skipping one Unity version, because goes so extremely fast. E.g. i skilled 2017, 2018 and 2020 completely, as was never needed to move there, and now is 2022 turn, so will probably never use 2022 either at all in my case.