You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be some issue with FBOs and the Presentation class. This issue is related to drawing FBOs on an FBO (possibly). In Fringes fork of this repo, after updating to use new Art2d texShader handler, the title screen does not appear. This is a presentation. Removing nested FBO writes revealed that the Presentation drawing methods appear upside down and in the wrong place (the latter issue is due to it not being drawn off screen). With the nested FBO, the title screen appears black. Also, the cursor does not draw, indicating there is a state issue.
Musings about what might solve the issue include inspecting the rendering pipeline, utilizing a GL debugger, resolving any pipeline issues with the shader.
A related issue may be the class that replaces/handles glScissor (has no useful functionality anymore?), and figuring out how to clean up or remove this feature if no longer needed.
To Reproduce
Steps to reproduce the behavior:
Invoke a looping Presentation onto an FBO in a GLWindow loaded into the windows list
Expected behavior
Draw like it used to when using immediate mode to draw the FBOs to screen.
The text was updated successfully, but these errors were encountered:
Describe the bug
There seems to be some issue with FBOs and the Presentation class. This issue is related to drawing FBOs on an FBO (possibly). In Fringes fork of this repo, after updating to use new Art2d texShader handler, the title screen does not appear. This is a presentation. Removing nested FBO writes revealed that the Presentation drawing methods appear upside down and in the wrong place (the latter issue is due to it not being drawn off screen). With the nested FBO, the title screen appears black. Also, the cursor does not draw, indicating there is a state issue.
Musings about what might solve the issue include inspecting the rendering pipeline, utilizing a GL debugger, resolving any pipeline issues with the shader.
A related issue may be the class that replaces/handles glScissor (has no useful functionality anymore?), and figuring out how to clean up or remove this feature if no longer needed.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Draw like it used to when using immediate mode to draw the FBOs to screen.
The text was updated successfully, but these errors were encountered: