mojira.dev
MCL-22768

Launcher deletes custom resolutions from JSON file

Most of my installations have a non-default resolution in the launcher_profiles.json file.  With the past 2 launcher versions, launching Minecraft will remove the custom resolution from the JSON file.

Spefically, these lines:

      "resolution" : {
        "height" : 1440,
        "width" : 2560
      },
 

Linked issues

Attachments

Comments 17

Moreover, the launcher refuses to save any resolution changes at all, even when creating a "new installation" entry.

Hi there!

Could you please record a video of this issue?
Does this issue occur on standard release version as well as BETA?

Also, just a reminder, to make your bug report as effective as possible, please try and include the following steps to reproduce the problem:

Steps to Reproduce:

  • 1.

  • 2.

  • 3.

Observed Results:

(Briefly describe what happens)

Expected Results:

(Briefly describe what should happen)

This ticket will automatically reopen when you reply.

Issue also occurs for me since yesterday or so. Used launcher version: Windows 10.0 2.3.508.

Basically no matter which resolution is set in the installation's properties it will simply launch the game in default resolution.

Steps to reproduce:

  1. Go to Installations tab

  2. Open the "Edit installation" screen on an installation (e.g. Latest release)

  3. Set resolution to something from the dropdown or custom (e.g. 1600x900)

  4. Click "Play" on the installation or the main screen. The game will launch in 854x480 instead.

Hi again!

Could you please record a video of this issue?
Also please upload launcher_log file from main minecraft folder in your Application Support folder.
Also please check if this issue occurs on standard release version of the Launcher (not beta).

This ticket will automatically reopen when you reply.

This seems to be an issue specifically with the beta version of the launcher.

The standard release (at least on macOS with version 2.3.462) seems to behave correctly.

Phoenix616's repro steps will also repro the issue on the beta macOS installer.

7 more comments

Quick update: We just released a fix for this onto the Launcher's Beta channel; please take a look - this should fix your issue. And then if things look good we'll push this to release on Monday. 

Beta 2.3.520 addresses the issue for me.  Thanks

Yes, the beta fixes the issue for me as well

Launcher version: Windows 10.0.2.3.520

 

Thank you!

Thanks, b.2.3.520 fixed this for me also.

Pushed to release now. 

migrated

(Unassigned)

Confirmed

Retrieved