Anyone else getting total lockups? - by doctormidnight
doctormidnight on 26/2/2005 at 21:34
That's with the HL2/Source editor. Besides, AA is automatically set to application preference when Catalysts are installed, and I highly doubt that T3Ed is running with AA requests to the card.
[NAUC]Chief on 26/2/2005 at 21:42
It has been known that UEd at any rate has had serious problems with ATI cards when AA has been enabled, the most frequent was the lack of being able to select anything/add textures etc. So it could be AA causing some problems.
doctormidnight on 27/2/2005 at 04:18
[QUOTE='[NAUC]Chief']It has been known that UEd at any rate has had serious problems with ATI cards when AA has been enabled, the most frequent was the lack of being able to select anything/add textures etc. So it could be AA causing some problems.Bah, none of this actually worked so I'm removing it to save anyone the trouble of doing it.
Hit Deity on 27/2/2005 at 07:04
Isn't that Cat, from Red Dwarf? So :cool:
Thanks for the info, will try shortly...
Komag on 27/2/2005 at 08:05
Are you saying to change to 2x antialiasing and not "Aplication Preference"? Usually its best to leave things on App Pref. If you're saying change from 4x or 8x down to 2x I guess that's good.
The vsync and truform settings are good, but I prefect mipmap and textures on the highest, as anything less is ATI messing them up to one degree or another.
doctormidnight on 27/2/2005 at 08:23
Mine were all set to application preference, as soon as I set it at 2x, it went away. As you can tell from my other post, I've been using it all night and screwing things up left and right, but at least those are all user error. T3Ed hasn't crashed once yet today.
Komag on 27/2/2005 at 08:57
Call me crazy, but I just can't believe that forcing 2x AA would solve the editor's crashing problem. Do you think it could be something else, and just a coincidence in timing?
doctormidnight on 27/2/2005 at 09:15
Quote Posted by Komag
Call me crazy, but I just can't believe that forcing 2x AA would solve the editor's crashing problem. Do you think it could be something else, and just a coincidence in timing?
No. I came home, sat down, read the thing about AA, made the changes, and started up the editor. Unless of course someone is using glyph and/or voodoo magic on my system, in which case I'm not going to complain.
pl4gu3 on 27/2/2005 at 13:39
I made all the changes and still get crashes :(
I don't see how it can be AA, because it worked fine for me before, with AA application controlled.
I run Catalyst 5.2, maybe reverting to older drivers would help? because after I reboot windows says its a video driver problem
It also seems that if fastwrite is disabled my PC doesn't completely lock up, it just sends me back to windows (640*480, 16 colors, so i still have to reboot)
doctormidnight on 27/2/2005 at 22:06
Quote Posted by pl4gu3
I made all the changes and still get crashes :(
I don't see how it can be AA, because it worked fine for me before, with AA application controlled.
I run Catalyst 5.2, maybe reverting to older drivers would help? because after I reboot windows says its a video driver problem
It also seems that if fastwrite is disabled my PC doesn't completely lock up, it just sends me back to windows (640*480, 16 colors, so i still have to reboot)
I just had another lockup. I'm going to try something else, because I think I may have started a completely new map after making the change. I wonder if it's possible that the problem occurs only when a map is loaded, i.e., one that has been previously worked on. Which is really frustrating because I like the map I had made so far :(
