Hey everybody,
my GTK just fucked up my map I guess, look at this:
What basically happened was that GTK started letting brushes disappear when I clipped them, and then started to duplicate the whole func_rotating for no reason… that s when I deleted all its brushes and safed the map, but its seems one of them survived and became a giant 
I can’t find it in the .map so how do I get rid of it?
Its rotating at the same speed as the radar btw.
Another pic:
While the “brush” goes through buildings, terrain and clip without problems, it can get stuck on players. Nevertheless the real radar keeps turning.
The “brush” can also push players off the roof.
What s strange too, is when I completely delete the little radar, the “brush” stays in the map after a new compile :???:
You could open your map in notepad and search for func_rotating and delete those brushes with that are func_rotating and have that texture. Just save a backup of your map first, then you could also probaly export your radar to a seperate map file and then reimport into the fixed map.
Check your filters. Maybe you filtered translucent(Alt+4), clip(Alt+7) or both types of brushes. That might be the reason that you can’t see the brush in the editor.
If you can finally see the brush in Radiant, select the brush with Alt+Strg+LeftMouseClick to be sure you selected the whole entity and delete it.
Good luck!
@ thegnat: will try that to learn that way
already solved the prob by:
now I need to see what happens when I put the real radar into that map again 
I have something similar happening all the time.
I’m adding brushes here and there and when I need to select some brushes, say for texturing, I notice that if I shift-click twice the red selection becomes darker and then I know I have a duplicate brush there and delete it.
The point is that I don’t duplicate these brushes myself.
And unfourtantely, the brush cleaner doesn’t recognize these brushes either.
@ thegnat: I didn’t have anything filtered in my radiant apart from models…
I think this is the problem, I found it in the prefab of the small radar:
// entity 1
{
"classname" "func_rotating"
"spawnflags" "1"
"speed" "50"
// brush 0
{
( 388 -3654 1540 ) ( 388 -3654 1596 ) ( 420 -3658 1596 ) common/clipweap_metal 0 56 0 0.500000 0.500000 0 5 0
( 388 -3650 1596 ) ( 388 -3650 1540 ) ( 420 -3654 1540 ) alpha/fence_m01 0 112 0 0.250000 0.250000 0 256 0
( 460 -3656 1512 ) ( 348 -3656 1512 ) ( 348 -3660 1512 ) common/clipweap_metal 0 -36 0 0.500000 0.500000 0 5 0
( 388 -3652 1624 ) ( 388 -3652 1624 ) ( 420 -3656 1624 ) common/clipweap_metal 0 -36 0 0.500000 0.500000 0 5 0
( 420 -3654 1540 ) ( 420 -3662 1540 ) ( 420 -3654 1596 ) common/clipweap_metal 36 56 0 0.500000 0.500000 0 5 0
( 388 -3652 1624 ) ( 388 -3652 1624 ) ( 388 -3652 1512 ) common/clipweap_metal 36 56 0 0.500000 0.500000 0 5 0
}
}
It loads with the prefab of the radar into the map. Then I get the giant rotating brush again. When I ctrl+alt-select the radar and delete it, this entity stays in the map. Deleting this entity in the .map-file when opened in the editor makes it disappear though.
Still strange.
Anyone curious enough feel free to test it out in his own map though :bump:
Have you tried deleting it from the text file? i.e. if you opened it up in notepad?
Also, you could change the texture from common/clipweap_metal to alpha/fence_m01. This will allow you to see it easier in the editor as the clipweap is slightly translucent. Also, if the brush is huge, then if you are inside it in Radiant, then you might not be able to see it to delete it.
Also, if you look at each of the lines of plane definition, the fourth and the sixth (last) planes are corrupted. They need three points to define them as planes, but two of their points are the same so cannot define a plane. You could alter these lines to give you three points in each and hopefully this will let you see it in Radiant. You could try something like:
// entity 1
{
"classname" "func_rotating"
"spawnflags" "1"
"speed" "50"
// brush 0
{
( 388 -3654 1540 ) ( 388 -3654 1596 ) ( 420 -3658 1596 ) alpha/fence_m01 0 56 0 0.500000 0.500000 0 5 0
( 388 -3650 1596 ) ( 388 -3650 1540 ) ( 420 -3654 1540 ) alpha/fence_m01 0 112 0 0.250000 0.250000 0 256 0
( 460 -3656 1512 ) ( 348 -3656 1512 ) ( 348 -3660 1512 ) alpha/fence_m01 0 -36 0 0.500000 0.500000 0 5 0
( 388 -3652 1624 ) ( 388 -3652 1623 ) ( 420 -3656 1624 ) alpha/fence_m01 0 -36 0 0.500000 0.500000 0 5 0
( 420 -3654 1540 ) ( 420 -3662 1540 ) ( 420 -3654 1596 ) alpha/fence_m01 36 56 0 0.500000 0.500000 0 5 0
( 388 -3652 1624 ) ( 388 -3652 1625 ) ( 388 -3652 1512 ) alpha/fence_m01 36 56 0 0.500000 0.500000 0 5 0
}
}
That should hopefully be ok, I’ve just altered the two planes by a fraction of a degree so shouldn’t have any unexpected intersecting planes making two prisms…anyway… probably just easier to delete them in notepad.
Orange, I’m glad to some extent that the brush cleaner doesn’t recognise them as there are some circumstances when I’d prefer to have two identically shaped brushes overlaying each other. The duplicate brushes that you are talking about probably wouldn’t be caused by you accidentally pressing the spacebar as the duplicate would be offset from the other one. However, if you do use the undo process, then sometimes this will create a duplicate brush, I’ve noticed it does it a lot when you use the GTKGensurf plugin and you’re not all too happy with the terrain it has created for you.
erm sorry Tickles… the prob s been solved already. As I wrote, I deleted this entity in the .map file when I opened it with a text-editor. Thx anyway.
Changing the texture won’t help at all because the brush simply didn’t show up in the radiant, even when I made a huge select inside over the whole area.
Oops, sorry, when you said “Still strange”, I assumed that it was still there but didn’t bother you as much. Maybe I shouldn’t have scanned the post 
Well, glad to hear that it’s sorted and deleted from the text editor 
Have fun.