Packaging, map paths

Development Platform & Builds
, ,
1

I’m a new unreal developer, so if I’m missing something please point me in the right direction

Recently ran into an issue with map paths breaking upon renaming. They are super long and specific to a drive’s initial path in my current project by default.

I found this “error” by going to the build dropdown and selecting “Map Check” (Packaging Results):
Warning Warning Unable to generate long package name for …/…/…/…/…/Dev/Unreal Projects/TwinStickShooter 411/Content/Maps/ArenaMap.umap because FilenameToLongPackageName failed

These maps appear to be configured in file → package product → packaging settings.

Despite the error this seems to work just fine when packaging if the path is correct.

If I rename my project the path’s don’t change and the game breaks when trying to load maps.

If I remove the references entirely it still works just fine.

Initially I thought I found a bug, but this behavior is so strange I feel like I’m missing a step.

2

Hello w.c.ahlswede,

After renaming your project, right-click on the ‘Content’ folder within the Content Browser and select the ‘Fix Up Redirectors in Folder’ option.

Could you provide me with your full log from the failed packaging attempt so I can take a look?

There shouldn’t be a need to rename your project if these errors were initially not causing your project to fail to package. Warning messages are different from Error messages in that they sometimes are just warning something could go wrong. The FPackageName::FilenameToLongPackageName converts the supplied filename to long package name. Throws a fatal error if the conversion is not successful.

Thanks,