Search Issue Tracker

In Progress

Under Consideration for 2022.3.X, 6000.0.X, 6000.1.X, 6000.3.X

In Progress in 6000.2.X

Votes

1

Found in

2022.3.62f1

6000.0.48f1

6000.1.3f1

6000.2.0a10

6000.3.0a1

Issue ID

UUM-104762

Regression

No

The Player becomes unresponsive after resolution switch in Exclusive Fullscreen mode when using DX12 Graphics API

-

Reproduction steps:
1. Open the attached “IN-100647.zip” project
2. Build and Run the project (File > Build and Run)
3. In the Player, click on the “1920x1080” button
4. Observe the resolution change
5. Click on the “1600x1024” button
6 Repeat 3rd step and observe the Player

Expected result: The resolution changes, and the Player is interactable/responding properly
Actual result: The buttons do not work anymore, and the Player is in “Not Responding” state

Reproducible with: 2022.1.0a5, 2022.3.62f1, 6000.0.48f1, 6000.1.3f1, 6000.2.0a10

Reproducible on: Windows 10 (User reported), Windows 11
Not reproducible on: no other environment tested

Notes:
- Sometimes the issue reproduces after fewer or more resolution changes (button presses)
- Does not reproduce with DX11 (Could not test Vulkan since it does not support Exclusive Fullscreen mode)
- After the Player becomes unresponsive, Alt + F4 does not work to exit it, and the process must be ended through the Task Manager
- The issue is a bit inconsistent to test, but usually restarting the project, rebuilding it and pressing the buttons more times makes the issue always reproducible

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.