- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
please.
When Intel will be released drivers for GMA X3000 (HW T&L and vertex shader 2.0 or 3.0)?
in February?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Two things would be my guess.
1. Lots of pages to update, including the knowledgebase for each chipset, etc.
2. By putting them on individual motherboard sites first, they have a slower uptake of the drivers, so if there is a showstopper it affects fewer people before they find out about it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes. Intel has "unified" drivers which work on everything from 945G onward.
The only reason these drivers would not work is if your specific laptop vendor has made them not work (with the intention of providing their own, modified driver).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you tried forcing software TnL? By default the drivers are currently using HW TnL, and in some cases the way the software is written makes itmore efficient to run in SW with a powerful CPU than use the chipset HW.
To enable SW TnL for a specific game, open the registry, do a search for
_3DMark06.exe
In that same area, create a new DWORD entry: "_[name of executable for the game]"
Set it to 1 for SW TnL. Swap it back to 0 for HW TnL.
Note that there are like a billion subdirectories (okay more like 12) which contain _3DMark06.exe and you'll have to create the same new entry in each one, just to be sure.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
*edit* Also, i noticed that the games that had graphical texture problems in 15.4.4 still have them when forcing software mode under 15.7. Will the devs be doing anywork on the software mode compatibility in the future?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
XP:
Vista32:
Vista64:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This happens pretty much all the time, or used to. There's nothing to it really other than a proliferation delay. The folks who maintain the website are not the same ones who released the drivers and perhaps the message only went out (so far) to the motherboard guys.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Intel is nowhere near the "stable" level of the drivers yet. They still need a lot more effort.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Put it this way: 14.32.2 does not fix the "Default resolution problem". They're not holding up 14.32 to introduce that one. And my source has no 15.7.x yet (if there's one on the roadmap, it's not yet released internally).
If there were a problem with 14.32 and 15.7 which made these guys think they needed to stop distributing them, they'd yank them from the motherboard sites as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You've got no argument from me; something as obvious as the "default to 800x600" bug should have been found-- if not by Intel's validation labs, certainly by the motherboard and PC vendors who had the driver for XY weeks to evaluate before it went Production Version.
I've got no answer for the rest of your queries. I don't know if the driver team follows this Forum (closely or otherwise), but I suspect they don't want to deal with the venom. In a way I can sympathize: it's easy for me to sit here and chat back and forth with you guys: it's just my employerand not my particular work being criticized. It stings for me, but not as much.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
archibael:Put it this way: 14.32.2 does not fix the "Default resolution problem". They're not holding up 14.32 to introduce that one. And my source has no 15.7.x yet (if there's one on the roadmap, it's not yet released internally).
If there were a problem with 14.32 and 15.7 which made these guys think they needed to stop distributing them, they'd yank them from the motherboard sites as well.
I don't have that "Default Resolution" problem with XP Service Pack 2 and 14.32 drivers. I think the reason they didn't figure out the problem is because it might be just an intermittent problem-it doesn't appear with all computers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
FWIW, I've had confirmation that the issueI reported (scaling at native resolution) is being investigated, and will be part of a new driver at some stage.
I would think that the 800x600 problem would be considered a higher priority since there's a simple workaround for my issue, but it could well be that they just haven't been able to replicate thethatissue yet.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Duplicate Post
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
archibael:Put it this way: 14.32.2 does not fix the "Default resolution problem". They're not holding up 14.32 to introduce that one. And my source has no 15.7.x yet (if there's one on the roadmap, it's not yet released internally).
If there were a problem with 14.32 and 15.7 which made these guys think they needed to stop distributing them, they'd yank them from the motherboard sites as well.
Looks like we were both right, DavidC1
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page