Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 2017.1.X, 2017.2.X
Votes
1
Found in
2017.1.0f3
Issue ID
933341
Regression
No
[WSA] Input gets queued during splash screen, played out over N frames after splash is complete
Steps to reproduce:
1. Open the attached project(SplashScreen.zip)
2. Open the test scene
3. Switch platform to Windows Store
4. Build for WSA Universal
5. Open VS solution
6. Deploy on local machine
7. Press escape during the splash
8. Input is ignored until splash screen is over after Editor closes
Note:
Not reproducible on the standalone build
Actual results: Input is ignored until splash screen is over after Editor closes
Expected results: Input should be ignored
Reproduced with: 5.5.4p2, 5.6.2p4, 2017.1.0p1, 2017.2.0b4, 2017.3.0a1
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
- [macOS] Unable to install VisionOS Module using HUB 3.8.0-beta.2
- NullReferenceException is thrown when pressing the "Enter" key to select an item in a ListView
- Burst internal compiler errors are thrown when creating a new 2D project
- Tile Paint action disappears from Undo History when Tile Selection tool has been used beforehand
- The pregenerated LightDefinition.cs.hlsl does not match the source LightDefinition.cs when regenerating shader includes
unity_oOWkIslGJHEkrQ
Oct 23, 2020 01:33
I know this is an old discussion, but I came across this problem while making a game and ended here.
What I did was a quick fix but only works if you only want to ignore touch or click inputs during the splash screen. (Doesn't work for ignoring KeyCode inputs)
Basically, what I did was I added a panel on my canvas which is supposed to "block" touch / click inputs and just SetActive it to true in the Start function and added a condition that checks if the splash screen is done. If yes SetActive it to false. It worked for me, hope it works for those who are dealing with the same problem.
Pascal-Lohscheidt
Jun 05, 2019 21:45
Hey, I still have that issue with touch input. It basically queues the touches until the scene is loaded. So Rendering.SplashScreen.isFinished doesn´t help.
Should I report that as a new issue?