I was a bit surprised for ARB_imaging and PBO missing (there are pretty common extensions). So I checked in the OpenGL viewer extension database (http://www.realtech-vr.com/glview/) and 9600 is reported as having these extensions.
For Cg shaders, I heard that there are ways to make them running with ATI hardware but I never tried (GLSL is perfect for me).
Radeon 9600 Pro vs. GeForce 2
Well, according to Delphi3d 9600 doesn't support imaging and PBOs.
By the way, could you explain what is imaging (never heard of it), and what are PBOs used for (yes, like VBO for pixel data, but really what does it result in? Offscreen rendering?).
Edit: In the thread about ATi and texture rectangle, they say it isn't accessable from GLSL (indeed 9600 doesn't seem to have ARB_texture_rectangle). Is that really so? No NPOT textures for me? Or could this (or even better real NPOT) be added later in drivers?
[Edited by - Seroja on March 16, 2006 7:45:26 AM]
By the way, could you explain what is imaging (never heard of it), and what are PBOs used for (yes, like VBO for pixel data, but really what does it result in? Offscreen rendering?).
Edit: In the thread about ATi and texture rectangle, they say it isn't accessable from GLSL (indeed 9600 doesn't seem to have ARB_texture_rectangle). Is that really so? No NPOT textures for me? Or could this (or even better real NPOT) be added later in drivers?
[Edited by - Seroja on March 16, 2006 7:45:26 AM]
Quote:Original post by ntsQuote:Original post by oconnellseanm
So stay away from it, unless you can find stable drivers, which ATI is not well known for.
FUD.
Actually, I've had similar problems with my 9800. It's OK most of the time, but if I try to play a newish game or turn up the LOD on my own stuff it locks the computer unless it's VERY well cooled. I bought a better cooler for it, but it still has it's moments unless I have all my fans on full. I assume oconnellseanm speaks from experience, as do I. No FUD here.
I'd still advise Seroja to go with the 9600. They're good cards and the 3 or 4 of my friends who have them haven't had the heat/crash issue at all.
nts, you say you've used 9600s but have you used a 9800 for any period of time?
Quote:Original post by mrbastard
nts, you say you've used 9600s but have you used a 9800 for any period of time?
No I have not extensively used 9800s (not at all with newer games) but I doubt that all of them overheat and lock up, otherwise I suspect that hardware sites would be all over it. There are also a few different reasons a card would overheat, including bad case ventilation.
Just out of interest what temperatures are you getting for it? I think up to 60 (under load) for that generation would be fine.
I was calling FUD on his comment on the stable drivers and not his 9800 overheating. I have not had driver trouble with ATi cards since the 9xxx series, the 7xxx ones (at the time) did have some problems though.
In French we have a good proverb: "The grass always looks more green on the other side of the fence".
I develop daily with a varied set of ATI and NVidia cards. Some have advantages/drawbacks, of course, but in the end i haven't noticed a higher amount of problems on ATI vs NVidia, and that includes drivers (which are pretty buggy on both sides). Last month, my 7800 GTX had overheating problems. I installed a new fan in the case to help and haven't had any problem since. Should i have blamed NVidia for that ?
Y.
I develop daily with a varied set of ATI and NVidia cards. Some have advantages/drawbacks, of course, but in the end i haven't noticed a higher amount of problems on ATI vs NVidia, and that includes drivers (which are pretty buggy on both sides). Last month, my 7800 GTX had overheating problems. I installed a new fan in the case to help and haven't had any problem since. Should i have blamed NVidia for that ?
Y.
Quote:Original post by nts
There are also a few different reasons a card would overheat, including bad case ventilation.
You're probably right, but it still seems more prone to overheating than most cards. That said, at the time I went for it because the nvidia alternatives had massive loud fans. Maybe I should have gone for the noisey but well cooled option.
Quote:Original post by nts
Just out of interest what temperatures are you getting for it?
I have no idea. I don't think it has a heat sensor of it's own (though I vaguely remember that another 9800 variant does) and I've no thermometer to test it with. As Ysaneya implies, it may not be the 9800 that locks the PC, but the heat it generates causes something else (probably CPU) to overheat.
Quote:Original post by nts
I was calling FUD on his comment on the stable drivers and not his 9800 overheating.
Fair enough. I haven't had any particularly bad experiences with ATI drivers in the last few years. They're not great, but I haven't used a recent nvidia card/driver to compare them to.
I have a Radeon 9600 and have had absolutely zero problems with it. It performs as expected. It's becoming a little to slow for my tastes, but other than that it's a winner.
I had a radeon 7000 something in the past and I do remember those drivers being a pain to install, but that was at least three years ago.
I had a radeon 7000 something in the past and I do remember those drivers being a pain to install, but that was at least three years ago.
About the OpenGL extensions ;
The imaging subset is a set of functionnality for manipulating images (filters, convolution, histogram,...). It has been in the spec for a long time ago (I don't remember when it appeared) and most cards do support it.
As far as I know, PBO are mainly designed for asynchronous pixel data transfer between the CPU and the GPU. Before PBO, you used glReadPixels which needs the driver's render queue to be flushed. When you issue a glReadPixel aimed at a PBO, the driver can postpone the readback until you access the PBO, therefore allowing asynchronous data transfer. I can think of situations where it could prove very usefull but I have never encountered any.
For the time being, I think most applications can avoid needing reading data from the graphic card. In the near future, with the development of GPGPU, transfering data back from the GPU to the CPU will be more needed and this extension could prove very usefull.
Offscreen rendering will typically use EXT_framebuffer_object for rendering and eventually PBO for reading back the datas.
Delphi3D database is not that up to date. You chould check the driver history to be sure.
The imaging subset is a set of functionnality for manipulating images (filters, convolution, histogram,...). It has been in the spec for a long time ago (I don't remember when it appeared) and most cards do support it.
As far as I know, PBO are mainly designed for asynchronous pixel data transfer between the CPU and the GPU. Before PBO, you used glReadPixels which needs the driver's render queue to be flushed. When you issue a glReadPixel aimed at a PBO, the driver can postpone the readback until you access the PBO, therefore allowing asynchronous data transfer. I can think of situations where it could prove very usefull but I have never encountered any.
For the time being, I think most applications can avoid needing reading data from the graphic card. In the near future, with the development of GPGPU, transfering data back from the GPU to the CPU will be more needed and this extension could prove very usefull.
Offscreen rendering will typically use EXT_framebuffer_object for rendering and eventually PBO for reading back the datas.
Delphi3D database is not that up to date. You chould check the driver history to be sure.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement