non-normalized path warning

Development Getting Started & Setup
,
1

Hi all,

I’m relatively new to Unreal. I recently upgraded from UE5 early access to UE5.1. Every since then, I get these errors in my Output Log, repeated four times each.

LogConfig: Warning: GConfig::Find attempting to access config with non-normalized path /Users/Shared/Epic Games/UE_5.1/Engine/Config/Layouts/DefaultLayout.ini. Please use FConfigCacheIni::NormalizeConfigIniPath before accessing INI files through ConfigCache.
LogConfig: Warning: GConfig::Find attempting to access config with non-normalized path /Users/Shared/Epic Games/UE_5.1/Engine/Config/Layouts/UE4ClassicLayout.ini. Please use FConfigCacheIni::NormalizeConfigIniPath before accessing INI files through ConfigCache.

It’s usually triggering when I switch to a Blueprint window (often repeating dozens of times in blocks of four).

Any suggestions for how to fix this?

7 Likes
2

Did you solve it?

4

Nope, unfortunately the warning messages persist :frowning:

5

I have a same problem. Please someone tell us solution

6

Same problem here no apparent solution. Doesn’t seem to affect gameplay.

7

in my project it was a plugin that was trying to acess my DefaultGame.ini By inline FString DefaultGameIni = FPaths::ProjectConfigDir() + TEXT("/DefaultGame.ini");
I just had to change this to

inline FString DefaultGameIni = FConfigCacheIni::NormalizeConfigIniPath(FPaths::ProjectConfigDir() + TEXT("/DefaultGame.ini"));
8

I went through my project and disabled all the plugins which either I enabled (in my case mesh editor mode) and anything under plugins that wasn’t published by Epic Games (like IDE plugins). I’m still getting this message. Which plugin were you using specifically?

9

Just to be sure there were no plugins hanging around that I wasn’t aware of I wiped UE 5.1 from my system and re-installed it via the Epic Games Store Launcher. Problem persists.

10

It was Widget Studio Plugin, but note this was my case. Did you try to access any of your config file in any place in your code?

I traced my issue by going into the engine code specificly the function that was causing this log to appear

Under ConfigCacheIni.cpp FConfigFile* FConfigCacheIni::Find(const FString& Filename)

Depending on what was displaying for you “which ini file” try to search all your cpp files

11

Hello. I ran into the same problem in Widget Studio. I would like to share my solution.
Open
image

Replace line 15 with

FString DefaultGameIni = FPaths::ProjectConfigDir() + TEXT(“DefaultGame.ini”);

on

FString DefaultGameIni = FConfigCacheIni::NormalizeConfigIniPath(“DefaultGame.ini”);

Compile your project.

1 Like
12

All my projects are blueprint projects… I’ve never edited a C++ file, and I don’t know how to compile the project. I haven’t installed any plugins. I’ve uninstalled and reinstalled Unreal, the problem persists.

1 Like
13

April 2023. Problem still exists. I’ve tried:

  • Reinstalling Epic Launcher
  • Removing and Reinstalling UE 5.2
  • I’ve even cleaned and reinstalled OS (MacOS Ventura)

I’m on Apple M2 Max, using Xcode 14.2.

14

@whtspdr Did you manage to resolve this issue eventually?

15

Unfortunately, no.

1 Like
16

I found some ticket mentioning similar issue. It should be fixed in 5.2.0 (not the previews).

17

Indeed, it is fixed in 5.2 (release)

18

The same problem is happening to me. If someone can tell us what the solution is, we would really appreciate it

19

Check my message above. It is now fixed in 5.2 (release version)

20

I have same problem in Unreal 5.2.

1 Like
21

Two years later… March 2024… The problem persists!!

1 Like