weird face selection problem

(GRouZER) #1

When i select a brush face on some brushes this problem occurs.
And it’s just one brush!

(MindLink) #2

Seems like you got a duplicate brush at that place. Just select the whole brush, and when the same error occurs delete it with backspace, that should leave you with the second one. Just take care not to select both brushes (that happened when the selection is deep red instead of flashing red/original color like in your picture)

(GRouZER) #3
(MindLink) #4

Oops didn’t see that, sorry… Just had a look at the pic :banghead: :smiley:
Ran the cleanup tools?
Strange thing, really looks like a duplicate plane there.

(chavo_one) #5

If you are getting z-fighting like that in radiant, then it is NOT just one brush. You have duplicated that brush by accident, so now you need to delete the extra copies.

(GRouZER) #6

I am 100% sure that that brush is ONE brush.

did the brush cleanup but no luck :angry:

(Drakir) #7

Brush cleanup wont delete that problem of your. What u simply must do is select the brush and just hit “Backspace”.

(BXpress) #8

just make this wall new… wouldnt be that much work:D

(Loffy) #9

Hi!
I’ve seen that too in my mapping project and I agree with the mappers above: I can be duplicate brushes. Shift + left click and hit Backspace. If it totally disapears, then you know I we were wrong and it was a single brush. Then just hit Alt + Z to undo that last action. But I think it will just delete the obsolete brush.
// Loffy

(redfella) #10

There was a bug in one version of radiant that sometimes created a duplicate brush right after hitting “undo”. Most notably it occured when and only when someone was undoing a texture. This may or may not be what you experienced and where just not aware of it.

(GRouZER) #11

I’s not a duplicate brush.
I’ve checked other brushes and there are more brushes screwed up :angry: , and when i make a new brush is has the same screwedup face.

Shift + left click and hit Backspace

done that multiple times, nothing happens.

I do get this line several times in the log when i run the brush cleanup tool:
“Possible Phantom Brush Found, will not rebuild”
edit: this seems to be some brushes which were selected when running the brush cleanup tool, and have nothing to do with the z-fighting problem.

I think that could be it, i also had a problem with q3radiant v202 when you hit ctrl+z something weird happened, something with textures or something.

The current version of radiant i have is 1.3.12, i could install 1.3.11 but that version has a bug that causes the terrain to disapper sometimes for some reason, and have to reinstall radiant to get it fixed, that’s why i installed 1.3.12 :banghead:

(Moonkey) #12

You could try copying the whole thing into a new map (hit i to invert select everything). Hopefully the weird stuff will get left behind.

(GRouZER) #13

Doen’t work unfortunately :banghead:

(rgoer) #14

Sorry to beat this to death, but when you say “nothing happens” do you mean that: the brush completely disappeared, as if it were a single brush and you deleted it; or: you hit backspace and the brush stayed visible? If it’s the latter, then you do, in fact, have a duplicate brush.

(GRouZER) #15

When i do the key combo, nothing changes, so there are still two faces overlapping each other.
I have done the key combo several times but still two overlapping faces.

(rgoer) #16

Ah, you are simply selecting the face.

Select the entire brush. Then hit backspace. Then post back.

(GRouZER) #17

…the brush disappears.

And another oddity is when i have selected a face and look in the length of the brush there is z-fighting, and then turn 180° there is no z-fighting ,and then when turning 180° back to the first view it’s z-fighting again :???:, .

(G0-Gerbil) #18

I took a look at the source file and there is indeed no duplicate brush.
Having said that, it didn’t show the problem on my setup so…

He’s done the obvious thing like installed new drivers etc, reinstalled radiant.

I’d say it’s some weird graphics card glitch personally, but that doesn’t really help him fix it sadly :frowning:

(GRouZER) #19

Whoooohooo! i think i have solved it, it’s the motorcycle model that caused it :???: .
Unfortunately it’s that model it’s perfect for my map :frowning: .