/tg/Station 13

Ever since the map loading update I haven't been able to figure it out and my compile to run time for testing takes like 5 minutes per go, up from runtimestation's 30 seconds. Please help

In dreammaker, uncheck everything in _maps except for runtimestation.dm and compile.

Wait really I thought that was removed with the map building update thing

Ticking the map's DM forces it to load that specific map when you start the server.

Wow it worked
I could have sworn just ticking the boxes was removed, was it readded

Yea, it was added shortly after the loading was changed to runtime instead of compiling.

selecting runtime doesn't seem to improve compile time, only round loading time

wait there's a fucking map that loads quicker for testing???

i am retarded

tacolizard wrote:selecting runtime doesn't seem to improve compile time, only round loading time

That's because maps aren't compiled in, but loaded at runtime. (Technically the miscellaneous z levels that show up are compiled in, but theyr'e irrelevant for this discussion)

Oranges wrote:

tacolizard wrote:selecting runtime doesn't seem to improve compile time, only round loading time

That's because maps aren't compiled in, but loaded at runtime. (Technically the miscellaneous z levels that show up are compiled in, but theyr'e irrelevant for this discussion)

I like to turn those off too for even more sanic compiling

MisterPerson wrote:I like to turn those off too for even more sanic compiling

dam u crazy man

MisterPerson wrote:

Oranges wrote:

tacolizard wrote:selecting runtime doesn't seem to improve compile time, only round loading time

That's because maps aren't compiled in, but loaded at runtime. (Technically the miscellaneous z levels that show up are compiled in, but theyr'e irrelevant for this discussion)

I like to turn those off too for even more sanic compiling

teach me

PKPenguin321 wrote:

MisterPerson wrote:

Oranges wrote:

tacolizard wrote:selecting runtime doesn't seem to improve compile time, only round loading time

That's because maps aren't compiled in, but loaded at runtime. (Technically the miscellaneous z levels that show up are compiled in, but theyr'e irrelevant for this discussion)

I like to turn those off too for even more sanic compiling

teach me

Pretty easy, just tick only "runtimestation.dm". If you want lavaland and stuff, tick "loadallmaps.dm" along with runtimestation.

that's what i normally do, but it doesn't improve compile time. I think MisterPerson was talking about something else.

tacolizard wrote:that's what i normally do, but it doesn't improve compile time. I think MisterPerson was talking about something else.

Compile time of the dmb is not affected by maps, but after compiling the dmb, the extra maps are compiled - this is avoided if you disable them. Additionally, the game starts much, much faster if you are set to only Runtimestation.

Gun Hog wrote:

PKPenguin321 wrote:

MisterPerson wrote:

Oranges wrote:

tacolizard wrote:selecting runtime doesn't seem to improve compile time, only round loading time

That's because maps aren't compiled in, but loaded at runtime. (Technically the miscellaneous z levels that show up are compiled in, but theyr'e irrelevant for this discussion)

I like to turn those off too for even more sanic compiling

teach me

Pretty easy, just tick only "runtimestation.dm". If you want lavaland and stuff, tick "loadallmaps.dm" along with runtimestation.

ok but this doesnt really touch compile time because of dynamic building i thought

As I said before, the extra (non-station z-level) maps are compiled after the dmb. Your map selection does not affect compile time of the dmb, but if you do not load the extra z-levels, you can skip compiling them afterwards. Your total compile time will decrease because you are not compiling the extra z-levels. As I also said before, the game starts much, much faster when you are loading Runtimestation instead of a fully sized map. They have a monstrous loading time while Runetimestation takes only a few seconds.