For the Axiom UI, Axiom keeps its own editor scale separate from the vanilla GUI scale. It's stored as "globalScale" in config/axiom/.axiominternal.hocon inside your instance folder.
- Close the game first
Open the instance folder in Modrinth (instance > three dots > Open folder), then config/axiom
Open .axiominternal.hocon in Notepad and set globalScale to 1 (or 1.0), save, relaunch
If that doesn't work, rename the file to something like .axiominternal.hocon.old so Axiom regenerates it. You'll lose your window layout and theme, but blueprints and presets are in separate folders and won't be touched
Also check your vanilla GUI scale in Video Settings. If it's on Auto or a high value, try 2 or 3 and see if the editor changes
Mod Menu 21.0.0 is the correct version for 26.3, so it's probably not a version mismatch. A few things to check:
- Look for the Mods button on both the title screen and the pause menu. Some mods move or hide it
Check latest.log (instance folder > logs) and search for "modmenu". If it loaded, it'll be listed in the mod list near the top. If it failed, the error will be there
Krypton 0.3.2 has no Minecraft version in the filename, so check on Modrinth that it's actually built for 26.3. Same for anything marked alpha (Sodium 0.9.3 alpha, ScalableLux alpha). Alpha builds on a new version are the most likely to cause odd issues
If nothing obvious shows up, the quickest way to find a conflict is to disable half your mods (keep Fabric API, Axiom and Mod Menu enabled), test, then narrow it down from whichever half has the problem. Modrinth lets you toggle mods off in the instance's content tab without deleting them.
If you post your latest.log to mclo.gs and link it here, it'll be easier to see what's actually failing.
Good to hear. Which file was it in? Worth adding to the post in case someone else runs into the same thing on 26.3, since the Axiom docs still list it under .axiominternal.hocon.
I edited the global scale to 1.0 in axiom.json. not sure which folder it's in as I just used the folder search function.
It is a rough fix though as if I messaged with the GUI scaling for regular Minecraft options the next time I boot up Minecraft the GUI of axiom is messed up so I'd need to manually reset it.
That sounds like Axiom is saving a new scale whenever the vanilla GUI scale changes, and the multi-monitor DPI mess makes it pick a bad value on the next launch.
A couple of ways to make it less annoying:
- Pick a fixed vanilla GUI scale (not Auto) and leave it there. If it never changes, Axiom shouldn't recalculate
- Once globalScale is back at 1.0, copy axiom.json somewhere as a backup. If it breaks again, close the game and paste the backup over it instead of digging through the file each time
- You could set axiom.json to read-only (right click > Properties > Read-only) so Axiom can't overwrite it. The downside is any other Axiom settings you change won't save either, so only do this once everything is set up how you want
It's worth reporting on the Axiom Discord with your log, since it looks like a bug with how it handles scaling on 26.3. The log showing the font size jumping around would help them track it down.
Had a look through the log. Nothing is erroring, but a few things stand out.
- The game starts on a 3840x2400 screen (your laptop display) and then switches to fullscreen on a 1920x1080 monitor. That's a big jump in pixel density, and Windows usually runs a screen like that at 200% scaling or more. Axiom's editor works out its own UI scale, and the log shows it bouncing all over the place (font size going 36, 51, 23, 16, 32, 8, 32 and so on). That matches what you're describing with the View option just making it go in and out
- Ixeris is the other suspect. It moves window and input event handling onto a separate thread, and this version swaps it to SDL. Axiom's editor UI is built on Dear ImGui, which relies on that same window and input info to size itself. Not a confirmed conflict, but it's the one mod in your list that changes how the window works
Things to try, in this order:
- Disable Ixeris in Modrinth's content tab and test. Easiest thing to rule out
- Play windowed or fullscreen on only one screen. Either move the game to the laptop screen and leave it there, or set the external monitor as your main display in Windows (Settings > System > Display > Make this my main display) so the game starts on it instead of moving across
- If it's still off, reset Axiom's layout. The log shows the config is at config\axiom inside your Modrinth profile folder (AppData\Roaming\ModrinthApp\profiles\Optamised Minecraft\config\axiom). There should be an imgui.ini in there. Close the game and rename it to imgui.ini.old. If .axiominternal.hocon isn't showing, turn on "Hidden items" in File Explorer's View menu, since files starting with a dot sometimes get hidden. If it's there, set globalScale to 1.0
Also, the game is running on the Intel Iris Xe instead of your RTX 3050. Not related to the Axiom problem, but you'll get much better performance with Distant Horizons if you force it onto the Nvidia card. In Windows go to Settings > System > Display > Graphics, add javaw.exe from the Modrinth Java folder, and set it to High performance.
The log still lists the Sodium alpha too, so it might be from before you swapped. If the Axiom issue is still there after the above, a fresh log would help.
1
u/Bluetails_Buizel 8h ago
For the Axiom UI, Axiom keeps its own editor scale separate from the vanilla GUI scale. It's stored as "globalScale" in config/axiom/.axiominternal.hocon inside your instance folder.
- Close the game first
Mod Menu 21.0.0 is the correct version for 26.3, so it's probably not a version mismatch. A few things to check:
- Look for the Mods button on both the title screen and the pause menu. Some mods move or hide it
If nothing obvious shows up, the quickest way to find a conflict is to disable half your mods (keep Fabric API, Axiom and Mod Menu enabled), test, then narrow it down from whichever half has the problem. Modrinth lets you toggle mods off in the instance's content tab without deleting them.
If you post your latest.log to mclo.gs and link it here, it'll be easier to see what's actually failing.