New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove support for fixed-function pipeline #3505

Closed
codeanticode opened this Issue Jul 27, 2015 · 4 comments

Comments

Projects
None yet
3 participants
@codeanticode
Member

codeanticode commented Jul 27, 2015

Right now the default profile in the GL renderer is GL2ES1, so users still have the chance to access the fixed-function pipeline (FFP).

However, with the deprecation of FFP already being several years old, and GLSL programming becoming more widespread, there is little reason to keep FFP around. The GL renderer does not use it at all, since we run our own shaders to handle all rendering operations, including lighting and texturing. We do incur in some redundancy by not removing it, since GL2ES1 still handles the FFP uniforms (transformation matrices, lighting parameters), but Processing does not use them.

@codeanticode codeanticode added this to the 3.0 beta 1 milestone Jul 27, 2015

@codeanticode codeanticode self-assigned this Jul 27, 2015

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Jul 27, 2015

Member

So is your plan to remove it? Or are you asking whether you should? (FWIW, I definitely say remove it.)

Member

benfry commented Jul 27, 2015

So is your plan to remove it? Or are you asking whether you should? (FWIW, I definitely say remove it.)

@codeanticode

This comment has been minimized.

Show comment
Hide comment
@codeanticode

codeanticode Jul 27, 2015

Member

Mainly the second, I wanted to get some feedback before going ahead.

Member

codeanticode commented Jul 27, 2015

Mainly the second, I wanted to get some feedback before going ahead.

@codeanticode codeanticode modified the milestones: 3.0 final, 3.0 beta 1 Aug 5, 2015

@JakubValtar

This comment has been minimized.

Show comment
Hide comment
@JakubValtar

JakubValtar Aug 18, 2015

Contributor

Are we done here?

Contributor

JakubValtar commented Aug 18, 2015

Are we done here?

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Aug 19, 2015

Member

That's for @codeanticode to answer.

Member

benfry commented Aug 19, 2015

That's for @codeanticode to answer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment