in development Vulkan API Discussion

Unfortunately I see mainstream VR going the other way, for them the current PPD seems good enough and the focus for many is better FOV for more "presence" and raising the bar hardware wise means fewer customers.

Yes, this is because increasing the fov is the simplest and least expensive thing, obviously without considering the deformation of the current lenses, the CA and etc ... So they start first to sell this then slowly integrate high ppi screens and fovrendering, then I believe that unfortunately the improvement of lenses will take place as the last thing.

there seems to be technology already

https://www.tomshardware.com/news/nanotech-metalenses-virtual-reality-augmented-reality,36216.html

I see that HP are touting a new headset with something like 2k * 2k resolution, implying that not all manufactures are shooting at the lower end of the market. Add in eye tracking to facilitate foveated rendering and allow us to move the pixels and things are looking rosy.

we will see, seeing the ridiculous cost of the Xtal, which does not seem great to me, I think that hp vr would be a step forward. Xtal currently at that price is blocking the market.

They are already on it. Using Vulkan that is.

Are they working on the engine as we speak? Or is Vulkan already implemented into the current engine? I was under the impression that DCS was on a really old outdated engine and the switch to Vulkan would be a game changer. I don't notice a difference at all since I started playing it.

Are they working on the engine as we speak? Or is Vulkan already implemented into the current engine? I was under the impression that DCS was on a really old outdated engine and the switch to Vulkan would be a game changer. I don't notice a difference at all since I started playing it.

The last update (a few months ago now) was that the engine was Vulkan capable. However the real work of migrating the shaders was starting. So again, I wouldn't expect to see it anytime (too) soon.

I never expected this thread to reach so many pages, I'm impressed.

Would be even cooler in future if there's some kind of feature that DCS would need in graphics that vulkan doesn't have, ED can simply go to the github and request changes/extension.

For something like visually-physically correct sim, thing would probably need to be done differently under the hood than traditional FPS games the industry was built upon where real physics are nonexistent.

Has the Vulkan api proven to improve VR performance in any other games/sims? I keep hearing conflicting wishful thinking. I've heard it should improve VR experience a lot, but I also hear that it's not a guarantee that it will.

Not by itself, but it makes it easier to implement multi-threading.

Has the Vulkan api proven to improve VR performance in any other games/sims? I keep hearing conflicting wishful thinking. I've heard it should improve VR experience a lot, but I also hear that it's not a guarantee that it will.

Go read the comments about it's use in FS2.

That other sim claims to be gpu bound. Seems dubious.

But I’ll clarify anyway; maybe a modest improvement by itself.

But we still need multi-threading.

If we assume the ED is moving to Vulkan for reasons beyond S&Gs, then it only makes sense that 1 of 2 reasons would be logical. Either there is a performance benefit, or they want broader platform support. DCS as a whole is multi-threaded, however the excess threads are primarily being leveraged for IO operations (loading assets). D3D11 is always limited (without crazy amounts of work) to the order of operations in the main thread leaving the least amount of time for the thread to forward rendering tasks to the GPU. With Vulkan (and Dx12) the option is there for render related requests to be handled asynchronously. That means this get sent to the gpu without waiting behind everything else behind the main sim thread.

Has the Vulkan api proven to improve VR performance in any other games/sims? I keep hearing conflicting wishful thinking. I've heard it should improve VR experience a lot, but I also hear that it's not a guarantee that it will.

It should improve everything across the board, VR will always perform worse than a monitor as long as the workload is bigger.

Peak peformance also depends on the optimization of graphical features and shaders that were written for Vulkan or converted. Initially it is expected it may not be as optimized as a previous mature API.

with adding Vulcan support, I suggest to retain the DirectX 11 and upgrade it to DirectX 12. Add dual rendering configuration support to allow user to switch between Vulcan or DirectX.

 

Vulcan vs DirectX 12:

 

Vulcan with deferred rendering:

 

my gameplay video on current release version: https://www.youtube.com/user/jokeracts :thumbup: :D

That vulkan vs dx12 benchmark video is from 2017.

Above are my results on the specs in sig of that same exact benchmark done today. 3dmark cost me like $5USD during a sale i think.

Vulkan is completely fine by me vs dx11 and older. I'm also fine with DX12 because I'm already using 10 and i thought i read somewhere in these forums that win7 was getting dx12 support recently, but vulkan does come with the peace of mind that it's not tied to any specific version of Windows and I fully support that.

My PC isn't built specifically for DCS, so their choice of vulkan over directx only helps in that it can be a substantial performance increase over dx11. But I have no qualms with ED doing it differently than the market trends, as in the long run, until MS abandons the idea of limiting directx versions to specific versions of windows, adoption of vulkan in the development community is honestly the more customer friendly move.

DX12 API is now supported on Windows 7,

However Vulkan has superior object management.

Besides, Vulkan being developed and supported by an industry consortium and not just one company is major plus in my book.

Vulkan update?

Been a while since we heard something about Vulkan api. Any info about it and how it would affect performance nonvr and vr?

Been a while since we heard something about Vulkan api. Any info about it and how it would affect performance nonvr and vr?

Give it another 2 to 5 years. Maybe 1-2 if we're *really* lucky (and you don't mind a really buggy, half-finished pre-alpha Open Alpha.)

This stuff isn't happening overnight--it's insanely effort-intensive, and ED have to spend most of their time and effort doing something that could make them enough money to stay in business :)

As for how it affects performance, well obviously it should improve it! Otherwise, why bother? :)

AD

There is a long thread already about Vulcan API here

https://forums.eagle.ru/showthread.php?t=217784

Post from Skatezilla on Vulcan progress:

https://forums.eagle.ru/showthread.php?p=3848803#post3848803

Post from Skatezilla on Vulcan progress:

https://forums.eagle.ru/showthread.php?p=3848803#post3848803

The Last update on Vulkan is that the Base Engine was Complete, and work had started on Converting all of the Shaders and textures to the new API

Wow, looks like Vulkan might come earlier than a lot of people feared...

Wow, looks like Vulkan might come earlier than a lot of people feared...

No one Fears Vulkan..

No one Fears Vulkan..

....but the Reaper, now that's a whole different story! Or should I say a different song! :D

No one Fears Vulkan..

:thumbup:

nVidia has this in their GameWorks Software Suite for almost a year already as well.

Question

Does this mean there will also an update to the nVidia profile for DCS? The current nVidia profile is from April 23, 2009(coming up on 10 years). Still thinks we are on DX9 as well as Geforce Experience does not pick up DCS World being installed.

Question

Will DCS be adding nVidia Gameworks Software Suite?

The Last update on Vulkan is that the Base Engine was Complete, and work had started on Converting all of the Shaders and textures to the new API

Question

Once the Vulkan API is implemented, will DCS still use Deferred Shading or will DCS use Forward Rendering?

Happy Simming,

Monnie

:thumbup:

 

 

 

Question

Does this mean there will also an update to the nVidia profile for DCS? The current nVidia profile is from April 23, 2009(coming up on 10 years). Still thinks we are on DX9 as well as Geforce Experience does not pick up DCS World being installed.

 

Question

Will DCS be adding nVidia Gameworks Software Suite?

 

 

 

 

Question

Once the Vulkan API is implemented, will DCS still use Deferred Shading or will DCS use Forward Rendering?

 

 

Happy Simming,

Monnie

Its up to nVidia to male a new profile

No DCS will not use Game Works

Likely Deferred.

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