r/WildStar•
Timiniel

Vulkan API and SDK released today - could Carbine/Wildstar benefit?

Hey folks.

For those who don't know, Vulkan is the successor to OpenGL, based around low level optimizations to the draw call and allowing the developer further control over the actual process.

Its impact is seen strongly on games which are capped by the CPU (which wildstar is a great example of).

The Wildstar engine is developed inhouse by Carbine, and this means they are not tied to some external development process on it. This also means that changing such a thing would mean a lot of work for them. However, in return, it is a potential solution to many of the performance issues that plague the game, and would allow for (if the devs properly used the framework) have a visibly better performance in a wide array of machines and OSes.

Here's anandtech's short article on it http://www.anandtech.com/show/10035/vulkan-10-released for those who are interested.

So, should the company take extra work, in its weakened, smaller state, to try and ensure a better future? Is it too late? Are the gains too small to justify the costs? What do you people think ? Is the massive rework too massive for the game? Are the players who quit because of performance completely lost or could they be fished back with the promise of a better performance? How much customer satisfaction would the company gain from the current players being more happy with performance in large scale events/the capital/etc?

DISCLAIMER: THIS IS A DISCUSSION POST. It is not asking Carbine to do anything, not criticizing anything, not meant as anything of the sort what so friggin ever, so don't pretend it is. Last time I made a thread everyone kept trying to treat it as criticism instead of discussion, and if you will do the same here I will delete the thread just like last time.

Posted Feb 16, 2016, 6:41 PM UTC

07
gnoani•

Obviously adding support for Vulkan (and DX12) would reduce the performance impact of the game, but either one would be a large amount of work. They would also add entirely new testing and QA requirements to every future update, and entirely new opportunities for bugs. ("This hotfix breaks Vulkan for some reason, we have to delay it until we figure out why!")

This increase in workload for every update would persist until they decided to drop a rendering method (like DX9).

Is it worth the boost? I don't know.

4
serbaldrig<World Last>•

Would require rewriting basically all of the game code interacting with the CPU/GPU, along with architecture changes to properly take advantage of the capabilities of Vulcan. A lot of work for an unknown amount of gain.

It's also very important to note that Vulcan is currently only supported on Kepler and first and second generation Maxwell based Nvidia GPUs. And here's the AMD side, similar story. So currently Vulcan won't actually help with low end PCs which Wildstar struggles on, but will help with mid to high end PCs where performance is already adequate.

With that in mind, I'd say that it is definitely not worth the time to rewrite enormous portions of the engine to utilize Vulcan.

3†
TiminielOPI craft, therefore I am.•

Ehm, I'm not sure I understand some of your assessments. What do you mean by architecture changes and unknown amount of gain?

We know how effective low-level optimizations are, there have been testes of metal, mantle and dx12, and all are congruent in their results. Vulkan, doing the same thing and even being based on mantle, will get similar results, which are not "unknown".

Not only that but the supported cards are, well, not that limiting. You are definitely wrong here, and for two different reasons:

First, it's not just low end PCs that have poor wildstar performance. All AMD processor machines suffer, be they high or low, and the multi-core capabilities of Vulkan will easy that immensely. You have the tests made on Mantle and DX12 to corroborate that already, the performance increase was immense! The percentage of AMD users is not negligible, and this could be beneficial to them even if they do not have poor machines.

Second, the graphics cards affected are four and a half years old in some cases, and according to the latest steam survey that I saw, they seem to cover more than half of the users. A measure that improves such a large percentage of the playerbase seems odd.

Third, performance being "adequate" is not exactly accurate. The biggest optimizations that Vulkan brings is on the CPU side, not the GPU side, and that is what caps wildstar's performance in, well, dare I say 99% of the cases?

While I too think it might not be worth the time, your premises to justify that conclusion are very inaccurate :... You probably (if you're interested in these things) should refresh your information on this...

-4
das_regal•

A decent Vulcan implementation would be fantastic, the problem is that it's not a trivial task to rework an engine to use a different API. It would take about the same amount of work as porting things between computing platforms, more depending on how much middleware Wildstar uses. With as badly as Wildstar is programmed at current, I doubt Carbine has the talent to even get it done. Vulkan requires mastery of low level programming.

With how the game has performed lately, it probably isn't going to happen. NCSoft isn't going to dump more money into a sinking ship before seeing that it can float again.

3
Cahoots82•

IMO, this is a backburner issue. Far more pressing concerns with the game currently to spend time working on optimization.

1
quicktails•

They better optimize for steam launch. People dismiss optimization as a high end rig problem until they consider how many players they're losing when they can't run or play the game.

1
Geno_DCLXVI•

When is WildStar launching on Steam, by the way?

1