Search Issue Tracker
Fixed in 5.4.3
Votes
50
Found in
5.4.0b15
Issue ID
793204
Regression
Yes
Unity throws "GfxFramebufferGLES: An active RenderTargetSetup has dangling pointers." while Unity Remote is in use
1. Open attached project
2. Open Unity Remote 4
3. Open Scene "Game"
4. Press play
5. When Unity Remote starts showing game view errors will appear in console
Regression from 5.4.0b10
No repro with 5.3.4p5
Comments (27)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Progress indicator in Meta Quest Build Profile configuration is barely visible
- Slightly transparent objects disappear completely in Web Player when using RenderGraph
- Visual Scripting Components are hidden behind a throbber when Multiplayer Play Mode is running with at least one local instance
- Video Player does not throw an error when playing a video with unsupported encoding settings
- Errors indicating that TMP Extras were not Imported logged when opening the Render Pipeline Converter Window while in Play Mode
reinfeldx
Jan 05, 2017 03:38
I just ran into this problem when I first tried to use Unity Remote 5 and Gibson79's antialiasing fix worked for me.
My setup:
Unity Remote 5 v2.0
Unity v5.4.2f1 Personal for Mac
iPhone 5 running iOS 10.2
JeffreyG_18
Dec 13, 2016 07:16
why does my game lag when this problem occurs in my game?? anyone experience the same problem?
binyuman
Nov 21, 2016 08:14
antialias works , THANK YOU
alxcancado
Nov 05, 2016 18:49
GIBSON79OCT 06, 2016 08:21
Disabling Antialias in Edit->Project Settings->Quality solved the problem, for me ;)
THANKS!
kiriyee
Oct 17, 2016 11:30
On 5.4.2f1 it still happens.
Shushustorm
Oct 16, 2016 03:59
Updated to 5.4.2f1, but this still happens.
It's very easy to reproduce.
What's going on?
aharnam
Oct 10, 2016 14:43
Still occurring
gibson79
Oct 06, 2016 08:21
Disabling Antialias in Edit->Project Settings->Quality solved the problem, for me ;)
purbanics
Oct 01, 2016 08:17
I just updated to Unity 5.4.1f1 and started getting this error.
Is there a solution or do we have to wait for Unity to fix this?
justcallmevincent
Sep 28, 2016 07:26
Issue still present on 5.4.1f1