in development Vulkan API Discussion

So when should we expect Vulcan then? The usual two weeks? Joking aside, ED's total silence on this is killing me

ED stated last year that a pre-requisite was an update to textures.

My guess is that includes not only the terrain, but also all vehicles, AI and playable. I believe that to be the reason for the recent warbird visual update and the ones planned for the KA50, A10 and similar.

As we have no timelines for the above, probably fair to assume months rather than weeks.

ED stated last year that a pre-requisite was an update to textures.

My guess is that includes not only the terrain, but also all vehicles, AI and playable. I believe that to be the reason for the recent warbird visual update and the ones planned for the KA50, A10 and similar.

As we have no timelines for the above, probably fair to assume months rather than weeks.

Wish they would let the fans help out recreating the textures/sounds, outsource that stuff!.

Wish they would let the fans help out recreating the textures/sounds, outsource that stuff!.

A formula for uncontrolled, unaccountable chaos!

A formula for uncontrolled, unaccountable chaos!

AMEN.

ED stated last year that a pre-requisite was an update to textures.

My guess is that includes not only the terrain, but also all vehicles, AI and playable. I believe that to be the reason for the recent warbird visual update and the ones planned for the KA50, A10 and similar.

As we have no timelines for the above, probably fair to assume months rather than weeks.

Well, not really, the engine uses PBR, which is a Standard across all PBR Enabled Renders.

The old models are getting updates, because they are in need of them, to keep them on the same quality level as the new modules.

Things need changed on the Textures and Shaders, but not the way you are thinking.

Wish they would let the fans help out recreating the textures/sounds, outsource that stuff!.

Not gonna happen.

Things need changed on the Textures and Shaders, but not the way you are thinking.

Is this for better or for worse? Any clue on why the devs just won't give us an update on this?

Because there is nothing to tell? Mostly a sign priorities have shifted.

How do you showcase lines of code being written? or individual parts of something larger?

Does it really matter whether Vulkan is being released now or in 9-18 months? It will not be a magic bullett, rather one part of many engine improvements and in concert with a gradual move to more multi-threading of the various components, this is how i see it play out. Its not about getting a one-off fps bump, which would be nice though. Rather, it's about getting the engine to a state where it can take advantage of all that parallelsim that is coming in the hardware space. Vulkan will just be one aspect of this. And probably an important one. We've got 8-16 cpu cores in the consumer space, and in the not too distant future we will probably see MGM gpu designs. And for that we need a proper and clean Vulkan implementation.

How do you showcase lines of code being written? or individual parts of something larger?

I dunno, some other guy suggested that razbam get live cams so that we can see that they are working hard :music_whistling:... I keeed... I keeed...

But on a more serious note in an update that its still the plan would be nice.

are you waiting to purchase hardware for it?

I been playing a game with Vulkan API on, World War Z and everything on Ultra TAA, and it runs way smoother and much cooler on the CPU and GPU.

You would also have to play it on directx as comparison, to really know know what's going on.

With Battlefield 4 you had a ingame option to switch api and on my old core 2 quad with hd7750 it was really noticable smoother with vulkan (mantle).

"Wolfenstein II The new colossus" was really looking awesome and I could run it with everything maxed out on my fx8350 with rx580 at ~60 FPS, which I couldn't with any game at that time. Later I found out it uses Vulkan.

Sure these games have nothing to do with DCS, but I think it's a good indicator

You would also have to play it on directx as comparison, to really know know what's going on.

With Battlefield 4 you had a ingame option to switch api and on my old core 2 quad with hd7750 it was really noticable smoother with vulkan (mantle).

 

"Wolfenstein II The new colossus" was really looking awesome and I could run it with everything maxed out on my fx8350 with rx580 at ~60 FPS, which I couldn't with any game at that time. Later I found out it uses Vulkan.

 

Sure these games have nothing to do with DCS, but I think it's a good indicator

I think he mentioned it because the Vulkan API is a recent addition to that game.

You would also have to play it on directx as comparison, to really know know what's going on.

With Battlefield 4 you had a ingame option to switch api and on my old core 2 quad with hd7750 it was really noticable smoother with vulkan (mantle).

 

"Wolfenstein II The new colossus" was really looking awesome and I could run it with everything maxed out on my fx8350 with rx580 at ~60 FPS, which I couldn't with any game at that time. Later I found out it uses Vulkan.

 

Sure these games have nothing to do with DCS, but I think it's a good indicator

it has both Vulkan and directX 11. Runs smoother on Vulkan. and a lot cooler.

I dunno, some other guy suggested that razbam get live cams so that we can see that they are working hard :music_whistling:... I keeed... I keeed...

 

But on a more serious note in an update that its still the plan would be nice.

Dev : *clack clack clack*

Voice from baby monitor mounted above desk : You forgot to close that syntax line.

Dev : *silence*

Developer update?

We are approaching mid-year now, any comment from the devs on the progress of the Vulkan implementation and what we can expect to see? Really appreciate all the hard work that is being done in DCS and understand why things move slowly, only looking for an update and a comment on performance/improvements with Vulkan more than a time frame. Well, maybe a rough time frame :smilewink:

Rough time frame you ask, rough you get. Anything from "now" until "its done", inclusive.

We are approaching mid-year now, any comment from the devs on the progress of the Vulkan implementation and what we can expect to see? Really appreciate all the hard work that is being done in DCS and understand why things move slowly, only looking for an update and a comment on performance/improvements with Vulkan more than a time frame. Well, maybe a rough time frame :smilewink:

Honestly I'm hoping next year and thats more of a "hope" than a realistic guess. I'm "hoping" we see the VR improvement in the next 3 months.

Honestly I'm hoping next year and thats more of a "hope" than a realistic guess. I'm "hoping" we see the VR improvement in the next 3 months.

I'm on the same trajectory. Lot of shaders to touch for Vulkan. So yeah, VR update in 3 months, and Vulkan rollout Q1 next year.

https://www.khronos.org/events/vulkanised-is-back

14:45 - 15:30 – Optimising a AAA Vulkan Title on Desktop (Lou Kramer, AMD)

wags,

is the team still at work on Vulkan or is it on hold?

Probably not, they wouldn't invest in something like that only to stop in the middle, the last update was about the shader stuff, that's a large part.

Probably not, they wouldn't invest in something like that only to stop in the middle, the last update was about the shader stuff, that's a large part.

The best laid plans of mice and men often go awry.

Unforeseen things can happen in the course of a project, the respective engineers can quit or, god forbid, worse. Other projects can take precedence, requiring a shift in ressources. Basically, everything can happen. That's not even factoring in hitting unforeseen roadblocks which is common when switching to different technologies, especially complicated ones like the graphics API.

But it's their job to build a good game? Especially one that keeps evolving into a bigger product day after day. I don't see how that's an excuse. "X can happen and Y may be a problem". It's their responsibility to calculate/foresee at least some of these errors. My boss won't give a toss if I'm late for work tomorrow, why should we keep cutting slack of off ED's terrible coding?

They will never, NEVER stop working on upcoming money-maker modules like the F-16 and take a better look at the existing product until their customers say something about the current state of the game. I wish them the best of luck and that they have taken my thoughts (that are shared by many members in this community) seriously and keep their head down after the F-16 comes out.