![]() (though, you can try new OGSR yourself, but it's better when MotZ authors will officially state new OGSR release support. Just wait for new OGSR engine release and, then, wait when MotZ authors will port their mod to the new release. OGSR already supports autodetection of Steam version, but the new version is not released yet. ![]() (when it will be released, you won't need to step 3) Add -steam key to the launch params in the game properties in the Steam Library Rename OGSR's folder bin_64 to bin, if OGSR executable file name is different from XR_3DA.exe, rename it to XR_3DA.exeģ. Rename your original bin to bin_backup (or bin_orig or whatever)Ģ. Tl dr - speaking from firsthand experience, it isn't possible to trick steam into tracking MotZ' playtime This should work:ġ. I was able to get Steam to run my mods for Vampire the Masquerade and thought maybe I could do the same here. Tl dr - speaking from firsthand experience, it isn't possible to trick steam into tracking MotZ' playtime It works for, say, CoP standalones as they use Stalker-COP.exe as a wrapper to launch xrEngine, but OGSR's method is very particular and doesn't work anything like the base game's launcher does Shadow Hearts II Director's Cut (Disc 2) Shadow Man 2econd Coming: Shadow Man 2econd Coming: Shadow Man 2econd Coming: Shadow The Hedgehog: Shadow Tower Abyss: Shadow of Destiny: Shadow of Ganymede: Shadow of Memories & Zone of the Enders Z.O.E Tentou Houei-you Movie-ban: Shadow of Memories: Shadow of Memories (Tentou Houei-you Movie-ban. Or rather, it'll launch into the 32-bit executable, not the 64-bit. If you attempt to the game will simply fail to launch, as MotZ boots from xrEngine, not setup-bp.exe Originally posted by cyäegha:that works for mods that don't use OGSR, but MotZ does this necessitates creating a shortcut to xrEngine.exe in bin_64 and appending -steam to the target field, and because steam doesn't actually allow you to change the path that SHoC's gameID refers to, you physically cannot launch any OGSR-engine mod via re-naming the executable ![]()
0 Comments
Leave a Reply. |