It's that damn Builder Brush causing my crashes! (Testers needed to verify)

SubJeff on 4/3/2005 at 00:28

Are you causing brush intersections? I had a crash once when this happened - 2 addition brushes overlapping.

Gestalt on 4/3/2005 at 03:05

The drivers (Catalyst 5.1) for my Radeon 9600 are screwing up when I subtract an area from above a previously-subtracted area. I'm guessing this is mostly an ATI problem?

Bumbleson on 5/3/2005 at 08:43

Quote Posted by Subjective Effect

Are you causing brush intersections? I had a crash once when this happened - 2 addition brushes overlapping.

I didn't take special care of this (I don't even know yet why intersections should be a problem - the lockups have taken much more of my time than the actual study of the editor), but I think not. I made a simple cube, subtracted it, moved the BB elsewhere (away from the first), subtracted again - CRASH.
After reading Hit Deity's solution I tried that, but as soon as I brought the geometry back into view - CRASH. I will try again and avoid intersections, but I doubt that will help. It seems to be an ATI problem.
Why am I always buying the wrong graphics card? :( (Answer: They are all bad one way or another)

Hit Deity on 5/3/2005 at 14:54

Have you tried Build All after placing one of those? And/or the wireframe mode, and maybe turning off/on the ION button to see if one mode works for you?

Bumbleson on 5/3/2005 at 19:00

Build all seemed to help a bit but I can't / don't want to build all after every single brush and if I forget it there will come a time when it'll crash again, most probably when I forgot to save something... :(
I'll try wireframe next, but I'm quite unhappy with all of these solutions, knowing that it's probably a video driver problem. We don't know whether it'll happen with wireframe as well, maye when the geometry has become complex enough. I'd prefer to know what's the cause and how to avoid the problem for good. :erg:

This thing starts to remind me of Dromed more and more. Or maybe I'm just in a bad mood today :nono:

Mandrake on 5/3/2005 at 21:59

Quote Posted by Bumbleson

Maybe the designers using the Editor only used Nvidia cards, and therefore never spotted the bug ? I havn't seen anyone (including me) with a Nvidia card experience this problem...

(Although I've found other ways to crash the editor :cheeky: )

scumble on 6/3/2005 at 00:54

Quote Posted by Bumbleson

It happens to me too and I use a Radeon 9800 Pro with Catalyst 4.12.

It might be worth just upgrading your drivers. I'm sure I have the 5.2 drivers and it's perfectly fine working with brushes (Sapphire 9000 Pro)

jay pettitt on 6/3/2005 at 01:24

Just in case word hasn't got about yet. There is a simple work around:

Quote Posted by Durinda D'Bry

Only one pretty simple solution I have for now: when working with brushes I switch preview window to mode in which only wireframe is shown. Then I do brush operations, do geometry build, select some "textured" mode for peview and perform texturing operations etc. This works without any problems.

belboz on 6/3/2005 at 04:39

I would suggest you increase the size of your virtual memory, I use 3 gigabytes, and I haven't had a crash.

Bumbleson on 6/3/2005 at 05:48

Don't get me wrong, I appreciate every possible solution, but isn't that just guesswork? Did you have crashes before raising your virtual memory to 3 GB? Besides, I don't have that much space available (yes, I know, I need a bigger hard disk ;) ). I know, we're all only guessing here, but we should narrow down the things that actually improved editor stability for somebody.