Skip to content
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

3D rendering strategy #786

Closed
bvssvni opened this issue Dec 22, 2014 · 2 comments

Comments

@bvssvni
Copy link
Member

commented Dec 22, 2014

Piston does not have advanced 3D rendering libraries yet. There are 2 major features I would like to have:

Managing 3D assets with contiguous arrays: #587

This will make it easier to manage the geometry for a whole scene and the structure could in theory be understood by GPU shaders.

Update content in real time with Verse protocol: #553

In addition, there are many different rendering techniques which might require bottom-up design. Are there any ideas how this can be split up into modular pieces?

@bvssvni bvssvni added the discussion label Dec 22, 2014

@bvssvni

This comment has been minimized.

Copy link
Member Author

commented Dec 22, 2014

With contiguous arrays you can append geometry at the end of the buffer and move the index ranges to point to the position. This makes the old geometry garbage in the buffer, but this can be clean up incrementally. Unused memory can be inferred from the whole structure using set algorithms.

@bvssvni

This comment has been minimized.

Copy link
Member Author

commented Feb 14, 2015

If we support metadata layers in the range hierarchy, then we can build a library for ordering drawcalls that uses grouping per material etc. http://realtimecollisiondetection.net/blog/?p=86

@bvssvni bvssvni closed this Feb 24, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.