Gma 945 Modded Drivers
Current test version of Chell that supports all the chipsets that Chell 1.7b did. It does not need a separate driver for the GMA 3150 - just download and go! Has a new interface and Installer - please test and give feedback. Remember to use before installing.Note Windows 64 bit users: I am aware the driver didn't install and updated the installer accordingly - please redownload to get the fixed copy. Yeah, I noticed it's still broken. Fixed yet again - please try again Chell supports the GMA 950, GMA 965 (X3000), the GMA 3000, GMA 3100, GMA 3150 and some of the GMA X3100. Hello, i am a user of Intel HD graphics 1000 (i3 Processor with intel hd graphics) and i have downloaded the tools package that you have uploaded, i currently use a driver that i made myself also based as what intellimodder32 did, i used the REG Modder Application and made Left4Dead start in 'Hardware Mode', i then relaunched game in native resolution and started it, i now lag much less as before i used the REG Modder, this app that you guys made are excellent and i want to thank you for that perfect package!
I wanted also that we combine all our Knowledge to make optimal drivers for our intel graphics, so maybe you also can make drivers for other than GMA 950, like for all intel graphics and improve them! If you want to check the driver i made, check out this link for download:, i wanted also to know more about some reg modding files, like the 'addgame' file, it adds a 3D context game to registry without need to modify and reinstall driver, if i am wrong please correct me! Also it would be cool if you put AJAX chat in this forum! Thanks for your work again. One thing I would recommend is to try setting it in 'Software Mode' - that should make the card emulate Vertex shaders on the CPU rather than hardware.
That should give you a more noticable boost. This is also the default setting when you add an exe files using 3DContext from the inf file.Addgame is just a normal reg file that inserts enteries to the same place that the other tools use. Generally, dword:00000000 is hardware mode, dword:00000001 is software mode and dword:00000002 is 'unknown'.With older hardware (like the 9xx series), the Vertex Shader is seriously lacking - since the hardware only provides one and it's lacking features (it's only version 2 with some stuff missing). Using Software mode, it renders Vertex Shaders with the CPU instead while leaving other 3D rendering and Pixel Shaders to the Hardware. A Bonus is that the Vertex Shaders are also of a higher level with better feature support since it's using Version 3 instead of Version 2.
This may have a similiar boost with never cards likes the HD series - you should check it out. Hello, thank you for replyingWell just before that i try the REG Modder application, i have modified the driver inf and added games to 3D Context, but those exe have the symbol @ before them, so i installed driver and check diffrence, i still had lag, but when i use your REG Modder on the game in Hardware mode, i had a boost and i lagged much less! One question is your REG Modder add games with symbol or with @ symbol? Because maybe it is that what it boosted the game, i should put instead of @! Thanks again.EDIT: I discovered something!, as you said i have put a custom addgame with the game name and when i put the symbol @ with value 1, the game doesn't crash, but there is no boost, but when i put the symbol with the same value, it crashes, i think that is the problem with intelli modder driver on windows 8, because people said that on windows 7 it works!
But on windows 8 games crashes, i think that the symbol with value 1 crashes games, but with symbol @ it doesn't, that's why the driver for windows 7 isn't supported on windows 8 because it doesn't recognize the symbols on windows 8, so changing the symbol to @ in the driver should work but less boost, but when use value 0 with it should work with a boost, the same thing than using REG Modder. They all add games with before it.
Nvidia Modded Drivers
It's strange that setting games with set to hardware mode (0) works so well, but I guess it's down to how the chipset were made. It's worth a try if you think it would work. In the inf file you'd have to change the @ to an and make sure it's set as 0 instead me 1 to get the same effect as using a Reg Modder.EDIT: I'll make a guess as to why this is with Windows 8 - It could be that Windows' own DirectX software renderer might be getting in the way. By forcing the driver to use hardware rendering, you end up using DirectX rendered on the HD Graphics chipset rather than the CPU.
This is probably why you notice a boost in performance. Microsoft's Windows Advanced Rasterization Platform (WARP) is pretty new. It's present in Windows 7, but not enabled by default and you could download it for Vista.Intel would have known about it and since it's a better software renderer than the one they provide with the driver, it would make sense that they'd try to use it where it's present. That's probably why it's part of the drivers for Windows 7 with the newer graphic chipsets.
So using that, we'll assume that @ is used to enable the WARP renderer for that game.Since WARP is enabled by default on Windows 8 for most intergated chipsets, this means the @ does absolutely nothing. Now using would enabled Intel's internal software renderer (when set to 1), but since it's older, it would explain why newer games would crash when using it. But by using to set the game to hardware render (when set to 0), you force the system to use the Intel graphical chipset instead of WARP - hence the boost in performance. Compatibility might go out the window for ultra-new games, but that's pretty impressive.This has been an interesting decussion to say the leastEDIT: Maybe try running a 3D Benchmarking program while alternating settings and see if there is any change to the scores. That should give you a good idea of the difference it makes. WARP will probably lose out in frames per second while pure hardware mode should get better frames per second. WARP might win out with sheer rendering ability though.
Going on what we think @ and does, this makes sense.WARP is present in Windows 7, but unlike Windows 8 it's not turned on by default. WARP can render most DirectX 10 and DirectX 11 games without any trouble, while the older software renderer in the Intel driver can only handle most of DirectX 9.0c and some of DirectX 10. Also at best the Intel one only gives us Vertex Shaders up to version 3, where WARP (and the hardware itself) can give us up to version 10.So if @ enables WARP for that game on Windows 7, then newer games should be playable, but maybe a little slow. If we use , then the game will only have a Vertex shader version 3, which will make newer games crash as it doesn't support the newest graphics instructions.
But by disabling software rendering by forcing hardware rendering through , you get Vertex shaders up to version 10 done by the graphics chipset itself. Since almost all new games support that, they would run without problems and since it's being done on the hardware rather than software, it frees up the CPU and gives you a minor boost in speed.Ok, maybe that's a little complicated. But let me summerize: WARP is good, but slower than hardware. It's enabled on Windows 8 by default, but not Windows 7. @ probably turns on WARP for that game on Windows 7. Intel's own software render is old and only supports up to vertex shader version 3 - which is too old for the newest games. So the newest games will crash if it's turned on using.
The HD 1000's hardware pixel and vertex shaders are atleast version 10, so most games should work with them. Using set to 0 forces the use of hardware rendering, which is way faster than WARP. Does that make more sense now? Yes, but still one question, you say that the intel software renderer is too old to run new games that why it crashes, but people say that quantic driver works on Windows 7, that driver have with 1 value on games and they say games doesn't crash, maybe the software renderer driver is only compatible with windows 7? Maybe, but maybe it is not working on windows 7 because maybe the person that said that have tried a games that is not in 3D Context, anyway yea that's clear thank you very much i understand now.
Intel 945 Drivers
Knowing IntelliModder32, that's very likely. I had to add 3D Context myself when I redid their driver.
Gma 945 Modded Driver Windows 7
It was in the inf file mind you, but wasn't used by the device's driver settings at all.Could also be a version mismatch issue - if the Pixel Shader version is high, the game might be assuming that the Vertex Shader is at a similar or higher version. So using would give you Pixel Shaders at version 10 while Vertex Shaders are only at version 3 - the game would be expecting atleast version 10 Vertex Shaders and be sending version 10 instructions - which would make the Software Vertex Shader freak out - and the game will crash.EDIT: Btw feel free to start your own thread for your driver and other related questions.
And I changed the forum's name to reflect that it's more than just GMA that's supported now. It should be capable of whatever resolution the device can support - and maybe a bit further - I can set mine as high as 1920x1080, but it won't work with my monitor. I do note that it seems to force Generic PnP Monitor as the monitor device though. Maybe this has to do with a setting in the original IntelliModder32 driver. I'll have to look. Incidentally, what is your vendor and device ID? I may have made a mistake with the Mobile versions of the gma 950.
You can get it from Screen Resolution- Advanced Settings- Adapter- Properties- Details- Hardware Ids. It will be in the Value box and look something like PCIVEN8086&DEV2772. If it's vendor 8086 and device 27AE then it's probably my goof.