Sophie: blender-manual-2.49a-1ark i586

blender-manual-2.49a-1ark.i586.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
<HTML
><HEAD
><TITLE
>Installing the script</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="Blender Documentation Volume I - User Guide"
HREF="book1.html"><LINK
REL="UP"
TITLE="From Blender to YafRay Using YableX"
HREF="c10945.html"><LINK
REL="PREVIOUS"
TITLE="From Blender to YafRay Using YableX"
HREF="c10945.html"><LINK
REL="NEXT"
TITLE="The Interface"
HREF="x10990.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Blender Documentation Volume I - User Guide: Last modified April 29 2004 S68</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="c10945.html"
ACCESSKEY="P"
>&#60;&#60;&#60; Previous</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>From Blender to YafRay Using YableX</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="x10990.html"
ACCESSKEY="N"
>Next &#62;&#62;&#62;</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="section_yable_install"
></A
>Installing the script</H1
><P
>&#13;Yable is a script, that is a simple text file that can be loaded in 
Blender, hence we cannot talk properly of an installation. As a matter of
facts is sufficient to load it in Blender's Text Window and press <B
CLASS="keycap"
>ALT-P</B
>
to launch it. Before doing so we must anyway pay attention to two 
fundamental points:
</P
><P
></P
><UL
><LI
><P
>&#13;You need a full Python installation
(the right one for your Blender version), downloadable at www.python.org;
</P
></LI
><LI
><P
>&#13;You must edit line 81 of the Yable script.
</P
></LI
></UL
><P
>&#13;The first is a necessary condition so that the script could find the 
required Python modules, while the second is needed to set up the 
directory in which the settings and the XML generated from Yable will 
be saved.  Setting, for example, line 81 to:
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="programlisting"
>&#13;YABLEROOT = "C:/"
</PRE
></TD
></TR
></TABLE
><P
>&#13;Implies that
every time that you export a scene from a file <TT
CLASS="literal"
>foo.blend</TT
>, 
a new folder called <TT
CLASS="literal"
>foo</TT
> will be created in 
<TT
CLASS="literal"
>C:/</TT
>  containing all the elements of the scene.  
In this way, even if you close Blender, and then you reopen the file 
and restart the script, Yable will be able to retrieve the settings, 
since it search them in a folder that it has the same name of the 
current <TT
CLASS="literal"
>.blend</TT
> file.  
</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="./stylesheet-images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;This automatic naming is very handy, but unfortunately implies also that if we want to
save the <TT
CLASS="literal"
>.blend</TT
> file with a different name, 
you must re-export it from Yable at least once, so that the settings will 
be written again.  Otherwise you can copy the contents of the old
folder into the new one.
</P
></TD
></TR
></TABLE
></DIV
><P
>&#13;If you want, you can also set up an external viewer that start 
automatically in order to show the result of the rendering:  
If you so desire you must edit line 90, setting the 
<TT
CLASS="literal"
>VIEWERAPP</TT
> variable the path to the 
chosen application.
</P
><P
>&#13;As said before, all the data will be saved in the directory defined as
<TT
CLASS="literal"
>YABLEROOT</TT
>, all <I
CLASS="emphasis"
>except</I
> the textures. 
Is important that all the images used for the scene are in the same 
directory, and that such directory will be indicated correctly to Yable, 
but this is done at run time in the pertinent Text Button
appearing as soon as the script is launched 
(<A
HREF="x10959.html#BSG.YAB.F.MAN.100"
>Figure 1</A
>).  
The <I
CLASS="emphasis"
>full</I
> path to the textures is required.
</P
><DIV
CLASS="figure"
><A
NAME="BSG.YAB.F.MAN.100"
></A
><DIV
CLASS="mediaobject"
><P
><IMG
SRC="PartBE/yable/gfx/fig001.png"></P
></DIV
><P
><B
>Figure 1. Texture Dir setting and startup button.</B
></P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="c10945.html"
ACCESSKEY="P"
>&#60;&#60;&#60; Previous</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="book1.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="x10990.html"
ACCESSKEY="N"
>Next &#62;&#62;&#62;</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>From Blender to YafRay Using YableX</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="c10945.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The Interface</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>