Aller au contenu

Photo

Antialiasing Mode


  • Veuillez vous connecter pour répondre
28 réponses à ce sujet

#1
athleos

athleos
  • Members
  • 10 messages
Mass Effect 2 does not allow anti-aliasing. I use a geforce 285 but when  Antialiasing is forced at 16X  by the nvidia control panel the game is still jaggy. Is the game designed this way to keep it stable, or is there a way to enable Antialiasing?

Thanks Bioware for making a beauitful game, it was worth the $70cdn.Image IPB

#2
crapmonster13

crapmonster13
  • Members
  • 659 messages
Not sure about nvidia but on ATI card, we just simply have to rename MassEffect2.exe to UT3.exe and set the AA settings accordingly in Catalyst.



Honestly though, while it looks noticeably better I left it off since it will dramatically cut down your fps. The game still looks great jaggys or not on max settings either way.

#3
Wyvern76

Wyvern76
  • Members
  • 30 messages
Wow, I was just about to post the same.

I have a ATI 5870 and have noticed no Anti-aliasing even when forced in the driver. 0 to 16X all looks the exact same.



Please, how do we turn on AA.

Please how do we turn on "hidden" settings to move beyond XBOX graphics?

Thank you.

#4
sticks435

sticks435
  • Members
  • 317 messages
For ATI users, you need to download the latest hotfix drivers. Nvidia users can use a program called Nhancer to override the driver, since Nvidia has yet to release updated drivers with a ME2 specific profile. You'll need to use the AA compatibility setting of Unreal ENgine 3. There should also be plenty of threads on this. You can access the search directly at social.bioware.com/forum/1/search

Modifié par sticks435, 04 février 2010 - 06:33 .


#5
Spawnyguy

Spawnyguy
  • Members
  • 11 messages
I finally got AA to work by selecting the ME2 profile in Nvidia control panel and selecting the override application setting. I have AA set 8x and the game looks so much better now. Also installed nhancer.

#6
Wyvern76

Wyvern76
  • Members
  • 30 messages

sticks435 wrote...

For ATI users, you need to download the latest hotfix drivers.


Installed newly released Catalyst 10.1 drivers and still ME2 is ignoring driver AA settings. So that's no go.

I frankly thought that the forced driver settings was the point of driver settings. To ignore games settings.

#7
Galeo Deus

Galeo Deus
  • Members
  • 15 messages
The problem is the huge performance hit. UE3 has had horrible implementation of AA, if it has it at all.



On my powerful rig if I even force 2xaa I got from silky 60fps 100% of the time to constant 10+ fps drops in combat or random areas.

#8
Wyvern76

Wyvern76
  • Members
  • 30 messages

crapmonster13 wrote...

Not sure about nvidia but on ATI card, we just simply have to rename MassEffect2.exe to UT3.exe and set the AA settings accordingly in Catalyst.

Honestly though, while it looks noticeably better I left it off since it will dramatically cut down your fps. The game still looks great jaggys or not on max settings either way.



Runs smooth and fine at 16x Edge Detect using the rename methode. Some odd textures in some places using AA though.

I'm running a ATI 5870 and Core 2 Quad @4Gbz

#9
jemtec2

jemtec2
  • Members
  • 1 messages
Another thing to consider is Resolution.

Make sure you are running your native resolution for the Monitor, or you won't see what you should be seeing anyway.

If its native to 1440X900 in 16:10 for instance, then run it there.

I see alot of guys complaining about their cards not "running to spec" when in fact they are, but they are trying to run on the wrong resolution.


#10
Wyvern76

Wyvern76
  • Members
  • 30 messages
Yep. 52" HDTV, 1080i 16:9 screen.

Been playng at 1600x900. ATI let me make up that rsolution. It's a CRT rear-projection so that is kosher. Also uses the driver settings to remove all over-scan.



Agree with the above poster about screen resolutions.

I do IT in the field. Wouldn't believe how many new computers are all running 1024x768 because NO users know better.

#11
ushae

ushae
  • Members
  • 260 messages
Google 'nHancer' and download it. When you open it add Mass Effect 2 to the profiles, then under the compatibility tab, under Direct 3d add 080100C5 Unreal Engine 3. Then you can change AA X2/X4/X8. For some odd reason you can't force it through the normal Nvidia tab.



P.S. It makes the game look amazing :)

#12
Wyvern76

Wyvern76
  • Members
  • 30 messages
Actually 1920x1080 runs silky with 8xAA. Suprising.

Not having the huge drop in FPS like Galeo Deuce.

So it can be done. It can be nice. Just probably way beyond recommended specs.

#13
Trylane

Trylane
  • Members
  • 183 messages

ushae wrote...

Google 'nHancer' and download it. When you open it add Mass Effect 2 to the profiles, then under the compatibility tab, under Direct 3d add 080100C5 Unreal Engine 3. Then you can change AA X2/X4/X8. For some odd reason you can't force it through the normal Nvidia tab.

P.S. It makes the game look amazing :)



You may also have to correct the executable with nhancer if a profile is already existing.

If your graphics card is fast enough (GTX285 or so) you can try a "combined" mode (like 16xS) instead of only multisampling. That will eliminate a lot of shimmering that multisampling is powerless against.

#14
SylPain

SylPain
  • Members
  • 8 messages
ATI users:



In summary:

1) Rename MassEffect2.exe to UT3.exe

2) Select AA 2x, 4x, or 8x from the Catalyst Control Center

3) Run UT3.exe



On my 5850 (OC'd to 950 MHz) I get >50 fps everywhere EXCEPT the Flotella trial. Using 4x AA with Adaptive MultiSample mode. SuperSample mode looks fantastic, but hits the framerate WAY too hard.



Tip: I use D3DOverrider to force the v-sync and triple buffer (may not be necessary for this game).

#15
Outshined87

Outshined87
  • Members
  • 4 messages
http://support.amd.c...-Crossfire.aspx



Direct link for ATI users. This allowed me to force AA without changing the execute file (even though I'm not running Crossfire).

#16
Wyvern76

Wyvern76
  • Members
  • 30 messages

Outshined87 wrote...

http://support.amd.c...-Crossfire.aspx

Direct link for ATI users. This allowed me to force AA without changing the execute file (even though I'm not running Crossfire).



I did think that HotFix was odd to only fix it for Crossfire.

Just made a copy of MassEffect2.exe and named that UT3.exe, then made a shortcut and called that short cut MassEffect2 on my desktop. So I have it both ways. Good enough. Image IPB



*mumbles*
Now if there was only a High Percision Z-buffer tweak.... 

#17
RiotLaFontaine

RiotLaFontaine
  • Members
  • 264 messages
AA is auto for me on ATI 4850 HD Radeon bootcamped (iMac) with Windows 7 at max resolution. Catalyst drivers installed, but no settings beyond default have been changed.

#18
Earmack

Earmack
  • Members
  • 7 messages
If u have SLI or multi-gpu video card just install sli update 4: http://www.nvidia.co..._update_v4.html

After this update AA work fine without any change name lie ut3.exe or masseffect.exe, just start u original masseffect2.exe & or foced from nvidia control panel

Modifié par Earmack, 07 février 2010 - 08:26 .


#19
Gilean11

Gilean11
  • Members
  • 6 messages

ushae wrote...

Google 'nHancer' and download it. When you open it add Mass Effect 2 to the profiles, then under the compatibility tab, under Direct 3d add 080100C5 Unreal Engine 3. Then you can change AA X2/X4/X8. For some odd reason you can't force it through the normal Nvidia tab.

P.S. It makes the game look amazing :)


Well, I tried that.  Problem is under "Direct 3D compatability" I don't have the option to select that code (080100C5).  That code IS under "AA compatability" however, and I selected it there.  Tried entering it manually under Direct 3D and it doesn't seem to take.  And I've tried all the AA settings with this set up (to include supersampling and combined options) and for the life of me I'm not seeing a differenct in the game.  Still have jaggies.  Anybody know what I'm doing wrong?

UPDATE:   Figured it out.  I just needed the newest NVidia driver.  FYI to all, the creator of NHancer also has a pre-set profile for ME2 over on his website.  The settings are slightly different that what ushae said above, but it's definitely working for me.  AA in ME2 is very pretty.

Modifié par Gilean11, 14 février 2010 - 05:45 .


#20
vometia

vometia
  • Members
  • 2 721 messages

Outshined87 wrote...

http://support.amd.c...-Crossfire.aspx

Direct link for ATI users. This allowed me to force AA without changing the execute file (even though I'm not running Crossfire).

I honestly didn't expect that to work on my setup, but I'm pleased to see that it did.  Anything other than "box" is very laggy and a bit funky-looking for my tastes (I guess my 4890 isn't the newest kid in town any longer...) but a modest 4x setting gives barely any lag and tames some of the nastier-looking jaggies, so I'm very pleased with this.

#21
peterfaj

peterfaj
  • Members
  • 14 messages
Renaming it to UT3.exe doesn't help. I also downloaded the "hotfix", but there was no hotfix in it. It only started their awful new installer manager which showed what ATI stuff I already have installed.
I'm not running crossfire.

EDIT: Actually, never mind. I saw that the AA actually works no matter the name of the executable and without the hotfix. There was still some jaggedness and I thought it does not work at all until trying without AA again.
Sorry for this useless post.

AA does however hurt the framerate. The whole game runs perfectly smooth on all max without AA, but even 2xAA already makes some scenes laggy.

Modifié par peterfaj, 19 février 2010 - 10:10 .


#22
matejkrajci

matejkrajci
  • Members
  • 3 messages
 hi 

i have problem with nHancer. It does not start , only write : ''The NVAPI reported no attached nVidia displays in the system.'' How to fix it ? Please help me... 

I have : 
-Windows 7 64bit
-nVdivia geforce GT325M

#23
athleos

athleos
  • Members
  • 10 messages
A new Nvidia driver 197.13 allows excellent anti-aliasing 4x, 8x or 16x


#24
matejkrajci

matejkrajci
  • Members
  • 3 messages
I have driver 197.16. Why it does not work ? damn

#25
deathtard

deathtard
  • Members
  • 60 messages

matejkrajci wrote...

I have driver 197.16. Why it does not work ? damn


Same here.