Skip to content

[Windows] Multiple surfaces create / destroy during startup #63299

@clarkezone

Description

@clarkezone

As part of investigating #40068 it has become apparent that surface creation in the startup path on Windows is non-optimal with an initial surface created at (100,100), destroyed and a new one created at the correct dimensions. I have a fix for this that is dependent on the fix for 40068 landing in Engine first.

Metadata

Metadata

Assignees

Labels

platform-windowsBuilding on or for Windows specifically

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions