- #No scaling option in ati catalyst control center windows 7 movie#
- #No scaling option in ati catalyst control center windows 7 drivers#
- #No scaling option in ati catalyst control center windows 7 update#
- #No scaling option in ati catalyst control center windows 7 driver#
However, when I play a game on my 22" screen I want to use 22" of my screen! Not just 19" or whatever it becomes when all the borders are added. My graphics card is not the best there is, therefore if I want to play a new game I usually run it at a lower resolution that native in order to get a decent fps (my screen interpolates quite good from lower resolutions so the amount of blur it adds is not an issue). But since the resolution isn't really lowered, just simulated (it still sends a 1680x1050 signal to the monitor) I can't switch to 75Hz for that resolution However if I lower the resolution from 1680x1050 to 1280x800 I can set the monitor to 75Hz and movies will run smoothly. The "problem" is that my monitor only shows 60fps when run in its native resolution which will result in a jerky picture.
#No scaling option in ati catalyst control center windows 7 movie#
This means that the movie is played at 25 or 50fps. I live in a country that uses the PAL system for TV and DVDs. Well, I thought so at first as well, but the most major problem is that it doesn't only fix the aspect ratio, it adds black bars on all sides of the display! So if I set a resolution that has the same AR as my native, win7 adds black borders both above, under and on the sides of the picture. Personally, I'd prefer the black bars than having any circle in the game show up as a stretched oval (this especially with people's faces too). That's been one of the more irritating things in my opinion. Random question: Why do you *want* to have the display stretched? Circles will show up as ovals, faces will be disproportionate, etc. I think it's just Windows finally being smart enough to properly display aspect ratios (4:3 as opposed to 16:9, for example.) If your resolution is set to one that is 4:3 with a widescreen monitor, it will display as 4:3 with the black bars on the sides. And still ATI haven't released another driver:
#No scaling option in ati catalyst control center windows 7 driver#
Although the driver release date in device properties is newer than the original (April 28 2009).
#No scaling option in ati catalyst control center windows 7 update#
it didn't work neither! The black bars were still appearing! I don't know what they did update but it sure as _ didn't fix that. after installation, I went to try setting my native 1600 x 1280 in 1024 x 768 and. You can't imagine how happy I was when I saw it that it was downloading! Then. I got here: 1280x800, 75Hz, CVT, no black borders.ĭoes that work for the ATI ? : yesterday I received an update from Microsoft Update of the ATI 2600 HD XT driver. In Timing standard, select one of the options available (GTF, DMT, CVT.) continue testing those options until you get no black borders. Fill your desired resolutions settings and GDI Refresh Rate. Go to Display -> Manage Custom Resolutions 4.
Enter in NVIDIA Control Panel, choose advance settings. I found a solution! 1. Install the lastest NVIDIA driver.
Unless someone else chimes in to actually help you resolve the problem easily enough the only thing I could suggest is to submit the Feedback to MS (via Submit Feedback link on most of your Window headers) and shoot ATi an email as well describing your issue. As an afterthought, I have no problem displaying a native resolution, or stretched on my panels using either nvidia cards' control panel options or selecting display mode on the panel itself, hence why I said you may be barking up a wrong tree.
#No scaling option in ati catalyst control center windows 7 drivers#
Some drivers will always provide native ( or 1:1) display, some always stretch and some will give you a choice. I agree they should but often enough don't and reasons for it may vary not in the least that the driver model or API may have changed and the OEM is not yet fully compliant. Second, just because the driver handles certain tasks in one way on one system does not translate to doing the same in another. As to which party is actually responsible I couldn't say. As such of course this may still be a bug (in your case) to be addressed. Dan, First, keep in mind that the drivers for 7 are for all intents and purposes in beta, so the OS is not the only changing variable.