From 8f03ba5f8ce3ed22ac08eacdce609712e8ad4154 Mon Sep 17 00:00:00 2001 From: Simon Stucki Date: Tue, 20 Aug 2024 16:05:24 +0200 Subject: [PATCH] Drop superfluous line --- report/parts/discussion.tex | 1 - 1 file changed, 1 deletion(-) diff --git a/report/parts/discussion.tex b/report/parts/discussion.tex index 12128b7..d81db52 100644 --- a/report/parts/discussion.tex +++ b/report/parts/discussion.tex @@ -204,7 +204,6 @@ \subsubsection*{Qualitative Assessment} \item{Web-based Path Tracer Comparison} - Comparison to other web-based path tracers such as \texttt{three-gpu-pathtracer} \cite{ThreeJsPathTracerJohnson}, \texttt{Three.js PathTracer} \cite{ThreeJsPathTracerLoftis}, or \texttt{dspbr-pt} \cite{PathTracerDassault}. \end{itemize} - \section{Conclusion} For the given use case of using production \gls{CAD} data with manifold assembly configurations and customer-specific materials, the path tracer developed in this thesis is a suitable choice. While there are a variety of areas to improve on, the proposed solution constitutes a fully functional renderer encompassing technical features such as using \gls{BVH}, parallelization on \gls{GPU} based on \gls{WebGPU}, and supporting \gls{MIS}; rendering features including anti-aliasing, generating a wide range of global illumination effects, and supporting the \gls{OpenPBR} standard; usability features such as incremental rendering, camera controls, and scene loading; benchmarking setups for reliable performance measurements and extensive documentation to facilitate use of the renderer.