StarCraft II and Star Citizen. There are developers who are adamant they won't dumb down their games just to cater to the lowest common denominator: consoles.

The sad thing is, PCs have been on the receiving end of poor console port, and PC gamers are fed up of it. We shouldn't be accepting these piss poor creations and adjust our specs (or influence our GPU purchasing decision for that matter) to cater to this.

I dont mind games going to consoles first, because they're faster to be developed based on a single spec sheet, before they go PC (which have to handle multitude of differing specs). Case in point: GTAV. I refuse to play the inferior console version and waited that 6 months long to play the PC version, and it was worth it. That was a PC game done right, not a PC port.

I dont get it either. I need Windows 10 to run Killer Instinct, Quantum Break and Gears of War Ultimate Edition. And I use Nvidia cards. While these AMD fanboys champion DX12 and yet they dont even run DX12-related games, only citing "future-proofing" as their excuse. They still run CS:GO or DOTA or whatever simpler games that does not even need DX12 to run at all, nor are they graphics intensive. Go figure!

Are they waiting for the "magic DX12 driver" that's gonna turn their mediocre cards into 980Ti or Titan X, that finally allows them to play Rise of The Tomb Raider beyond 1080p at acceptable framerates in two to three years later? Since it's "future proof" and all.

DOOM just released its Vulkan API support via Steam. New update is live to patch the game to select between OpenGL and Vulkan. Gonna see how it works on my rig.

ADDENDUM: Finished replaying the Foundry level, my favorite. I am well aware of the performance of my 1080 card at specific locations in the game, and unless this is placebo effect, I'm getting minimum 60fps upwards even on enemies infested locations, a steady 80++fps, and I swore loudly when I saw a few 100fps. Card is GTX1080FE OCed to 2012Mhz core 10800Mhz memory. While before on OpenGL, it was drops to upper 40s (48-49), steady 50s and spikes up to 80fps on certain locations. Gonna replay this back in OpenGL to see if this was true, or if it was simply driver optimization across the board for the game, irregardless of OpenGl or Vulkan. By the way, I'm playing on 4K Ultra settings.

This post has been edited by stringfellow: Jul 12 2016, 12:01 AM

If you say so. I'm getting performance bump on my rig. This whitepaper does say Vulkan being supported on Nvidia cards. Funnily they only mention support up to 900 series. https://developer.nvidia.com/Vulkan

Replayed the Foundry level back on OpenGL4.5, yup, the bump is there previously on Vulkan. I'm getting 95 where I'm supposed to get 100, and steady 70 instead of the 80s on Vulkan. The steady 50s was what I remembered when I finished Doom last month, they're really done well on even the OpenGL side of things.

Enough of this. Playing INSIDE now.

This post has been edited by stringfellow: Jul 12 2016, 12:23 AM

Okay, I've replayed the Foundry level again for 3 more times going back and forth with OpenGL and Vulkan, and I'm going to bed now.

Generally no difference between OpenGL and Vulkan on my GTX1080, or if there is, it's pretty much in the margin of errors. There was a difference a month back when I finished my Doom run and moved on, but there are no difference between OpenGL and Vulkan on it. If AMD cards are improving, congratulations on them, iD is working with Nvidia to get their version of Async Compute to work. Until then, I couldn't be more happier with steady 80fps with drops to 70s and highs of 100s on 4K at Ultra.

No thanks. I've never gone AIB in my life and am not gonna start now. Fat cards are no go. These cards may look fierce and "sexy" to the average teenager, but to me they look garish and unrefined. The Apple DNA in me wants minimalism. Plus the fact that the FE blows hot air out of the case. The last "FE" that I had that blew hot air INTO the case was the GTX690, and I am not gonna have my case internals "cooked" that way again.

Those with Pascal cards and VR headsets.



Nvidia's VR Funhouse is out. #PlayMoreGames

3DMark Time Spy Benchmarking Utility is out. Update your 3DMark app on Steam.

Results from Time Spy 3DMark DX12 benchmarking on my GTX1080, running at 2012Mhz core 10800 memory and 4.8Ghz 4790K.

An obvious AMD fanboy himself, the video maker. He's asking people to take the 1060 as "not the MSRP price of USD249", and instead be more realistically priced at USD270-280, but he kept referring to his own RX480 at USD199, when 4GB cards are extremely limited in quantities and/or have sold out/out of production, and folks are more likely to get the USD239 8GB version or the AIB version priced at 249 Pound Sterling like the Sapphire Nitro.

A shill is a shill.

This post has been edited by stringfellow: Jul 16 2016, 10:35 AM

Solution:


This post has been edited by stringfellow: Jul 18 2016, 04:53 PM

Made safer for prude workers with prude bosses: add spoilers.

This post has been edited by stringfellow: Jul 18 2016, 04:54 PM

GTX1080 at 2.1Ghz core clock isnt a myth, gents. It's just hard to get at stable.

Got mine up to 2100Mhz core, 11010Mhz memory, with highest temperature at 78C.





And the corresponding Heaven benchmark score.



This post has been edited by stringfellow: Jul 19 2016, 02:12 PM

He could've just finished a benchmark run, and the card is cooling off with zero/little load.

Personally to me, as long as the card runs below 82C and not throttling, I'm not complaining. If I'm running water and I get these results, then I'll just add teabags into the reservoir and have myself some cakes with my tea.

If that's the lowest, then you have a problem. If it's a "current" temperature readout, it could be many different scenarios unless you're already idling a long time and the temp hasn't budged.

Evaporated too fast to make any good tea.

Like I said, there are many scenarios. Custom fan curves, cards cooling down, stuffy case internals with poor airflow. It's up to the person to evaluate and it's more accurate for the user facing the situation to evaluate since he knows what kind of ambient temperature he's living in.