Search Issue Tracker
Won't Fix
Votes
1
Found in
4.3.0f4
Issue ID
579772
Regression
No
FPS drop when using Assistive Touch
To reproduce:
1. Open the attached project
2. Build and run for iOS 7 (iPad mini retina)
3. See that FPS is 60
4. Go to General Settings -> Accessibility -> Assistive Touch
5. Go back to the app
6. Notice that FPS has dropped to 40
RESOLUTION:
Additional investigation concluded that this needs to be fixed on iOS side. There's not much we can do.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
- “GUIStyle” and “NullReferenceException” errors thrown in the Console when opening Object Field during script compilation
Add comment