# OpenGL [Design Hiccup] Particles and Transform feedback

## Recommended Posts

I am currently trying to finish up my particle system. The core of it is built, but I keep running into a major hiccup!

For my system I am targeting OpenGL 3.3 and using transform feedback in order to create a State Particle System.

Each of my particles in this current point in time have the following attributes: Current Position, Deviation from the Starting Position, Velocity, Starting Velocity, Acceleration, Current Lifetime, and Lifespan (starting lifetime). In addition to this, each particle is to be represented as a quad and have texture coords for their image.

My hiccup or major block comes in with the transform feedback and the output varyings.

In my particle update area, my transform feedback is using GL_POINTS to iterate over each particle where it outputs the new velocity, acceleration, etc. The major drawback/part in this update is that one run of GL_POINTS (one particle update) will output 4 positions (one for each corner of a quad). I do this to prevent floating point discrepancies between the positions, since they should be all the same and a single difference means I get a graphics glitch. After everything is said and done my VBO ends up looking like:

//All particle data is stored in the same buffer
//Particle1                                                                 //Particle2
[Position1, Position2, Position3, Position4, Velocity...][Position1, Position2, Position3, Position4, Velocity...]


My mega block / kicker

My hiccup comes in right here. While I can update the buffer above perfectly, the other major thing I need to do is read it for rendering.

This is the part I cannot seem to get down. Due to the VBO's data and its makeup, my shader cannot properly read in the data. It gets confused and ends up using a Velocity, Acceleration, etc as a position causing my particles to get rendered incorrectly

I thought about just having extra dummy data in my VBO, so that my Vertex Pointers would see my VBO data correctly.

Basically I decided to pad the attributes other than position:

//All particle data is stored in the same buffer
//Particle1                                                                                                                                                         //Particle2
[Position1, Position2, Position3, Position4, Velocity, DummyVelocity1, DummyVelocity2, DummyVelocity3...][Position1, Position2, Position3...


But I get left hooked by my transform feedback, since output varyings can only write the exact way they are configured and have no ability to offset or skip certain blocks of data. My attributes run over each other when updating, making me run into the same problem above.

I thought to combat this I could just write more/double up on my output varyings. But I get right hooked by the GL_MAX_TRANSFORM_FEEDBACK_INTERLEAVED_COMPONENTS limit as I easily am already close to the maximum.

Once I start using texture coords or even if I decide my particles need another attribute I will go over the max. Making this solution a no go

Now, I'm left kind of in the dark as to what to do. I thought about doing a double update pass, where I run though my "non render attributes" and update them, outputing the results to a VBO. Then running a secondary update, using results from the first update to update each particle's position and the output from this update would go to a third buffer and get used in the render. Something like:


//First pass: updating the velocity, acceleration, etc. Uses its own varyings
glBindBufferBase(GL_TRANSFORM_FEEDBACK_BUFFER, 0, nonRenderVBO);
glBeginTransformFeedback(GL_POINTS);
glDrawArrays(GL_POINTS, 0, particleCount);
glEndTransformFeedback();

//Second pass: updating the positions. Uses its own varyings
glBindBuffer(GL_ARRAY_BUFFER, nonRenderVBO);
glBindBufferBase(GL_TRANSFORM_FEEDBACK_BUFFER, 0, positionVBO);
glBeginTransformFeedback(GL_POINTS);
glDrawArrays(GL_POINTS, 0, particleCount);
glEndTransformFeedback();

/*Later on: use the positionVBO in my render method*/



BUT I feel like this is a very horrible idea / poor solution.....

Any ideas on what I could do so I can get over this roadblock? Any help would be appreciated

Edited by noodleBowl

## Create an account

Register a new account

• ### Forum Statistics

• Total Topics
628378
• Total Posts
2982334
• ### Similar Content

• 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?

• 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.

• 10
• 9
• 15
• 24
• 11