Hardware AA and ANSIO problems
by Matt Williamson · in Torque Game Engine · 08/11/2003 (8:21 pm) · 9 replies
Hey guys,
I've been playing around with torque for a little bit now and I just updated to the latest head through cvs.
I searched around on the forums and didnt really find any solution to my problem...
Whenever i have AA and/or ANSIO enabled on my videocard... any 2D gui screen is black except for a small area around my cursor, but in the game all is fine (except for menus and such if im in the terrain editor or something).
If i have AA/ANSIO disabled, all is well in the 2D guis.
I have never had this problem before, it just started with the latest head update....
any ideas as to what might be causing this problem? I know i could aways go back to an older version, but that's no fun! :)
I also think i remember encounting a similar problem to this in T2, not positive tho.
System Specs:
Duron 750
Radeon 9500 Pro w/ Cat 3.5
256MB RAM
Windows 2000 SP3
Thanks in advance for any light that could be shed on this situation :)
I've been playing around with torque for a little bit now and I just updated to the latest head through cvs.
I searched around on the forums and didnt really find any solution to my problem...
Whenever i have AA and/or ANSIO enabled on my videocard... any 2D gui screen is black except for a small area around my cursor, but in the game all is fine (except for menus and such if im in the terrain editor or something).
If i have AA/ANSIO disabled, all is well in the 2D guis.
I have never had this problem before, it just started with the latest head update....
any ideas as to what might be causing this problem? I know i could aways go back to an older version, but that's no fun! :)
I also think i remember encounting a similar problem to this in T2, not positive tho.
System Specs:
Duron 750
Radeon 9500 Pro w/ Cat 3.5
256MB RAM
Windows 2000 SP3
Thanks in advance for any light that could be shed on this situation :)
#2
i also noticed that the loading mission screen shows up, but it flickers a lot like it wants to dissapear
very weird....
Just tried it out in Vice City and i didnt have any problems, so im not thinking it's a hardware issue, but you never know.
08/11/2003 (8:39 pm)
It happens in both OpenGL and DirectXi also noticed that the loading mission screen shows up, but it flickers a lot like it wants to dissapear
very weird....
Just tried it out in Vice City and i didnt have any problems, so im not thinking it's a hardware issue, but you never know.
#3
08/12/2003 (8:56 am)
I'm having the same problem with the 3.5 drivers on my 9800 Pro, so I think its a driver issue.
#4
08/12/2003 (10:27 am)
You have to turn off dirty rect rendering in GuiCanvas to fix this bug, I believe; it's a quirk specific to ATI cards.
#5
I'm going to have a peak in guiCanvas to see if I can disable dirty rect rendering
08/12/2003 (11:04 am)
Thanks Ben! :)I'm going to have a peak in guiCanvas to see if I can disable dirty rect rendering
#6
d
08/12/2003 (8:21 pm)
Ben - since you seem to know the most about the issue, you should really drop a line to devrel@ati.com so they can look into what the root cause of the issue is...d
#7
No way around this.
08/13/2003 (7:49 am)
David: The problem is that with FSAA the back-buffer gets trashed. The way the Torque canvas normally updates is with dirty regions so it basically only draws where the mouse cursor is. With FSAA under ATI cards, it will trash the back buffer, so that doesn't work at all. No way around this.
#8
The GUI is so simple that rendering it at 30 or 60 fps fixed would be trivial and shouldn't affect performance. Guess that's the way around that... ;)
d
08/13/2003 (7:13 pm)
I don't like to rely on the contents of the backbuffer after a swap -- that's dangerous with new technologies and optimizations...The GUI is so simple that rendering it at 30 or 60 fps fixed would be trivial and shouldn't affect performance. Guess that's the way around that... ;)
d
#9
08/13/2003 (9:40 pm)
Yeah, just re-render the whole thing each time. It'll probably give you like...90fps instead of 200. The only thing that this kills, performancewise, is text rendering. Text is a HOG. Just throw in a call to 'resetDirtyRegions()' before it builds an update rect. Or better yet, just kill that call and set the updateRect to the bounds.
Torque Owner Nathan Martin
TRON 2001 Network