The map is actually stored in the DMB, so when rebuilding hte DMB it has to be covered.

You can always just un-check the files you don't want included while you're testing if the code compiles, and then re-check them when you're ready to compile the finished game.

CaptFalcon33035 wrote:

Code generally doesn't take too long to compile, it's the RSC.

I doubt that. BYOND is only supposed to update the resource file if something has actually changed.

I compile SS13 manually: by running a batch script which uses the new dm.exe program. I modified a file through the sourcecode, saved it and compiled -- it didn't change. Appearantly, compiling via dm.exe does not count such files as modified.

From what I can tell it takes a lot of time to check for compile errors, and since there's so many lines of code (some which is still in it's raw, decompiled state) it takes a heck of a long time to compile.

Here how I think it's doing the compiling:
1. It grabs all the .dm files and chunks them into one big file. I don't think this takes too long.
2. It checks every line of code in that file for errors. This takes a lot of time.
3. If it didn't find any errors, it looks for the skin file and puts that in the .rsc. Maybe some things in the .dmb are changed as well. This takes some time.
4. Next it grabs the 493 KB map file that comes with it. It includes it in the .dmb, which also takes up some time.
5. Next it actually writes the .dmb file. It stored it in the buffer/memory until this step.

I find it annoying that I have to wait a lot of time for this thing to compile. You change a 0 to a 1 and you have to recompile the entire beast.

EDIT: I checked. Without any resources apart from the skin file and no map, I get 30 seconds. With all of it in, I get 49 seconds. Almost 20 seconds extra!

-- Data

How long is the code itself?


Even with 500x500 size maps and about 20,000 something lines of code I'm still getting fast compile times.

Falacy wrote:

what do you consider fast <.< it should be instant, taking 30+ seconds to compile is rediculous

Be glad that you are not working in some major non-Byond project. Some of those compile times range from five minutes to overnight (no joke).

I would rather wait the extra 30-seconds and have better security on the integrity of my code rather then a few seconds of my non-existent life.

George Gough

I've done a quick Comparison with WOTS 2.0 and 1.8's Compile Times.

WOTS 2.0

Lines of Code(Approx.) 15,932 Lines
.DMB File Size: 850 KB
.RSC File Size: 8,636 KB
Map Size: 1,855 KB
Compile Time: 32 Seconds(WITH Other programs Running)

WOTS 1.8(Much More Buggier, Inefficient, more "Complete", etc)

Lines of Code(Approx.) 28,936 Lines
.DMB File Size: 1002 KB
.RSC File Size: 8,893 KB
Map Size: 1,852 KB
Compile Time: 1 Minute, 2 Seconds(WITH Other programs Running)

Now, WITHOUT The Map File
WOTS 2.0

Compile Time: 3 Seconds(WITH Other Programs Running)

WOTS 1.8
Compile Time: 7 Seconds(WITH Other Programs Running)

It seems to me that Lines of Code Influence how long the compile time takes, but .RSC and Map files is what is taking your time.

This shouldnt at all effect security and/or integrity of anything, basicaly im just asking for the compile we have now to still do what it does, compile the code, load the map, the icons, whatever it might do. But if i dont change the map or the icons, just give me a quick compile so I can recompile the code and check it against the already existant map file and icons.

Its insanely anoying to modify something in the code for half a second, then have to wait 30 seconds for it to compile, then take another half a second to test whatever I just modified. and then if it didnt turn out exactly like i wanted i have to repeat the process

That isn't how you should be programming. You should basically be your own compiler. I often write several procs before I even hit compile.

Except that doesn't happen to me. Often times after writing huge blocks of code and hit compile I don't even get 1 error or warning. It's not that difficult to screw up the BYOND syntax for christ's sake.


What is difficult later is checking to make sure your code did what you wanted it to do. And the compiler will never be able to verify that for you.

Falacy wrote:

yea and then you have 1 thing thats not working right somewhere in one of those procs and youre screwed. I compile every time I take a pause to readback, or at least once after every system/proc i build just to make sure its actualy going to compile, then I usualy test it afterwords to make sure it actualy ran like I wanted it to

That is a good thing, at least only when you finish a function and are ready to test it.

If you have a problem with compile times like that then solve it with your brain...load the maps from an external file. I believe that there are some libraries out there that allow you to do that.

George Gough

Alt-Text, man! ALT TEXT!