Hi,
Here's a list of things off the top of my head that I feel would really help get people begin developing with ati hardware.
1) weekly demo of a opengl and a directx trick - src code. From the community with a prize every once in a while. It doesn't have to be h/w schwag. A $10.00 t-shirt will do. People want to be helpers.
2) Write a book on shaders and extensions. There's one coming out explaining Cg. A few are available on your site, but they're demo's without a label saying what extensions are being used.
3) every extension that is offered in ogl needs a demo on how to use it. Don't make us hunt and peck for scraps of code.
4) Create an SDK, single download bonanza of all the tools you think you need to dev for ati.
5) Give us rendering plugings for all the major rendering tools.
6) Free Textures and models.
7) Rip off any other ideas from nvidia's site. You're taking knowledge not trade secrets so it's alright. (i don't mean code of course, just web site layout and general topics)
8) The community will help you and you don't have to give prizes to do it. I bet if you offered http space, that would be enough to get a sizeable dev site going.
9) case and point, noobies use ogl to dev on because the user base is there. Some of course use dx, but for beginners an important thing is how much info is out there. Almost nothing for dx. If you extrapolate this to ati and nvidia. People will consider nvidia slightly easier to dev for h/w as their dev site is extensive.
Elminate the struggle and you'll gain the support.
10) get a co-op student to do this for ya. It'll cost 10$ over a summer but think of the returns.
b.
Here's a list of things off the top of my head that I feel would really help get people begin developing with ati hardware.
1) weekly demo of a opengl and a directx trick - src code. From the community with a prize every once in a while. It doesn't have to be h/w schwag. A $10.00 t-shirt will do. People want to be helpers.
2) Write a book on shaders and extensions. There's one coming out explaining Cg. A few are available on your site, but they're demo's without a label saying what extensions are being used.
3) every extension that is offered in ogl needs a demo on how to use it. Don't make us hunt and peck for scraps of code.
4) Create an SDK, single download bonanza of all the tools you think you need to dev for ati.
5) Give us rendering plugings for all the major rendering tools.
6) Free Textures and models.
7) Rip off any other ideas from nvidia's site. You're taking knowledge not trade secrets so it's alright. (i don't mean code of course, just web site layout and general topics)
8) The community will help you and you don't have to give prizes to do it. I bet if you offered http space, that would be enough to get a sizeable dev site going.
9) case and point, noobies use ogl to dev on because the user base is there. Some of course use dx, but for beginners an important thing is how much info is out there. Almost nothing for dx. If you extrapolate this to ati and nvidia. People will consider nvidia slightly easier to dev for h/w as their dev site is extensive.
Elminate the struggle and you'll gain the support.
10) get a co-op student to do this for ya. It'll cost 10$ over a summer but think of the returns.
b.
