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.


Unreal Project takes very long to load on first start

Problem

When opening the Modding SDK Unreal project for the first time, the editor takes a very long time to load or appears to be stuck indefinitely.

In some cases, it may look like:


Possible Cause

The Modding SDK is delivered without precompiled shaders.

This means:

On systems with:

shader compilation can take a significant amount of time.


Possible Solution

Once the shaders are compiled:

This behavior is expected and only occurs during the first startup or after major engine or SDK updates.


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:

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 combined path length can exceed 255 characters, causing the build process to fail.


Possible Solution

`C:\SubwaySimSDK\`

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