29 lines
1.8 KiB
TeX
29 lines
1.8 KiB
TeX
\fresh{}
|
|
|
|
\section{Content preparation\label{d3i:rust-exporter}}
|
|
|
|
The piece of software that does the preprocessing of the model mostly consists in file manipulation and is written is Rust as well.
|
|
It successively preprocess the geometry and then the textures.
|
|
The MPD is generated by a library named \href{https://github.com/netvl/xml-rs}{xml-rs}, and that works like a stack:
|
|
\begin{itemize}
|
|
\item a structure is created on the root of the MPD file;
|
|
\item the \texttt{start\_element} method creates a new child in the XML file;
|
|
\item the \texttt{end\_element} method ends the current child and pops the stack.
|
|
\end{itemize}
|
|
This structure is passed along with our geometry and texture preprocessors that can add elements to the XML file as they are generating the corresponding files.
|
|
The other details of the preprocessing is available in Section~\ref{d3:dash-3d}.
|
|
|
|
\subsection{Geometry preparation}
|
|
The content preparation starts with the geometry.
|
|
It structures the faces of the model into a $k$-d tree, and then shrink the bounding boxes to avoid having empty space.
|
|
The cells of our $k$-d tree structure are our adaptation sets, so we traverse them and sort the faces by area and make segments, recording all the metadata in the MPD\@.
|
|
|
|
\subsection{Materials and texture preparation}
|
|
Then, we prepare the materials and the textures.
|
|
Exporting the materials files is quite straightforward: we simply add an attribute to each material specifying the number of faces painted with this materials in the model so we know the size of the buffers we need to allocate.
|
|
We then prepare the textures.
|
|
In OpenGL, texture sizes must be power of two.
|
|
So the first thing we do is resize the input texture to the next power of two.
|
|
We save it, add its metadata to the MPD, divide the size by two and keep doing this process until one of the dimension is less than 32 pixels.
|
|
|