Project

General

Profile

Statistics
| Branch: | Revision:

library / src / main / res / raw @ e979d285

Name Size
blit_depth_fragment_shader.glsl 2.16 KB
blit_depth_vertex_shader.glsl 2.43 KB
blit_fragment_shader.glsl 2.08 KB
blit_vertex_shader.glsl 2.1 KB
main_fragment_shader.glsl 5.79 KB
main_vertex_shader.glsl 9.11 KB
normal_fragment_shader.glsl 1.89 KB
normal_vertex_shader.glsl 1.93 KB
oit_build_fragment_shader.glsl 4.71 KB
oit_clear_fragment_shader.glsl 2.89 KB
oit_collapse_fragment_shader.glsl 3.25 KB
oit_render_fragment_shader.glsl 3.73 KB
oit_vertex_shader.glsl 2.64 KB
preprocess_fragment_shader.glsl 2.13 KB

Latest revisions

# Date Author Comment
e979d285 04/25/2020 12:18 AM Leszek Koltunski

Add the first two VERTEX 'pseudo-matrix' effects: VERTEX_MOVE & VERTEX_QUATERNION i.e. implementations of those two MATRIX effects in VERTEX queue.

The point(s):

1) preparation for the upcoming MeshBase.preApply(VertexEffect effect) API that's going to supersede the current much more limited MeshBase.apply(MatrixEffect effect)...
b35570ad 03/04/2020 10:54 PM Leszek Koltunski

Minor.
Looks like MeshBase.join() actually works.
23b733db 03/03/2020 10:31 PM Leszek Koltunski

Further corrections.
7602a827 05/02/2019 10:41 PM Leszek Koltunski

Rename all the classes that are not exported to application to 'Internal'
50be8733 01/12/2019 04:24 PM Leszek Koltunski

Correct Distort.
353f7580 01/11/2019 11:15 PM Leszek Koltunski

Make Distort truly 3D.
b24e4719 01/02/2019 03:57 PM Leszek Koltunski

Make the Fragment effects truly 3D: change their 4D 'region' into a 3D 'center' (a point in 3D) and 3D 'region' (which is now a set of 3 radii defining an ellipsoid around the center)

Also corresponding changes to the applications.
4aa38649 12/30/2018 01:37 AM Leszek Koltunski

Redefine the Vertex Region from (x,y,r,unused) to (x,y,z,r). This takes into account the 'Z', which makes it possible to warp only one side of a 3D Mesh like Sphere.

Also corresponding changes in applications.
e71dd7fb 12/11/2018 01:04 PM Leszek Koltunski

Improve computation of the thickness of the postprocessing halo - should be independent of the size of underlying object now.
Still it is not completely ok, it appears to depend on the ModelView matrix (use the Effects3D app to rotate the object around Z-axis to see this)
a16bf106 12/10/2018 01:39 PM Leszek Koltunski

Make the Effects3D app a bit more user-friendly.

View revisions

Also available in: Atom