aboutsummaryrefslogtreecommitdiff
path: root/src/shader
AgeCommit message (Collapse)Author
2018-12-19Extract equilibrium functionAdrian Kummerlaender
2018-12-19Loopify density functionAdrian Kummerlaender
…seems to be correctly unrolled during compilation. Or at least no performance impact is visible.
2018-12-19Use GLSL's mix function for color scalingAdrian Kummerlaender
2018-12-19Tidy up external influence implementationAdrian Kummerlaender
2018-12-18Hacky mouse-based fluid interactionAdrian Kummerlaender
2018-12-18Use pressure as velocity norm display amplifierAdrian Kummerlaender
2018-12-18Purify collide shaderAdrian Kummerlaender
i.e. move fluid vertex placement to appropriate vertex shader. Do not amplify or shift fluid moments in any way prior to passing it to the display pipeline.
2018-12-17Clean up stream and collide compute shadersAdrian Kummerlaender
2018-12-17Try out velocity norm color mappingAdrian Kummerlaender
2018-12-16Filter weird origin vertexAdrian Kummerlaender
The same thing occurs in computicle. I suspect some initialization / compute shader invokation problem. On the other hand: Why would that happen for the origin vertex and not e.g. the first or last vertex in memory? To be investigated further.
2018-12-16Generate fluid display using geometry shadersAdrian Kummerlaender
This should provide much more flexibility. For our purpose it would be useful if the vertex shader was executed after the geometry shader (to apply the projection matrix) but alas this is not the case. Thus the MVP matrix is applied during geometry construction and the vertex shader only provides density extraction.
2018-12-16Regeneralize ComputeShader wrapperAdrian Kummerlaender
2018-12-16Parametrize lattice resolutionAdrian Kummerlaender
2018-12-15Hacky D2Q9 BGK LBM on GPU using GLSL compute shadersAdrian Kummerlaender
Improvised on top of computicles's scaffolding. Works in a world where _works_ is defined as "displays stuff on screen that invokes thoughts of fluid movement".