Documentation: RobotLocomotion/drake@ef5fd46

Author: drake-jenkins-bot

doxygen_cxx/structdrake_1_1geometry_1_1_render_engine_vtk_params.html

@@ -264,6 +264,11 @@ <h2 class="memtitle"><span class="permalink"><a href="#a606a9df3866a52308dad9851
 
 <p>If <code>true</code>, <em>all</em> lights that are <em>able</em> to cast shadows will do so. </p>
 <p>Several important notes when designing your lighting: </p><pre class="fragment">- Point lights do not cast shadows.
+- Spot lights will not cast shadows if the spot light angle is 90 degrees
+  or more. At 90 degrees, the spot light is now a half-point light.
+  Even though 89.9 degrees _would_ enable shadows, it is still an
+  impractical value. To actually see shadows, the `shadow_map_size` value
+  would have to be absurdly large to support such a wide extent.
 - Directional lights will create a shadow map that spans the whole scene.
   If your scene includes a geometry that is significantly larger than
   the locale you're rendering, this will significantly reduce the

pydrake/pydrake.geometry.html

@@ -9909,9 +9909,14 @@ <h1>pydrake.geometry<a class="headerlink" href="#pydrake-geometry" title="Permal
 <p>Several important notes when designing your lighting:</p>
 <ul class="simple">
 <li><p>Point lights do not cast shadows.</p></li>
-<li><p>Directional lights will create a shadow map that spans the whole scene.</p></li>
+<li><p>Spot lights will not cast shadows if the spot light angle is 90 degrees</p></li>
 </ul>
-<p>If your scene includes a geometry that is significantly larger than
+<p>or more. At 90 degrees, the spot light is now a half-point light.
+Even though 89.9 degrees <em>would</em> enable shadows, it is still an
+impractical value. To actually see shadows, the <code class="docutils literal notranslate"><span class="pre">shadow_map_size</span></code> value
+would have to be absurdly large to support such a wide extent.
+- Directional lights will create a shadow map that spans the whole scene.
+If your scene includes a geometry that is significantly larger than
 the locale you’re rendering, this will significantly reduce the
 efficacy of the directional light’s shadows. Consider truncating that
 larger geometry. A common case would be to use a HalfSpace to define

pydrake/searchindex.js

@@ -522,12 +522,15 @@ <h2 id="post-release-tutorials-updates">Post-release tutorials updates</h2>
         <ol>
           <li>In the left-hand panel of your screen, take note that each notebook
 appears in two places – in “NOTEBOOKS” near the top and in “FILES”
-near the bottom. The “NOTEBOOKS” is the old copy; the “FILES” is the
-new copy. Our goal is to replace the old copy with the new.</li>
+near the bottom. The “NOTEBOOKS” is the older copy (from the prior
+release); the “FILES” is the new copy (from this release). Our goal
+is to replace the old copy with the new.</li>
           <li>Scroll down to the “FILES” and choose the top-most name. Right click on
 it and select “Move to notebooks”.
 Be patient because the web interface could be slow, and there might be
-delay between copying and deleting the file.</li>
+delay while copying the file.
+Note that even though the button says “Move”, it actually only <em>copies</em>
+the file; it does not delete the item from “FILES”.</li>
           <li>Because a notebook of that name already existed in “NOTEBOOKS” (the old
 copy), the moved notebook will be renamed with a <code class="language-plaintext highlighter-rouge">-2</code> suffix.</li>
           <li>Scroll up to “NOTEBOOKS”. Right click on the old copy (without <code class="language-plaintext highlighter-rouge">-2</code>)
@@ -549,9 +552,8 @@ <h2 id="post-release-tutorials-updates">Post-release tutorials updates</h2>
           <li>Leave the notebook output intact (do not clear the outputs). We want
 users to be able to read the outputs on their own, without necessarily
 running the notebook themselves.</li>
-          <li>The moved notebook no longer appears in “FILES”, so you can always
-use the top-most <code class="language-plaintext highlighter-rouge">*.ipynb</code> in “FILES” as your checklist for which
-one to tackle next.</li>
+          <li>Go back to “FILES” and right-click then “Delete” on the notebook you
+just copied; it should still be the top-most <code class="language-plaintext highlighter-rouge">*.ipynb</code> in “FILES”.</li>
         </ol>
       </li>
     </ol>