TGEA 1.7.1 -- Multiple Render Targets?

#1 Looking at the code, it seems to me that the setActiveRenderTarget method only does a setRenderTarget for Color0, i.e. while attachTexture attaches the given to the specified render slots, MRT is never really set up.

Same goes for 1.8 BTW.

Here's the snippet from 1.7.1:

// Deal with texture target case.
   if(GFXPCD3D9TextureTarget *gdtt = dynamic_cast<GFXPCD3D9TextureTarget*>(target))
   {
      // Clear the state indicator.
      gdtt->stateApplied();

      // Set all the surfaces into the appropriate slots.
      D3D9Assert(mD3DDevice->SetRenderTarget(0, gdtt->mTargets[GFXTextureTarget::Color0]), 
         "GFXD3D9Device::setActiveRenderTarget - failed to set slot 0 for texture target!" );

      D3D9Assert(mD3DDevice->SetDepthStencilSurface(gdtt->mTargets[GFXTextureTarget::DepthStencil]), 
         "GFXD3D9Device::SetDepthStencilSurface - failed to set depthstencil target!" );

      // Reset the viewport.
      D3DSURFACE_DESC desc;
      gdtt->mTargets[GFXTextureTarget::Color0]->GetDesc( &desc );
      RectI vp( 0,0, desc.Width, desc.Height );
      setViewport( vp );

      // Exit!
      return;
   }

#2 Should probably look something like this (untested):

// Set all the surfaces into the appropriate slots.
      for( U32 i = GFXTextureTarget::Color0, rtIndex = 0; i <= GFXTextureTarget::Color4; ++ i, ++ rtIndex )
         if( gdtt->mTargets[ i ] != NULL )
            D3D9Assert( mD3DDevice->SetRenderTarget( rtIndex, gtdd->mTargets[ i ] ),
               avar( "GFXD3D9Device::setActiveRenderTarget - failed to set slot '%i' for texture target", rtIndex ) );

//Edit:
And the corresponding deactivation code should probably set all render targets except for Color0 to NULL.

#3 Indeed, that would make sense, but upon implementation this yields bizarre results. If anyone has anymore insight into this, it'd be greatly appreciated.

#4 What are the bizarre results? These could be for many reasons.

Off the top of my head
Formats don't have to match but bit depth does.
D3D will set the view port to the full size of the last render target set.

#5 Specifically, things do not render. The screen is black while facing meshes(which are invoking the multiple render targets). The texture formats are identical to each other.

#6 By "screen is black" do you mean that Color0 isn't getting any data, too? (otherwise the bizarre results after the change are the same bizarre results as before the change--black render targets :)

I implemented the above change and the corresponding cleanup in 1.8 and everything works fine. Haven't actually tried making use of MRT but at least Color0 isn't affected at all--and as all the SetRenderTarget calls are there, MRT *should* work (but okay, that's a statement worth little until it actually is proven to run).

Are you sure you are complying with all restrictions that apply to MRT? Max number of simultaneous render targets supported by your card, etc. (see here)

//EDIT: typos

#7 Yes, essentially neither of the render targets appear to be receiving any data. I've worked with Multiple Render Targets before and the current settings match all of the qualifications.