weird rendering artifact

Started by raft, March 07, 2013, 11:44:20 PM

Previous topic - Next topic

EgonOlsen


raft

yup :-\

btw, seldomly I got an app crash, with the stacktrace below logged to file. maybe relevant?

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
J  org.lwjgl.opengl.GL11.nglTexCoord2f(FFJ)V
J  com.threed.jpct.GLBase.blit([Ljava/lang/Object;FF)V
J  com.threed.jpct.GLRenderer.execute(I[Ljava/lang/Object;)V
J  com.threed.jpct.FrameBuffer.blit(Lcom/threed/jpct/Texture;IIIIIIIIIZLjava/awt/Color;)V
J  raft.glgui.opengl.TexturePack.blit(Lcom/threed/jpct/FrameBuffer;Lraft/glgui/opengl/TexturePack$Entry;IIIIIZLjava/awt/Color;)Ljava/awt/Dimension;
J  raft.glgui.opengl.TexturePack.blit(Lcom/threed/jpct/FrameBuffer;IIIIZLjava/awt/Color;)Ljava/awt/Dimension;
J  raft.glgui.opengl.GLFont.blitString(Lcom/threed/jpct/FrameBuffer;Ljava/lang/String;IIILcom/threed/jpct/RGBColor;)V
J  raft.jumpy.gl.JumpyTWL.render()V

EgonOlsen

Maybe...but it doesn't make much sense except that it indicates some driver problem. The crashing command is something like


GL11.glTexCoord2f(<float>, <float>);


...and i don't see how this can crash anything under normal circumstances. Buffered blits don't do it that way, which might be the reason why they work...

raft

mm, my best bet seems to be sticking to Config.glBufferedBlits=true.

EgonOlsen

Yes. It's the only way that jPCT-AE knows anyway.