0. Every graphics object in Scilab 5.x is _intrinsecally_ 3D.
When you are using any graphic functions, the 3D rendering pipeline is
constantly put under pressure: if you want to enjoy a "full steam"
experience, please ....
1. Install the _latest_ ( _stable_versions_ please) video drivers for
your hardware/software gears.
Scilab 5.x uses some advanced 3D features that are implemented ONLY on
the latest generation video drivers. NVIDIA lead the way but, in the
last months, ATI has improved the performances and support
considerably. Intel is lagging behind, but the Scilab dev. team is
providing a solution ....
2. If your Scilab graphic performance is poor, you can activate the
GL_CANVAS mode using
-->usecanvas(%t)
"GL_CANVAS mode" is available ONLY in the latest "nightly_builds_5.1"
http://www.scilab.org/download/index_download.php?page=nightly_builds_5.1
and it will be included in the following Scilab 5.1 release. We are
working on some auto detection routines that will automatically
activate this mode "just in case". You will go back to the standard
"GL_PANEL" mode using
-->usecanvas(%f)
The "GL_CANVAS" mode sacrify some advanced "uicontrol" features for
more compatibility and speed on "old generation" graphics pipelines.
Scicos is FULLY functional using "GL_CANVAS".
3. My hardware/software gear does not have a functional 3D pipeline
You can still use Scilab as "text" application (with some very slow
graphics), but Scicos will be practically un-usable :( because the
Scicos editor needs a fully functional Scilab graphics pipeline.
In the next post: "how to install the correct 3D graphic driver, live
longer and prosper with Scilab 5.x".