daid / daid/EmptyEpsilon

[Bug] `multimonitor=1` at fullscreen using multiple resolutions results in perpetual mode switching loop

Open
#2,701 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
869
Forks
222
Avg merge
18h 33m
Merged PRs (30d)
1

Description

Steps to reproduce

  1. Connect two external displays to a Win11 system, each with a different native resolution.
  2. Build EE off master and launch with multimonitor=1 and fullscreen=1.

This also affects multimonitor=2 with two displays. A separate but likely related issue affects multimonitor=n+1 (#2702).

Expected behavior

EE launches into full screen on each display, and each display runs at its native resolution.

Observed behavior

EE launches into full screen on each display, but both displays perpetually switch fullscreen resolutions, resulting in an endless loop of mode switching (blackout, input cycle, resolution change, blackout, etc.).

Workarounds

  • Exit full screen (Alt+Enter) on the primary display after launch. Full screen remains active on the second display, and the mode switching loop stops.
  • Set fullscreen=0 and use windowed mode on both displays.
  • Ensure that both montiors use the same native display resolution. This was reproducible only with monitors of different resolutions (4k and 1080p in testing); monitors of the same resolution (1080p both in testing) work fine.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Reproduce on Win11 with multimonitor=1 and fullscreen=1 using 4K and 1080p displays, then trace the fullscreen resolution-switching behavior; done when each display stays fullscreen at its native resolution without repeated mode changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
game-dev, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.