Re: [Paraview] BOX - volume?
Hi Bertwim, The problem you're experiencing is not an issue of missing extensions, but rather a bug in ATI's driver. Projected tetrahedra is disabled when an ATI device is detected to avoid that bug(ParaView will hang). However it's not a big deal. because you can use the Bunyk raycast algrothim instead. After your data is on screen scroll to the bottom of the properties panel and look for the field Select mapper, set that to Bunyk ray cast, then change the representation to volume. Burlen On 10/15/2014 06:58 PM, B.W.H. van Beest wrote: I am still busy with finding out which etensions are needed, and how I can enable them. THis opebnGL-world is a bit alien to me, so it will take some time. Regards, Bertwim On 10/14/2014 11:07 PM, Aashish Chaudhary wrote: Looks like certain extensions are still not quite working on yours system even with the proprietary driver. I will see if I can run your code on my laptop but that would be for tomorrow. ** Assuming that this is not data dependent issue (which it should not). I think its probably this line causing the issue: bool driverSupport #if defined(__APPLE__) = true; #else = !(extensions-DriverIsATI() (extensions-GetDriverGLVersionMajor() = 3)) || extensions-GetIgnoreDriverBugs(ATI texturing bug); #endif On line number 181: can you change this code to : this-HasHardwareSupport=renwin!=NULLthis-IsSupported(renwin); to this-HasHardwareSupport=1; - Aashish On Tue, Oct 14, 2014 at 4:53 PM, B.W.H. van Beest b...@xs4all.nl mailto:b...@xs4all.nl wrote: Progress indeed. But I don't understand what you are saying about the transfer function. I' starting to wonder if I have two issues occurring simultaneously. In a new thread I just posted I described my problem in getting the colours in place. I need to write to a vtk file first and load it back. I just found that when I just did that and then switched fo volume rendering, an error was there about the absence of an opengl extension: ERROR: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, line 185 vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required extensions are not supported. This is complete unknown terrain for me. Regards, Bertwim On 10/14/2014 09:58 PM, Burlen Loring wrote: progress! it sounds like volume rendering is working on the wavelet dataset. You do need the scalars for volume rendering, so make sure you have those when you try. You need to select the scalars in the drop down also, I usually do this before changing to the volume representation. You also may need to edit the transfer function. For testing you could make the opacity over the entire scalar range in which case you should see a solid cube. If you've done all that and don't see anything it's likely that the dataset is messed up. Add a dataset-Print(cerr) statement to the end of your request data, look in the information panel and verify correct number of points and scalar ranges. If all else fails post the dataset to the list. After creating your cube go to the file menu and save data. On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: Hi Burlen, I have upgraded to the AMD drivers. Thanks for the hint. It has improved the situation a bit. Furthermore, I created the wavelet source. When selecting volume representation, I do see a three 3 picture, in all 5 volume rendering mode (smart, raycast and texture mapping, ray cast only, texture mapping only, GPU based). The picture a rather fuzzy, but then I don't know what I'm supposed to see here. The good news is that the openGL errors I had before when displaying a wavelet, now have gone. The situation with my own cube, though, has unchanged. unfortunately. The cube disappears in volume representation node, also when I re-inserted scalar values for each of the 8 vertices. Regards, Bertwim On 10/14/2014 06:06 PM, Burlen Loring wrote: Hi Bertwim, In recent releases of ParaView I have experienced issues/flakeyness with volume rendering. Something you should try: Create the wavelet source, then in the properties panel find volume rendering mode and set it to ray cast only. This has worked for me on a number of systems. may or may not work, but worth a try. The output you pasted below shows that although you've got a sweet ATI GPU you're not taking advantage of it! You're using the Intel integrated GPU with Mesa drivers. If I were you I would install proprietary the AMD drivers http://support.amd.com/en-us/download. This should give you nice performance boost and may even solve the OpenGL errors you reported, which these days are as often (or more) a result of bugs in the Mesa
Re: [Paraview] BOX - volume?
Got it! Impressive, your knowledge on these matters. Regards, Bertwim On 10/16/2014 07:53 PM, Burlen Loring wrote: Hi Bertwim, The problem you're experiencing is not an issue of missing extensions, but rather a bug in ATI's driver. Projected tetrahedra is disabled when an ATI device is detected to avoid that bug(ParaView will hang). However it's not a big deal. because you can use the Bunyk raycast algrothim instead. After your data is on screen scroll to the bottom of the properties panel and look for the field Select mapper, set that to Bunyk ray cast, then change the representation to volume. Burlen On 10/15/2014 06:58 PM, B.W.H. van Beest wrote: I am still busy with finding out which etensions are needed, and how I can enable them. THis opebnGL-world is a bit alien to me, so it will take some time. Regards, Bertwim On 10/14/2014 11:07 PM, Aashish Chaudhary wrote: Looks like certain extensions are still not quite working on yours system even with the proprietary driver. I will see if I can run your code on my laptop but that would be for tomorrow. ** Assuming that this is not data dependent issue (which it should not). I think its probably this line causing the issue: bool driverSupport #if defined(__APPLE__) = true; #else = !(extensions-DriverIsATI() (extensions-GetDriverGLVersionMajor() = 3)) || extensions-GetIgnoreDriverBugs(ATI texturing bug); #endif On line number 181: can you change this code to : this-HasHardwareSupport=renwin!=NULLthis-IsSupported(renwin); to this-HasHardwareSupport=1; - Aashish On Tue, Oct 14, 2014 at 4:53 PM, B.W.H. van Beest b...@xs4all.nl mailto:b...@xs4all.nl wrote: Progress indeed. But I don't understand what you are saying about the transfer function. I' starting to wonder if I have two issues occurring simultaneously. In a new thread I just posted I described my problem in getting the colours in place. I need to write to a vtk file first and load it back. I just found that when I just did that and then switched fo volume rendering, an error was there about the absence of an opengl extension: ERROR: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, line 185 vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required extensions are not supported. This is complete unknown terrain for me. Regards, Bertwim On 10/14/2014 09:58 PM, Burlen Loring wrote: progress! it sounds like volume rendering is working on the wavelet dataset. You do need the scalars for volume rendering, so make sure you have those when you try. You need to select the scalars in the drop down also, I usually do this before changing to the volume representation. You also may need to edit the transfer function. For testing you could make the opacity over the entire scalar range in which case you should see a solid cube. If you've done all that and don't see anything it's likely that the dataset is messed up. Add a dataset-Print(cerr) statement to the end of your request data, look in the information panel and verify correct number of points and scalar ranges. If all else fails post the dataset to the list. After creating your cube go to the file menu and save data. On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: Hi Burlen, I have upgraded to the AMD drivers. Thanks for the hint. It has improved the situation a bit. Furthermore, I created the wavelet source. When selecting volume representation, I do see a three 3 picture, in all 5 volume rendering mode (smart, raycast and texture mapping, ray cast only, texture mapping only, GPU based). The picture a rather fuzzy, but then I don't know what I'm supposed to see here. The good news is that the openGL errors I had before when displaying a wavelet, now have gone. The situation with my own cube, though, has unchanged. unfortunately. The cube disappears in volume representation node, also when I re-inserted scalar values for each of the 8 vertices. Regards, Bertwim On 10/14/2014 06:06 PM, Burlen Loring wrote: Hi Bertwim, In recent releases of ParaView I have experienced issues/flakeyness with volume rendering. Something you should try: Create the wavelet source, then in the properties panel find volume rendering mode and set it to ray cast only. This has worked for me on a number of systems. may or may not work, but worth a try. The output you pasted below shows that although you've got a sweet ATI GPU you're not taking advantage of it! You're using the Intel integrated GPU with Mesa drivers. If I were you I would install proprietary the AMD drivers
Re: [Paraview] BOX - volume?
Got it! Impressive, your knowledge on these matters ... Thanks Regards, Bertwim On 10/16/2014 07:53 PM, Burlen Loring wrote: Hi Bertwim, The problem you're experiencing is not an issue of missing extensions, but rather a bug in ATI's driver. Projected tetrahedra is disabled when an ATI device is detected to avoid that bug(ParaView will hang). However it's not a big deal. because you can use the Bunyk raycast algrothim instead. After your data is on screen scroll to the bottom of the properties panel and look for the field Select mapper, set that to Bunyk ray cast, then change the representation to volume. Burlen On 10/15/2014 06:58 PM, B.W.H. van Beest wrote: I am still busy with finding out which etensions are needed, and how I can enable them. THis opebnGL-world is a bit alien to me, so it will take some time. Regards, Bertwim On 10/14/2014 11:07 PM, Aashish Chaudhary wrote: Looks like certain extensions are still not quite working on yours system even with the proprietary driver. I will see if I can run your code on my laptop but that would be for tomorrow. ** Assuming that this is not data dependent issue (which it should not). I think its probably this line causing the issue: bool driverSupport #if defined(__APPLE__) = true; #else = !(extensions-DriverIsATI() (extensions-GetDriverGLVersionMajor() = 3)) || extensions-GetIgnoreDriverBugs(ATI texturing bug); #endif On line number 181: can you change this code to : this-HasHardwareSupport=renwin!=NULLthis-IsSupported(renwin); to this-HasHardwareSupport=1; - Aashish On Tue, Oct 14, 2014 at 4:53 PM, B.W.H. van Beest b...@xs4all.nl mailto:b...@xs4all.nl wrote: Progress indeed. But I don't understand what you are saying about the transfer function. I' starting to wonder if I have two issues occurring simultaneously. In a new thread I just posted I described my problem in getting the colours in place. I need to write to a vtk file first and load it back. I just found that when I just did that and then switched fo volume rendering, an error was there about the absence of an opengl extension: ERROR: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, line 185 vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required extensions are not supported. This is complete unknown terrain for me. Regards, Bertwim On 10/14/2014 09:58 PM, Burlen Loring wrote: progress! it sounds like volume rendering is working on the wavelet dataset. You do need the scalars for volume rendering, so make sure you have those when you try. You need to select the scalars in the drop down also, I usually do this before changing to the volume representation. You also may need to edit the transfer function. For testing you could make the opacity over the entire scalar range in which case you should see a solid cube. If you've done all that and don't see anything it's likely that the dataset is messed up. Add a dataset-Print(cerr) statement to the end of your request data, look in the information panel and verify correct number of points and scalar ranges. If all else fails post the dataset to the list. After creating your cube go to the file menu and save data. On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: Hi Burlen, I have upgraded to the AMD drivers. Thanks for the hint. It has improved the situation a bit. Furthermore, I created the wavelet source. When selecting volume representation, I do see a three 3 picture, in all 5 volume rendering mode (smart, raycast and texture mapping, ray cast only, texture mapping only, GPU based). The picture a rather fuzzy, but then I don't know what I'm supposed to see here. The good news is that the openGL errors I had before when displaying a wavelet, now have gone. The situation with my own cube, though, has unchanged. unfortunately. The cube disappears in volume representation node, also when I re-inserted scalar values for each of the 8 vertices. Regards, Bertwim On 10/14/2014 06:06 PM, Burlen Loring wrote: Hi Bertwim, In recent releases of ParaView I have experienced issues/flakeyness with volume rendering. Something you should try: Create the wavelet source, then in the properties panel find volume rendering mode and set it to ray cast only. This has worked for me on a number of systems. may or may not work, but worth a try. The output you pasted below shows that although you've got a sweet ATI GPU you're not taking advantage of it! You're using the Intel integrated GPU with Mesa drivers. If I were you I would install proprietary the AMD drivers
Re: [Paraview] BOX - volume?
I am still busy with finding out which etensions are needed, and how I can enable them. THis opebnGL-world is a bit alien to me, so it will take some time. Regards, Bertwim On 10/14/2014 11:07 PM, Aashish Chaudhary wrote: Looks like certain extensions are still not quite working on yours system even with the proprietary driver. I will see if I can run your code on my laptop but that would be for tomorrow. ** Assuming that this is not data dependent issue (which it should not). I think its probably this line causing the issue: bool driverSupport #if defined(__APPLE__) = true; #else = !(extensions-DriverIsATI() (extensions-GetDriverGLVersionMajor() = 3)) || extensions-GetIgnoreDriverBugs(ATI texturing bug); #endif On line number 181: can you change this code to : this-HasHardwareSupport=renwin!=NULLthis-IsSupported(renwin); to this-HasHardwareSupport=1; - Aashish On Tue, Oct 14, 2014 at 4:53 PM, B.W.H. van Beest b...@xs4all.nl mailto:b...@xs4all.nl wrote: Progress indeed. But I don't understand what you are saying about the transfer function. I' starting to wonder if I have two issues occurring simultaneously. In a new thread I just posted I described my problem in getting the colours in place. I need to write to a vtk file first and load it back. I just found that when I just did that and then switched fo volume rendering, an error was there about the absence of an opengl extension: ERROR: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, line 185 vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required extensions are not supported. This is complete unknown terrain for me. Regards, Bertwim On 10/14/2014 09:58 PM, Burlen Loring wrote: progress! it sounds like volume rendering is working on the wavelet dataset. You do need the scalars for volume rendering, so make sure you have those when you try. You need to select the scalars in the drop down also, I usually do this before changing to the volume representation. You also may need to edit the transfer function. For testing you could make the opacity over the entire scalar range in which case you should see a solid cube. If you've done all that and don't see anything it's likely that the dataset is messed up. Add a dataset-Print(cerr) statement to the end of your request data, look in the information panel and verify correct number of points and scalar ranges. If all else fails post the dataset to the list. After creating your cube go to the file menu and save data. On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: Hi Burlen, I have upgraded to the AMD drivers. Thanks for the hint. It has improved the situation a bit. Furthermore, I created the wavelet source. When selecting volume representation, I do see a three 3 picture, in all 5 volume rendering mode (smart, raycast and texture mapping, ray cast only, texture mapping only, GPU based). The picture a rather fuzzy, but then I don't know what I'm supposed to see here. The good news is that the openGL errors I had before when displaying a wavelet, now have gone. The situation with my own cube, though, has unchanged. unfortunately. The cube disappears in volume representation node, also when I re-inserted scalar values for each of the 8 vertices. Regards, Bertwim On 10/14/2014 06:06 PM, Burlen Loring wrote: Hi Bertwim, In recent releases of ParaView I have experienced issues/flakeyness with volume rendering. Something you should try: Create the wavelet source, then in the properties panel find volume rendering mode and set it to ray cast only. This has worked for me on a number of systems. may or may not work, but worth a try. The output you pasted below shows that although you've got a sweet ATI GPU you're not taking advantage of it! You're using the Intel integrated GPU with Mesa drivers. If I were you I would install proprietary the AMD drivers http://support.amd.com/en-us/download. This should give you nice performance boost and may even solve the OpenGL errors you reported, which these days are as often (or more) a result of bugs in the Mesa drivers than in VTK. Burlen On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: OS: OpenSuSe 13.1 # lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] # glxinfo name of display: :0 display: :0 screen: 0 direct rendering: Yes
Re: [Paraview] BOX - volume?
Progress indeed. But I don't understand what you are saying about the transfer function. I' starting to wonder if I have two issues occurring simultaneously. In a new thread I just posted I described my problem in getting the colours in place. I need to write to a vtk file first and load it back. I just found that when I just did that and then switched fo volume rendering, an error was there about the absence of an opengl extension: ERROR: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, line 185 vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required extensions are not supported. This is complete unknown terrain for me. Regards, Bertwim On 10/14/2014 09:58 PM, Burlen Loring wrote: progress! it sounds like volume rendering is working on the wavelet dataset. You do need the scalars for volume rendering, so make sure you have those when you try. You need to select the scalars in the drop down also, I usually do this before changing to the volume representation. You also may need to edit the transfer function. For testing you could make the opacity over the entire scalar range in which case you should see a solid cube. If you've done all that and don't see anything it's likely that the dataset is messed up. Add a dataset-Print(cerr) statement to the end of your request data, look in the information panel and verify correct number of points and scalar ranges. If all else fails post the dataset to the list. After creating your cube go to the file menu and save data. On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: Hi Burlen, I have upgraded to the AMD drivers. Thanks for the hint. It has improved the situation a bit. Furthermore, I created the wavelet source. When selecting volume representation, I do see a three 3 picture, in all 5 volume rendering mode (smart, raycast and texture mapping, ray cast only, texture mapping only, GPU based). The picture a rather fuzzy, but then I don't know what I'm supposed to see here. The good news is that the openGL errors I had before when displaying a wavelet, now have gone. The situation with my own cube, though, has unchanged. unfortunately. The cube disappears in volume representation node, also when I re-inserted scalar values for each of the 8 vertices. Regards, Bertwim On 10/14/2014 06:06 PM, Burlen Loring wrote: Hi Bertwim, In recent releases of ParaView I have experienced issues/flakeyness with volume rendering. Something you should try: Create the wavelet source, then in the properties panel find volume rendering mode and set it to ray cast only. This has worked for me on a number of systems. may or may not work, but worth a try. The output you pasted below shows that although you've got a sweet ATI GPU you're not taking advantage of it! You're using the Intel integrated GPU with Mesa drivers. If I were you I would install proprietary the AMD drivers http://support.amd.com/en-us/download. This should give you nice performance boost and may even solve the OpenGL errors you reported, which these days are as often (or more) a result of bugs in the Mesa drivers than in VTK. Burlen On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: OS: OpenSuSe 13.1 # lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] # glxinfo name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions:
Re: [Paraview] BOX - volume?
You could try it without modifying any code by setting the following cmake variable. VTK_IGNORE_GLDRIVER_BUGS:BOOL=ON and recompile ParaView. With my ATI Radeon HD7780 projected tetrahedra just hangs. Burlen On 10/14/2014 02:07 PM, Aashish Chaudhary wrote: Looks like certain extensions are still not quite working on yours system even with the proprietary driver. I will see if I can run your code on my laptop but that would be for tomorrow. ** Assuming that this is not data dependent issue (which it should not). I think its probably this line causing the issue: bool driverSupport #if defined(__APPLE__) = true; #else = !(extensions-DriverIsATI() (extensions-GetDriverGLVersionMajor() = 3)) || extensions-GetIgnoreDriverBugs(ATI texturing bug); #endif On line number 181: can you change this code to : this-HasHardwareSupport=renwin!=NULLthis-IsSupported(renwin); to this-HasHardwareSupport=1; - Aashish On Tue, Oct 14, 2014 at 4:53 PM, B.W.H. van Beest b...@xs4all.nl mailto:b...@xs4all.nl wrote: Progress indeed. But I don't understand what you are saying about the transfer function. I' starting to wonder if I have two issues occurring simultaneously. In a new thread I just posted I described my problem in getting the colours in place. I need to write to a vtk file first and load it back. I just found that when I just did that and then switched fo volume rendering, an error was there about the absence of an opengl extension: ERROR: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, line 185 vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required extensions are not supported. This is complete unknown terrain for me. Regards, Bertwim On 10/14/2014 09:58 PM, Burlen Loring wrote: progress! it sounds like volume rendering is working on the wavelet dataset. You do need the scalars for volume rendering, so make sure you have those when you try. You need to select the scalars in the drop down also, I usually do this before changing to the volume representation. You also may need to edit the transfer function. For testing you could make the opacity over the entire scalar range in which case you should see a solid cube. If you've done all that and don't see anything it's likely that the dataset is messed up. Add a dataset-Print(cerr) statement to the end of your request data, look in the information panel and verify correct number of points and scalar ranges. If all else fails post the dataset to the list. After creating your cube go to the file menu and save data. On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: Hi Burlen, I have upgraded to the AMD drivers. Thanks for the hint. It has improved the situation a bit. Furthermore, I created the wavelet source. When selecting volume representation, I do see a three 3 picture, in all 5 volume rendering mode (smart, raycast and texture mapping, ray cast only, texture mapping only, GPU based). The picture a rather fuzzy, but then I don't know what I'm supposed to see here. The good news is that the openGL errors I had before when displaying a wavelet, now have gone. The situation with my own cube, though, has unchanged. unfortunately. The cube disappears in volume representation node, also when I re-inserted scalar values for each of the 8 vertices. Regards, Bertwim On 10/14/2014 06:06 PM, Burlen Loring wrote: Hi Bertwim, In recent releases of ParaView I have experienced issues/flakeyness with volume rendering. Something you should try: Create the wavelet source, then in the properties panel find volume rendering mode and set it to ray cast only. This has worked for me on a number of systems. may or may not work, but worth a try. The output you pasted below shows that although you've got a sweet ATI GPU you're not taking advantage of it! You're using the Intel integrated GPU with Mesa drivers. If I were you I would install proprietary the AMD drivers http://support.amd.com/en-us/download. This should give you nice performance boost and may even solve the OpenGL errors you reported, which these days are as often (or more) a result of bugs in the Mesa drivers than in VTK. Burlen On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: OS: OpenSuSe 13.1 # lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] # glxinfo name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI
Re: [Paraview] BOX - volume?
You can create a wavelet source and then display it as a volume. On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest b...@xs4all.nl wrote: Can perhaps somebody point me how to address the following. When I create a new source (say: a box) I get an a box that can be displayed via its surfaces, its constituing points, or wireframe representation. But I need a volume rendering (so that I can add e.g. a clipping plane) How do I get that? Regards, Bertwim ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- *| Aashish Chaudhary | Technical Leader | Kitware Inc.* *| http://www.kitware.com/company/team/chaudhary.html http://www.kitware.com/company/team/chaudhary.html* ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] BOX - volume?
Aashish, Thanks for the suggestion. However, doing this gives me all kinds of opengl errors (invalid instruction). Besides that, the wavelet gives me a cube indeed, but I need to understand when I can have a volume rendering. I created new Source's (e.g. tri-prism, a wedge, a box with boundaries of finite thickness etc.). But I cannot get volume rendering to work, grr. (See other thread) Kind Regards, Bertwim On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: You can create a wavelet source and then display it as a volume. On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest b...@xs4all.nl mailto:b...@xs4all.nl wrote: Can perhaps somebody point me how to address the following. When I create a new source (say: a box) I get an a box that can be displayed via its surfaces, its constituing points, or wireframe representation. But I need a volume rendering (so that I can add e.g. a clipping plane) How do I get that? Regards, Bertwim ___ Powered by www.kitware.com http://www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- /| Aashish Chaudhary | Technical Leader | Kitware Inc. / /| http://www.kitware.com/company/team/chaudhary.html/ ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] BOX - volume?
So when you created a wavelet source and change the representation to volume you got the errors? Can you post those errors? Thanks, On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest b...@xs4all.nl wrote: Aashish, Thanks for the suggestion. However, doing this gives me all kinds of opengl errors (invalid instruction). Besides that, the wavelet gives me a cube indeed, but I need to understand when I can have a volume rendering. I created new Source's (e.g. tri-prism, a wedge, a box with boundaries of finite thickness etc.). But I cannot get volume rendering to work, grr. (See other thread) Kind Regards, Bertwim On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: You can create a wavelet source and then display it as a volume. On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest b...@xs4all.nl wrote: Can perhaps somebody point me how to address the following. When I create a new source (say: a box) I get an a box that can be displayed via its surfaces, its constituing points, or wireframe representation. But I need a volume rendering (so that I can add e.g. a clipping plane) How do I get that? Regards, Bertwim ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html http://www.kitware.com/company/team/chaudhary.html* -- *| Aashish Chaudhary | Technical Leader | Kitware Inc.* *| http://www.kitware.com/company/team/chaudhary.html http://www.kitware.com/company/team/chaudhary.html* ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] BOX - volume?
Hi Aashish, This is what I do: 1. start paraview 2. Sources - Wavelet - Apply. A cube is displayed (Outline representation). 3. Select 'Volume representation cube disappears. Then: = Generic Warning: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, line 487 failed at glBindTexture 1 OpenGL errors detected 0 : (1282) Invalid operation Generic Warning: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, line 487 failed at glBindTexture 1 OpenGL errors detected 0 : (1282) Invalid operation Generic Warning: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, line 487 failed at glBindTexture 1 OpenGL errors detected 0 : (1282) Invalid operation = On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: So when you created a wavelet source and change the representation to volume you got the errors? Can you post those errors? Thanks, On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest b...@xs4all.nl mailto:b...@xs4all.nl wrote: Aashish, Thanks for the suggestion. However, doing this gives me all kinds of opengl errors (invalid instruction). Besides that, the wavelet gives me a cube indeed, but I need to understand when I can have a volume rendering. I created new Source's (e.g. tri-prism, a wedge, a box with boundaries of finite thickness etc.). But I cannot get volume rendering to work, grr. (See other thread) Kind Regards, Bertwim On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: You can create a wavelet source and then display it as a volume. On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest b...@xs4all.nl mailto:b...@xs4all.nl wrote: Can perhaps somebody point me how to address the following. When I create a new source (say: a box) I get an a box that can be displayed via its surfaces, its constituing points, or wireframe representation. But I need a volume rendering (so that I can add e.g. a clipping plane) How do I get that? Regards, Bertwim ___ Powered by www.kitware.com http://www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- /| Aashish Chaudhary | Technical Leader | Kitware Inc. / /| http://www.kitware.com/company/team/chaudhary.html/ -- /| Aashish Chaudhary | Technical Leader | Kitware Inc. / /| http://www.kitware.com/company/team/chaudhary.html/ ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] BOX - volume?
What graphics card / graphics driver version / OS this system has? - Aashish On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. van Beest b...@xs4all.nl wrote: Hi Aashish, This is what I do: 1. start paraview 2. Sources - Wavelet - Apply. A cube is displayed (Outline representation). 3. Select 'Volume representation cube disappears. Then: = Generic Warning: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, line 487 failed at glBindTexture 1 OpenGL errors detected 0 : (1282) Invalid operation Generic Warning: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, line 487 failed at glBindTexture 1 OpenGL errors detected 0 : (1282) Invalid operation Generic Warning: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, line 487 failed at glBindTexture 1 OpenGL errors detected 0 : (1282) Invalid operation = On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: So when you created a wavelet source and change the representation to volume you got the errors? Can you post those errors? Thanks, On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest b...@xs4all.nl wrote: Aashish, Thanks for the suggestion. However, doing this gives me all kinds of opengl errors (invalid instruction). Besides that, the wavelet gives me a cube indeed, but I need to understand when I can have a volume rendering. I created new Source's (e.g. tri-prism, a wedge, a box with boundaries of finite thickness etc.). But I cannot get volume rendering to work, grr. (See other thread) Kind Regards, Bertwim On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: You can create a wavelet source and then display it as a volume. On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest b...@xs4all.nl wrote: Can perhaps somebody point me how to address the following. When I create a new source (say: a box) I get an a box that can be displayed via its surfaces, its constituing points, or wireframe representation. But I need a volume rendering (so that I can add e.g. a clipping plane) How do I get that? Regards, Bertwim ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html http://www.kitware.com/company/team/chaudhary.html* -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html http://www.kitware.com/company/team/chaudhary.html* -- *| Aashish Chaudhary | Technical Leader | Kitware Inc.* *| http://www.kitware.com/company/team/chaudhary.html http://www.kitware.com/company/team/chaudhary.html* ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] BOX - volume?
OS: OpenSuSe 13.1 # lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] # glxinfo name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.3 OpenGL core profile shading language version string: 1.40 OpenGL core profile context flags: (none) OpenGL core profile extensions: GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_base_instance, GL_ARB_blend_func_extended, GL_ARB_copy_buffer, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_shader, GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, GL_ARB_occlusion_query2, GL_ARB_pixel_buffer_object, GL_ARB_point_sprite, GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, GL_ARB_shader_texture_lod, GL_ARB_shading_language_420pack, GL_ARB_shading_language_packing, GL_ARB_sync, GL_ARB_texture_buffer_object, GL_ARB_texture_buffer_object_rgb32, GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map_array, GL_ARB_texture_float, GL_ARB_texture_multisample, GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, GL_ARB_texture_rectangle, GL_ARB_texture_rg, GL_ARB_texture_rgb10_a2ui, GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, GL_ARB_texture_swizzle, GL_ARB_timer_query, GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, GL_ATI_blend_equation_separate, GL_ATI_texture_float, GL_EXT_abgr, GL_EXT_blend_equation_separate, GL_EXT_draw_buffers2, GL_EXT_draw_instanced, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, GL_EXT_framebuffer_multisample_blit_scaled, GL_EXT_framebuffer_sRGB, GL_EXT_packed_depth_stencil, GL_EXT_packed_float, GL_EXT_pixel_buffer_object, GL_EXT_provoking_vertex, GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_rgtc, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode,
