AA doesn't work due to monitor?

[Clorky]

Hello, I've got some graphical issues here, i made two topics, where i describe my problem with anti-aliasing, but now i think i know where the problem is.

I have a monitor (with TV tuner - Philips 221T1SB), native resolution of 1920x1080, but there is an Overscan in Catalyst. It says from left to right '10%' and '0%', if i set it (all the way to the left) on 10%, i get screen with black borders (you know what i mean), but if i set it to 0%, i get a filled monitor. It does make sense, but why the hell is there such an option?

I never had any AA issues before, but now, with this monitor, here they go. I can't find any solution, i have only one lead = overscan, or pretty much anything with the CCC settings.

Yes, i almost forgot. After a bit of trying to configure the monitor with remote, i found there is a PC channel option, few other channels, and then a HDMI option. I have monitor through HDMI, but why i get black screen when i select the PC channel?
That might be another problem.

I tried almost everything. Please guys, give me a hand. I don't want jaggies!

 

[Hitman928]

The overscan has to do with setting your monitor to a non-native ratio. So, if you set your monitor to a 16:10 ratio when it is a 16:9 monitor, you can use overscan (or underscan) to better fit the picture to your screen. Hence, setting it to 0% at 1080p gives you a full picture. This is mostly useful when connecting to an HDTV as some TV's have a weird physical ratio even when they are a "1080p" TV. This shouldn't be causing aliasing effects with how you have it. So, do you get aliasing in games or are you talking about while trying to watch TV?

 

[Clorky]

I got jaggies while playing. I'm using it as monitor...

 

[Hitman928]

Noticeable jaggies while gaming is normal at 1080p. Are you using some form of anti-aliasing?

 

[tweakboy]

Theres no way your gonna lose AA like that.

It has to be something on your end. its free up to 8x CSAA ,,,,,, maybe your not configuring properly in npanel. gl

 

[Clorky]

I have AMD, not nVidia.

SMAA injectors crashes the game, MSAA 4x doesnt work.

 

[Hitman928]

I have AMD, not nVidia.

SMAA injectors crashes the game, MSAA 4x doesnt work.

Ok, what game is having the issue? Some newer games don't support msaa and can't be forced through the control panel. Have you tried enabling morphological aa? It's a post process aa and should work with almost any title.

 

[MTDEW]

Yes, i almost forgot. After a bit of trying to configure the monitor with remote, i found there is a PC channel option, few other channels, and then a HDMI option. I have monitor through HDMI, but why i get black screen when i select the PC channel?
That might be another problem.

I tried almost everything. Please guys, give me a hand. I don't want jaggies!

1: The reason you get a blackscreen when selecting PC Channel/input option is that this setting changes what input/hookup you're using from the pc to the monitor, and you're using an HDMI cable hookup, not the PC/VGA connection.
So there is no issue and nothing wrong here, and YES HDMI gives better image quality than VGA, so you're using the right connection.

2: As mentioned above, when using HDMI / 1080p with Radeon cards , having to adjust overscan to 0% is completely normal. Nothing wrong here either.

3: AA not working has absolutely NOTHING to do with overscan, they are not even remotely related.

4: As Hitman928 keeps asking , you need to state what game and what AA settings you're trying to use.
Its not as simple as just setting AA in the Catalyst Control panel and it just works for all games anymore.

 

[Clorky]

Thanks, that really helped me.

Using any AA doesn't works in any game. For example Far Cry 3. I can't get it to work! In DX11, anything i try, i get terrible jaggies.

 

[Clorky]

Even MLAA doesn't seems to cover the edges... at all...

If i could just run the SMAA Injector, but there is NO ANTI ALIASING using it.

 

[Hitman928]

Any chance to post some pics of what you are seeing? Also a screenshot of your CCC settings would be nice. This is definitely NOT a monitor issue if AA isn't being used. It could be a driver issue as well, I suppose, or some setting somewhere that is stuck which is blocking AA being enabled. Although MLAA should still be enabled as it is entirely seperate from MSAA.

Last resort (outside of entire OS re-install) would be to wipe the comp clean of all AMD drivers, software, and third party apps. Re-install drivers and CCC and re-test. We shouldn't need to go there though if we can figure what is causing it.

 

[MTDEW]

The problem is Far Cry 3 uses Deferred rendering.
Which i'm personally tired of, it sucks on pc's and results in completely unoptimized console ports.

To put it short and to the point, you're never going to get rid of all the jaggies on EVERYTHING in-game.
So it depends what objects/scene you are using to "test" your AA settings as to whether or not you'll be able to see any results.

Here is a LINK that will explain it better.
Just scroll down to the Deferred rendering with multi-sample anti-aliasing (MSAA) part and read it.
Here is a short quote...

Many modern games use what’s called a “deferred rendering” engine, which defers the game’s application of lighting to a second pass of the renderer. This has the advantage of dramatically increasing the amount of lights that can be used in a scene, but it makes high-quality multi-sample anti-aliasing (MSAA) quite difficult to implement, as it cannot perform AA on the lighting.

The deferred engine rose to prominence as a way to make the most of the fixed hardware resources in a modern game console. Generally forfeiting MSAA, and a comparatively limited diversity in game textures, were evidently deemed acceptable casualties in the push for more realistic lighting. Rather than work to implement the visually superior MSAA filter, most developers have come to rely on post-processed AA filters (like FXAA) as a way to get “good enough” anti-aliasing at appreciably high framerates.

Thankfully, Ubisoft and AMD worked very closely to implement MSAA into Far Cry 3’s deferred engine. This approach required a careful analysis of each scene/level in the game, selectively enabling MSAA on sections of the scene (like trees and lighting) that would benefit from the technique, while avoiding MSAA on sections that would slow the game with no visual improvement.

 

[Clorky]

I reinstalled drivers using Driver Sweeper several times. After trying to install, there was everytime an issue while installing any kind of driver. The announcement, that It's completed was in yellow.
After installing 12.8 drivers, it seems to be OK, Far Cry 3 is definitely better looking.

Ok, is there a way to make the SMAA injector work?

 

[Hitman928]

I don't know about SMAA injector as I don't use it, but you'll probably want to use the latest 12.11 betas if you haven't tried those already, they have specific updates for Far Cry 3.

 

[Clorky]

I'll go for them, OK.

But as i said before, they report some kind of error upon installation. I'll remove all the drivers using Driver Sweeper now, and then I'll install 12.11 Beta 11.

 

[Hitman928]

Let us know what the error says when you go to install. Be very specific with what the error says, a screenshot or a copy and paste would be great.

 

[Clorky]

Pretty weird... Everything ran 'Successful'.

 

[Hitman928]

Pretty weird... Everything ran 'Successful'.

Hmm, after a quick search, it seems that turning off UAC, then uninstalling and reinstalling fixed this for some people, it's worth a try. If you type UAC into the start menu, it will bring up the shortcut to turn it off, just slide the slider to the bottom, restart comp, then start the uninstall/reinstall process.

 

[Clorky]

I already had it on the bottom...

 

[Hitman928]

Well, that settles that then. I also found this if you're willing to try it:

http://www.sevenforums.com/graphic-...control-center-ccc-will-not-open-install.html

 

[Hitman928]

Oh, and make sure your antivirus is completely off while installing, they can interfere sometimes too.

 

[Clorky]

I'll do.

Thanks.