Jump to content
  • Advertisement
  • Remove ads and support GameDev.net for only $3. Learn more: The New GDNet+: No Ads!

  • 02/16/16 08:00 AM
    Sign in to follow this  

    Vulkan Tutorial 1: Introduction to Vulkan on Qualcomm® Snapdragon™ Processors

    Graphics and GPU Programming

    khawk
    • Posted By khawk

     

    Vulkan is the latest graphics API from Khronos and it’s designed to make it easier for developers to use the GPU for greater realism in 3D graphics and greater efficiency in compute applications. Qualcomm Developer Network is introducing you to what Vulkan is, what Vulkan is not, and other things you should know about the new Vulkan API and your graphics development.



      Report Article
    Sign in to follow this  


    User Feedback


    There are no comments to display.



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

  • Advertisement
  • Advertisement
  • Latest Featured Articles

  • Featured Blogs

  • Popular Now

  • Similar Content

    • By glararan
      Hello,
      I am university student. This year I am going to write bachelor thesis about Vulkan app using terrain to render real places based on e.g. google maps data.
      I played World of Warcraft for 10 years and I did some research about their terrain rendering. They render map as grid of tiles. Each tile had 4 available textures to paint (now 8 by expansion WoD) However I found issue about this implementation, that's gaps between tiles. Is there any technique which solves this problem? I read on stackoverflow that guys find only solution in using smooth tool and fixing it manually. Main question: is this terrain rendering technique obsolete? Is there any new technique that replaces this method to render large map as small tiles?
      Should I try to implement rendering terrain as grid of tiles or should I use some modern technique (can you tell me which is modern for you?). If I should implement terrain as one large map to prevent gaps between tiles how textures are applied for such large map?
       
      Thanks for any advice.
    • By LukeCassa005
      I'm writing a rendering system for our in-house game engine. My idea at first was to include only a Vulkan backend,but then Apple refused to port vulkan to MacOs and Microsoft relased their DXR raytracing for DirectX12. There is stil Radeon Rays for vulkan, but DXR is directly integrated with the graphic API. So we were thinking of a multiple backend rendering system with Vulkan for windows and Linux, Directx12 for Windows and Metal2 for MacOs. But this system would lead to an incredible amount of code to write than a single API, so my questions were:
      Should we stick to a Vulkan and maybe use a translation layer like MolteVk to port it to macOs ? Is it worth tl write the multiple APIs renderer ? Should we write a different renderer for each platform and then ship separate executables ? (Sorry for possibly bad English 😁)
    • By FusionDev


      I have been coding since the 90's, and have released a few minor succesfully 3D engines over the years, Vivid3D/Trinity3D/Aurora - Probably not heard of them, but I am quite skilled in the concept.

      So upon the announcement of RTX cards and their features, I was highly motivated to create a modern 3D engine, in C++(Visual studio 2017) using Vulkan. Atm I have a GTX 1060 - which is v.fast and is more than enough to build the base engine. In a few months I'll be getting a RTX 2070 to implement raytracing into the engine etc.

      The engine has only been in dev for a week or so, but it already has a basic structure, using classes. It will be a easy to use 3D engine, with support for model imports using AssImp.

      So my point is, I am looking for any other Vulkan coders, who might be interested in helping develop the engine? The code is on GitHub - open but I can make it private if we decide to commercialize the engine to make money/support futher development.

      I want to make a Deus Ex like mini-game to test and promote the engine, so you can help with that too, even if you are a 3D artist and interested, because I am just a coder atm. 

      So yeah, if anyone is interested pls drop me a email or reply here, and I'll add you to the gitHub project(I'll need your github username)

      Note - a C# wrapper is planned also, if you are a c# coder and would like to help with that, demos/wrapper etc, that would be very cool.   My email is antonyrwells@outlook.com

      Thank you.
    • By swiftcoder
      Folks continue to tell me that Vulkan is a viable general-purpose replacement for OpenGL, and with the impending demise of OpenGL on Mac/iOS, I figured it's time to take the plunge... On the surface this looks like going back to the pain of old-school AMD/NVidia/Intel OpenGL driver hell.
      What I'm trying to get a grasp of is where the major portability pitfalls are up front, and what my hardware test matrix is going to be like...
      ~~
      The validation layers seem useful. Do they work sufficiently well that a program which validates is guaranteed to at least run on another vendor's drivers (setting aside performance differences)?
      I assume I'm going to need to abstract across the various queue configurations? i.e. single queue on Intel, graphics+transfer on NVidia, graphics+compute+transfer on AMD? That seems fairly straightforward to wrap with a framegraph and bake the framegraph down to the available queues.
      Memory allocation seems like it's going to be a pain. Obviously theres some big memory scaling knobs like render target resolution, enabling/disabling post-process effects, asset resolution, etc. But at some point someone has to play tetris into the available memory on a particular GPU, and I don't really want to shove that off into manual configuration. Any pointers for techniques to deal with this in a sane manner?
      Any other major pitfalls I'm liable to run into when trying to write Vulkan code to run across multiple vendors/hardware targets?
      ~~
      As for test matrix, I assume I'm going to need to test one each of recent AMD/NVidia/Intel, plus MoltenVK for Apple. Are the differences between subsequent architectures large enough that I need to test multiple different generations of cards from the same vendor? How bad is the driver situation in the android chipset space?
    • By Enitalp
      Hi
      I'm searching for a good implementation of Vulkan in C#, Don't need to be the fastest as it's for an Editor, but i need the most complete and most active one.
      Saw a few ones but with no update in the past 5 months. Don't want to implement a "dead" library as my usage is for the next 3/4 years.
      Any idea ? thanks
       
  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!