The forum has been set to read-only mode. For community discussion and questions, head over to our Discord: https://discord.taleoftwowastelands.com

"Misconfigured INI settings detected" despite following guide

General help and technical troubleshooting. Ask for help here if you can't find an answer in the FAQ.
Post Reply
LuckyGrunt
Posts: 4
Joined: Mon Aug 22, 2022 8:35 pm

"Misconfigured INI settings detected" despite following guide

Post by LuckyGrunt » Mon Aug 22, 2022 8:48 pm

So, I'm being told via in-game pop up that my ini settings are misconfigured in the "falloutcustom.ini".

I've followed the guide to a tee, and yet this pops up every single time I've loaded the game since downloading TTW. Is there a fix for this? I've already deleted the ini settings and opened both games through Steam, selecting the ultra settings, and nothing else. I even uninstalled both games and reinstalled everything to try to get it to work, and no dice.

On a possibly related note, whenever I start the game, I never get the option to start in DC (not that I really want to, but I'd still like the option). I don't know if that's related, but that's also an issue.

Any help would be greatly appreciated.

Thanks. Peace and love, my dudes.

User avatar
RoyBatty
Gary
Posts: 7742
Joined: Sun Apr 27, 2014 10:26 am
Location: Vault 108

Re: "Misconfigured INI settings detected" despite following guide

Post by RoyBatty » Mon Aug 22, 2022 10:57 pm

Sounds like MO2 isn't working properly. Not sure what to do about that, perhaps ask on the MO2 discord.
Image

LuckyGrunt
Posts: 4
Joined: Mon Aug 22, 2022 8:35 pm

Re: "Misconfigured INI settings detected" despite following guide

Post by LuckyGrunt » Tue Aug 23, 2022 9:37 pm

I'll try that and see what they say.

Thanks.

LuckyGrunt
Posts: 4
Joined: Mon Aug 22, 2022 8:35 pm

Re: "Misconfigured INI settings detected" despite following guide

Post by LuckyGrunt » Fri Aug 26, 2022 7:54 pm

Okay, so it turns out that when I copied the INI settings to paste into MO2, I missed the very last character in the sequence, so that was apparently what was causing it. Now I've got a completely different issue, but I'll make a new thread.

Post Reply