Restore Projector support on macOS (magenta overlays since v14.0)#3135

⚠ WITHDRAWN — NOT A TTS BUG. The cause was on our side: the mod’s own bundles had no Metal variant. Nothing for Berserk to fix. The original report is left below for the record; its diagnosis is wrong. See the comment for what actually happened.

Since the Unity 6 engine upgrade (v14.0, December 2025), any mod that uses Unity Projectors renders them as solid magenta on macOS: range rulers, coherency circles, deployment zones, movement templates, spell/AoE templates. The confirmed case is Star Wars Legion, where all four Projector overlays are broken. The failure is engine-side, not mod-specific: even a vanilla red cube turns magenta under a projection. Projectors are the engine’s only way to drape an overlay onto 3D terrain, scenery and miniatures, so affected mods have no real alternative. If your mod shows magenta shapes on a Mac, this is why. Windows is unaffected. Mac has been broken for 8 months.

The cause has been diagnosed and documented: the macOS build of TTS no longer includes the Standard-shader “receiver” variants that Projectors need. Full technical write-up with reproduction steps and screenshots here: https://github.com/Berserk-Games/Tabletop-Simulator-Modding/issues/7

The request: include those shader variants back in the macOS build. Based on our findings this is a build-configuration fix, not an engine rewrite, and it would instantly repair every affected mod on the Workshop.

v14.0 shipped native Apple Silicon support, which was great news. This one missing piece is what currently makes TTS wargaming unplayable on the Macs that update was built for.

If you play on a Mac and your mods show magenta shapes, please upvote.

Withdrawing this: the cause was on our side, not TTS.

The magenta came from the mod’s own AssetBundles. They were built in 2022 for StandaloneWindows64 only, so they carry no Metal variant, and a shader with no variant for the active graphics API renders magenta — Unity behaving exactly as documented. TTS moving to Metal in v14 is what exposed it. There is nothing for
Berserk to fix, and I was wrong to file it here.

What misled me: every test bundle I built while investigating was also targeting Windows, so I kept shipping DirectX shaders into a Metal player and reading the magenta as evidence about the engine. Rebuilding one bundle for StandaloneOSX, changing nothing else, fixed it.

If you upvoted this because Star Wars Legion shows magenta on your Mac: the bundles are rebuilt and working, and they are now with the mod’s maintainers. The fix will reach you through the mod itself — nothing for you to install or do.

If you maintain another mod with the same symptom, the recipe is one file that serves both platforms: build for StandaloneWindows64 and for StandaloneOSX, then stack the macOS SubShader behind the Windows one in the same shader. Unity falls through to the next SubShader when the first has no variant for the current API.
Do not try to merge them inside one pass — it fails silently. Details and tooling: https://github.com/Berserk-Games/Tabletop-Simulator-Modding/issues/7

Thanks to the 28 of you who backed this. You were right that something was broken; I was wrong about where.