dash-3d-tmp/phd
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Work

Browse Source
This commit is contained in:
Thomas Forgione
2019-10-03 12:03:42 +02:00
parent aeb78691db
commit a71b0be28b
15 changed files with 485 additions and 520 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/conclusion/future-work.tex
View File

@@ -15,7 +15,7 @@ Geometry data is transmitted as OBJ files which is the worst possible format for
Being able to support multi resolution geometry would be even better, and even if performing multi resolution on a large and heterogeneous scene just like ours is difficult, we have no doubt that semantic information can help this task.
\subsection{Performance optimization}
Performance has already been discussed in Chapter~\ref{d3i}.
Performance has already been discussed in Chapter~\ref{d3}.
However, in this work, we never tried to remove data from the media engine when it is no longer useful.
This means that on a really large scene, performance is bound to become damaged due to the growing amount of data to render, and the saturation of memory.
For our system to be able to support such scenes, it needs to unload data.