Hi Christian,
Thanks for the suggestion. I will try that. It would involve considerable
changes to the visualization setup and update callbacks.
Regards,
Josiah
On 21 January 2014 16:15, Christian Buchner christian.buch...@gmail.comwrote:
can't you split your data set across several 3D
Hi Josiah,
Try changing the pixel format from GL_FLOAT to GL_UNSIGNED_BYTE to see if
it's a memory issue.
Robert.
On 21 January 2014 08:56, Josiah Jideani josh.jide...@gmail.com wrote:
Hi,
I am involved in a project where I have to build a 3D image from processed
ultrasound data. The 3D
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Josiah,
On 21/01/2014 9:56, Josiah Jideani wrote:
...
The code has been working fine until I developed a new imaging algorithm and
had to
increase the size of the volume. Here is the code snippet that sets up the
viewer:
... The
Hi Ulrich,
Thanks for replying.
I think I phrased that sentence wrong. I made it seem like it was my
modifications causing it, but that is not the case because I recreated the
problem without my modifications. The previous dimension for the 3D
texture is 127x2048x63, and the problem occurs
Hi Josiah,
Can you check the GL_MAX_3D_TEXTURE_SIZE with something like GPU Caps
Viewer?
Even my GTX680 only supports 2048. So basically you might be hitting the
limit.
cheers
Sebastian
Hi,
I am involved in a project where I have to build a 3D image from
processed ultrasound data. The
Hi Sebastian,
I checked the KInfocenter on OpenSUSE and it says the Max. 3D texture size
is 2048. The OpenGL wiki says For 3D textures, no dimension can be
greater than GL_MAX_3D_TEXTURE_SIZE in size.
So I guess I'm violating this criteria and hence the wierd result. This
leads me to my next
can't you split your data set across several 3D textures and join these
back together during the visualization phase?
2014/1/21 Josiah Jideani josh.jide...@gmail.com
Hi Sebastian,
I checked the KInfocenter on OpenSUSE and it says the Max. 3D texture size
is 2048. The OpenGL wiki says For
7 matches
Mail list logo
