Search Issue Tracker
Won't Fix
Votes
1
Found in
5.1.1f1
Issue ID
714586
Regression
No
[D3D9] Update is stopped executing with Run In Background enabled under D3D9 with Fullscreen Mode set to Exclusive
Steps to reproduce:
1. Open the attached project
2. Build and run the scene with these settings (should be set by default):
D3D9 Fullscreen Mode: Exclusive Mode
Graphics API: Direct3D9
Run In Background: Enabled
3. Switch to desktop (Alt+Tab)
4. Open the 'output_log.txt' for the player ([BuildFolderName]/[BuildName]_Data/output_log.txt)
5. Notice once the player was left in background it stopped executing Update() functions and "HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost)" was spammed every frame instead
6. If you switch back to the game window and switch to the editor again (leaving game window in the background), you'll notice that it continued executing Update() once it was the active program again, and stopped as you left it in background
Notes: Does not happen if Fullscreen Mode is set to Fullscreen Window. Also does not seem to happen under D3D11 graphics API.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Deployment fails with unexpected status code 0 0 when deploying a Cloud Code module
- Sprite Atlas Samples throw multiple warnings when changing the original Editor verion
- Deleting 2D Lights while Lighting Explorer is open throws “GUI Error” and “NullReferenceException” errors in the Console window
- "Couldn't open file for reading" error occurs when running binary2text on a file larger than 2 GiB
- AssetReference Variable Asset Reference Type is tied to list position and will produce unexpected results when creating or duplicating AssetReference Variables
Add comment