Map does not compile after adding skybox

[ソーピ-ちゃん]

I am using hammer.exe from garrysmod (basically because the source sdk over steam does not want to launch, i dont know why) and i created a little map and wanted to add a skybox. After doing that I try to compile but hammer.exe does not respond anymore and my cpu is on 100%. I even tried to create a skybox and paste the map in afterwards, same result. Does anyone have an Idea how to solve this problem? I wanted to make a 3D Skybox later but with this its impossible and I cannot afford to start making the map from scratch :(

[Peter Brev]

CPU will always rise to 100% when compiling. You can limit that with -threads # (where you put your number, so if you have 4 cores, and want to use 2, you put -threads 2).

Garry's Mod causes a lot of havoc, and we still don't know why. It's probably that the game uses a version of the Source engine that isn't being liked by Hammer at all and the author doesn't care about fixing it at the difference of Black Mesa.

Using Hammer from Half-Life 2 mitigates the problem but requires you to port the map over to Garry's Mod after compiling.

[ソーピ-ちゃん]

Originally posted by speedvoltage:

Using Hammer from Half-Life 2 mitigates the problem but requires you to port the map over to Garry's Mod after compiling.

I am not sure if I really want to do this. I also wonder why this only happens now. My other map had a skybox and no problem whatsoever. And with this map I tested also just to place 6 Sides of a block around the map with normal texture and it also does not work. When the Block is removed it compiles again (taking longer than normal but it does)

[Peter Brev]

Originally posted by speedvoltage:

Garry's Mod causes a lot of havoc, and we still don't know why. It's probably that the game uses a version of the Source engine that isn't being liked by Hammer at all and the author doesn't care about fixing it at the difference of Black Mesa.

[Stroyed]

Originally posted by Soapy-kun:

Originally posted by speedvoltage:

Using Hammer from Half-Life 2 mitigates the problem but requires you to port the map over to Garry's Mod after compiling.

I am not sure if I really want to do this. I also wonder why this only happens now. My other map had a skybox and no problem whatsoever. And with this map I tested also just to place 6 Sides of a block around the map with normal texture and it also does not work. When the Block is removed it compiles again (taking longer than normal but it does)

If you mean porting over the map, it's literally just uploading the map's file to the Garry's Mod workshop.

[ソーピ-ちゃん]

Originally posted by Stroyed:

Originally posted by Soapy-kun:

I am not sure if I really want to do this. I also wonder why this only happens now. My other map had a skybox and no problem whatsoever. And with this map I tested also just to place 6 Sides of a block around the map with normal texture and it also does not work. When the Block is removed it compiles again (taking longer than normal but it does)

If you mean porting over the map, it's literally just uploading the map's file to the Garry's Mod workshop.

Ok but i want to test the map right away, or does e.g. halflife 2 start then and i can walk around there?

[ソーピ-ちゃん]

I tested now another thing. I created a new map with a block to walk on and a skybox around and it works. So I dont know whats wrong with the other map... Are there any problems known that might occur, like misplaced objects or something?

[Peter Brev]

Are you even applying the tools/toolsskybox texture? It sounds ridiculous but you never know.

[ソーピ-ちゃん]

Originally posted by speedvoltage:

Are you even applying the tools/toolsskybox texture? It sounds ridiculous but you never know.

I understand that ;) I created a block with the tools/skybox texture. And then made it hollow with 32. I tried 64 as well, but did nothing change. And i can clearly say that the method works with a new map.

[ソーピ-ちゃん]

So i did some what of reverse engineering the map. I created the skybox and basically copied part per part the map over there. Apparently the compiler has a problem with the stairs i made. I made some railings with a block next to one stairstep and 2 blocks as pillars onto that block and that construction repeatedly next to every stairstep. Then a long block turned with ALT to make it diagonally onto those mentioned blocks. I hope you understand my dexcription ;) Anyways, with them the compiling now takes several minutes. Much longer than without them.

My first map had much more Textures and Objects and stuff and still got compiled in less than 10 seconds. I am not sure why Hammer has such problems with those stair railings. I will try to maybe simplify that, maybe then i have "solved" the issue.

[libertarian ettin]

Try making the stair railings func_detail.

[PLAB]

okay so i had the same problem, i have a sky box that SHOULD be working, but its not compelling. turns out the reason (or at least my reason) for this happening is because I had too many unnesisary block brushes. its a pretty simple fix, go to every block brush that isn't a core part of the maps layout (like if you have support beams or small details) and press "CTRL+T" to turn them into a func_detail. once you do that, it should work, worked for me. but if that doesn't work, I think this problem comes from poor optimisation, so exparament with different ways of optimising