Sign in to follow this  
Freddy Indra Wiryadi

OpenGL How long does it take to learn Particle Rendering with DX11 Compute Shader without prior DX experience ? (Other necessary information provided inside)

Recommended Posts

Hello, I am new to DirectX (never touched directX) and currently I am going to start my Bachelor Thesis, which is to render a particle systems with dx11 compute shader (C++) and test the performance advantage of it. rolleyes.gif

My related prior experience:

- C++ language

- learning the very basic stuffs of OpenGL & Computer Graphics

- creating simple 3D strategy game with C++ & DarkGDK + Lua

- creating 3D FPS game with Unity3D

- creating simple 2D HTML5 Game with javascript

- playing around with game development/game programming (the high level approach)

 

I seldom go low level like directX, now I want to try it, and I really need your information, biggrin.png

do u guys think I can manage to finish it in around 3-4 months ? (for my bachelor thesis) cool.png

 

What's the approximated time to learn rendering a moderate particle systems with dx11 compute shader ? blink.png  (based on my prior experience stated above)

 

I heard that Compute Shader is on advance category, is it that difficult ?

 

Really appreciate your help laugh.png

Edited by Rayphoenix

Share this post


Link to post
Share on other sites

That's really hard to tell without knowing how good in learning you are. I would bet some people could do it in a week (or course not the whole thesis, just to learn and make a working simple compute shader particle system). And many people wouldn't learn it in years.

Also, how flexible/universal should the system be? Is it supposed to have some kind of configuration (via a dialog or some "script" file) for different kinds of particle behaviour and appearance (flames, rain, show, smoke, sparks, missile trails etc)?

And against what are you planning to compare the performance advantage? Against a CPU particle system?

Edited by Tom KQT

Share this post


Link to post
Share on other sites

That's really hard to tell without knowing how good in learning you are. I would bet some people could do it in a week (or course not the whole thesis, just to learn and make a working simple compute shader particle system). And many people wouldn't learn it in years.

Also, how flexible/universal should the system be? Is it supposed to have some kind of configuration (via a dialog or some "script" file) for different kinds of particle behaviour and appearance (flames, rain, show, smoke, sparks, missile trails etc)?

And against what are you planning to compare the performance advantage? Against a CPU particle system?

I am not going to use any external script in this case.

Yeah, comparing it with general particle systems which is computed by the CPU.

Share this post


Link to post
Share on other sites

Hm, really hard to say, but it is doable IMHO. Particle systems are not SO complicated, it's not a whole rendering engine.

I seriously think that you COULD make a first working prototype in like two weeks if you really wanted. And then have time to improve it and make those performance tests.

 

But maybe I'm too optimistic :) Also it depends on how much time do you have, if you have only evenings after school, it may be harder.

Share this post


Link to post
Share on other sites

Hm, really hard to say, but it is doable IMHO. Particle systems are not SO complicated, it's not a whole rendering engine.

I seriously think that you COULD make a first working prototype in like two weeks if you really wanted. And then have time to improve it and make those performance tests.

 

But maybe I'm too optimistic smile.png Also it depends on how much time do you have, if you have only evenings after school, it may be harder.

I think I would have around 4-6 hours effective time per day. I am quite hesitant whether it's enough to finish everything in time, but I really want to do this for my thesis (instead of some other potential topics that came up in my mind).

 

Hopefully I can create particle systems that's not too complex utilizing compute shader, but sufficient enough for performance test.

Thx for your opinion happy.png

Share this post


Link to post
Share on other sites

It sounds like an interesting topic.  Of course, everyone learns at a different rate, but if you already understand the basics of C++, then the main things you need to get up to speed on are the following:

 

1. Usage of Direct3D: This is a big topic if you need to learn every nook and cranny of the device context.  Since you are looking for performance advantages, I assume you do indeed want to know all about it...

2. Usage of Compute Shader: The mechanics of learning the compute shader are not so difficult.  You can get the concept in one day if you have a good reference.  The trick is trying to find the best possible memory layout and usage and the corresponding threading model to go with it.

3. Making the particle system on the GPU: That is what it is all about :)

4. Implementing the same thing on the CPU: That is also a whole other problem, with CPU architectures to worry about.

 

Overall, it seems like a pretty big task, but it should be possible for a thesis.  Of course, if you have questions you can always post them here and people are generally very helpful.

Share this post


Link to post
Share on other sites

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

Sign in to follow this  

  • Announcements

  • Forum Statistics

    • Total Topics
      628359
    • Total Posts
      2982259
  • Similar Content

    • By test opty
      Hi all,
       
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
       
       
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Thanks, 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
       
       
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
      Thanks!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
      Thanks.
  • Popular Now