AMD killing Crossfire branding in favor of ...mGPU..not to be confused with mobile GPUs

[Cyracus]

1 hour ago, ARikozuM said:

This also officially kills any chances off multi-GPU engines being made since most "AAA" developers care more for the bottom line than they do making the best they can make.

Wasn't crossfire/sli support 99% on the developers anyway? Now it'll just be how well they do the dx12

[bcredeur97]

Im calling it crossfire. 

 

you cant stop me! 

[Jito463]

1 hour ago, Armakar said:

Personally, instead of "I'm crossfiring two Vega 64'S" , I like the sound of "I'm running two nuclear reactors"

Only two?  Amateur.  

[Marinatall_Ironside]

4 hours ago, Cyracus said:

I run dual vega 64s or I run vega 64s in tandem, either sounds spiffy enough to me

I run Quad/4-way Vega 64

[Marinatall_Ironside]

1 hour ago, leadeater said:

For game engines like Unreal I'm sure it'll be inbuilt and fairly usable, much more so than getting crossfire to work anyway.

Hopefully so. I also wonder if CryEngine V has a fairly usable multi-GPU implementation like Unreal Engine 4.

[Skanky Sylveon]

2 hours ago, leadeater said:

For game engines like Unreal I'm sure it'll be inbuilt and fairly usable, much more so than getting crossfire to work anyway.

Agreed, the name is stupid though.

 

 

mmmmmmmm, tasty GPU.

[ApolloFury]

6 hours ago, Syntaxvgm said:

How would you even refer to running two AMD GPUs now? 

I run two Vega 64s in crossfire mGPU?

I run two Vega 64s in multi-GPU?

Doesn't sound as cool. 

Why not simply "I run dual Vega 64s"?

I rarely heard anyone (in a face to face conversation) say "I ran them in crossfire/SLI" since saying dual already speaks for itself. 

No need to say "multi" since dual is already considered a "multi" setup.

imo

 

EDIT: other examples

"I run dual R9 290s"

"I run 2 R9 290s"

 

I can see the issue if you have two of different GPUs, for example
"I run 7850 and 7870 in...crossfire? mGPU?? dual mode???!" (I am not actually sure if those two are compatible )

[Delicieuxz]

6 hours ago, Name Taken said:

Noticing a pattern with AMD and their poor naming decisions.

I know - just like renaming their overclocking tool from Overdrive to Wattman. Typically, a company would choose to go from a boring, flat-sounding, random, non-descriptive name to a descriptive, energizing, premium-sounding name. AMD decided to do the opposite.

[Cooked Karambawn]

Run them in parallel?

 

[Syntaxvgm]

1 hour ago, ApolloFury said:

Why not simply "I run dual Vega 64s"?

I rarely heard anyone (in a face to face conversation) say "I ran them in crossfire/SLI" since saying dual already speaks for itself. 

No need to say "multi" since dual is already considered a "multi" setup.

imo

 

EDIT: other examples

"I run dual R9 290s"

"I run 2 R9 290s"

 

I can see the issue if you have two of different GPUs, for example
"I run 7850 and 7870 in...crossfire? mGPU?? dual mode???!" (I am not actually sure if those two are compatible )

But then how do I distinguish myself from those miners??

[Monkey Dust]

8 hours ago, Cyracus said:

I run dual vega 64s or I run vega 64s in tandem, either sounds spiffy enough to me

'I run a brace of Vega 64s' sounds spiffier still.

[LAwLz]

AMD is not rebranding Crossfire to mGPU. They are simply killing off Crossfire in the hopes that people will switch over to the Multi-GPU features that exist in Dx12 and to some degree Vulkan.

Its not as much "rebranding and changing Crossfire" as it is just straight up abandoning it. 

[JediFragger]

8 hours ago, Moress said:

It'll always be crossfire to me!

I started to call it Crapfire for quite a while now. Terrible.

 

I miss my 295x2 when it used to be kickass

[JediFragger]

55 minutes ago, LAwLz said:

Its not as much "rebranding and changing Crossfire" as it is just straight up abandoning it. 

They may as well call it 'We ain't got the resources for this shit anymore (and haven't for a fair while), let's put the onus onto the developers'!!!

 

Doesn't exactly roll off the tongue though

[Misanthrope]

Actually it is my understanding that SLI and Crossfire profiles involve more direct collaboration between the hardware vendor and the devs whereas multi gpu is just up to the devs since it doesn't needs to "sync" anything just splits rendering between cards and goes with the lowest common denominator, basically taking advantage of DX12/Vulkan

 

The good news is that we've seen this works even across vendors i.e. 1060 + 580 multi gpu. The bad news is that this is basically supported exactly by one "game" afaik AOTS and it just doesn't looks like support will increase.

 

So either multi gpu set ups will get better or more likely, they are to be fully deprecated within 1 or 2 more hardware cycles.

[leadeater]

26 minutes ago, Misanthrope said:

The good news is that we've seen this works even across vendors i.e. 1060 + 580 multi gpu. The bad news is that this is basically supported exactly by one "game" afaik AOTS and it just doesn't looks like support will increase.

Not sure about cross vendor support but Civ 6 supports DX12 mGPU, I use it over crossfire but more just to see how well it worked. Rather uneventful as both worked well so I stuck with DX12 mGPU.

[Trixanity]

They're killing the branding and probably trying to back off any commitment to multi GPU support on DX11. The 'new' name is just using existing naming convention put forth by Microsoft in their DX12 documentation as far as I'm concerned. It's not something AMD came up with.

 

They are also trying to push (have done so for a while) for increased DX12 support. For obvious reasons. It reduces the work required by AMD's driver team and it's also helpful to the performance of their cards, so it's a win-win if they can increase DX12/Vulkan adoption.

[Taf the Ghost]

And everyone will still call it Crossfire.

[NumLock21]

Amd can call it

Prepare to cringe...

 

AMD Fusion Technology

 

Fusion-the process or result of joining two or more things together to form a single entity.

 

[rattacko123]

8 minutes ago, NumLock21 said:

Amd can call it

Prepare to cringe...

 

AMD Fusion Technology

 

Fusion-the process or result of joining two or more things together to form a single entity.

 

AMD Fusion already exists...

*shudders*

[ZestyJalapeno]

Maybe they're just paving the way for their MCM gpus

[Doobeedoo]

14 minutes ago, NumLock21 said:

Amd can call it

Prepare to cringe...

 

AMD Fusion Technology

 

Fusion-the process or result of joining two or more things together to form a single entity.

 

It's already a thing like APU or CPU and GPU working together for everything as much as possible to leverage the maximum compute performance etc. 

[Doobeedoo]

Hmm Crossfire resonated well. But oh well, I'm interested to see how it goes from here. Leverging new APIs for games and mGPU features opposed to Crossfire profiles which took different approach. 

[Misanthrope]

2 hours ago, leadeater said:

Not sure about cross vendor support but Civ 6 supports DX12 mGPU, I use it over crossfire but more just to see how well it worked. Rather uneventful as both worked well so I stuck with DX12 mGPU.

I stand corrected. Not only that but I'd be genuinely interested in cross-vendor mgpu so let's hope it comes to even more games (it should but still a maybe imo)

[Sniperfox47]

11 hours ago, leadeater said:

For game engines like Unreal I'm sure it'll be inbuilt and fairly usable, much more so than getting crossfire to work anyway.

Unless you're on Linux, then RIP.

 

Note, I don't mean because Linux doesn't support mGPU, Vulkan has the same kind of support as DX12.

 

It's just that Unreal Engine 4 is already "Broken AF™" on Linux without them failing and implementing broken Multi-GPU too.