Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
3.0.0b1
Issue ID
357989
Regression
No
Camera.targetTexture confuses camera callbacks
Camera.targetTexture or RenderTexture.active with Camera.RenderWithShader are making trouble.
If I set the camera's targetTexture in OnPreRender or OnPostRender in a script attached to the camera, it turns out those functions get called only once. Not once per frame, just once. The render texture gets filled properly, but the framebuffer isn't filled anymore, as I end up with some empty dark grey scene.
If I put a debug line in Update, I can see it gets called every frame.
If however I set my render texture into RenderTexture.active, then OnPreRender or OnPostRender are called every frame. However my render texture isn't filled (just black and 0 alpha) while the framebuffer is with what should be in the render texture, and my normal scene isn't drawn (or rather is drawn over).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment