Hammer randomly deletes brushes.

[smashballs]

I haven't ran into this issue in a long time especially sense I figured out that solids can't touch the sides of the map limits! The first time it happened was with a skybox 3 days ago, I had displacements by the power of 4 scaled to 0.0625 and for some reason Hammer decided to delete them after a couple times of saving. Now this is happening with my latest project, I have a spike that stand 125 units tall and has a poly count of 15 so I copied and pasted it several times around some walls I made and after I saved I began to work on a door then suddenly Hammer closes. I went to start it up and it shot me the message saying 21 solids were deleted, I fixed it then it said 5 solids were deleted, same thing after i fixed it, then it said 2 solids were deleted and I eventually got it to work.

I wan't to know what causes the issue though, I have done some hardcore looking (I probably suck and Googeling) I didn't find anything on how to solve these faces from being deleted, I kind of fixed it although I wan't to know the proper way to address this issue rather then play a short game of Jenga blocks with Hammer.

[[KIRBY]]

my first guess was invalid solids, but then again, you did use spikes, and you cant have invalid faces on them until you make them concave or turn them inside-out. do you have any screenshot or maybe a map file that we could take a look at here?

[smashballs]

my first guess was invalid solids, but then again, you did use spikes, and you cant have invalid faces on them until you make them concave or turn them inside-out. do you have any screenshot or maybe a map file that we could take a look at here?

This is the set up, I don't know how it would cause problems.

I also have another question because I would rather stay away form making to many threads about things I can't find.
Is there an easy way to add lighting to a func_door or at least make the func_door not have pitch black textures from touching faces?

[[KIRBY]]

alright here is explanation to your problem
you have too many faces touching eachother, this makes source go crazy and can remove faces from brushes, also if you have too many faces with the same texture, everything will break too.

as for func_door, it uses lightmaps, so if door is dark on one side, it will stay like that even if you move it to a very bright room, use normal doors instead

or just learn to model, blender is free, 3ds max can be acquired under student license

[ErikKiller]

The spikes aren't func_detail? How does that affect the compile time?

[smashballs]

The spikes aren't func_detail? How does that affect the compile time?

It doesn't really affect it that much surprisingly, speaking that the map is fairly simple right now (I just started) the vrad takes a long time but it always does on maps this size especially that optimization will come last after each part, when the fort will for sure maintain its walls, I will turn the spikes into one big func_detail.

[smashballs]

alright here is explanation to your problem
you have too many faces touching eachother, this makes source go crazy and can remove faces from brushes, also if you have too many faces with the same texture, everything will break too.

as for func_door, it uses lightmaps, so if door is dark on one side, it will stay like that even if you move it to a very bright room, use normal doors instead

or just learn to model, blender is free, 3ds max can be acquired under student license

Thank you for the heads up, i wasn't sure why Hammer didn't like my spikes.

Well I could do that or possibly try something else, possibly spawning the door outside then putting its origin to match it as if it were in the door frame then parent the door to a func_movelinear so the door will move back into the door frame and it will have a descent light map cast on it.

Maybe I could just make the door a func_physbox (I don't know if it will set a specific light map) then parent that to a tiny invisible block that will be the door.

[beach]

Maybe I could just make the door a func_physbox (I don't know if it will set a specific light map) then parent that to a tiny invisible block that will be the door.

No, this will not work but the first guess may work but anyway it's not the good way.
You must use a modeling software and make a mdl, if you don't want to learn a new software you can use propper instead.

[smashballs]

Maybe I could just make the door a func_physbox (I don't know if it will set a specific light map) then parent that to a tiny invisible block that will be the door.

No, this will not work but the first guess may work but anyway it's not the good way.
You must use a modeling software and make a mdl, if you don't want to learn a new software you can use propper instead.

Thank you very much! I had no idea I could do that! I could never figure out things like blender but Hammer had always been simple for me to make cool objects.

And my PC almost broke during a compile just now! It just turned off and went to a blue screen saying Dual Bios at the top then booted again and now its fine

I guess my PC does that when the processors overload? Hammer loves to cook all the Process power it can... even on a 8 core processor AMD FX-8350 4.00GHz.

That never happened before...

[LordDz]

By looking at that screenshot, I'm guessing none of those pillars are func_detailed?
Anything that isn't a block or a wall meant to block vision: func_detail it.

[smashballs]

By looking at that screenshot, I'm guessing none of those pillars are func_detailed?
Anything that isn't a block or a wall meant to block vision: func_detail it.

I know, I got that already... I am not going to func_detail it till i am ready and I am sure I don't have any modifications on the mind. I am going to make all the spikes one big func_detail because it would be easier (I didn't know about that funky leaf ambient problem before I made them)