Disappearing objects on GTKRadiant 1.5.0

[Dessicated corpse]

Why is this happening?

[^misantropia^]

Solar flares, probably. Or filters.

[dONKEY]

Depends exactly what you mean.
Could be you have triggered some of the filters, could be your install is borked, could be a video card issue.
All depends exactly what you mean.

[Noruen]

Dissapearing OBJECTS (what do you mena "objects"?) in editor, or BRUSHES in editor? Or brushes after compilation in game? Or items after compilation in game?

[Dessicated corpse]

When I use GTKRadiant 1.5 some objects disappear, it's not in game. And I don't even know that there were filters that made objects disappear. These are the objects that keep disappearing.

[Noruen]

But what do you mean "objects"? Models? Or what?

And only SOME, or ALL these objects disappear?

[Eraser]

Under the "view" menu (if I remember correctly) there are a few options to show/hide specific kinds of entities or brushes (such as detail and/or structural brushes). Maybe you've hidden detail brushes and (accidently) made a brush detail?

[corsair]

looks like the patch mesh you're showing isn't disapearing at all; it's just not subdivided/smoothened as you'd expect. It's only in the editor that you'll find that small patch meshes will subdivice so sparesely they wont look curved at all. It should look ok in-game.

If you're refering to something else; I wonder how you would go about showing - something which is missing - in a screenshot.

[Dessicated corpse]

It can't be an option anyway, because when I compile, the objects that disappeared in GTKRadiant 1.5 aren't in the map. And if you look at the picture, you'll see the object I mean. And here's the map, http://www.megaupload.com/?d=DRDJMGC0 and here's the bsp, http://www.megaupload.com/?d=BTGG7ET4.

[Eraser]

Oh, your comment about "it's not in game" was a bit ambiguous between whether or not the object disappeared in-game or whether the disappearing didn't happen in-game. I think most people assumed the latter.

So just to be clear, these brushes disappear in GtkRadiant and if you compile the map they're not visible in the game itself either?

If it's not appearing in game, then it can't be one of the view options of Radiant. What sort of brushes are disappearing? Are they curves? Are they plain brushes? Are they brushes cut up in strange ways? Is the compiler giving any warnings or errors? Do you have any idea when brushes disappear, or does it seem completely random?

[Dessicated corpse]

When I open up GTKRadiant 1.5, the objects that are in this image disappear (the objects I mean by are marked with a red square), but when I open the map in a different version of GTKRadiant, it shows the objects. But it can't be an option in GTKRadiant 1.5, the objects actually get deleted when I open up the program, so if I compile it after saving the map, the objects won't show in game. It doesn't really have anything to do with the game or the compiler.

[cityy]

That might be related to 1.5's vertex editing system. Sometimes when I work on terrain brushes that show up in gtkr1.4 don't show up in 1.5. You should just redo these brushes and watch out for odd vertex constructions.

Edit: Are we even talking about brushes or are your disappearing objects patches?

[Noruen]

I'm probably totally blind, but I didn't see any objects in that red square instead of some brush. So, that corner-brush in red square is disappearing?

[dONKEY]

Cityy is correct. 1.5 automatically cleans your brushwork. If it finds 'bad' brushes it deletes them. You need to take care how you construct/edit each brush. Older versions of the editor allowed you to make bad brushes, sometimes even by accident. 1.5 won't allow this to happen either. It is a good idea if u use both editors to save back up files.

[Dessicated corpse]

It doesn't delete the brush, it deletes the whole object.

[roughrider]

It doesn't delete the brush, it deletes the whole object.

Do wha?!?

The whole thing, IIRC, means the brush got deleted. Can't be any simpler than that I would imagine.

[dONKEY]

What u mean be whole object?
A group of brushes?
An entity?

[neoplan]

If you have very big brushsizes in your map (like several thousand units) it is also possible that gtk removes brushes/patches from the mapfile.

[Dessicated corpse]

That's just stupid, why would it automatically remove a brush that's bad? Why won't it just have some notifying message instead of the program deleting your brushes without your permission?

[obsidian]

Instead of making everyone guess what the problem is, why don't you just take the time to actually describe the problem in some detail so we all know exactly what you are talking about. It's impossible to help you unless you make yourself clear in terms of:

1) What the problem is and what you need help with.
2) What exactly did you do to create the problem.
3) What have you already tried to fix the problem.

Normal people would just do a few experiments to see for themselves if they can fix the problem. Maybe try deleting and recreating the brushes (if you are even talking about brushes, or patches or a group - I'm not even clear on what is disappearing).

Also, have you actually checked your filters? You said you didn't even know there were filters, do you know where to find them now? You haven't confirmed whether or not you made sure they were all toggled off. Letting us know whether you've checked those is critical, but you left out that kind of information.

[Dessicated corpse]

Hahahaha, I already showed you the image. You're just being assholes and you're pretending that you don't know what I mean in the image. I've already said so many times that the thing I mean is in the red fucking square, dickheads.

[cityy]

[Eraser]

Oh boy.
That's all I'll say.
Oh.... boy....

[ShadoW_86]

Very nice. I can already see how eagerly everybody will help you. Normally I never take voice in such stupid conversations. In this case, I think you deserved a ban.

[obsidian]

I think you need to calm down.

How do you expect us to tell if it's a brush, patch mesh or entity from your image? We tried asking you but you seem to gloss over our questions.