Thank you Samase 0.7.31 used.

Samase MOD starcraft remastered v 1.23.9.10145 Execution error.... T.T

Please Samase bug fix update.

Thank You Neiv

2022 Happy New Year~!!

Okay, updated to work with the current patch: Download

Hi,
Is there any prerequisites I need to have installed to run Samase?
I've been trying to run samase version 0.7.42, but I get the error "Couldn't extract DLL: Access is denied. (os error 5)". It seems to be when starcraft is about to be launched, since I can successfully run samamse with the --pack parameter but then I get the same error when trying to run the self executing exe created.

Oh, and if it is relevant, I have StarCraft remastered version 1.23.9.10145

Thank you for this awesome looking tool!

Huh, it fails to write a file to a temp directory. Most likely to "%TEMP%\samase", not sure why that would ever fail.

Anyway, here's an update that reports the exact path that is failing, so try it and see if you see something on your system that would prevent accessing that path. May be antivirus software that doesn't trust the exe?

Download

In other news, this update also has support for locale paths. That is, `Locales\enUS\Assets\rez\stat_txt.json` now gets priority over plain `rez\stat_txt.json` if the game is currently in English.

You can still use the non-locale paths in case you only want to support one language, or if there is a specific language that should be "preferred default" for languages that you don't have localized files for.

Samase will always try to load a file for any locale if it exists, instead of loading default Blizzard files. The full file lookup order is now:

1) Currently active language `Locales\___\Assets\PATH`
2) Plain `PATH`
3) Any other language `Locales\___\Assets\PATH` in order enUS, deDE, esES, esMX, frFR, itIT, jaJP, koKR, NOLA, plPL, ptBR, ruRU, zhCN, zhTW
4) If the path starts with `HD2` or `SD`, check steps 1-3 without the `HD2`/`SD` prefix
5) Load default Blizzard file

Thanks for the quick response.

It was indeed my antivirus that blocked the dll in the Temp folder.

It works great now, thanks!

fucc i been using this for a while and its so good

i cant get it to work anymore tho


the log says its working

[2022-02-02][16:56:29.401][src\file_hook.rs:923][INFO] Loading custom tileset/ashworld.dds.vr4
[2022-02-02][16:56:29.402][src\file_hook.rs:923][INFO] Loading custom tileset/ashworld.dds.vr4


but the modded ashworld.dds.vr4 that I've been using for months that used to work is just not anymore.
my creep tiles (the first few tiles in the set) are loading up as default instead of the solid R / G / B colors I set

any ideas family

probably hard to know whats up without the exe/files/anything more

using

samase-0.8.2.exe

ashworld.dds.vr4 with the first couple creep tiles set to solid R G B
(download: https://www.mediafire.com/file/bnnej3e47oeb6rr/AshWorld.dds.vr4/file)

and this green screen map to test:

Attachments:

Nevermind i'm dumb

it was working the entire time

Its been a while since I tried to put together a mod for SC.. like back to the original game. I dropped my old moded DAT files into a directory and ran samase-0.8.2. The log files says the DAT files are loaded... but there are no changes to unit/weapons/upgrades, etc in the game. I'm running version 1.23.9.10145 or SCR. Looking for some suggestions :-/

Noone will be able to help without more details, can you share the mod? Are you actually launching the modded executable? If the DAT files are very old maybe they're made with something that wouldn't work now

I tried running SC by launching it via samase and I also tried creating an executable. Neither approaches worked. I am running SC via Lutris on an Ubuntu box. Here are the exe and mod files.

I was able to use PyMS to decompile DAT files. Next I'm going to try recompiling them and see if that changes anything.

Thanks

Alright lmao I would have no idea if anything on Linux works or how to make it work, sorry

Thank you, Samase!

Attachments:

Hello everyone!

I'm and old man, and not well computer educated. I just wanted to remember the days when I loved and played SC a lot in the LAN, back in 90xx. I bought SC:Remastered and found that the standard AI isn't good enough, but the Ladder/ranked is the way too good for me

Could you help me with the launching Samase + BWMetaAI that I found at GitHub:

I did everything step by step as they instructed:

When I launch "samase.exe custom" in the Terminal or (by a shortcut, no matter) I get the error "Fatal Error -- No open_file". See the screenshot in the attachment.

PS: Or may be there is another method to play SC with a better AI?

Thank you in advance.

Attachments:

Post has been edited 1 time(s), last time on Aug 8 2023, 11:44 am by vga257.

Not exactly sure what's that about, maybe your system's Windows is somehow different. But I built a new version with a change that may let it launch properly, or at least show some different error: http://www.staredit.net/?downloadAttachment=12066&key=10216960

Thank you for your efforts, I really appreciate.

I was able to start SC:R, select multiplayer > map > top vs bottom > me vs computer > start and once my nexus appears SC:R closes with the error message attached.

Probably there is something in the BWMetaAI.

Attachments:

If you can share the crash dump I can take a look, but it may be that the stricter AI script checks added in a patch don't work with BWMetaAI, or there is just some other issue with its AI scripts.

Sure, here is the dump

Attachments:

Ah, you have ARM64 hardware, it's probably having issues due to that. The crashdump seems to point
to a cause unrelated to samase, so not sure if that's even fixable.

But it may be just that the 32-bit SC:R doesn't work on your system at all? Launching the game through
Battle.net will default to 64-bit exe, but samase doesn't have full support for 64-bit game yet,
so it launches the 32-bit one instead.

I'll attach 64-bit build so you can try with that instead, it probably works fine for just AI script
replacements. If it still crashes (or has different kind of launching issues?) then send a crashdump,
*maybe* it's a different cause that can be fixed.

Attachments: