Initial Setup of v1.5 Rogue Trader Template - WittleWolfie/OwlcatModdingWiki GitHub Wiki

With official patch 1.5, Owlcat switched the game's version of Unity to 6000.0.52f1 and in the process introduced a number of issues in the modding template. Owlcat have said they won't address these until the patch for DLC3 ships in approximately mid-2026, so in the meantime follow these steps to get the template functioning correctly.

Note that these instructions are for installing the template under Windows. Other operating systems haven't been tested and may encounter additional issues.

  1. Extract WhRtModificationTemplate.tar somewhere on your system. Due to path length issues, ideally this will be in the root of a drive.
  2. Install Unity Hub if you don't already have it and choose Add -> Add Project From Disk. Browse to the template folder.
  3. Click on the template in the project list.
  4. You will be prompted to download and install the required version of Unity (6000.0.52f1) if you don't already have it. DO NOT USE AN OLDER VERSION OF UNITY!
  5. Once the editor has finished loading, you will see a large number of errors in the console referring to RenderPipelines. To address these, go to Window -> Package Manager and under the "In Project" list find Core RP Library, which should show a Custom version. Click the Remove button and click OK to the popup messsage.
  6. With the uninstallation complete, close the Package Manager and exit the editor.
  7. In File Explorer, go to the template's folder and in \Assets\RogueTraderAssemblies\ search for *recorder* and delete the two DLLs and two meta files (Unity.Recorder.dll / Unity.Recorder.dll.meta / Unity.Recorder.Base.dll / Unity.Recorder.Base.dll.meta).
  8. In the same folder, search for *RenderPipelines* and delete the three DLLs and three meta files (Unity.RenderPipelines.Core.Editor.dll / Unity.RenderPipelines.Core.Editor.dll.meta / Unity.RenderPipelines.Core.Runtime.dll / Unity.RenderPipelines.Core.Runtime.dll.meta / Unity.RenderPipelines.Core.ShaderLibrary.dll / Unity.RenderPipelines.Core.ShaderLibrary.dll.meta).
  9. From Hub, load the template again. It will take a while as it loads shaders, and then once the editor is open it will start compiling them.
  10. Once the compilation is finished, in the Console if you click on the Clear button all error messages should be removed.
  11. Exit the editor and you'll get another compilation pop-up. Wait until it completes and then load the template again from Hub.
  12. The only error in the console should be regarding references.xml being not found. This is normal in a vanilla template. Exit the editor.
  13. Download MicroPatches-Editor-Installer.exe. At the time of writing, v1.20 is the latest version available.
  14. Move the exe into the template folder and run it. Once it is complete you can close and delete it. N.B.: If the screen flashes up briefly and closes, then it likely failed to find a copy of Player.log in the game's AppData folder. Make sure to run the game to generate a log file. MicroPatches uses this to locate the game's install folder.
  15. Load the template from Hub again. The editor will get stuck with the progress bar at around 20%. Open Task Manager, go to the Details tab, right click on a Unity.exe process and choose End Task. Continue until no Unity.exe process remains running.
  16. In File Explorer, go to the template's folder and in \Library\APIUpdater\ delete project-dependencies.graph.
  17. Load the template from Hub again. This will take a while as it processes blueprints.
  18. Once the editor opens, you should have no errors. You are now ready to create and export mods for v1.5.