Changeset 253 for trunk/VUT

Timestamp:

08/26/05 17:06:03 (19 years ago)

Author:

mattausch

Message:

 

Location:

trunk/VUT/doc/SciReport

Files:

• images/chc_shadows.png (added)
• images/transp_delayed.png (added)
• images/transp_wrong.png (added)
• online.tex (modified) (4 diffs)

trunk/VUT/doc/SciReport/online.tex

@@ -46 +46 @@
         \centering \footnotesize
         \begin{tabular}{c}
-        \includegraphics[width=0.5\textwidth, draft=\DRAFTFIGS]{images/ogre_terrain} \\
+        \includegraphics[width=0.6\textwidth, draft=\DRAFTFIGS]{images/ogre_terrain} \\
         %\hline 
-        \includegraphics[width=0.25\textwidth, draft=\DRAFTFIGS]{images/vis_viewfrustum} \hfill \includegraphics[width=0.25\textwidth, draft=\DRAFTFIGS]{images/vis_chc} \\
+        \includegraphics[width=0.3\textwidth, draft=\DRAFTFIGS]{images/vis_viewfrustum} \hfill \includegraphics[width=0.3\textwidth, draft=\DRAFTFIGS]{images/vis_chc} \\
         \end{tabular}
-\label{tab:averages}
-  \caption{Top row: The rendered scene. Bottom row: The visualizion of the rendering overdraw.
+%\label{tab:online_culling_example}
+  \caption{(top) The rendered terrain scene. (bottom) Visualizion of the rendered / culled objects.
     Using view frustum culling (left image) vs. occlusion queries (right image).
     The yellow boxes show the actually rendered scene objects. The
@@ -77 +77 @@
 In figure~\ref{fig:online_culling_example}, the same scene (top row) is rendered using view frustum
 culling (visualization in the bottom left image) versus online culling using occlusion queries (visualization 
-in the bottom right image). We can clearly see the large overdraw that happens for view frustum culling.
+in the bottom right image). It can be seen that with view frustum culling only many objects are still rendered.
 %Using spatial and assuming temporal coherence
 
@@ -691 +691 @@
 \label{sec:initial}
 
+\begin{figure}
+\centering 
+\includegraphics[width=0.49\textwidth,draft=\DRAFTIMAGES]{images/transp_wrong}
+\includegraphics[width=0.49\textwidth,draft=\DRAFTIMAGES]{images/transp_delayed}
+\caption{(left) all passes are rendered with CHC. Note that the soldiers are
+visible through the tree. (right) Only the solid passes are rendered using CHC, afterwards the transparent passes.}
+\label{fig:online_transparency}
+\end{figure}
+
+
 To achieve maximal performance on modern GPU's, one has to take care of a number of issues.
 First, it is very important to reduce material switching. Thus modern rendering engines sort the 
@@ -706 +716 @@
 only the first passes using the algorithm (e.g., the solid passes), determining the visibility of the patches, and 
 render all the other passes afterwards. This approach can be used when there are passes which require a special
-kind of sorting to be rendered correctly (e.g., transparent passes, shadow passes).
-
-
+kind of sorting to be rendered correctly (e.g., transparent passes, shadow passes). In figure~\ref{fig:online_transparency},
+we can see that artifacts occur in the left image if the transparent passes are not rendered in the correct order after
+applying the hierarchical algorithm (right image). In a similar fashion, we are able to handle shadows~\ref{fig:chc_shadows}.
+
+\begin{figure}
+\centering 
+\includegraphics[width=0.35\textwidth,draft=\DRAFTIMAGES]{images/chc_shadows}
+\caption{We can correctly handle shadow volumes together with CHC.}
+\label{fig:chc_shadows}
+\end{figure}
 
 \subsection{Batching multiple queries}