Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.1.0b5
6000.2.0a3
7000.0.0a19
Issue ID
UUM-97228
Regression
No
WebGL Template Thumbnails in Player Settings stop displaying after Building and Running game
*Steps to reproduce:*
# Ensure that the Web module is installed on your Unity Version via Unity Hub
# Open a Unity Project
# Open Player Settings via Edit > Project Settings > Player
# Navigate to the Web settings tab
# Open the dropdown for 'Resolution and Presentation'
# Observe that under the 'WebGL Template' section, that the templates have visible thumbnails
# Open Build Profiles Window via File > Build Profiles
# If it is not already active, select the Web Platform and click 'Switch Platform'
# Click 'Build And Run'
# Wait for your project to build and run
# Reobserve the WebGL Template section in Player Settings
*Actual results:* The thumbnails on the templates have stopped displaying. You have to restart the Editor for them to display again
!image-2025-02-06-17-21-48-364.png|width=340,height=176!
*Expected results:* The thumbnails on the templates still display
!image-2025-02-06-17-03-17-345.png|width=380,height=173!
*Reproducible with versions:* 7000.0.0a19, 6000.2.0a3, 6000.1.0b5, 6000.1.0a1
*Not reproducible with versions:* 6000.0.37f1, 2022.3.58f1, 2021.3.45f1
*Can't test with versions:* -
*Tested on (OS):* Windows 11
*Notes:*
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
- The tag adder functionality does not work if a space is entered instead of a name
- Errors thrown in the Console when configuring In-App Purchases package
- Longer Scaler Profile names go out of the"Scaler Profilers" section
- AI Navigation window UI elements overlap when the AI Navigation window is docked and resized
- Editor freezes after some time when using NavMeshQuery::Raycast
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.