i was never able to run the hdri realtime demo in dx9 wich looks so nice, on my very own hw configuration. the mainboard is just… no comment. i can run it everywhere else with my card, just not in my own pc… hehe
it always crashed to freeze so it was THE test to the new savetyguard ati built around it, to prevent bluescreens in such cases. and yeah, it worked, reset to desktop, and wanted to mail the report…
then i got a blackscreen. and my pc hasn’t showed up to do any task since then… after a while i reset, and watched into outlook. there was no sent mail… so i’m not sure now if that worked or not.
what i know is, that new savety thingy is not yet perfect…
oh, but, the demo never ran that LONG without crashing the system
else, great job. you cannot blame ati for that ****ty mainboard it works in all other systems…
I also wonder how they are doing the prevent the BSOD? Some kind of trap calling that catches basic errors? Or do they check each and every command before it reaches the GPU (although this would make me think it would be way too slow)
I am mainly curious as to the stability of the drivers. As I have said before, ATI + rage 128 left me with a VERY bad taste in my mouth.
ATi’s a long way from the Rage 128 days. You don’t have to worry about whether or not your card will work. Common problems these days include the odd problem with vertex program generic attributes or the occasional game that exhibits some small visual problem.
In short, you should not feel afraid picking an ATi card on the basis of their drivers.
No glSlang, No version 1.4/1.5, no betatest of ARB uber_buffers ( but the ATI_uber_buffers seems to be there, but i have no constants to try it)
I havent had any real problems with sability before, and i havent tested teh generic attributes yet ( that seems like a good thing)… But why did they waste time on the shader effects, and not on making it with a higher opengl versionnumber?
They had glslang GL2 in some kind of beta version back in 3.6 drivers, remved that but didnt exposed the newer glslang ARB ( ive seen the calls in the driver, i think they just disable it for release), Giving us the oppertunity to test the API even if the extension still is very buggy should be a good thing. They done that before with VBO, and the implementations of that was pretty much fixes when the drivers that exposed the exstension came out. More of things like that.
Originally posted by DopeFish:
[b]Hmm not working via wglGetProcAddress?
The extension string is displayed here, and the glslang samples Ive got run… and Im using Cat3.8[/b]
Me too, and I don’t have any new exposed extensions. Maybe it’s because I’m on R300 (9500Pro), and you are on R350 (9800)?
Just to get this on the record, my GL version is 1.3.3966. The reports should start showing up on Delphi3D any day now.