AMD Catalyst Beta Driver with Mantle Support Delayed

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Status
Not open for further replies.
Would you guys REALLY want them to rush a release and give you unpolished crap or wait a little bit and get a version with the bugs IRONED OUT. i take option b.
 


Yes, that is exactly right and correct!

How comes you have worked that out whilst some of the other posters haven't?
 
Yes, that is exactly right and correct! How comes you have worked that out whilst some of the other posters haven't?
Because this article was released over 5 hours before the patch article.
http://www.tomshardware.com/news/amd-mantle-driver-delayed,25919.html

Now how comes I could figure that out and you couldn't?
 


Because this article about the patch being released is dated earlier? http://www.tomshardware.com/news/battlefield-mantle-catalyst-drivers,25908.html look at the day not the time, the 30th is earlier than the 31st. :kaola:
 
i would personally take the bugs no problem. amd drivers have never bothered me. i can name quite a few beta games that were horrid.... skyrim one of them, it was near unplayable 2 months before the official release but i still logged 100 hours. i have no problems with errors but maybe because i do lots of beta games for is why i have no problem with glitches. console and apple people have problem with glitches.
 


Seriously?

The driver delay article came out 11 hours later than the BF Mantle patch release article. These are two different subjects. You two are either trolling this Moderator or can't comprehend dates & times.
 


It's a bit of both but I have one hand on my banhammer and I'm not afraid to swing it but thank you for the support! :lol:
 
what is this arguement about. dice officially released the mantle patch. the leaked modded mantle kernal driver is working for some but is buggy as hell. the official amd release of the mantle driver hasn't happened. is this hard to comprehend.
 


For some it seems to be.
 


That will all depend on how much AMD keeps paying them to support it. Nobody codes for free for the smallest portion of gpus in the market. We are talking a portion of AMD's gpus which is already only 35% of discrete, while NV owns 65%. Think about how many games USE physx. It doesn't get used unless NV is paying someone so they can make a statement about how great it is. TressFX same story (but at least that works on most gpus). They have to code for PC and 2-3 consoles already (all different) and now Mantle too? Add Android/iOS and you might be talking 5-6 versions? WOW. That's a lot of work to sell ONE game.

If consoles had used this and we were talking last gen using it (retarded but just saying if they did), I'd say completely different stuff. But reality says neither console wants competition or easy porting for their games to other platforms. I have no need to buy a console if I can just wait a few months for a good port. I don't see how this will ever get massively used, as APU's are about to get crushed by Intel's x86 versions (who have now said they are serious about coming for ALL low-end fruit) and by the end of the year or Q1 a bunch of 20nm ARM socs will be coming for low end also. So AMD will be burning from both ends on APU/CPU. Couple that with AMD's already low market share in Discrete and you don't have a lot of people that will be able to use this no matter how great it is.

AMD late again too? I thought we were just waiting on BF4 fixes, but it was also AMD still working on Mantle drivers. You can make a great game for the price of MANTLE optimizations just for this one project? $8million? I hope this is just because they mantle'd the crap out of this one game just to show max/best case scenario that you can get, and that this is NOT the normal cost for such a small audience. The Witcher was made for less than $8mil (witcher 2 went to 15mil due to adding consoles). Coding for more crap isn't cheap.
 
What a refreshing comment read on a Sunday morning! No surprises here since reading many posts in the forum there are actually AMD card users that believe that mantle was already integrated in BF4 and working awesome! Even selling the cards to other posters based on that misconception.It will be like all other new technology limited support for 1-2years and will either stay or go away after that.
 


Released? That's funny cause it still has a BETA tag on it. Funny how you couldn't "Work that out". Its not meant for a full release up until around 2015. Until then its just open beta. Tell me again how this free software, which is optional, is a bad thing.
 
I wonder if this new driver will allow me to fold and watch telly at the same time with my 7790?
I hope so, because the current one doesn't, although I can GPU fold on my NVIDIA & watch any video at the same time. Currently, with my MSI 1GB GDDR5 GHz edition, it shows "waiting for idle", though the CPU folds fine with other usage. It's likely that Stanford University (where folding@home originates) will have to make & release the patch themselves. Weird, my Geforce GT 425M with 1GB DDR3 will fold with several pages open, but the MSI 1GB GDDR5 7770 won't, Cat
 
didn't these drivers break the game the moment they rushed it out? Wasn't the publisher EA sued by their investors for this? Or was that just me confusing two stories? I mean I am an NIVIDIA guy and I say AMD does help its users a lot but its odd how glitchy BF4 is.
 


DirectX support in BF4 was never properly installed. There is a DX folder in your game folder where you can run the DX install and it will add the necessary components. Without this, yes the game is very buggy because it doesn't properly use DX 10/11. Most users have never done this and so still say the game is "broken".

I think part of this was probably because it was planned to be an "either/or" situation with Mantle, but it certainly doesn't hurt to have the DX components installed anyway, so I'm not sure why DICE still hasn't changed this.
 
Status
Not open for further replies.