Hello,
Could anybody tell how to use subj from OpenGL? Is it possible at all? The example on Ati site uses D3D 
[This message has been edited by h2 (edited 03-09-2001).]
Apparently, there’s actually no way to use those in OpenGL
As for the pixel shaders and EMBM …
ATI is kinda WEAK in it’s OpenGL support !
RADEON doesn’t support pixel shaders. Three-texture multitexture is available via a combination of extensions.
The ATI_envmap_bumpmap extension exposes EMBM and is already in the drivers. If you’re a registered developer you should already have access to this.
How come then that the “MFC pixel shader” DX8 SDK sample is running with HAL and is running much faster then with the REF rasterizer? Doesn’t that mean that it is rendering the pixels shading stuff in hardware? Or have I misunderstood something?
What driver version do you use Humus? I have the lastest beta they released on their site and MFC pixel shader uses the reference rasterizer.
I don’t think you’re running MFC Pixel Shader on the HAL on RADEON™. Can you look at it in a debugger and see where it’s looking for the pixel shader version supported? RADEON™ should be reporting 0.0.
-Jason
[This message has been edited by JasonM [ATI] (edited 03-10-2001).]
Originally posted by JasonM:
The ATI_envmap_bumpmap extension exposes EMBM and is already in the drivers. If you’re a registered developer you should already have access to this.
[/b]
Can anyone be a registered developer? Its just that when I looked they were asking for contact details for a Marketing representative. I’m just a late night OpenGL hacker who wants to keep up with the DX8 boys.
Yeah. I would like to have access to that driver.
I tried to find it on the web, just in case it would have been leaked 
, but I could not find it.
Originally posted by JasonM [ATI]:
[b]I don’t think you’re running MFC Pixel Shader on the HAL on RADEON™. Can you look at it in a debugger and see where it’s looking for the pixel shader version supported? RADEON™ should be reporting 0.0.
-Jason
It reports 1.0
Look, there’s a registry key called “PixelShaderVersion”. If I set this to “10” this sample runs supposedly with hardware support for PixelShaders version 1.0, if I set it too “0” or remove the key it’ll only run with REF renderer.
I have a screenshot here with it running with HAL if you want more proof:
http://www.geocities.com/SiliconValley/Cable/9070/pixelshader.gif
[This message has been edited by Humus (edited 03-11-2001).]
Why isn’t that in your tweaker Humus?
It is.
Look in advanced settings.
It’s working allright, but if you try and run the NVEffectBrowser, it just crashes if you use hardware device.
So maybe they implemented a chunk of it, or dx8 can actually use “normal” texture and coloring if the shader is simple??
Guilty as charged. We implemented the subset of pixel shaders that translate into legal multitexture combinations on RADEON™ You didn’t say you were tweaking the registry
Unless you hack the registry, we will report 0.0 pixel shaders. The whole “0.5 pixel shader” thing turned into a real hairball, and you can get a lot of the RADEON™ functionality through DX8’s enhancements to SetTextureStageState (stuff like LERP, MAD, TEMP and ARG0), so we decided to focus on other areas.
-Jason
P.S. This isn’t exactly an OpenGL topic so, if you have related questions that don’t belong here, feel free to ping me directly at JasonM@ati.com. And ping devrel@ati.com to enquire about becoming a registered developer.
[This message has been edited by JasonM [ATI] (edited 03-12-2001).]
I’m really happy an ATI guy comes on this forum !
I’m registered dev since a few months now and … i got almost no info except some beta drivers which were already outdated by some illegal (leaked?) distributions.
No OpenGL docs (ATI_VERTEX_STREAMS ???) !
So some questions :
- What are those VERTEX_STREAMS exactly (it is like the DX vertex streams ?)
- Does ATI plan to add more support to OpenGL for the charisma/pixeltapestry features highlighted in the feature lists ? E.g. some kind of register combiners, pixel shaders, etc …
Thanks for enlightening me, Jason !
Oh yes, one GOOD thing : PN_TRIANGLES rock !
PS : Hi Humus, how are you ? 
[This message has been edited by paddy (edited 03-13-2001).]
Hi Paddy! I’m fine, except that ATi just sort of rejected my request of becoming a registered developer … but if you say you didn’t get much out of it, well perhaps I shouldn’t be too unhappy …
paddy,
How did you get ATI_PN_TRIANGLES specs? Through devrel program?
No there’s a released doc on ati’s site.
Let me search for the link …
http://www.ati.com/na/pages/resource_centre/dev_rel/CurvedPNTriangles.pdf
Sorry, but it’s general description of that PN triangles are, it’s not extension specification.
h2. The fonction definitions are in the glAti.h that they give on their website. You can easely figure it out. This extension is awesome!!
Now I would love to have fonction definition and tokens for EMBM.
This is my personnal opinion and message to Jason[ATI], but i think you will all agree.
First of all, at I/O Labs, we work with both ATI and NVidia cards, and have to take advantage of both. I’m registered developper for both manufacturers. Both GF and RadeON are great pieces of hardware.
When you develop software to support an NVidia card, you just have to browse their web site to find plenty of eyecandy demos with source code and tons of papers about how to implement their hardware at the best.
On the ATI site, you can find the ATI development kit, which is not bad but too limited. I’m pretty sure the RadeON is a great card, but we need more precise informations about how to use it’s fantastic capabilities. The specs of the Charisma engine and the Pixel Tapestry are in my opinion as impressive as the GF3 specs, and they are over 8 months old. Most of them are supported in DX8 with 3102 drivers, but ATI must give us some software pieces that really show their practical usage. In OpenGL it’s different, and the main priority is to add some extensions to be able to use those awesome DX8 features in GL too. And i’m not only talking about EMBM. The RadeON pixel pipeline should be capable of some kind of pixel shader (a register combiner equivalent). And where is the priority buffer ?
It’s too bad such a good GFX card lacks of software support. The hardware is there.
I hope my frenchie’s english is not too bad …
My half-a-cent
[This message has been edited by paddy (edited 03-13-2001).]