Screen resolution bug stuck at 1600x1200

[Smart0ne]

Every time i start game i got 1600x1200 resolution, i can change it in settings, but it never saves. and i got 1600x1200 after restart again :(

[Thomastronaut]

引用自 OnionKnight：

We are not actively working on this issue because we cannot reproduce it, we would need help from anyone experiencing this issue to provide at least the lines regarding windowing and resolutions from the log file.

Also as mentioned earlier try changing to borderless fullscreen.

Changing to borderless fullscreen definitely seems to solve the issue, but unfortunately it also lowers the framerate drastically. Would you like me to send you my user_settings.config or something? And where can I do so?

[OnionKnight]

I don't think user_settings.config will help, I've already had a look at a few and they seem to check out. My next step was to add a bunch of logging in the engine that says what resolutions it is trying to set. These are found in %APPDATA%\ParadoxInteractive\Magicka2\logs on Windows.
If you can find the most recent log where the issue happens it would help if you could paste the relevant lines from the log as a reply to this thread.

[Thomastronaut]

引用自 OnionKnight：

I don't think user_settings.config will help, I've already had a look at a few and they seem to check out. My next step was to add a bunch of logging in the engine that says what resolutions it is trying to set. These are found in %APPDATA%\ParadoxInteractive\Magicka2\logs on Windows.
If you can find the most recent log where the issue happens it would help if you could paste the relevant lines from the log as a reply to this thread.

Is this what you're looking for?

[Resolution] SKIPPED 640/400 adapter 0, output 0. Reason: TOO SMALL
12:34:16.171 [Resolution] SKIPPED 640/480 adapter 0, output 0. Reason: TOO SMALL
12:34:16.171 [Resolution] 16/10 resolution 800 / 600 adapter 0, output 0
12:34:16.171 [Resolution] 16/10 resolution 1024 / 768 adapter 0, output 0
12:34:16.171 [Resolution] 16/10 resolution 1152 / 864 adapter 0, output 0
12:34:16.171 [Resolution] 16/9 resolution 1280 / 600 adapter 0, output 0
12:34:16.171 [Resolution] 16/9 resolution 1280 / 720 adapter 0, output 0
12:34:16.171 [Resolution] 16/10 resolution 1280 / 768 adapter 0, output 0
12:34:16.171 [Resolution] 16/10 resolution 1280 / 800 adapter 0, output 0
12:34:16.171 [Resolution] 16/9 resolution 1360 / 768 adapter 0, output 0
12:34:16.171 [Resolution] 16/9 resolution 1366 / 768 adapter 0, output 0
12:34:16.171 [Resolution] 16/10 resolution 1440 / 900 adapter 0, output 0
12:34:16.171 [Resolution] 16/9 resolution 1600 / 900 adapter 0, output 0
12:34:16.171 [Resolution] update values
12:34:16.171 [Resolution] Native aspect ratio sixteen_nine
12:34:16.171 [Resolution] Native resolution 1600 x 900
12:34:16.171 [Resolution] Native resolution 1600 x 900
12:34:16.171 [Resolution] Native aspect ratio sixteen_nine
12:34:16.195

[OnionKnight]

引用自 Thomastronaut：

Is this what you're looking for?

Mainly I want the lines that begin with "[Window]" after the timestamp, but it would be relevant if your problem is that the resolution is set to 1600x900 but your desktop resolution is something else.

[Thomastronaut]

引用自 OnionKnight：

引用自 Thomastronaut：

Is this what you're looking for?

Mainly I want the lines that begin with "[Window]" after the timestamp, but it would be relevant if your problem is that the resolution is set to 1600x900 but your desktop resolution is something else.

12:34:12.551 [Window] Desktop resolution determined to be 1600x900.
12:34:12.552 [Window] Opening window with size 1280x720 and fullscreen

[OnionKnight]

引用自 Thomastronaut：

12:34:12.551 [Window] Desktop resolution determined to be 1600x900.
12:34:12.552 [Window] Opening window with size 1280x720 and fullscreen

Thank you. What is your desktop resolution? Is it 1280x720? Have you changed any DPI settings for fonts?

[Thomastronaut]

引用自 OnionKnight：

引用自 Thomastronaut：

12:34:12.551 [Window] Desktop resolution determined to be 1600x900.
12:34:12.552 [Window] Opening window with size 1280x720 and fullscreen

Thank you. What is your desktop resolution? Is it 1280x720? Have you changed any DPI settings for fonts?

My desktop resolution is 1600x900, but I usually play games in a lower resolution to get more FPS. As far as I know, no settings have been changed.

[OnionKnight]

引用自 Thomastronaut：

My desktop resolution is 1600x900, but I usually play games in a lower resolution to get more FPS. As far as I know, no settings have been changed.

Okay, so you are trying to run at 1280x720, your desktop resolution is at 1600x900 but you get the game in 1600x1200? Or is it 1600x900?

There is something I could try changing but it's a long shot.

[Thomastronaut]

引用自 OnionKnight：

引用自 Thomastronaut：

My desktop resolution is 1600x900, but I usually play games in a lower resolution to get more FPS. As far as I know, no settings have been changed.

Okay, so you are trying to run at 1280x720, your desktop resolution is at 1600x900 but you get the game in 1600x1200? Or is it 1600x900?

There is something I could try changing but it's a long shot.

My desktop resolution is 1600x900. Every time I start up the game, the resolution has been reset to 1600x900, even though I've previously changed it to 1280x720.

[Scorpion]

I just installed and played Magicka 2 for the first time have the same problem.

1920x1080 - Native resolution of monitor
1920x1080 - Desktop resolution
1920x1080 - Screen resolution in Magicka 2's user_settings.config
1600x1200 - Magicka 2 resolution at launch (every launch)
1920x1080 - Magicka 2 resolution after Alt+Tab out, Alt+Tab in

In all my logs, the [Window] data looks like this:
01:26:58.239 [Window] Desktop resolution determined to be 1920x1080.
01:26:58.239 [Window] Opening window with size 1920x1080 and fullscreen = 1.

In some of the logs, there is an additional line later that looks like this:
01:28:18.140 [Window] Setting size to 1920x1080.

I do notice some other lines about e.g. a 2715x1527 native resolution and "WRONG SCREEN OUTPUT". I would be happy to provide these logs or perform additional tests if someone would like further detail.

[Пустельга]

引用自 OnionKnight：

Check inside the folder %APPDATA%\ParadoxInteractive\Magicka2, do you have a user_settings.config? If you do, make sure it's not set to read-only. When you apply settings the game will write the new resolution to this file so you have to ensure it's able to do that. You could even open it yourself and edit the values inside it to set the resolution you want.

Thanks for help, I completely broke my game. I checked the read-only option and now every time I try to access options in game it just crashes with no error message. There is [1920 1080] in config file set to default (I didn't change anything), but it's still running 1600x900.

Edit: deleting the .config didn't change anything, I just had to set up my options again, restart and see that 1600x900 over and over again. Guess I have to set it up manually every time I get into the game, like I did before.

Edit 2: and here's the logs from the latest log file with [window]

18:08:11.485 [Window] Desktop resolution determined to be 1920x1080.
18:08:11.485 [Window] Opening window with size 1920x1080 and fullscreen = 1.
18:08:48.895 [Window] Setting size to 1920x1080.
18:08:49.412 [D3DRenderDevice::set_resolution] width: 1920 height: 1080 success: 1

Despite what it says, it's still launching the game in 1600x900
(but at least it's doing it in fullscreen)

Maybe it has something to do with my native screen resolution?
Because most of my games can run at whopping 2715x1527 DSR
Thanks to Nvidia GeForce Experience settings, this line proves it:

[Resolution] Native resolution 2715 x 1527

[Hitori]

引用自 OnionKnight：

We are not actively working on this issue because we cannot reproduce it, we would need help from anyone experiencing this issue to provide at least the lines regarding windowing and resolutions from the log file.

Also as mentioned earlier try changing to borderless fullscreen.

Since this issue is still happening and i reacently got the game i did some checking.
The following between the "" is a copypaste of the config files content.
"
}
screen_resolution = [
1920
1080
]
sound"

This bug only happens when using fullscreen setting.

Using borderless sets default to the screens resolution so even if the bug affects this setting as well it is impossible to tell as it by default (and only possible setting) becomes 1920x1080.

The copypasted line i provided is being overwritten when the game starts as i tested using the following alternative line.
"
}
screen_resolution = [1920x1080
]
sound"

When using windowed setting the game behaves like normally expected (according to the resolution used/set).

And when altering the resolution in fullscreen the new resolution is being written into the config file.
Tested example:
"}
screen_resolution = [
1680
1050
]
sound"

This bug is fairly annoying, so i suggest you get back on trying to fix this issue.


And apparently copypasting the config files content has messed upp the steam forum as all the text is all bunched upp with no enter key inputs beeing recogniced.

[Tomkatt]

I'm having this issue as well on a 4k display. Interestingly, if I set the game resolution to 1080p, it resets to 1600x1200 at next launch. If I set the resolution to 2560x1440, at next launch the resolution is 1440x900. Very odd. It's completely repeatable though.

[PaleBlueDot]

I have exactly 2 Stingray engine games, this and Vermintide, both have this bug. It is a Stringray bug and the developers should report it to Autodesk

[CamoFlash7]

While experiencing this issue right now, and opening Google Chrome to search for answers, I found this thread.

After finding no answers, I swapped back to my Magicka 2 game tab, I noticed it swapped, from 1600 x 1200 to 1920 x 1080, all by itself, in Fullscreen mode as well. It seems like I accidentally found a work around for the problem.

If you Alt + Tab to another window, such as Google Chrome in my case, and Alt + Tab back into Magicka 2, it fixes the Resolution, temporarily of course, to your Desktop resolution.

It doesn't fix the problem but it seems like a decent workaround.