Skip to content

Conversation

@tychedelia
Copy link
Member

Prereq to doing anything useful with geometry.

I went back and forth about whether this should be a separate API object. But it's not in Bevy and so I think it's fine to express in terms of graphics here too. This is what Bevy calls "camera driven rendering", where the main graphics context is also a camera. There are pros and cons here but this is close to processing4 and so good enough for now, I think.

@tychedelia tychedelia requested a review from catilac December 23, 2025 07:25
Copy link
Contributor

@catilac catilac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm! i love the way the modes are broken out. wonderous worlds ahead :P

Comment on lines +368 to +369
// TODO: allow specifying up vector?
// does anyone actually use anything other than Vec3::Y here?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fwiw I think it's fine to leave out specifying an up vector at least for now.
but gosh suddenly i want to see a sketch where the upvector changes over a time based function!

@catilac catilac merged commit f77cc47 into processing:main Dec 23, 2025
4 checks passed
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.

2 participants