This is an old revision of the document!
Table of Contents
Troubleshooting
This page lists common problems that may occur while working with the SubwaySim 2 Modding SDK, along with possible solutions or approaches.
The solutions listed on this page are suggestions and troubleshooting approaches. They may not resolve every issue, as some problems can have multiple or more complex causes.
Troubleshooting
This page lists common problems that may occur while working with the SubwaySim 2 Modding SDK, along with possible solutions or approaches.
The solutions listed on this page are suggestions and troubleshooting approaches. They may not resolve every issue, as some problems can have multiple or more complex causes.
BuildMod.bat fails with an error
Problem
When running BuildMod.bat, the build process aborts with an error and does not complete.
A log file is created in the following directory:
`AppData\Roaming\Unreal Engine\AutomationTool\Logs\C+Program+Files+Epic+Games+UE_5.4`
Inside the log file, an error message appears indicating that:
- a file path is too long
- or a file name exceeds the allowed character limit
This is a known limitation related to Unreal Engine and Windows file system path lengths.
Possible Cause
Unreal Engine (and the Automation Tool) has a maximum path length limit.
If:
- the SDK is located in a deeply nested directory
- asset folder names are very long
- file names are excessively long
the combined path length can exceed the allowed limit, causing the build process to fail.
Possible Solution
- Move the Modding SDK to a directory with a short path, for example:
`C:\SubwaySimSDK\`
- Check your plugin folder structure for:
- very long folder names
- deeply nested directories
- Shorten asset names where possible
- Avoid unnecessary subfolder depth inside your plugin
After reducing path and file name lengths, run BuildMod.bat again.