Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.3.1p3
Issue ID
763846
Regression
No
[iOS] Performance 'tweaks' for low-end devices are not being applied in custom shader that is inheriting from standard
Steps to reproduce:
1. Open attached project (ShaderPerformance.zip)
2. Build 'TriangulationBug' scene for iOS
3. Deploy the generated Xcode project to a low-end device
4. Notice that the custom shader doesn't have the standard shader 'tweaks' applied, thus decreasing FPS (you can tap with two fingers to switch between custom and standard shaders and see the FPS difference)
iPad Mini 1 (iOS 6.1) and iPad 2 (iOS 8.1):
Standard shader: 30 FPS
Custom shader: 23-24 FPS
iPhone 4 (iOS 7.0):
Standar shader: ~10 FPS
Custom shader: 6-7 FPS
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment