Theodore Watson

Thanks for this Eduard. It is really helpful to see this to understand the issue. My first impression is that this is a pretty specific use case and def feels...

Ahh good to know! I can check what the correct naming is for the different distros and revise. See #6493 - I think you mentioned we needed this for all...

note: this happens for both ES1 and ES2 on iOS but doesn't happen on macOS. ping @julapy @tgfrerer @danoli3

The black triangle only seems to come up if you are drawing in non default orientation > window width. Nothing to do with fbo allocation size - just draw size.

@danoli3 @cuinjune - I just tried again with the nightly and the issue is still there. You have to do mouse down / touch to see it. I am on...

 Here is a gif showing how even a ofScale where the fbo is drawn greater than the window size causes issues. Code to reproduce below: ``` //-------------------------------------------------------------- void ofApp::setup(){...

Thanks for confirming @cuinjune Wondering if it might have something to do with the viewport? Its really strange.

@cuinjune @danoli3 - fyi it doesn't seem to happen when hardware orientation is set to true. Also I am not sure if this is right but currently OF_ORIENTATION_90_RIGHT results in...

okay one more clue: Setting ``` ofViewport(0, 0, ofGetWidth()-1, ofGetHeight()-1); ``` At the top of draw fixes it. Though having this: ``` ofViewport(0, 0, ofGetWidth(), ofGetHeight()); ``` doesn't. Really, weird....

It also seems to affect images / textures as well as FBOs. If you take the imageLoaderexample and change: ``` ofScale(0.5, 0.5, 1.0); ``` in draw to: ``` ofScale(1.5, 1.5,...