Bug fixes #270
Bug fixes #270
Conversation
…ections are not cleared
|
Hard for me to understand: Is the LOD selection now independent of the window size? If no, where is it taken into account? |
|
Yes it is now. I am just finding the projection of (n) pixel in a distance and, I am finding which LOD of the data has the closest number of voxels of the whole data for that projected pixel. The TUVOK one was much more complicated. If volume is 4k^3, 256^3 blocks, 5 depth, and sse is 2 ( 1 voxel is two pixels ) and volume is just front of the near plane, you can directly use the 2048^3 volume where each voxel is exactly two pixels of the data. |
|
so ? |
…sibiles are improved
bilgili
force-pushed
the
bug_fixes
branch
3 times, most recently
from
3660024
to
f1ba50a
Compare
|
|
||
| // Explicit registration required because the folder of the data source plugin is not | ||
| // in the LD_LIBRARY_PATH of the test executable. | ||
| lunchbox::PluginRegisterer< livre::MemoryDataSource > registerer; |
There was a problem hiding this comment.
I remember the RH and Ubuntu was behaving differently in link time about registering the data sources ( I had a problem with uvf before thats why I have added ).
|
+1 Can you change the default camera pos to 1.5? Then the front of the volume will be on the near plane for a square window. |
|
0.6 ( 0.5 the half width of volume + 0.1 near plane ) will make the volume right in front of the plane. 1.5 The volume will be farther ( double checked ). 1.5 includes all the volume. |
No description provided.