User Tools

Site Tools


manual:troubleshooting

This is an old revision of the document!


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 issue is related to a Windows file system limitation.


Possible Cause

Windows has a maximum file path length of 255 characters.

Unreal Engine and its Automation Tool strictly rely on this limitation.

If:

  • the Modding SDK is stored in a deeply nested directory
  • plugin folder structures are very deep
  • asset or folder names are very long

the combined path length can exceed 255 characters, causing the build process to fail.


Possible Solution

  • Extract the Modding SDK to a directory with a very short path, for example:

`C:\SubwaySimSDK\`

  • Avoid deeply nested folder structures inside your plugin
  • Shorten folder and asset names where possible
  • Keep paths inside the plugin as flat and concise as possible

After reducing path and file name lengths so that they remain below 255 characters, run BuildMod.bat again.


manual/troubleshooting.1768294569.txt.gz · Last modified: by dcs

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki