ideasman42 at gmail.com
Tue May 20 06:24:11 CEST 2014
Can you point to functions/lines-of-code which have this mistake?
Are any worth resolving before release?
On Tue, May 20, 2014 at 1:44 PM, Jason Wilkins
<jason.a.wilkins at gmail.com> wrote:
> Please be careful not to get GL_TEXTURE_2D when you
> mean GL_TEXTURE_BINDING_2D.
> I see this error over and over. It actually shows that saving the texture
> state isn't even needed since this code ends up corrupting the texture
> binding instead if restoring it.
> I'd recommend just stomping on texture state and always binding the texture
> you wanna use right before using it and assuming it's been stomped if you
> call a drawing function in another module.
> That's better than thinking the texture state has been saved when it hasn't.
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers