can't select my main monitor

[Whostin]

in settings i can only play the game with my other monitors and not my primary one. If anyone has a fix i'd appreciate it

[Yokuho]

just press windows+shift+ left or right arrow key

[Buster]

Originally posted by Yokuho:

just press windows+shift+ left or right arrow key

For me at least, it goes back to the other monitor every time there's a loading screen. Plus if your main monitor is in a higher res, it doesn't show up as an option since the monitor isn't an option. Worked fine pre-launch patch, tested it this morning..

[Tiearian]

Here's three things that cud do the trick:
1. Press Alt+Enter, it will make the screen go windowed mode, drag it to the correct screen and press Alt+Enter again. It will go full screen on that monitor. Now close the game and start it back up so it saves the preference on close. Make sure you close the game correctly tho, don't AltF4.

2. If that doesn't work, you could also try unplugging your monitor that you want the game to recognize, while the game is open, and then plug it back in,(the DisplayPort or HDMI Cable) and see if the monitor now gets recognized by the game and the option becomes available to switch to it in the settings.

3. You could also try disabling the your secondary monitor temporarily, and starting the game so that it's forced to launch on the monitor you want it on. Go into the settings and change any option and save. Exit game, and re-enable your other monitor/s. See if the game keeps retains the monitor you want it on, now.

The issue just could be certain monitor types not being recognized by the game due to how the monitors model number is labeled within windows or something. Could just be a certain character used in the model number. If this is the case it's an oversight by the devs. cud be any number of things tho.

Obviously none of this should be required for the end-user. But hey if it works, at least your problem is resolved for the time being.

[Vashwave]

I have this exact same thing in other Unreal 5 engine games. Whenever it goes from loading screen to another it goes to my second monitor (and its extra ♥♥♥♥♥♥ if the main monitor is bigger than the 2nd one). I will say I noticed whenever this happens in settings the game doesn't recognise my main monitor anymore but it does on first boot, its undoubtedly related.

[tofu]

Same problem

[Ninjeste]

I'm going to be insane with this bug

[Vashwave]

Here is what I did as a fix that I posted in another thread about this.

This worked on my machine™ to stop the game moving screens at the cost of a 1px border;

In \AppData\Local\MultiVersus\Saved\Config\WindowsClient\GameUserSettings.ini I changed all the resolutions listed to my desired resolution but 1px smaller, and all 3 of the fullscreenmode make it "2"

Far as I understand this works because while it looks full screen it's technically in window mode now (but not "Windowed Fullscreen") and windowed doesn't care if the monitor you are trying to play it on is not detected, just window position.

[ChillTerrone]

Well, happy not to be the only one with this problem

[Whistarn]

Originally posted by Vashzaron:

In \AppData\Local\MultiVersus\Saved\Config\WindowsClient\GameUserSettings.ini I changed all the resolutions listed to my desired resolution but 1px smaller, and all 3 of the fullscreenmode make it "2"

This has worked for me, at least for now. Was having the same problem with Remnant 2 back when the DLC came out and the only similarities between the games is Unreal Engine.

I have 2 different monitors and my second only supports 1080 and I do wonder if that's the issue the engine is getting on with.

[Halo2]

Originally posted by Vashzaron:

Here is what I did as a fix that I posted in another thread about this.

This worked on my machine™ to stop the game moving screens at the cost of a 1px border;

In \AppData\Local\MultiVersus\Saved\Config\WindowsClient\GameUserSettings.ini I changed all the resolutions listed to my desired resolution but 1px smaller, and all 3 of the fullscreenmode make it "2"

Far as I understand this works because while it looks full screen it's technically in window mode now (but not "Windowed Fullscreen") and windowed doesn't care if the monitor you are trying to play it on is not detected, just window position.

this fixed it for me, thank you so much

[Vashwave]

Originally posted by Whistarn:

Originally posted by Vashzaron:

In \AppData\Local\MultiVersus\Saved\Config\WindowsClient\GameUserSettings.ini I changed all the resolutions listed to my desired resolution but 1px smaller, and all 3 of the fullscreenmode make it "2"

This has worked for me, at least for now. Was having the same problem with Remnant 2 back when the DLC came out and the only similarities between the games is Unreal Engine.

I have 2 different monitors and my second only supports 1080 and I do wonder if that's the issue the engine is getting on with.

Its a Unreal Engine 5 bug. As far as I can tell this is because it somehow for some reason stops seeing your main monitor at certain points (most noteablly loading screens) so it tries to be helpful in moving your game to what it thinks is your now only monitor.

I also have a 1080p secondary compared to 4K main but I do not think its the cause in itself, because if I unplug my secondary monitor and go in game and check the options menu to select monitor my main monitor is just listed "N/A" but at that point not like it has anywhere to move the game to so in that case if its affecting an actual real one monitor only user they won't care.

Edit: That said while I blame UE5 for it obviously this doesn't seem to be affecting everyone with 2 monitors so what the exact combination of things to trigger this is unknown.

[Halo2]

Originally posted by Vashzaron:

Originally posted by Whistarn:

This has worked for me, at least for now. Was having the same problem with Remnant 2 back when the DLC came out and the only similarities between the games is Unreal Engine.

I have 2 different monitors and my second only supports 1080 and I do wonder if that's the issue the engine is getting on with.

Its a Unreal Engine 5 bug. As far as I can tell this is because it somehow for some reason stops seeing your main monitor at certain points (most noteablly loading screens) so it tries to be helpful in moving your game to what it thinks is your now only monitor.

I also have a 1080p secondary compared to 4K main but I do not think its the cause in itself, because if I unplug my secondary monitor and go in game and check the options menu to select monitor my main monitor is just listed "N/A" but at that point not like it has anywhere to move the game to so in that case if its affecting an actual real one monitor only user they won't care.

Edit: That said while I blame UE5 for it obviously this doesn't seem to be affecting everyone with 2 monitors so what the exact combination of things to trigger this is unknown.

i didn't have this issue 2 days prior and booted my pc and changed nothing with windows or the game and it just started happening, probably just a common ue5 bug like you've explained

[Vashwave]

Originally posted by tt:

i didn't have this issue 2 days prior and booted my pc and changed nothing with windows or the game and it just started happening, probably just a common ue5 bug like you've explained

Actually I just had someone message me their GC controller emulation thing was causing it for them... quick question for you or anyone else with this issue, do any of you have "ViGEmBus" installed on your PC? (It comes with controller emulation software like DS4Windows and many others.)

[Overlordmoo]

Originally posted by Vashzaron:

Originally posted by tt:

i didn't have this issue 2 days prior and booted my pc and changed nothing with windows or the game and it just started happening, probably just a common ue5 bug like you've explained

Actually I just had someone message me their GC controller emulation thing was causing it for them... quick question for you or anyone else with this issue, do any of you have "ViGEmBus" installed on your PC? (It comes with controller emulation software like DS4Windows and many others.)

Can confirm I installed ViGEmBus earlier today in an attempt to get a GC controller working at immediately ran in to this issue. Uninstalling ViGEmBus has *not* resolved the issue. Can't currently find a fix.

[Overlordmoo]

Originally posted by Overlordmoo:

Originally posted by Vashzaron:

Actually I just had someone message me their GC controller emulation thing was causing it for them... quick question for you or anyone else with this issue, do any of you have "ViGEmBus" installed on your PC? (It comes with controller emulation software like DS4Windows and many others.)

Can confirm I installed ViGEmBus earlier today in an attempt to get a GC controller working at immediately ran in to this issue. Uninstalling ViGEmBus has *not* resolved the issue. Can't currently find a fix.

Okay, so. I think I've found the cause, just not yet the solution.

This occurs when playing with a controller, if you also have other controller emulation software installed. For context; I didn't have this problem until I tried to get a GC controller working for the game. I used a GC controller, a Mayflash adapter and this software https://github.com/Struggleton/Delfinovin I currently do not recommend installing this unless you want this issue to occur.


I have since uninstalled all of the software and run removal tools for any other files part of Delfinovin. However, the problem persists while using my PS4 controller after having uninstalled the game and removed all local files. I can't yet find a fix, but I can confirm it is related to the controller as the issue does not occur when using M+K.