Radeons and D3D8
Author
Hi folks!
I recently implemented my own little shader language with several codepaths for the nvidia chipsets. Now i wanted to implement further paths for ATIs radeon series, especially the 8500. The only problem is that i can''t find the D3D8 Vendor and chipset id. NVidia posted these on their web page, ATI did not.
Can anybody give me these hex-codes especially for ATI Radeon8500.
Many thanks in advance and
Happy coding
Incommunicado
It''s probably better to check the caps of the card and write a separate code path for each relevant area you wish to implement. Why? Well you write your code which works perfectly on GF1,2,3,4 and ATI Radeon 7500/8500/9000 and everything is perfect. BUT THEN Nvidia releases GF5. Suddenly your code doesnt recognize the card and has to default to a "safe" mode and all the lovely features are ignored. BAD.
Neil
WHATCHA GONNA DO WHEN THE LARGEST ARMS IN THE WORLD RUN WILD ON YOU?!?!
Neil
WHATCHA GONNA DO WHEN THE LARGEST ARMS IN THE WORLD RUN WILD ON YOU?!?!
Did you try looking at the ATI developer site? This part looks promising. Then again, that was probably the first place you checked, right?
Author
Hi again.
First of all thanks for the replies.
I do not have a Radeon at home so i cannot check the id at home, and i do not know someone with a card of that type either. ATIs developer site does not seem to offer much info and since i only got a crappy 33.6kbit modem i cannot download the larger demos and sources they offer.
To Neil:
Actually my own Highlevel shader language allows to code paths for various cards which might need various rendering passes. If you hardcode paths for several caps then your code will grow immensely. I know what im talking about since i tried this one out. I am also aware that futurecards will need support therefore my engine checks upon initialization the caps of any UNKNOWN card and tries to find the best next compatible card that is supported natively. To be more precise. If NV puts out their new NV30 it will run the most advanced pass it can find in the HL-shadercode.
For example:
GF4Ti can run GF4Ti, GF3, GF2, DEFAULT codepath
Radeon9700 can run Radeon8500, GF4Ti, GF2, DEFAULT codepath
etc.
Happy coding
Incommunicado
First of all thanks for the replies.
I do not have a Radeon at home so i cannot check the id at home, and i do not know someone with a card of that type either. ATIs developer site does not seem to offer much info and since i only got a crappy 33.6kbit modem i cannot download the larger demos and sources they offer.
To Neil:
Actually my own Highlevel shader language allows to code paths for various cards which might need various rendering passes. If you hardcode paths for several caps then your code will grow immensely. I know what im talking about since i tried this one out. I am also aware that futurecards will need support therefore my engine checks upon initialization the caps of any UNKNOWN card and tries to find the best next compatible card that is supported natively. To be more precise. If NV puts out their new NV30 it will run the most advanced pass it can find in the HL-shadercode.
For example:
GF4Ti can run GF4Ti, GF3, GF2, DEFAULT codepath
Radeon9700 can run Radeon8500, GF4Ti, GF2, DEFAULT codepath
etc.
Happy coding
Incommunicado
Have you checked in the DirectX DeviceCaps Database? There''s not much there in the way of ATI products, but it''s a start.
Reported for ATI Radeon 8500DV:
Driver ................ ati2dvag.dll
Description ........... ALL-IN-WONDER RADEON 8500DV
DriverVersion ......... 393229661454
VendorId .............. 0x00001002
DeviceId .............. 0x00004242
SubSysId .............. 0x02aa1002
Revision .............. 0
DeviceIdentifier ...... {D7B71EE2-0102-11CF-7C64-A022A2C2CB35}
WHQLLevel ............. 1
[edited by - don on July 30, 2002 11:26:02 PM]
Driver ................ ati2dvag.dll
Description ........... ALL-IN-WONDER RADEON 8500DV
DriverVersion ......... 393229661454
VendorId .............. 0x00001002
DeviceId .............. 0x00004242
SubSysId .............. 0x02aa1002
Revision .............. 0
DeviceIdentifier ...... {D7B71EE2-0102-11CF-7C64-A022A2C2CB35}
WHQLLevel ............. 1
[edited by - don on July 30, 2002 11:26:02 PM]
Author
Thanks very much for the replies, especially Don!
Now I can at last complete
the low level rendering stuff and put aside with that for a while to concentrate on game code again.
Happy coding
Incommunicado
Now I can at last complete
the low level rendering stuff and put aside with that for a while to concentrate on game code again.Happy coding
Incommunicado
Fair enough. Just thought that it might be one way around your predicament. Hope everything works out OK. Good luck.
Neil
WHATCHA GONNA DO WHEN THE LARGEST ARMS IN THE WORLD RUN WILD ON YOU?!?!
Neil
WHATCHA GONNA DO WHEN THE LARGEST ARMS IN THE WORLD RUN WILD ON YOU?!?!
It would be better to query for capabilities (vertex shader versions etc) than to hard-code device IDs. What happens if a new card comes out that you don''t have access to, and I run your game on it? Even though it may beat the Geforce4/Radeon, your code will run as if it were a a single-texture low-end card?
Different driver versions also expose different capabilities, so if you want it to be accurate, you''d have to build a database of driver versions as well.
Stay Casual,
Ken
Drunken Hyena
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement