Skip to content

GUI Scale 1x/2x and 3x/4x Behave Identically at 1080p Fullscreen #3891

Open

Description

@BCYASBU

Bug Description

When running Minecraft at 1920×1080 in fullscreen mode with Sodium installed, the GUI Scale setting does not behave correctly.

The available GUI Scale options are 1x, 2x, 3x, and 4x. However, 1x and 2x result in the same effective GUI size, while 3x and 4x also result in the same effective GUI size.

Reproduction Steps

Launch Minecraft with Sodium installed.
Set the resolution to 1920×1080.
Enable fullscreen mode.
Open the Video Settings and find the GUI Scale setting.
Set GUI Scale to 1x and observe the GUI size.
Change GUI Scale to 2x and compare the GUI size.
Repeat the test with 3x and 4x.
Expected Behavior
Each GUI Scale option should apply a different GUI scaling level when supported by the current resolution.

Actual Behavior
At 1920×1080 fullscreen:

1x and 2x have the same effective GUI scale.
3x and 4x have the same effective GUI scale.
This means that the four GUI Scale options effectively provide only two different GUI sizes.
Environment
Minecraft: 26.2
Sodium: 0.91
Java: 26.2
Resolution: 1920×1080
Display Mode: Fullscreen
GPU: Intel integrated graphics (Core i5-12500H)
Additional Information
The issue occurs when using 1080p fullscreen and appears to affect the GUI Scale setting specifically.

Log File

The latest.log does not contain any relevant errors or messages related to the GUI Scale issue.

Crash Report

N/A

Additional Testing

I also tested the issue with the Precise GUI Scalar mod.

With Precise GUI Scalar, I am able to adjust the GUI scale more precisely and get different GUI sizes. However, the GUI becomes blurry / has visible aliasing around text and UI elements when using the non-standard scaling values.

This suggests that the display resolution itself is not preventing the GUI from being scaled. The issue appears to be related specifically to how the standard GUI Scale options are calculated or applied in fullscreen at 1920×1080.

The original issue with Sodium remains:

1x and 2x result in the same effective GUI size.
3x and 4x result in the same effective GUI size.

Activity

  1. added
    P-did-not-follow-templatePriority: Lowest, user did not correctly fill in the issue template
    and removed on Aug 28, 2026
  2. douira commented on Aug 28, 2026

    @douira
    Contributor

    We require issues to send a game log.

  3. BCYASBU commented on Aug 29, 2026

    @BCYASBU
    Author
  4. BCYASBU commented on Aug 29, 2026

    @BCYASBU
    Author

    The log without using the mod Precise GUI Scalar

  5. BCYASBU commented on Aug 30, 2026

    @BCYASBU
    Author
    Image Gui Scale 1
  6. BCYASBU commented on Aug 30, 2026

    @BCYASBU
    Author
    Image GUI Scale 2
  7. BCYASBU commented on Aug 30, 2026

    @BCYASBU
    Author
    Image GUI Scale 3
  8. BCYASBU commented on Aug 30, 2026

    @BCYASBU
    Author
    Image GUI Scale 4
  9. BCYASBU commented on Aug 30, 2026

    @BCYASBU
    Author
    Image Image Video Settings
  10. astridellensdottir commented on Aug 31, 2026

    @astridellensdottir

    I'm unable to reproduce this issue in Sodium 0.9.2 for 26.2. You have a number of other mods installed; this appears to be an adverse interaction between one of your other mods and Sodium.

    Image Image Image Image
  11. BCYASBU commented on Sep 5, 2026

    @BCYASBU
    Author

    I removed all the other mods and tested it with Sodium 0.9.2 for 26.2, but the issue still occurs. So it doesn't seem to be caused by an interaction with another mod.

    latest.log

    Image Image Image Image
  12. BCYASBU commented on Sep 5, 2026

    @BCYASBU
    Author

    One more thing I noticed is that I have “Prefer Vulkan” enabled in the Graphics GUI. Could this be related to the issue?

    Also, I’m using LabyMod 4 as the launcher, but the instance I tested was a regular 26.2 Fabric instance downloaded separately, rather than the LabyMod version. So LabyMod itself shouldn’t be adding any other mods to the instance.

  13. added
    S-cannot-reproStatus: Developer can't reproduce
    and removed
    P-did-not-follow-templatePriority: Lowest, user did not correctly fill in the issue template
    on Oct 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    S-cannot-reproStatus: Developer can't reproduce

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions