View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0013801ParaView(No Category)public2013-01-18 05:402016-08-12 09:59
ReporterPaul Melis 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version3.98.0 
Target VersionFixed in Version 
Summary0013801: Incorrect image out (purple squares) with parallel GPU-based volume rendering
DescriptionI originally reported this problem for 3.14.1 on the mailing list, see thread "Errors with GPU-based volume rendering" in November 2011. Just found that with 3.98.0 this problem still exists.

I tested with running 2 pvserver processes (on 2 nodes, one per node). The problem can be demonstrated by creating the default wavelet source and switching to GPU-based volume rendering. The output shows a few purple squares (see screenshot), presumably the image-space bounding boxes of the per-node rendered views.

On the console there's also some errors:

paulm@v41-6:~$ DISPLAY=:0.0 mpirun -x DISPLAY pvserver --use-offscreen-rendering
Waiting for client...
Connection URL: cs://v41-6:11111
Accepting connection(s): v41-6:11111
Client connected.
after uniforms for textures ERROR (x501) Invalid value
framebuffer has an attachment error
framebuffer has an attachment error
SetupRender ERROR (x506) invalid framebuffer operation ext
framebuffer has an attachment error
framebuffer has an attachment error
after uniforms for textures ERROR (x501) Invalid value
framebuffer has an attachment error
framebuffer has an attachment error
SetupRender ERROR (x506) invalid framebuffer operation ext
framebuffer has an attachment error
framebuffer has an attachment error
render clipped 1 ERROR (x506) invalid framebuffer operation ext
render clipped 1 ERROR (x506) invalid framebuffer operation ext
after uniforms for textures ERROR (x501) Invalid value
[...]

The render nodes have NVidia GTX460's and driver 295.40. I can't easily test a newer driver version, but we'll be doing a cluster upgrade soon anyway, so I'll retest then.

There's workaround mentioned in the mailing list thread that still works: save to a state file and reload the state (this even works without restarting paraview).
TagsNo tags attached.
ProjectTBD
Topic Name
Typeincorrect functionality
Attached Filespng file icon Screenshot from 2013-01-18 11:26:05.png [^] (173,564 bytes) 2013-01-18 05:40

 Relationships

  Notes
(0036069)
Mathieu Westphal (developer)
2016-06-16 05:32

 Does not seems to happen with ParaView master opengl1
Can you try to reproduce with a newer version of paraview ?
(0036074)
Utkarsh Ayachit (administrator)
2016-06-16 09:01

 The volume rendering code has been rewritten from scratch for ParaView 5.0, so it's definitely worth a retry.
(0038316)
Kitware Robot (administrator)
2016-08-12 09:59

 Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.

 Issue History
Date Modified Username Field Change
2013-01-18 05:40 Paul Melis New Issue
2013-01-18 05:40 Paul Melis File Added: Screenshot from 2013-01-18 11:26:05.png
2016-06-16 05:32 Mathieu Westphal Note Added: 0036069
2016-06-16 09:01 Utkarsh Ayachit Note Added: 0036074
2016-08-12 09:59 Kitware Robot Note Added: 0038316
2016-08-12 09:59 Kitware Robot Status backlog => closed
2016-08-12 09:59 Kitware Robot Resolution open => moved
2016-08-12 09:59 Kitware Robot Assigned To => Kitware Robot

Copyright © 2000 - 2018 MantisBT Team