AFAIK copy is the most basic method, pbuffer is more advanced and FBO is the lastest shiny new RTT method.
That means that copy will generally work but with proper support of the drivers the other methods are much faster.
After narrowing down to which revision broke Gazebo for me, I located the problem: Line 411 in server/rendering/OgreAdaptor.cc: // Set the preferred RRT mode. Options are: "PBuffer", "FBO", and "Copy"
selectedRenderSystem->setConfigOption("RTT Preferred Mode", "PBuffer");
The option "PBuffer" crashes my client. "Copy" runs ok, but has graphic glitches (only a small section of the screen renders ok, the rest is the copy of the last line / column of pixels in the ok-area) and "FBO" seems perfectly fine. Is there an urgent reason why it's set to "PBuffer" by default? If yes, would it be possible to make it an option in .gazeborc?
-- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail