Toggy81 - Comments

I found the reason. 

The new stadium pack has a new version of CrowdInjection. 

So probably you copy and paste like me and have both versions conflicting, V2 and V3. 

Just delete V2 and the problem desapears.

This is by far the best skin!

However, this error only occurs on my BepInEx when I use it.

It happens when loading certain screens, which obviously take a long time.

Does anyone have any idea what it could be?

Amazing work!!!

Something's happening in my games: both sets of fans behind the goal are facing the opposite way. Does anyone know what might be causing this?

Looking forward to the new update!

Congratulations on the work.

I’m sharing this in case it helps someone facing a similar issue.

I was trying to understand why a stadium rendering mod was working normally for other people, but not for me. 

Since the very first installation of the game, I had noticed a strange behavior: whenever I launched fm.exe, either directly from the executable or via a shortcut pinned to the taskbar, the game would open, immediately close, and then start again.

I had already researched this double-initialization behavior and found similar reports, including on the official Sports Interactive forums, but I never came across a clear explanation or an actual solution.

Interestingly, this did not happen when launching the game through the PLAY button in Steam. 

However, I supose that the mod needs the game to be started via the executable, I kept running into this issue.

Occasionally, the mod would work — specifically when the game did not perform that second restart. That’s when I realized the real problem was the two instances: the first one loaded the mod correctly, but it was being terminated; the second instance would launch without applying the expected rendering changes.

After a week of frustration and exhausting tests, the fix turned out to be very simple: delete the Preferences folder located at:

C:\Users\YOUR_USERNAME\AppData\Local\Sports Interactive\Football Manager 2026\

Once I removed that folder, the game recreated the configuration files and stopped relaunching automatically. From that point on, it started in a single instance and the mod began working consistently.

So in my case, it wasn’t a Steam issue, nor a problem with the mod itself — it was just a corrupted local configuration in AppData.

Lastly, I’d like to congratulate the creator of the stadium rendering mod — outstanding work. It genuinely enhances the immersion and overall experience of the game.

I see. 

I checked one by one and added as comments splited in 

• #changed - the ones that I found the bundle with a misstype
• #This format xxxx:xxxx:bundle_name.bundle - particular cases that looks out of the pattern 
• #missing bundle - the ones that the bundle is not on the CustomStadium list

I send it here if you need it. My next step is go throw the previous versions to check if I can find the missing ones to add to the CustomStadium folder. 

Ok, thank you. 

I had to stop to work, but my intention was to use the app to check for mismatches in my team_mappings. 

For example, I noticed that in version 2.1, the bundle 631:Cheltenham.bundle is mapped, but although the JSON is Cheltenham, the bundle is cheltenham.bundle. I supose that I can just edit it and will work. 

Salford has both JSONs but not the bundle. I downloaded all previous versions to see if I can find it.

I don't know if this problem is general or if it's just in my case, where the steps was to install only version 2.0 and the 2.1 update. And of course I also needed to use v1.4 of StadiumInjection in order to fix my local GameAssembly.dll hash missmatch. 

Just sharing what I found in case it helps someone else.

I was getting the Harmony error:

Patching exception in method null

I don’t fully understand the technical side of it, but I did a small investigation:

• Verified Steam integrity
• Cleared BepInEx cache / interop / patchers
• Tested both public and public_beta branches (GameAssembly hash was identical)
• Tested with StadiumInjection running alone

The issue persisted.

After comparing files and checking the GameAssembly hash, I tried replacing the StadiumInjection.dll from v2.1 with the StadiumInjection.dll from v1.4 — and the Harmony null error stopped occurring.

I can’t say exactly why, but it seems there may be some kind of version mismatch between the injection included in v2.1 and my current GameAssembly build.

Now the injection loads correctly, but BassyStadiumTools reports multiple bundle validation errors (duplicate team IDs and “bundle not found”) related to the team_mappings included in version 2.1.

I will try to review and clean the mappings manually and report back.

Just posting this in case it helps others facing the same issue.

Thanks, but that doesn't seem to be the case. 

Yesterday, for some reason, it worked without me changing anything. 

It loaded the stadiums at the start of the game, but crashed before the first match finished. 

Today it doesn't work anymore and I can't understand why.

I reintalled the game and the mods and had the same error. How is possible only me in the entire world have this problem?  xD

Is the hotfix no longer necessary? Because now I only get this error after installing version 2.0 and then 2.1.

Finally I could make it work. Congratulations for the fantastic work!

I am playing with Strassbourg but with the MOD I couldn´t use my favorite view that is tactical because it is looking like this 

I downloaded version 1.1.1 justo to check and it works. So I implemented 2.0 and again I have the same error. Basically this version looks corrupted. 

Thanks for the tip. 

In my case the message sugest that something is missing in the script and reaching in a null pointer exception.

[Info : Stadium Injection] SceneLoadHandler, GoalReconfigureHandler, LightmapLoaderBehaviour, PresetLightingEnforcer, WeatherEnforcer registered with IL2CPP
[Info : Stadium Injection] Scene load handler registered!
[Error : Stadium Injection] Failed to apply Harmony patch: Patching exception in method null

Maybe something is missing in 2.0 that was in the previous ones and thats why it works for some people. But in my case that is the first time that I am installing it, just drop it in the folder is not working. 

I am trying to find the previous versions in order to get all the previous files, but couldnt fint it yet.

Or is possible that the update totally broke this version. 

Thanks for the reply. 

Is not the antivirus.

The other things like lightining are installed with no problem. Looks like the mod is missing something after the new FM release.

Also, this is the first time I installed it, so I dont have older files inside the games folder. I also used the hotfix after copied the files. 

I have this message 

[Info   😕tadium Injection] Scene load handler registered!
[Error  😕tadium Injection] Failed to apply Harmony patch: Patching exception in method null  

while running before game starts