strange issue with textures

[ofTheo]

I've noticed in your current master that if you load an ofImage or ofTexture at the top of the ofApp::setup function, nothing is rendered to the scene.

If you load the texture at the bottom of ofApp::setup the scene is not affected.
This is with OF 0.8.4 on OS X - curious if you have run into this.

Also creating an ofFbo in ofApp with 4 times multisampling causes crazy glitches in the renderer.
This is without even using the fbo. Just allocating it.

Could it be that the shaders are just grabbing the first texture ID and not the one meant for the rift.

ping @obviousjim

[mattebb]

Very weird - I vaguely recall someone on the oculus forums reporting some issues with texture ids, but can't remember if it was related at all. I'll do some investigation.

I presume you're using the default SDK rendering? (i.e. you haven't changed #define SDK_RENDER 1 ) inside the addon ofxOculusDK2.cpp?

[ofTheo]

I didn't touch the SDK_RENDER which is defined as 1.

The code to reproduce is with the OculusRenderingBasic example.

//--------------------------------------------------------------
void testApp::setup()
{

    testImage.loadImage("tex-003.jpg");  // ( load any image here ) 

    //then the rest of the example. 
    ofBackground(0);
    ofSetLogLevel( OF_LOG_VERBOSE );
    ofSetVerticalSync( true );

[ofTheo]

Also allocating an FBO works fine in the same location, but if the FBO has multisampling then nothing will be rendered.

Does seem a bit strange.

If I comment out SDK_RENDER it also doesn't render.