| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0003685 | VTK | (No Category) | public | 2006-08-31 15:58 | 2016-08-12 09:54 | ||||
| Reporter | Shang Mu | ||||||||
| Assigned To | Will Schroeder | ||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||
| Status | closed | Resolution | moved | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0003685: vtkRenderWindowInteractor / vtkOpenGLVolumeTextureMapper3D bug? | ||||||||
| Description | I'm volume rendering a 3D image read from DICOM sequence using vtkOpenGLVolumeTextureMapper3D, and the window is a vtkRenderWindowInteractor. When I use camera mode, the interactor works fine (generally smooth with a little lag), but if I switch to actor mode and move the actor, it takes more than half a minute to render a scene. Is it a bug or some implementation limitation? I'm using wxPython under Windows, so the class I used is actually wxVTKRenderWindowInteractor. This should not be the point though. | ||||||||
| Tags | No tags attached. | ||||||||
| Project | |||||||||
| Type | |||||||||
| Attached Files | |||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0036886) Kitware Robot (administrator) 2016-08-12 09:54 |
Resolving issue as `moved`. This issue tracker is no longer used. Further discussion of this issue may take place in the current VTK Issues page linked in the banner at the top of this page. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2011-06-16 13:11 | Zack Galbreath | Category | => (No Category) |
| 2016-08-12 09:54 | Kitware Robot | Note Added: 0036886 | |
| 2016-08-12 09:54 | Kitware Robot | Status | expired => closed |
| 2016-08-12 09:54 | Kitware Robot | Resolution | open => moved |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |