Aller au contenu

Photo

ME2 in Windows 7, CF 5850, cannot get Vsync to work?


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

#1
ajl716

ajl716
  • Members
  • 16 messages
I am having a problem with ME2 in Windows 7 Home Premium 64 bit. I cannot get Vsync to work using both CCC and d3doverrider. I get bad screen tearing when I make quick vertical or horizontal movements, and I didn't have this problem when I was running the same setup in Vista Ultimate 64. This is very annoying as I am quite sensitive to screen tearing and it's ruining the game for me : (

Any advice on what to do? Thanks for any help!

#2
BeresaadSoldier

BeresaadSoldier
  • Members
  • 169 messages
On d3doverrider you have to force triple buffering and force vsync. In your catalyst drivers, disable vsync since d3d will override it anyway.



Are you running anti-aliasing? And is your problem during cut scenes or during combat?

#3
ajl716

ajl716
  • Members
  • 16 messages
Hmm k I tried that, still getting tearing. I am forcing 4x AA with the "Box" filter in CCC, and the problem occurs in gameplay, cutscenes, and also in the opening BioWare logo screen.



Guess I'll have to keep fiddling around with it, but I swear this only started happening after I installed Win7..



Also I am having *snap crackle pop* sounds in the menu screens as well, running Xtremegamer with latest creative drivers, just in case that could have anything to do with the graphical problems. Both issues have surfaced only after my switch to Win7..

#4
ME-BlindNero

ME-BlindNero
  • Members
  • 48 messages
The game is capped at 60 fps, so vsync would add nothing.

Use ALchemy
, works on ME1 and ME2.


My PC specs

Modifié par ME-BlindNero, 22 avril 2010 - 02:54 .


#5
ajl716

ajl716
  • Members
  • 16 messages
Well, capped or not, I was getting screen tearing... until I disabled Catalyst AI. After doing so, the tearing has stopped, but now AA doesn't work. Sigh. So I guess it's play with no AA or play with tearing as of right now... and doesn't that disable CF if I don't have on catalyst AI?



thanks for the help anyways

#6
ME-BlindNero

ME-BlindNero
  • Members
  • 48 messages
Disabling Cat AI disables AFR, so effectively disables crossfire. You shouldn't do that.

You didn't have the screentearing before? In that case, revise your other CCC settings.
Mine:
AA: unticked "use application settings" > level 2x
AF: ticked "use application settings"
Cat AI: Standard
Mipmap: Quality
Vsync: always off
AA Mode: SSAA

Game settings:
fullscreen, widescreen, 1920x1200
HQ Bloom: on
film grain: off
motion blur: on
dynamic shadows: on
light environment shadows: on
cinematic lights: 3
spherical harmonic lighting: on
anisotropic filtering: 8x

Modifié par ME-BlindNero, 22 avril 2010 - 03:34 .


#7
rain4november

rain4november
  • Members
  • 6 messages
ajl716 - did you get your problem resolved? I'm not having the tearing issue you speak of, but I am seeing with a Radeon 5850 card, an odd net result from Mass Effect 2's own auto-configurator program. Have submitted a query to see if BioWare can assist here:



http://social.biowar...6/index/2764916

#8
searanox

searanox
  • Members
  • 714 messages

ME-BlindNero wrote...

The game is capped at 60 fps, so vsync would add nothing.

Use ALchemy
, works on ME1 and ME2.


My PC specs


Why would you even suggest using ALchemy for Mass Effect 2?  Mass Effect does use EAX, but it also uses OpenAL, so ALchemy isn't necessary on Windows Vista/7.  Mass Effect 2 does all its effects processing via OpenAL, thus there is no reason to use ALchemy with it.

The only reason to use ALchemy is to restore hardware acceleration and surround sound to DirectSound3D games, by converting the DirectSound3D calls to OpenAL.  This isn't necessary for games that natively use OpenAL, and while ALchemy works for other APIs like FMOD and Miles, there is no benefit to it, and it may in fact introduce more sound problems.

Modifié par searanox, 31 mai 2010 - 03:20 .