On 5 June 2017 at 01:16, Benjamin Moran <[email protected]> wrote:
> I hacked on this a bit more, and basically have a working implementation
> now. It's structured pretty much like the image module, which I think makes
> the most sense after all. There is a single codec, which is wavefront
> (obj) decoder based on the pyglet/contrib/model code. It works, but needs
> major cleanup.
>
> Richard, what would you say are vital method to have on the Model class?
> So far, I have a draw method (which people shouldn't use anyway), and an
> update method which allows shifting the model on one of the x, y, z axis
> (requiring lots of list slicing). Any thoughts on what methods would be
> most important to add? My personal use case is mainly for static
> background objects, so I'm not the best judge in this case!
>
ISTM that gross operations on the model (transformations on all vertices
like the translation - I think that's what you mean by "shifting the
model") should be handled entirely by a shader, and no actual vertex data
manipulation, since setting the shader variable will be infinitely faster.
Richard
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/d/optout.
