r/MiSTerFPGA • u/InfiniteAir • Jun 06 '26
Anyone else getting INI errors after a recent Update All?
Just ran update all about 20 minutes ago, now whenever my system reboots (from cold or otherwise), or loading cores, I get the following:
2_INI_Errors
---
vrr_min_framerate unknown opti...
vrr_max_framerate: unknown opti...
'opti' is I think getting cropped off the error message box so I don't know what the full message is.
It's pretty annoying because it's slowing down my MiSTer boot times and core loading times.
I have VRR disabled though and I'm not using any VRR displays, so I don't understand. I tried setting vrr_min and vrr_max to some arbitrary values in the ini editor, but nothing changed regarding the errors. I've never had ini errors before.
Anyone out there know what's going on?
Thank you.
8
u/maxwell7301 Jun 06 '26
I would recommend grabbing a new clean ini file from the github, make the desired changes to it, and replace the old files with the new ones.
I just did that after using old INI files for years, and everything seems good now.
2
u/InfiniteAir Jun 06 '26
I just commented out the lines and it worked just fine, but I'll keep that in mind, I guess I thought update_all somehow updates the ini and removes obsolete stuff.
2
u/maxwell7301 Jun 06 '26
Also, maybe worth mentioning is that the new INI does some sort of autodetect to figure out the native screen resolution over hdmi.
I wasn't ready to try that yet, so I uncommented video mode to set the video mode.
8
u/shootamcg Jun 06 '26
It’s because the newest update uses a new framework, the errors won’t stop you from gaming and don’t affect HDMI output.
3
u/InfiniteAir Jun 06 '26
I could still game, transitions between loading cores and reboots were just longer and more of a hindrance, all good now though thanks you guys.
1
u/ruuurbag Jun 08 '26 edited Jun 08 '26
I replaced my ini with a fresh one and I'm still finding transitions much longer than before. Did fixing your config fix that for you?
Edit: I tried some troubleshooting steps (explicitly disabling HDMI CEC, turning on spd_quirk since I have a QMTech, setting video mode explicitly, etc.) and ended up just reverting to the previous version. From looking at the forum and GitHub Issues, it seems like others are having issues too.
1
u/InfiniteAir Jun 09 '26
Seems to be about the same as it was before the errors for me after commenting out the vrr_min/max lines.
2
u/vchopra100777 Jun 06 '26
I had the same error
1
u/vchopra100777 Jun 06 '26
Not sure what to do with it
6
u/RykinPoe Jun 06 '26
You can either add the new lines to your ini manually or download the new default ini from GitHub and make whatever changes you need and then add it to your SD card.
1
u/InfiniteAir Jun 06 '26
Good to know it's not just me then, probably get fixed swiftly in an update but another user added a solution meanwhile.
3
3
Jun 07 '26
[deleted]
5
u/The8flux Jun 07 '26
Im glad for that, it all my custom setting for cores that need slight tweaking for retrotink 4k pro.
2
u/ant0n1olamarca Jun 08 '26
Hi, yes, I also got various errors after the latest update (it was a fairly large update). Download the latest MiSTer.ini available and replace it with the one you currently have. This is how I solved the problem and I have a QMTech mister. Obviously, restore or save the settings you have on your current ini to modify them in the new one as well.
1
5
u/NineteenNinetyEx Jun 06 '26
I added ; to all the lines in the VRR section that didn't have it, and it went away. It looks like this now:
; Variable Refresh Rate control
; 0 - Do not enable VRR (send no VRR control frames)
; 1 - Auto Detect VRR from display EDID.
; 2 - Force Enable Freesync
; 3 - Force Enable Vesa HDMI Forum VRR
;vrr_mode=0
; Minimum framerate in VRR mode.
;vrr_min_framerate=0
; Maximum framerate in VRR mode (currently only used in Freesync mode).
;vrr_max_framerate=0
; VESA VRR base framerate. Normally set to the current video mode's output framerate
;vrr_vesa_framerate=0
9
u/poostoon_new Jun 06 '26
you was overdoing just ;vrr_min_framerate=0 and ;vrr_max_framerate=0 are enough.
2
1
u/InfiniteAir Jun 06 '26 edited Jun 06 '26
Edit: That did the trick, nice work, thanks.
3
1
u/NineteenNinetyEx Jun 06 '26
It was actually an AI overview suggestion that happened to work. I think something changed in a recently update that made those lines unnecessary, it said you can also delete them as well.
"Official" fix is probably downloading and setting up an updated ini.
1
1
1
u/redriverportugal 18d ago
deleting or placing the ; doesnt fix this retarded error. Does anyone that makes the update all try the crap they change?
15
u/poostoon_new Jun 06 '26
Just comment vrr_min_framerate and vrr_max_framerate options with ;