Search Issue Tracker
Not Reproducible
Not Reproducible in 6000.5.X
Votes
0
Found in
6000.4.0b8
6000.5.0a6
Issue ID
UUM-133875
Regression
Yes
“Canceling DisplayDialog: Changing Virtual Texturing support Enabling or disabling Virtual Texturing requires a restart of the Editor” error is thrown when adding WebGL Build Profile
Reproduction steps:
1. Create a new project
2. File > Build Profiles
3. Press “Add Build Profile” button
4. Select Web platform in the Platform Browser window and press “Add Build Profile” button
5. Observe the Console
Actual result: “[Worker0] Canceling DisplayDialog: Changing Virtual Texturing support Enabling or disabling Virtual Texturing requires a restart of the Editor. This should not be called when not controlled by a human.” error is thrown
Expected result: No warnings or errors are thrown
Reproducible with: 6000.4.0a3, 6000.4.0b8, 6000.5.0a6
Not reproducible with: 6000.0.67f1, 6000.3.8f1, 6000.4.0a2 (79bd4f638ac0)
Reproduced on: macOS Sequoia 15.7 (Intel), macOS Sequoia 15.3 (Intel), macOS Tahoe 26.2 (M4), Windows 11
Note: Issue is not reproducible with other Build Profiles
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
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
Resolution Note:
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.