Doomulation
?????????????????????????
Ok... now for something intresting. This little proggie I made will check the capabilities of your gfx card. It might be intresting to see what everyones' cards support. Note, however, that not even I know not what all these functions are used for :whistling but some I know. The more supported, the better.
I can also say that unless your card has hardware vertex processing and pure hardware vertex support, it's crap. Because, mainly, this will give 100% speed boost when I tried (*cough* intel crap *cough*).
Anyway, test it out. This will be intresting.
EDIT 04-05-10 (YY-MM-DD):
Attached version 1.1. Changes:
- Rewrote pixel and vertex-shader version lookup code. It should now hopefully find the correct version. As to before, it now extracts the data from the structure instead of trying to test if the version is correct. If oddities still appear, then it's a d3d or driver problem.
- The least fully supported dx version should now be filled in I hope since it relies on information by which pixel shader version you have.
- Tried to implemt tooltips but failed horribly cry: Damn ms for making static text so lacking! )
- Looked up the vertex tweening and w-buffer support tests. And found that they are correctly written in the test. If the information is incorrect, then I'm afraid that it's either d3d or your drivers which is messing with you.
- Changed compiled filename.
I can also say that unless your card has hardware vertex processing and pure hardware vertex support, it's crap. Because, mainly, this will give 100% speed boost when I tried (*cough* intel crap *cough*).
Anyway, test it out. This will be intresting.
EDIT 04-05-10 (YY-MM-DD):
Attached version 1.1. Changes:
- Rewrote pixel and vertex-shader version lookup code. It should now hopefully find the correct version. As to before, it now extracts the data from the structure instead of trying to test if the version is correct. If oddities still appear, then it's a d3d or driver problem.
- The least fully supported dx version should now be filled in I hope since it relies on information by which pixel shader version you have.
- Tried to implemt tooltips but failed horribly cry: Damn ms for making static text so lacking! )
- Looked up the vertex tweening and w-buffer support tests. And found that they are correctly written in the test. If the information is incorrect, then I'm afraid that it's either d3d or your drivers which is messing with you.
- Changed compiled filename.
Last edited: