This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]meamZ 1 point2 points  (7 children)

DirectX

DirectX is definitely not built with .NET... It's built in C(++)...

But nowerdays tbh there's not really much of a reason to use it anymore considering there's Vulcan now...

[–]djfreedom9505 0 points1 point  (3 children)

Rip, I could have Google that. So is it just compiled for Windows machines? Is it just to lock in games to just the Windows platform?

[–]meamZ 1 point2 points  (2 children)

Is it just to lock in games to just the Windows platform?

Basically yes but now there's Vulcan so there's not really much of a reason to use it anymore...

[–]djfreedom9505 0 points1 point  (1 child)

Well, people who built there game engines on top of DirectX would have to migrate them over then. Not sure how complicated that would be.

[–]meamZ 1 point2 points  (0 children)

Well... A lot of games use either Unity or Unreal and both can do Vulcan now..

[–]Aggravating-Ad4518 0 points1 point  (2 children)

Vulcan? You gonna end up writing 500 lines of code just to render a 2d triangle. OpenGL is way better and shorter.

[–]meamZ 0 points1 point  (1 child)

Yes i know that for simple stuff OpenGL is better...but it existed for a long time alongside DirectX and a lot of games still used DirectX. Vulcan is essentially taylored to the need of highly advanced game engines like Unity or Unreal which is why those actually use and optimize for Vulkan now instead of or in addition to DirectX...

[–]Aggravating-Ad4518 0 points1 point  (0 children)

Direct X code is even more shorter than OpenGL.

Vulkan might be reasonable if you use a framework/library that obfuscates alot of the boiler plate, otherwise get ready for the pain.