Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0f3
Issue ID
902409
Regression
Yes
RenderToCubemap is not HDR compatible and causes camera not to be rendering in the scene anymore
Steps to reproduce:
1. Open attached project
2. Open Cubemap scene
3. Create a new cubemap
4. Select it and mark it readable
5. Select CUBEMAP -> Render into Cubemap in the top menu
6. Select your created cubemap and hit "Render!"
Expected result: Cubemap should be rendered without any errors and issues
Actual result: Cubemap is rendered without HDR, camera is not rendering the scene anymore, an error appears:
"Releasing render texture whose render buffer is set as Camera's target buffer with Camera.SetTargetBuffers!"
(Gif attached)
Reproduced in: 2017.1.0b1, 5.6.0f3, 5.6.0a1
Not reproduced in: 5.5.3f1
Regression since: 5.6.0a1
Fixed in: 2017.1.0b10
Backported to: 5.6.1p2
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
JayG81
May 09, 2017 15:15
Nevermind, it was a scripting problem. Didn't properly define something.
JayG81
May 09, 2017 12:11
My cubemaps don't seem to render in the PC build regardless of the rendering path, but they work in the editor.