Search Issue Tracker
Fixed
Votes
0
Found in
4.3.3b1
Issue ID
583781
Regression
No
[Emulation] UnityEditor should use the rendering settings of the platform it is used in.
UnityEditor should use the rendering settings of the platform it is used in.
The rendering path currently used by the editor should reflect the target platform. With the current setup, what you see in the game view does not reflect what you will actually see in the built version of the game, which contradicts many other aspects of the Editor’s target platform. Currently, the only ways to view the game with the mobile rendering path in the editor are to either change the standalone rendering path, or to change the actual camera’s rendering path.
This leads to confusion when using the camera’s depth texture in shaders. If the mobile path is set to forward while standalone is set to deferred, the depth textures will still function properly in the editor when targeting mobile platforms. Once you build the game for mobile however, the depth textures will stop working because you need to tell the camera to render the depth via script.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment