Same problem here, starting from scratch doesn’t seem to be the issue. Could this be a hardware/driver Issue? I’m putting my build of the 5.2 release on my Perforce server so a friend can try it on his machine.
Deleting the Unreal Engine folder from the AppData\Local folder worked. This folder is under C:\users[username]\AppData\Local\UnrealEngine. It is also a hidden folder.
Removing or reinstalling Unreal will most likely leave this folder unchanged, which is why some may still have this issue.
1 Like
Deleting all my project intermediate files and the AppData/Local folder had no effect for me.
Yeah, I did all you said above. However, I did one more step which was installing the engine on a brand new Laptop, which even hasn’t resolved my issue.
Thats odd.
2 Likes
Message for anyone still searching for temporary solution!
None of the above worked for me. Deleted Appdata folders - DDC - Empty project… I still get the warning. Because it’s annoying and flooding the output log, until someone find a solution, I disabled the LogPackageName log completely with adding those lines in DefaultEngine.ini.
[Core.Log]
LogPackageName=all off
Credits goes to that post:
https://forums.unrealengine.com/t/temporarily-disable-log/363133
Hope that helps someone…
5 Likes
While I appreciate the option to turn things off, it probably does not solve the issue that exists—just hiding it. I would appreciate it if we could get a statement from EPIC here. We are most likely not using a system that starts with uncommon and weird issues right after a fresh install – without knowing if it could end up in a blocker on builds later on.
3 Likes
Has no one found a solution at the moment? reinstalling unreal with deleting AppData/Local folders didn’t help. I just want to raise the topic, for more interest in it from EPIC
2 Likes
LogPackageName: Warning: DoesPackageExist called on PackageName that will always return false. Reason: Input '' was empty.
No fix yet, but did notice that when you scroll up and down in the world outliner it adds more logs
3 Likes
Same problem here
2 Likes
I’m guessing it’s that error too but I can’t find the fix. It’s really frustrating that we are not able to package our projects.
Keep this thread up, having same problems, tried all the sugestions there and the problem still exist
3 Likes
Yes, same issue here…
1 Like
Did you solve your problem? My problem remains the same
1 Like
None of the above worked for me.
2 Likes
Complete new fresh install of win10. Update windows+drivers yadda yadda. Install Epic Games Launcher. UE5. and yet STILL presented with the same error…
Has anyone reported this bug to Epic?
unfortunately there is no way to report this to epic, none of their emails work, and they dont have a number. the support ticket ive used in the past with no response.
so i kinda followed what you said but i dont know how to validate assets, or where the asset action menu is. and did you delete your map or ue5? please clarify each step, this error is messing up the auto texture i have on my map.
I solved the problem by following the above method, opening your project and closing it again, then going to delete all the files in Appdata/UnrealEngine/ and reopening the project. “It is important to open the project first and then close it”
1 Like
started having this issue when we upgraded to 5.2… you can collapse a folder in the outliner and it floods the logs… it’s really annoying because you don’t know if something is really wrong
EDIT: the solution provided by bengmusic worked for me, open the project, close it, remove the whole AppData/Local/UnrealEngine folder and its contents, then open the project again.
Another thing to mention, I always launch my projects from Rider/VS using the run debug button