Game open on the wrong display. Any fix?

[proslayer]

Sometimes the game decides to open on the wrong monitor (i have two). How to prevent this from happening? Is there any launch options i can add in steam?

[CarlZalph]

1 hour ago, proslayer said:

Sometimes the game decides to open on the wrong monitor (i have two). How to prevent this from happening? Is there any launch options i can add in steam?

Assuming you're running the game in full screen mode:

Spoiler

Quote

-force_edid_shorthand 0

Add that in the launch option then check the client_log.txt file for the edid shorthand outputs.

[00:00:00]: THREAD - started 'SimUpdateThread' (19516)
[00:00:00]: THREAD - started 'RenderThread' (23028)
[00:00:00]: Scanning display device ID:[4] for all known registry keys for stored EDIDs on attached monitors...
[00:00:00]:   EDID (shorthand): {3669B03C010000000820}
[00:00:00]: Scanning display device ID:[5] for all known registry keys for stored EDIDs on attached monitors...
[00:00:00]:   EDID (shorthand): {3669B03C790000000820}
[00:00:00]: [Connect] PendingConnection::Reset(true)
[00:00:00]: Platform: 1
[00:00:00]: Network tick rate: U=15(2), D=0

This is mine, for example.  The hex string in between the brackets is the bit to use.  If you pick the wrong one, then use the other hex string.

Quote

-force_edid_shorthand 3669B03C010000000820

[Valase]

You need to open the game, go into Options:

then into graphics and there you click on display:

after that apply and it will be saved as such.

[proslayer]

It will not be since the game now think monitor 1 is monitor 2. The next time i start the computer the game now remember what the right monitor is and switches back to it. Very annoying. Also the refresh rate get stuck at 75hz instead of 150hz.

On 1/5/2026 at 1:49 AM, CarlZalph said:

Assuming you're running the game in full screen mode:

  Hide contents

 

 

Add that in the launch option then check the client_log.txt file for the edid shorthand outputs.

 

[00:00:00]: THREAD - started 'SimUpdateThread' (19516)
[00:00:00]: THREAD - started 'RenderThread' (23028)
[00:00:00]: Scanning display device ID:[4] for all known registry keys for stored EDIDs on attached monitors...
[00:00:00]:   EDID (shorthand): {3669B03C010000000820}
[00:00:00]: Scanning display device ID:[5] for all known registry keys for stored EDIDs on attached monitors...
[00:00:00]:   EDID (shorthand): {3669B03C790000000820}
[00:00:00]: [Connect] PendingConnection::Reset(true)
[00:00:00]: Platform: 1
[00:00:00]: Network tick rate: U=15(2), D=0

This is mine, for example.  The hex string in between the brackets is the bit to use.  If you pick the wrong one, then use the other hex string.

 

Thanks dude. I will try this.

[Baark0]

glad im not alone in this issue. its a minor thing but its really annoying whenever it does happen, even if its easy enough to fix

[proslayer]

Yeah it's so annoying. I've been using this fix now for a week now and never had any issues so it seems to be working perfectly. Thank you so much for this @CarlZalph. I couldn't find this being mentioned anywhere other then a developer responded to a bug report a few years ago.