I'm waiting to see the implementation that is rumored to come in the Win10 release. If they make it part of the API and find a way to handle most of the CPU/multi-core scaling inside so that developers don't have to code that themselves, that WOULD be a game changer. But if it requires anything for the developers to do to take advantage of that, even if it's a new parameter, expect it to take some time for full adoption.
I've been seeing the commercials for this for months in Japan, hope it does make its way out west.
I think he's right. What I saw last year at CES I'd be willing to pay for (and believe that's what's in DK2)
Haven't seen anything yet...
I look at it from a package or project perspective. Before I move ANYTHING into implementation it undergoes an end-to-end test that should test all functionality as if it is in production. If they're doing these tests 90% of the issues we're seeing should have been caught and fixed. I lump a lot of the 10% like Destiny's KTO issues - ones which simply may have been too hard to catch during testing.
That's why I point my finger at whoever signed off on the pr...
Avoiding release day as a sole action will tell publishers they can still take advantage of gamers, we'll pay and pay what they ask. What other software - or even hardware for that matter - would you ever let that slide?
Was told it had to be that way, will adjust it.
Jason had no direct involvement in this piece, was not aware of it, and the only influence he had on it was the hashtag during a private discussion that happened to fit into the FB post that I was originally writing this for and then decided to expand upon that.
We do collaborate on things still since he was one of two that co-founded the site and we have kept in touch since.