Welcome to the ZDoom Forums!

So... I checked the SLADE forums for anything about why SLADE won't compile my ACS, and was able to find one thing from about... Well, exactly one year ago. According to SlayeR in that thread, it wouldn't compile because sladetemp.o and acs.err were missing. And they're missing from my folder, too. But I have no idea where they come from, and there are no actual solutions in that thread, or anywhere else in the forum. Not to mention, nobody's posted there since April 12th, hence why I'm asking here. But does anyone that uses SLADE happen to have those files that they could maybe put up here? Or even some sort of solution as to how to get it to work? Because right now, Doom Builder is borked for me (doesn't even start), and SLADE would be my preferred alternative...

tl;dr SLADE won't compile my ACS. I need sladetemp.o and acs.err. Please help

I don't really know anything about SLADE, but I can tell you it's not needed at all to complile your scripts. All you really need is ACC. Put your scripts in a text file and drag and drop the .txt on ACC.exe. Take the compliled lump and import it to your wad as the BEHAVIOR lump using SLumpEd or XWE.

Also, sladetemp.o and acs.err are simply intermediate files generated by the build process (therefore somebody else's won't help you).

Will it not compile anything at all, or just something you've written recently? If it's just the recent stuff, try upgrading ACC. SLADE comes packaged with an old version that won't support many new features.

Risen wrote:Will it not compile anything at all, or just something you've written recently? If it's just the recent stuff, try upgrading ACC. SLADE comes packaged with an old version that won't support many new features.

It comes back with a message that says "Compile Failed". I've tried that with the version of ACC it comes with, and the newest, and all the newest zdoom acs files and all that fun stuff, and it always comes out with the same result. Interestingly, SLumpEd also reacts the same when attempting to compile ACS.

Grof. Looks like I'll have to do it the somewhat harder way...

I have the same problem.
Sucks when repeatedly testing stuff because it takes so long compared to hitting the compile button in the map editor and being done with it.

Problem solved.

Stick your Slade folder somewhere where the path name won't have any spaces.

Like "c:\SLADE\".





I really wish I knew about that earlier...

Calling Slayer to this thread.

One should assume that this issue is addressed correctly by applications considering that Windows has been using 'Program Files' in the English versions for more than 10 years...

Not to mention that Program Files/SLADE is the default installation path for SLADE.