83 replies to this topic

[The Gunman]

I've started having issues too. I took a 2 month hiatus from the game: now my CF is broken.

I'm running Tri-Fire 7970s. Using driver version 14.2. I simply can't get any indication of scaling occurring. I have followed all instructions in the thread.

[Shamous13]

The Gunman, on 15 March 2014 - 05:38 PM, said:

I've started having issues too. I took a 2 month hiatus from the game: now my CF is broken.

I'm running Tri-Fire 7970s. Using driver version 14.2. I simply can't get any indication of scaling occurring. I have followed all instructions in the thread.

Download msiafterburner this has all of the tools that you need. I haven't dealt with tri-fire before.

[Shamous13]

frag85, on 14 March 2014 - 03:15 PM, said:

This is the flickering I get with AFR.
While in the video it appears to just be a slightly darker screen, the whole screen is flickering.

http://youtu.be/LH-T_i302vg

And the ghosting in AFR, if the game is not flickering its doing this:
http://youtu.be/yCBOBmTfuew



Framerates I'm seeing on tourmaline, walking out to the atlas and hanging a left.



I still believe its a problem with the 7970, drivers and MWO. Not every card is treated the same in the video card drivers, so people with say CF7770. 7870 or a 6000 series that got it working-good for them, they don't have 7970s.

It doesnt look like your cards are scaling correctly, this is caused by ultra-low power state, for AMD/ATI graphics cards in CrossfireX, one card basicly shuts down causing the other card to overload. To fix this you can either edit your registry or use the automated tool in the link provided. From what I have read you will need to do this every time you upgrade your drivers. can you confirm that you have done this.

[CeeKay Boques]

Frag if it helps, the Flickering with the MechLab on the alternating frames is what I had and its gone now...

However, the cards I was using aren't even the same gen as yours, 4850. Still...

[frag85]

Shamous13, on 17 March 2014 - 04:00 AM, said:

It doesnt look like your cards are scaling correctly, this is caused by ultra-low power state, for AMD/ATI graphics cards in CrossfireX, one card basicly shuts down causing the other card to overload. To fix this you can either edit your registry or use the automated tool in the link provided. From what I have read you will need to do this every time you upgrade your drivers. can you confirm that you have done this.

ULPS is disabled. If you looked at the graph I posted, you' can see that the cards are being utilized. If you are running CF 7970(or 7950)s and are seeing different results, post what you are doing to get proper CF scaling without the flicker or ghosting issue. This is the issue I've been seeing with a fresh install of Win7 and any driver version up to 14.2.

Technoviking, on 17 March 2014 - 11:29 AM, said:

Frag if it helps, the Flickering with the MechLab on the alternating frames is what I had and its gone now...

However, the cards I was using aren't even the same gen as yours, 4850. Still...

Cards with different chips are handled their own way in the drivers. They have nothing in common except they are made by AMD/ATI.

The Gunman, on 15 March 2014 - 05:38 PM, said:

I've started having issues too. I took a 2 month hiatus from the game: now my CF is broken.

I'm running Tri-Fire 7970s. Using driver version 14.2. I simply can't get any indication of scaling occurring. I have followed all instructions in the thread.

By any chance can you run MSI Afterburner and log your GPU usage, temps and clocks? You'll need ULPS disabled for logging to work right unless you start MSIAB after you get MWO running in fullscreen.

Edited by frag85, 17 March 2014 - 12:56 PM.

[Dazi_Shimazu]

frag85, on 17 March 2014 - 12:15 PM, said:

ULPS is disabled. If you looked at the graph I posted, you' can see that the cards are being utilized. If you are running CF 7970(or 7950)s and are seeing different results, post what you are doing to get proper CF scaling without the flicker or ghosting issue. This is the issue I've been seeing with a fresh install of Win7 and any driver version up to 14.2.




Cards with different chips are handled their own way in the drivers. They have nothing in common except they are made by AMD/ATI.




By any chance can you run MSI Afterburner and log your GPU usage, temps and clocks? You'll need ULPS disabled for logging to work right unless you start MSIAB after you get MWO running in fullscreen.

I have two Diamond Double Black Diamond 7970s and I can confirm this workaround does work. The ghosting and flicker is due to the shaders needing to be purged via the repair tool and reset to the new resources. If I can remember if I did anything special to fix the issue beyond this I will let you know. My memory is a failing device due to a chronic disease. I do know I am running the most current beta drivers from guru3d.com. I did have to make sure any and all ULPS in the registry were disabled. I ran the profile Borderlands 2. I also made sure that all the settings for catalyst center were defaulted. There is a lag stutter due to a problem with the engine on dx11 that should be fixed 3/18/2014. I will see if I can get more of a performance number at that time. You will have to disable AA as this causes you to have bugs too and I had this when logging in and running the game.

Edited by Kain Jackyll, 17 March 2014 - 03:14 PM.

[Shamous13]

frag85, on 17 March 2014 - 12:15 PM, said:

ULPS is disabled. If you looked at the graph I posted, you' can see that the cards are being utilized. If you are running CF 7970(or 7950)s and are seeing different results, post what you are doing to get proper CF scaling without the flicker or ghosting issue. This is the issue I've been seeing with a fresh install of Win7 and any driver version up to 14.2.

Just curious did you uninstall the drivers completely before installing 14.2 beta drivers? what size psu are you running and whats the rest of the hardware that you are running. I say that your gpu isn't scaling properly because you can see that the gpu1 and 2 have difrent load % and should be almost the same. also note you should be exiting out of the game and closing it prior to changing the ccc profile this can cause some wonky problems too..

[frag85]

Kain Jackyll, on 17 March 2014 - 03:07 PM, said:

I have two Diamond Double Black Diamond 7970s and I can confirm this workaround does work. The ghosting and flicker is due to the shaders needing to be purged via the repair tool and reset to the new resources. If I can remember if I did anything special to fix the issue beyond this I will let you know. My memory is a failing device due to a chronic disease. I do know I am running the most current beta drivers from guru3d.com. I did have to make sure any and all ULPS in the registry were disabled. I ran the profile Borderlands 2. I also made sure that all the settings for catalyst center were defaulted. There is a lag stutter due to a problem with the engine on dx11 that should be fixed 3/18/2014. I will see if I can get more of a performance number at that time. You will have to disable AA as this causes you to have bugs too and I had this when logging in and running the game.

Weird that you aren't getting the flicker or poor scaling. Doing the reset via the repair tool, or even a complete fresh install of MWO I either get no scaling (with the default, bioshock, any crysis profile, I have tried the Borderlands profile in the past for MWO but not on 14.2) or the flickering (with the AFR method). I've tried these on a fresh windows install (i keep a 2nd install of windows as a backup/testing install) and my normal gaming install just in case I had changed something that was affecting CF.

What resolution are you running? What kind of frame rates? I wonder if that is related. If you aren't running a large resolution, you could just not be utilizing your cards enough to notice. I know if I was running just 1920x, 1 card would be more than enough for 80-100FPS without much of a fuss. I'm just looking at being able to keep 85FPS for my 75hz display as 85 is one of those 'sweet spot' frame rates where tearing almost disappears. On my Nvidia SLI setup I was able to do this without a problem.

I wish there was a tool more powerful than RadeonPro (or RP had more options), along the lines of nvidia inspector where you can see what engines/games certain profiles were meant for. Inspector was much easier to set the 'bits' than to just go on a guessing game of assigning different game profiles, like I wouldn't be surprised if Bioshock and all the Cryengine games use the exact same CF method.

Edited by frag85, 17 March 2014 - 09:05 PM.

[Shamous13]

Try this, delete your user shader cache, run the repair tool, and add r_ShadersAsyncCompiling=0 to your user.cfg it MAY resolve the issue but no promises, I also found that having a custom user cfg was causing issues. try going to the basics with the following

cl_fov = 85
r_MultiGPU = 1
r_ShadersAsyncCompiling=0

also try adding r_flush=0 to your user.cfg

Colonel Pada Vinson, on 05 March 2014 - 09:51 PM, said:

and another updated user.cfg you can try. This is for very high spec and will be (7) when added to the package. adds some bonus ssdo & hdr / bloom for nicer lasers too.

Spoiler

;Field of View inside Cockpit (Default:75)
sys_spec_Quality=4
sys_spec_GameEffects = 4
sys_spec_ObjectDetail = 4
sys_spec_Particles = 4
sys_spec_PostProcessing = 4
sys_spec_Shading = 4
sys_spec_Sound = 4
sys_spec_Shadows = 4
sys_spec_Texture = 4
sys_spec_Environment = 4
r_ColorGrading = 0
r_DepthOfField = 0
r_GlowAnamorphicFlares = 1
r_HDRBloomMul = 0.5
r_HDRBlueShift = 0
r_HDRBrightLevel = 0.85
r_HDRBrightOffset = 5
r_HDRBrightThreshold = 6
r_HDREyeAdaptionCache = 0
r_HDRGrainAmount = 0
r_HDRLevel = 3
r_HDROffset = 10
r_HDRRendering = 1
r_UseEdgeAA = 1
;MotionBlur Fun
;r_MotionBlur = 5
;r_MotionBlurMaxViewDist = 100
;r_MotionBlurShutterSpeed = 0.00001
g_dofset_maxscale = 1
g_radialBlur = 1
r_UsePOM = 1
r_PostProcessHUD3DCache = 0
r_RainMaxViewDist_Deferred = 100
r_Sunshafts = 1
r_Flares = 1
q_Renderer = 3
q_ShaderFX = 3
q_ShaderGeneral = 3
q_ShaderGlass = 3
q_ShaderHDR = 3
q_ShaderIce = 3
q_ShaderMetal = 3
q_ShaderPostProcess = 2
q_ShaderShadow = 3
q_ShaderSky = 3
q_ShaderTerrain = 3
q_ShaderVegetation = 3
e_Shadows = 1
e_GsmCache = 0
e_GsmLodsNum = 4
e_GsmRange = 3
e_ParticlesShadows = 0
e_ShadowsCastViewDistRatio = 1
e_ShadowsMaxTexRes = 1024
e_ShadowsOnAlphaBlend = 0
e_ShadowsResScale = 4.0
r_ShadowBlur = 3
r_ShadowJittering = 2.5
r_ShadowsPCFiltering = 1
r_ShadowsUseClipVolume = 1
;r_FogShadows = 1
;bugged;r_ShadowsMaskResolution = 1
s_MPEGDecoders = 32
s_Obstruction = 1
s_ObstructionAccuracy = 1
s_ObstructionUpdate = 0.1
s_SoundMoodsDSP = 1
s_VariationLimiter = 1
e_WaterOceanFFT = 1
e_WaterTessellationAmount = 10
e_WaterTessellationAmountX = 85
e_WaterTessellationAmountY = 85
e_WaterTessellationSwathWidth = 10
r_WaterCaustics = 1
r_WaterReflections = 1
r_WaterReflectionsQuality = 5
r_WaterReflectionsMinVisiblePixelsUpdate = 0.05
r_WaterTessellationHW = 1
r_WaterUpdateDistance = 0.2
r_WaterUpdateFactor = 0.05
e_DynamicLightsMaxEntityLights = 32
e_GI = 1
e_GIAmount = 0.5
e_GINumCascades = 3
e_GIMaxDistance = 100
e_SkyType = 1
e_SkyUpdateRate = 1
e_TerrainAo = 1
e_TerrainNormalMap = 1
e_VegetationUseTerrainColor = 1
r_DetailDistance = 20
r_DetailTextures = 1
r_ssdo = 2
r_SSDOAmount = 0.9
r_SSDOAmbientAmount = 1.5
r_SSAO = 0
r_SSAOQuality = 3
r_SSAODownscale = 0
r_refraction = 1
r_SSReflections = 3
r_Beams = 3
r_BeamsDistFactor = 0.01
r_BeamsMaxSlices = 300
e_Clouds = 1
r_CloudsUpdateAlways = 1
r_Reflections = 1
e_GsmRangeStep = 4
e_GsmCastFromTerrain = 1
r_ChromaticAberration = 1.5
i_lighteffects = 1
g_ragdollMinTime = 15
g_ragdollUnseenTime = 3
g_ragdollDistance = 40
e_ObjQuality = 4
e_DecalsAllowGameDecals = 1
e_DecalsLifeTimeScale = 2
e_DecalsOverlapping = 1
e_Dissolve = 2
e_LodRatio = 40
e_Lods = 1
e_LodMin = 0
e_MaxViewDistSpecLerp = 1
e_OcclusionCullingViewDistRatio = 1
e_ProcVegetation = 1
e_streamCgf = 0
e_VegetationBending = 1
e_VegetationMinSize = 0
e_VegetationSpritesDistanceCustomRatioMin = 1
e_VegetationSpritesDistanceRatio = 1.5
e_ViewDistMin = 10
e_ViewDistRatio = 100
e_ViewDistRatioCustom = 100
e_ViewDistRatioDetail = 100
e_ViewDistRatioLights = 100
e_ViewDistRatioVegetation = 100
e_TerrainDetailMaterialsViewDistXY = 2048
e_TerrainDetailMaterialsViewDistZ = 256
e_TerrainOcclusionCullingMaxDist = 200
ca_AttachmentCullingRation = 300
ca_DrawFaceAttachments = 1
ca_useDecals = 1
es_DebrisLifetimeScale = 1
i_rejecteffects = 1
e_Tessellation = 1
e_DecalsForceDeferred = 1
r_DrawNearZRange = 0.08
e_ParticlesQuality = 4
e_ParticlesLights = 1
e_ParticlesMaxScreenFill = 160
e_ParticlesMinDrawPixels = 1
e_ParticlesMotionBlur = 1
e_ParticlesObjectCollisions = 2
r_UseParticlesHalfRes = 0
r_UseSoftParticles = 2
r_UseParticlesRefraction = 1
g_breakage_particles_limit = 160
g_joint_breaking = 1
g_tree_cut_reuse_dist = 0
e_CullVegActivation = 50
e_FoliageWindActivationDist = 25
e_PhysFoliage = 2
e_PhysOceanCell = 0.5
p_gravity_z = -36.3
p_joint_damage_accum = 2
p_joint_damage_accum_threshold = 0.2
p_max_MC_iters = 6000
p_max_object_splashes = 3
p_max_substeps_large_group = 5
p_num_bodies_large_group = 100
p_splash_dist0 = 7
p_splash_dist1 = 30
p_splash_force0 = 10
p_splash_force1 = 100
p_splash_vel0 = 4.5
p_splash_vel1 = 10
v_vehicle_quality = 4
es_MaxPhysDist = 200
es_MaxPhysDistInvisible = 25
r_DynTexAtlasCloudsMaxSize = 32
r_DynTexAtlasSpritesMaxSize = 32
r_DynTexMaxSize = 80
r_EnvCMResolution = 2
r_EnvTexResolution = 3
r_EnvTexUpdateInterval = 0.001
r_ImposterRatio = 1
r_TexSkyResolution = 0
r_TexAtlasSize = 2048
r_TexMinAnisotropy = 8
r_TexBumpResolution = 0
r_TexResolution = 0
r_TexturesStreaming = 0
r_VegetationSpritesTexRes = 64
e_TerrainTextureLodRatio = 1
e_CoverageBufferReproj = 1
e_TerrainTextureStreamingPoolItemsNum = 256

Edited by Shamous13, 18 March 2014 - 04:21 AM.

[frag85]

Shamous13, on 18 March 2014 - 04:16 AM, said:

Try this, delete your user shader cache, run the repair tool, and add r_ShadersAsyncCompiling=0 to your user.cfg it MAY resolve the issue but no promises, I also found that having a custom user cfg was causing issues. try going to the basics with the following

cl_fov = 85
r_MultiGPU = 1
r_ShadersAsyncCompiling=0

also try adding r_flush=0 to your user.cfg

Same boat as before. No scaling in Default, Bioshock or Borderlands or 100% scaling but flicker/ghosting in AFR.

What motherboard Chipset do you have? I was thinking back to when I switched from x58 to Z77 and how I had all sorts of new video driver issues on the Z77 that I did not have on the x58, and problems I had on x58 were gone on Z77. I'm thinking you are running something other than a Z77 board and that the issue is more driver related than MWO at this point.

[Shamous13]

I've got a crosshair v formula wit a fx8350. what brand of mother board do you have? a few thoughts what slots do you have your video cards plugged in too? the slots for your board are setup as listed below (asus listed below) and your cards should be pluged in too the first two slots.Have you updated all of your drivers for your MOB? have you updated the BIOS? also check that all of your connections from your psu are seated properly and that you have used every plug on the motherboard. what size of PSU do you have? I'm just going through the trouble shooting list.

2 x PCIe 3.0/2.0 x16 (x16 or dual x8) *²
1 x PCIe 2.0 x16 (x4 mode, black) *³
*3: The PCIe 2.0 x16 slot shares bandwidth with PCIe 2.0 x1_1 slot, PCIe 2.0 x1_2 slot and PCIe 2.0 x1_3 slot. The PCIe 2.0 x16 slot default setting is in x1 mode

Edited by Shamous13, 19 March 2014 - 04:19 AM.

[frag85]

Hm. I wonder if this could be related to a bug between the 79xx series cards and Z77 intel chipsets.

I've got a Gigabyte Z77x-UD3H, so its PCI-Express 3.0, x8 x8 with dual cards (verified link width using CPU-Z). More than enough bandwidth to support these cards. Its definitely not a power issue. I can run any number of the hundreds of games I own and MWO is the only game with this issue.

Thanks, But no need for basic troubleshooting at this point. Everything is updated and I've tried older versions of drivers and its either the same issues or new ones pop up. If the issue was here then booting to a fresh, updated windows install with only MWO and the latest drivers (or several versions older for GPU drivers) shouldn't see this issue. I'm pretty confident when I saw this is an MWO and/or driver issue at this point.


Edit: I was reading around on some Crysis 3 forums and apparently the flicker is a chronic problem for some people but not others, sometimes one driver version everything will be fine and the next everything is broken again. Its most likely cryengine and/or the drivers.

Edit2: Bug report set to AMD and I sent a message to one of the Catalyst developers.

Edited by frag85, 20 March 2014 - 03:31 PM.

[Silpher K]

Here is my current "working" setup that im using, no modified client cfg files.

my specs and setup:
i7-3770k @ 4.5
sabertooth z77
16GB 1866 ram
2x 670 FTW+ 4GB SLI
3x 1920x1080 in surround @ 6080x1080 with bezel correction
335.23 drivers
dx11 mode

playability:
sli confirmed functioning (scaled my fps 2x with crysis3 bits)
slight damage texture flicker
damage glow flicker (turned off so i dont see this)
notice a very very feint ghost image (almost like a burnt-in image you see on old TV sets) once a match starts, will be running repair tool to clear shaders and other things to try to fix this
otherwise very playable (30~40fps avg, or almost double this if not using TXAA)
no noticeable unusual performance dives compared to sli off

without sli bits, game is unplayable with dx11/txaa enabled for me at my resolution (im talking dips to 10~15fps unplayable)


inspector settings:




in game settings:


in game usage:

Edited by Silpher K, 23 March 2014 - 10:54 PM.

[frag85]

Silpher K, on 23 March 2014 - 07:44 PM, said:

blip

Any chance you can get a screen shot of all the games in that SLI bit? I'm wondering if the way MWO is handled is like any of those games when it comes to CF. Crysis3 doesn't do it for me and those other games visible aren't in the CF list.

[Silpher K]

frag85, on 25 March 2014 - 04:17 PM, said:

Any chance you can get a screen shot of all the games in that SLI bit? I'm wondering if the way MWO is handled is like any of those games when it comes to CF. Crysis3 doesn't do it for me and those other games visible aren't in the CF list.

:/
unfortunately there's only 1 (and a half of the one that's cut off) that's not in the screenshot

I'll just list them for you:
Need for Speed: Most wanted
Squadron 42 - Star Citizen
Crysis 3
Dying Light
Fire Loyalty (Huo Xian Zhong Chen)

[Mycrus]

Silpher K, on 23 March 2014 - 07:44 PM, said:

Here is my current "working" setup that im using, no modified client cfg files.

my specs and setup:
i7-3770k @ 4.5
sabertooth z77
16GB 1866 ram
2x 670 FTW+ 4GB SLI
3x 1920x1080 in surround @ 6080x1080 with bezel correction
335.23 drivers
dx11 mode

playability:
sli confirmed functioning (scaled my fps 2x with crysis3 bits)
slight damage texture flicker
damage glow flicker (turned off so i dont see this)
notice a very very feint ghost image (almost like a burnt-in image you see on old TV sets) once a match starts, will be running repair tool to clear shaders and other things to try to fix this
otherwise very playable (30~40fps avg, or almost double this if not using TXAA)
no noticeable unusual performance dives compared to sli off

without sli bits, game is unplayable with dx11/txaa enabled for me at my resolution (im talking dips to 10~15fps unplayable)


inspector settings:




in game settings:


in game usage:

Thanks ill try this

[Nick Rarang]

I don't have crossfire but I have to say my 5ghz Fx8350 and 7970 ghz sucks in this game. 13fps dips in extensive maps

[frag85]

Silpher K, on 25 March 2014 - 04:34 PM, said:

:/
unfortunately there's only 1 (and a half of the one that's cut off) that's not in the screenshot

I'll just list them for you:
Need for Speed: Most wanted
Squadron 42 - Star Citizen
Crysis 3
Dying Light
Fire Loyalty (Huo Xian Zhong Chen)

Cool thanks. Not even on the CF profiles list. lol. I went through and tried all the cryengine games again and still no go. This is so frustrating.

[Shamous13]

frag85, on 28 March 2014 - 07:01 AM, said:

Cool thanks. Not even on the CF profiles list. lol. I went through and tried all the cryengine games again and still no go. This is so frustrating.

I'm wondering if your PSU is on the week side or if you have a 12v rail on the way out. what brand and size of psu do you have?

[Sheridan Mackison]

I just read a review on Tom's Hardware that stated "With all of that said, you can see AMD's Radeon R7 265 is an overclocked Radeon HD 7850...". Has anyone bean successful setting up a 7850 and an R7 265 in crossfire?