Running MeshMolder with glIntercept logging reveals a lot of strange things......
2 posters
Page 1 of 1
Running MeshMolder with glIntercept logging reveals a lot of strange things......
For example, why on earth does it call
glGetIntegerv(GL_VIEWPORT)
glGetDoublev(GL_PROJECTION_MATRIX)
glGetDoublev(GL_MODELVIEW_MATRIX)
literally over one hundred thousand times in a row seemingly every frame? There is no situation where this could ever possibly be necessary. There are also thousands and thousands of instances of glPushMatrix and glPopMatrix causing GL_STACK_UNDERFLOW errors. Not trying to be rude here, just trying to point out some issues that might help you optimize the application.
glGetIntegerv(GL_VIEWPORT)
glGetDoublev(GL_PROJECTION_MATRIX)
glGetDoublev(GL_MODELVIEW_MATRIX)
literally over one hundred thousand times in a row seemingly every frame? There is no situation where this could ever possibly be necessary. There are also thousands and thousands of instances of glPushMatrix and glPopMatrix causing GL_STACK_UNDERFLOW errors. Not trying to be rude here, just trying to point out some issues that might help you optimize the application.
Akira1364- Posts : 3
Join date : 2016-08-20
Re: Running MeshMolder with glIntercept logging reveals a lot of strange things......
Hi Akira , download the last version, 7.03..i fixed this bug. If persist, please let me know. ..
Thank you for your help! I need feedback
*I'm testing glintersect...Really many bugs in opengl
Thank you for your help! I need feedback
*I'm testing glintersect...Really many bugs in opengl
Similar topics
» Meshmolder 7.0
» Meshmolder v2.0 in development
» Meshmolder Beta 7.0
» Meshmolder no youtube!!
» Meshmolder 10 in development!
» Meshmolder v2.0 in development
» Meshmolder Beta 7.0
» Meshmolder no youtube!!
» Meshmolder 10 in development!
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|