I’ve a simple feature request for next bugfix/maintenance release of Caps Viewer, if applicable & appropriate can we save a test benchmark score (those figuers showing up on top left of rendering window) in a basic plain text file just for record, later reference and for multi-driver corss-version performance/feature comparison sake? Would make life much better.Intel OBL Distribution (Commercial Use) License This LIMITED DISTRIBUTION LICENSE AGREEMENT (“Agreement”) is a contract between You and Intel Corporation and its affiliates (“Intel”). Driver v2696 (beta/dev/cookin.), besides its quirks (low WEI score, NFS-HP2 not working & missing options in CP) is functionally WAY TOO SUPERIOR than v2622 (stable/current). What an extraordinary perfomance increase a well-written piece of driver can produce. Even Simple Mesh test (MSAAx4 On) was chocking to death with 4-5 FPS. Couldn’t believe it was the same HD 2000 chip I tested with 2696. My goodness, that was horrible! Everything running in that 600×600 window went dark, blocky, jagged and abominably 16bit-ish, even with all sorts of different settings in intel CP. I returned back to my old trusted full-featured (no missing 3D options in intel CP) & WEI-compliant (Aero=5.5, 3D=6.1) driver v2622 and got major shocker when ran GL 2.1 Soft Shadow test with MSAAx4. Both v2669 & v2696 acrchives contain OpenCL setup & SDK files. Hope to see fixed caps viewer 1.15.2 soon Among the usuals, 2nd gen, it mentioned “3rd generation Intel(R) Core(TM) processors”. What caught my eye was the top line in both readme & install_readme. Don’t have system ready to test that right now. For its size, around 79MB, I took it for a perfect 32-bit but it came out 64. On brighter note, Quake4 allowed smooth playback for the first time with AAx2 coupled with ultra setting at 16:9.lol, HD2000 felt like HD3000 for a minute there. One game didn’t run far under this particular version of all those I tested NFS HP2… just dark blank. Among some of my test titles, I included few pre-2005 classics just to re-confirm backward-compatibility. WEI remained at 5.5 for Aero, but 3D bumped to 6.0 somehow. Those missing options under 3d custom tab are still missing. MSAAx4 mostly crashed the app, still I managed it with 500×500. FPS was not as bad as I was expecting, ranging 12-20. Not only that, it also ran all the OpenCL tests (CPU-parts). Well you know what, crazy thing happened finally after installing v2669. Getting really curious about your CL info. Real P.I.A., hardly reaching 16-17 FPS, without MSAA x4, of course. Infact all tests are giving 30/+ FPS some hitting 55-60 with MSAAx4, except fury Cube GL2.1 test. Though my test results are far more encouraging compared to these: Moreover, how come your viewer is showing OpenCL on main tab? Mine, same version, doesn’t show it at all. The last driver (again v2622)delivered same 5.5 Aero, but 6.1 3D… and tested rigorously. Tested thoroughly many times with various settings. Performance-wise, WEI is giving 5.5 for Aero, while 3D is 5.9. While a new field is there namely, Application Optimal Mode. My last version (v2622) showed 4 fields Texture Quality, AF, Vertex Processing, VSync. Features are missing in Intel Control Panel, under 3D tab (Custom Settings) in this one. Somethings wrong with these latest versions. Here is the complete list of all OpenGL extensions (GL=115 and WGL=14) exposed for a Sandy Bridge Core i5-2400 with a HD 2000 GPU under Win7 64-bit: Compared to the previous version ( v8.) 13 new OpenGL extensions have been added: is an OpenGL 3.1 driver and exposes 129 extensions. More information about this driver in the release notes. for the 3D module) fixes several game-related bugs and adds new OpenGL extensions.
Intel has published some days ago a new version of its graphics driver for HD Graphics 2000/3000 GPUs (2nd generation Intel Core i3 processor, 2nd generation Intel Core i5 processor, 2nd generation Intel Core i5 vPro processor, 2nd generation Intel Core i7 processor, and 2nd generation Intel Core i7 vPro™ processor).
0 kommentar(er)
