Einar Forselv
Einar Forselv
Pyglet 1.4 is ready soon that will solve a lot of the limitations in 1.3. We'll probably still stick with pyglet backend for moderngl_window. It does support using pyglet directly...
Note : Pyglet is moving from BitBucket to GitHub when 1.4 is released : https://github.com/pyglet/pyglet
We also have pyglet2 coming in the near future using the programmable pipeline. That adds more complications because it's not compatible with pyglet 1.x
Right now the parser will always triangulate. It's probably not hard to modify the following section to not triangulate based on some option https://github.com/greenmoss/PyWavefront/blob/2f18318674d85cb7c16298110161a15b38c53f92/pywavefront/obj.py#L416-L424
#88 would solve this. I completely agree that this is a necessary change. It's a result of the librarys original focus of rendering objects with VBOs pyglet. It needs to...
I'll try to remember to include some info in readme about this. Meanwhile see : https://github.com/pywavefront/PyWavefront/issues/87#issuecomment-464348971
I have mostly seen it in technical drawings of products. Typically the same material is used for the entire model, but some objects suddenly switch uvs for normals. So far...
I will add a fallback for this with a ``log.warn`` if I stumble over more files like this.
Not resolved yet. We need a way to handle this problem: https://github.com/greenmoss/PyWavefront/blob/ea28844c4851ac8777e617bec96ad060106994c3/pywavefront/obj.py#L322-L327
I use readthedocs for a few projects. works great.