Search Issue Tracker
Fixed
Fixed in 6000.0.45f1, 6000.1.0b13
Votes
0
Found in
6000.1.0b12
Issue ID
UUM-100910
Regression
Yes
The Windows-built project fails to load or run when using the "Fullscreen Window" or "Windowed" build resolution options
Steps to reproduce:
1. Create a new project (Tested with Uni 3D, Uni 2D)
2. Go to "File -> Build Settings..." (or "File -> Build Profiles" on Unity 6)
3. Add "Scenes/SampleScene" to build index
4. Press "Build" and wait for the build to finish
5. Double-click the built .exe
6. The cursor of mouse changes to a blue ring, indicating that it is waiting
7. Observe the app launch process and icon appears on the taskbar
\\
Actual results: The ring loader does not return to the cursor, and the application window is not running
Expected results: The application window runs and focuses correctly
\\
Reproducible with versions: 6000.1.0b12
Not reproducible with versions: 2022.3.60f1, 6000.0.43f1, 6000.1.0b11, 6000.2.0a7
\\
Tested on (OS): Windows 11
\\
Notes:
- When the Windows button is pressed, the window appears, and it works after that
- Also, after step 6, if you push the "Windows" key or the "Alt + Tab" keys to change the focus of OS, the application will appear.
- Not Reproducible with the resolution "Maximized Window or Exclusive Window."
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment