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

1.7 release work #1431

Merged
merged 9 commits into from
May 29, 2017
Merged

1.7 release work #1431

merged 9 commits into from
May 29, 2017

Conversation

est77
Copy link
Member

@est77 est77 commented May 27, 2017

No description provided.

@Narann
Copy link
Contributor

Narann commented May 27, 2017

Why are the reasons to remove partio? I guess it's because it's not often use while alembic support points (or even OpenVDB points)? I just ask. :)

Keep the good work! 👍

@est77
Copy link
Member Author

est77 commented May 27, 2017

Why are the reasons to remove partio? I guess it's because it's not often use while alembic support points (or even OpenVDB points)? I just ask. :)

We were only using it in an unit test which didn't have much value. We cannot render points or particles at the moment in any case.
When we add them, Alembic, OpenVDB points or even USD would be better choices.

Note that you can still use PARTIO inside OSL, for point cloud lookups, and similar stuff.

@luisbarrancos luisbarrancos added this to the 1.7.0 milestone May 28, 2017
@est77 est77 merged commit 57b8da9 into appleseedhq:master May 29, 2017
@est77 est77 deleted the est_release_work branch May 29, 2017 09:18
@Narann
Copy link
Contributor

Narann commented May 29, 2017

Thanks! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants