axeman wrote:You deserve a cookie! That was irritating me, hopefully they will make it easier to set properly in the future.
Shizoku wrote:Hi c0d3h4x0r, I've tried your solution as well as the one initially posted in this topic. Unfortunately when I use the Basic method it greys out "GO" and tells me to use the Advanced settings. When I use the Advanced method as described here, the scaling options are greyed out as well
Shizoku wrote:Finally I can play starcraft and tf2 with the proper widescreen.
Shizoku wrote:Hi c0d3h4x0r, I've tried your solution as well as the one initially posted in this topic. Unfortunately when I use the Basic method it greys out "GO" and tells me to use the Advanced settings. When I use the Advanced method as described here, the scaling options are greyed out as well.
I'm running an ATI Mobility Radeon HD 4330, on a Dell Inspiron 1545.
Welch wrote:Morphine...... lol "CATCHA RIDE..... You can paint it all kind of purty colors to BOOT!" I am going to call you Scooter from now on .
Welch wrote:*PS* I used your link there to post the issue to AMD.... I'd recommend everyone else take the 1 minute to do so also. This thread has been submitted for AMDs reference.
morphine wrote:This fix will not help you in legacy drivers, it only applies to recent Catalyst versions. You should use Mobility Modder and the latest drivers to first get a much updated driver, then second get the scaling working
Welch wrote:I don't believe they have failed at delivering the quarterly updates they promised... they just didn't fix a few of the large issues like this that they should have. They released 9.12 in December of this last year. The next update would be April, but im hoping they will come to their senses and add a quick hotfix for this issue before then, they might not though.
Welch wrote:I stand corrected, i thought we were talking about legacy drivers PERIOD. I'm using a HD2600 Mobility card hence my DX10 Legacy drivers.
Welch wrote:they don't really split their driver support up based on the cards supported DX version.
c0d3h4x0r wrote:I would suggest they rename the "legacy Catalyst" drivers to "Catalyst for DX9 Devices", and leave the major version number as "9.xx"
Then they should rename the "non-legacy Catalyst" drivers to "Catalyst for DX10 Devices" and change the major version number to "10.xx".
Then it would all be much clearer.
Welch wrote:I'm even more mixed up since i've been installing drivers for XP/Vista/Win7 for my Mobility 2600, my girlfriends AGP x1650Pro and then her AGP x3850Pro..... All different series, AGP to confuse it more and different DX versions.
Zoomastigophora wrote:I agree with the name change, but not the versioning. The versioning is based on year and month, which I think is pretty easy to follow.
Zommastigophora wrote:It's just that keeping both the legacy and non-legacy drivers named Catalyst causes undue confusion for everyone, exacerbated by AMDs terrible website organization.
Zommastigophora wrote:Yup, AMD's graphics driver structure is a goddamned mess at this point. AGP users need to use separate AGP hotfix drivers as regular Catalyst drivers don't officially support AGP cards past the HD2600 series. Mobility drivers are non-existent for Vista and later and XP users need to download and run the verification utility, and only if you are using a laptop from one of the supported vendors are you allowed to download a 10-month old driver. On the desktop, driver support has been fragmented between DX9 and DX10+ cards, with DX9 cards starting with X1k series and going back being put on the so-called Legacy drivers. This also means that laptop users with mobility versions of the DX9 cards need to run Mobility Modder on the legacy Catalysts, NOT the regular Catalysts on the AMD GAME site. And then, bizarrely enough, AMD puts their chipset and RAID drivers in the Motherboard/IGP Catalyst section, despite having a separate AMD Chipset Drivers section.
Zommastigophora wrote:What I don't understand is what changed in Windows 7 to suddenly break scaling for both nVidia and ATI (I wonder if Intel is affected). I hope the vendors get this fixed. I'd honestly prefer it if vendors would have a few driver revisions periodically dedicated solely to bug fixes.
c0d3h4x0r wrote:That's very non-obvious; I never realized that was there scheme. If they want it to be clear that's the versioning system, then they ought to change the versioning to "YYYY.MM.DD", e.g. "2009.11.25".
c0d3h4x0r wrote:There ought to be monthly driver releases on a regular schedule, to make sure no bug ever drives customers nuts longer than a month.
To get a Microsoft WHQL certification for a video card or driver, a vendor should have to be contractually obligated to Microsoft to provide driver updates directly to end-users (not indirectly through laptop manufacturers) monthly.
Users browsing this forum: Bing [Bot], Exabot [Bot] and 3 guests