VTK issueshttps://gitlab.kitware.com/vtk/vtk/-/issues2023-10-04T15:58:22-04:00https://gitlab.kitware.com/vtk/vtk/-/issues/15799regression: OpenGL2 backend broke support for LineStipple2023-10-04T15:58:22-04:00Kitware Robotregression: OpenGL2 backend broke support for LineStipple**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15799). Further discussion may take place here.**
---
The VTK 6.3 OpenGL2 backend does not support the vtkProperty::SetLineStipplePat...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15799). Further discussion may take place here.**
---
The VTK 6.3 OpenGL2 backend does not support the vtkProperty::SetLineStipplePattern() public API.
This is due to line stipple being removed from OpenGL version 3.1.
For us, this is an important regression in functionality, because we use line stipple in many places.https://gitlab.kitware.com/vtk/vtk/-/issues/15818Incorrect rendering with multiple vtkRenderer while using jogl window.2018-10-23T14:51:44-04:00Kitware RobotIncorrect rendering with multiple vtkRenderer while using jogl window.**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15818). Further discussion may take place here.**
---
Starting from java 7 we cannot use anymore the vtkPanel in java application on ...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15818). Further discussion may take place here.**
---
Starting from java 7 we cannot use anymore the vtkPanel in java application on OSX system (some part of the AWT library are not anymore supported) so we rely exclusively on OpenGL (using JOGL) to support VTK rendering in java application.
The problem is that there is a severe issue when we use any JOGL component (vtkJoglPanelComponent or vtkJoglCanvasComponent) for rendering.
As soon we have multiple renderer (vtkRenderer) in the render window (vtkOpenGLRenderWindow) the rendering view is limited to the last renderer viewport.
That is a big problem as even using something quite common as the vtkOrientationMarkerWidget to display 3D axis will internally use an extra renderer (with a specific viewport) and make rendering completely clipped.
That is something which has been discussed here:
http://markmail.org/message/2zozk4jqvlrq6dvv
As simple example to show the problem is to use multiple viewport example from VTK:
http://www.vtk.org/Wiki/VTK/Examples/Cxx/Visualization/MultipleViewports
Using this example inside a vtkJoglPanelComponent will make only the bottom right sphere visible (other part of the screen is blank).https://gitlab.kitware.com/vtk/vtk/-/issues/15828vtkButtonWidget(with vtkTex) cannot capture correct event/render at correct p...2018-10-23T14:51:31-04:00Kitware RobotvtkButtonWidget(with vtkTex) cannot capture correct event/render at correct position when the window has more than one renderers**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15828). Further discussion may take place here.**
---
1. create window
2. add two renderers to the window. one is up, one is donw
3...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15828). Further discussion may take place here.**
---
1. create window
2. add two renderers to the window. one is up, one is donw
3. add vtkButtonWidget to the window.
4. When click on the window, move the button to that position (on upper renderer)
Set current render as upper render.
capture the position
int x = this->Interactor->GetEventPosition()[0];
int y = this->Interactor->GetEventPosition()[1];
calculate bounds and put the widget
button->GetRepresentation()->PlaceWidget(bounds);
Now you have two option.
1) use input x,y input
2) calculate the x,y position according to the view port of renderer. Assume you put on the upper render, whose lowerleft maybe (0, 1/2 size of window)
5. Do render now. for case
1), the button will not put on correct position but to top of the window. Seems the position is calculated using (0,0) as lowerLeft
for case 2) the display is correct
6. Move your mouse to the button
Nothing happens. You cannot click the button and raise any event
I debug into vtkTexturedButtonRepresentation2D, it will check the positin of mouse and see if it in area of texture image of the button.
For case 2, seems the button assume the origin point is (0, 1/2 the size of window height). But the input of MoveAction use display coordination (assume the origin point is (0,0). So it not works
If you move the mouse down to lower. Example, the button at (20,60), the window size is (100,100), you move to (20, 10),the mouse changed and it think we are on the button. Actually not.
7. So, shall we change the renderer logic? or change the MoveAction/SelectAction logic? at least one is incorrect. I assume the render logic has something wrong.
https://gitlab.kitware.com/vtk/vtk/-/issues/15835vtkImplicitPlaneWidget2: tubing error2018-10-23T14:50:07-04:00Kitware RobotvtkImplicitPlaneWidget2: tubing error**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15835). Further discussion may take place here.**
---
When the plane is incident to one of the vertices of the box, the cutter produc...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15835). Further discussion may take place here.**
---
When the plane is incident to one of the vertices of the box, the cutter produces two points for this vertex, leading to an error during the tubing:
Generic Warning: In F:\lhabert\dev\VTK-6.3.0\Common\DataModel\vtkPolyLine.cxx, line 106
Coincident points in polyline...can't compute normals
Warning: In F:\lhabert\dev\VTK-6.3.0\Filters\Core\vtkTubeFilter.cxx, line 243
vtkTubeFilter (0000000020976ED0): Could not generate normals for line. Skipping to next.
https://gitlab.kitware.com/vtk/vtk/-/issues/15841vtkCutter not cutting vtkPolyhedron cells correctly2019-11-05T15:21:12-05:00Kitware RobotvtkCutter not cutting vtkPolyhedron cells correctly**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15841). Further discussion may take place here.**
---
In unstructured grids with a mix of polyhedral and hexahedral cells, vtkCutter ...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15841). Further discussion may take place here.**
---
In unstructured grids with a mix of polyhedral and hexahedral cells, vtkCutter produces a cut with missing faces - and it seems as if these missing faces are in the polyhedral cells next to hex cells.
See attached screenshot and vtu file.
[mesh.vtu](/uploads/9411bf053d3a9d49e402ba87ee7d1352/mesh.vtu)
![vtk_polyhedral_hex_cut](/uploads/992cb6b596b7d6ccb11165e294de0830/vtk_polyhedral_hex_cut.png)https://gitlab.kitware.com/vtk/vtk/-/issues/15845vtkBandedDataContourFilter does not fill contours properly2018-10-23T16:41:23-04:00Kitware RobotvtkBandedDataContourFilter does not fill contours properly**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15845). Further discussion may take place here.**
---
Download all attached files into a directory
Run
~/build/VTK/bin/vtkpython band...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15845). Further discussion may take place here.**
---
Download all attached files into a directory
Run
~/build/VTK/bin/vtkpython banded-contour.py
This generates a file band-4.vtp which is the band between contours at 40 and 50.
Load banded-contour.pvsm in ParaView. This shows contours at 40 and 50 and the band generated at the previous step.
The bug is that the band is not the proper fill of the space between the two contours. See also the attached images which shows the contours and then the contours and the band.
The following behavior is actually the bug we've seen in UVCDAT.
If you generate bands for all intervals (0,10), (10,20), ... (90,100) and load
those in ParaView, the generated image has missing triangles.
See contours-all.png
To try this:
1. Execute
~/build/VTK/bin/vtkpython banded-contour-all.py
2. Load in ParaView
banded-contour-all.pvsm
You'll see an image with missing triangles.
[banded-contour.pvsm](/uploads/a649e083a004cffb545d39b106d03d70/banded-contour.pvsm)
![band-40-50](/uploads/94b1a9afbce947283a95cae7eda49188/band-40-50.png)
[banded-contour.py](/uploads/3e130e1d91cf95765b2281e5654cea5b/banded-contour.py)
[banded-contour-all.py](/uploads/5ad0ca9d9ba4dc7a34e66980a526dcc4/banded-contour-all.py)
[banded-contour-all.pvsm](/uploads/33aad53a6ef10039e4311f764306d310/banded-contour-all.pvsm)
[band-input.vtp](/uploads/2ef2d06a0819028d2987b7f1585d841f/band-input.vtp)
![contours-40-50](/uploads/e25b4f2e759549465503e17bebe5c4cc/contours-40-50.png)
![contours-all](/uploads/6c345601a9bd4583a0ef9fba22f13f17/contours-all.png)https://gitlab.kitware.com/vtk/vtk/-/issues/15852vtkOpenGLRenderWindow::GetColorBufferSizes (OpenGL2, VTK 6.3) fails on a quad...2018-10-23T14:46:06-04:00Kitware RobotvtkOpenGLRenderWindow::GetColorBufferSizes (OpenGL2, VTK 6.3) fails on a quadro 4000M**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15852). Further discussion may take place here.**
---
With a quadro-4000M card under windows 7 64 bits, the glGetFramebufferAttachmen...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15852). Further discussion may take place here.**
---
With a quadro-4000M card under windows 7 64 bits, the glGetFramebufferAttachmentParameteriv calls in GetColorBufferSizes raise a GL_INVALID_ENUM.
I tried various tweaks (like not fixing attachment), to no avail.
It is the same graphics card for which I reported a non standard behaviour in 0015784, so it is definitely a flaky card, but the problem remains.
I modified the code to return 8-8-8-8 in case the glGetFramebufferAttachmentParameteriv calls fail, and everything now seems to be working fine on this machine.
I know it's ugly, but it's better than failing.https://gitlab.kitware.com/vtk/vtk/-/issues/15901Uninitialized information variables in image filters are causing crashes2018-10-23T16:25:24-04:00Kitware RobotUninitialized information variables in image filters are causing crashes**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15901). Further discussion may take place here.**
---
vtkImageResliceMapper has several uninitialized variables, for example in t...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15901). Further discussion may take place here.**
---
vtkImageResliceMapper has several uninitialized variables, for example in the GetIndexMatrix function. There the variables inOrigin, inSpacing, outOrigin and outSpacing are declared and then filled via inInfo->Get(vtkDataObject::SPACING(), inSpacing) and so on. These calls don't succeed in every case though, so that some of the variables can be left uninitialized. The same thing can happen in the RequestInformation function (inSpacing, inOrigin, inWholeExt, outSpacing, outOrigin, outWholeExt, maxBounds).
Leaving the variables in an uninitialized state causes the filter to misbehave. The following program demonstrates this:
```
#include "vtkBMPWriter.h"
#include "vtkCommand.h"
#include "vtkImageReslice.h"
#include "vtkRenderer.h"
#include "vtkRenderWindow.h"
#include "vtkRenderWindowInteractor.h"
#include "vtkSmartPointer.h"
#include "vtkSmartVolumeMapper.h"
#include "vtkStructuredPointsReader.h"
#include "vtkVolume.h"
#include "vtkWindowToImageFilter.h"
class MyCallBack: public vtkCommand
{
public:
static MyCallBack *New()
{
return new MyCallBack;
}
virtual void Execute(vtkObject* caller, unsigned long eventId, void* callData)
{
if (eventId != vtkCommand::KeyPressEvent) return;
vtkRenderWindowInteractor* interactor = static_cast<vtkRenderWindowInteractor*>(caller);
if (interactor == NULL) return;
char* pressedKey = interactor->GetKeySym();
if (strcmp(pressedKey, "9") == 0)
{
windowToImageFilter->Modified();
bitmapWriter->SetFileName("ImageResliceBug.bmp");
bitmapWriter->Write();
}
}
vtkSmartPointer<vtkWindowToImageFilter> windowToImageFilter;
vtkSmartPointer<vtkBMPWriter> bitmapWriter;
};
int main()
{
vtkSmartPointer<vtkStructuredPointsReader> pointsReader = vtkSmartPointer<vtkStructuredPointsReader>::New();
pointsReader->SetFileName("ironProt.vtk");
pointsReader->Update();
vtkSmartPointer<vtkSmartVolumeMapper> smartMapper = vtkSmartPointer<vtkSmartVolumeMapper>::New();
smartMapper->SetInputConnection(pointsReader->GetOutputPort());
vtkSmartPointer<vtkVolume> volume = vtkSmartPointer<vtkVolume>::New();
volume->SetMapper(smartMapper);
vtkSmartPointer<vtkRenderer> renderer = vtkSmartPointer<vtkRenderer>::New();
vtkSmartPointer<vtkRenderWindow> renderWindow = vtkSmartPointer<vtkRenderWindow>::New();
vtkSmartPointer<vtkRenderWindowInteractor> interactor= vtkSmartPointer<vtkRenderWindowInteractor>::New();
renderWindow->AddRenderer(renderer);
renderWindow->SetSize(500, 300);
renderWindow->SetPosition(100, 100);
interactor->SetRenderWindow(renderWindow);
renderer->AddActor(volume);
renderer->SetBackground(1.0, 1.0, 1.0);
vtkSmartPointer<vtkWindowToImageFilter> windowToImageFilter = vtkSmartPointer<vtkWindowToImageFilter>::New();
windowToImageFilter->SetInput(renderWindow);
vtkSmartPointer<vtkImageReslice> imageReslice = vtkSmartPointer<vtkImageReslice>::New();
imageReslice->SetInputConnection(windowToImageFilter->GetOutputPort());
vtkSmartPointer<vtkBMPWriter> bitmapWriter = vtkSmartPointer<vtkBMPWriter>::New();
bitmapWriter->SetInputConnection(imageReslice->GetOutputPort());
vtkSmartPointer<MyCallBack> callback = vtkSmartPointer<MyCallBack>::New();
callback->bitmapWriter = bitmapWriter;
callback->windowToImageFilter = windowToImageFilter;
interactor->AddObserver("KeyPressEvent", callback);
// Let's go
renderWindow->Render();
interactor->Start();
}
```
Pressing '9' will attempt to write a bitmap to file and crashes with an access violation in vtkWindowToImageFilter.cxx on line 484 on my machine (I'm using VTK 6.2 on windows using the OpenGL2 backend).
I suspect this crash doesn't happen if you set the spacing/origin etc in the reslice filter, but this wasn't necessary in VTK 5.10. Even if this is now required, forgetting this shouldn't cause a crash. Initializing the values to things like {0.0, 0.0, 0.0} for the origin and {1.0, 1.0, 1.0} for the spacing etc fixes the problem for me.
When you try to reproduce this issue, don't use a debug build of VTK, because then the variables are automatically initialized to sane values and don't contain random values (at least on windows).
David GobbiDavid Gobbihttps://gitlab.kitware.com/vtk/vtk/-/issues/15933Anti aliasing is off with VTK 6.3.02018-10-23T14:40:13-04:00Kitware RobotAnti aliasing is off with VTK 6.3.0**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15933). Further discussion may take place here.**
---
It seems the bug described in this issue: #15433
is not totally 100% fixed, I ...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15933). Further discussion may take place here.**
---
It seems the bug described in this issue: #15433
is not totally 100% fixed, I have the same issue using VTK 6.3.0.
In my case though I am using the vtkGenericOpenGLRenderWindow() (through vtkJoglPanelComponent). I was using the classic vtkPanel before.
https://gitlab.kitware.com/vtk/vtk/-/issues/159492nd order tensor storage inconsistency2018-10-23T15:52:57-04:00Kitware Robot2nd order tensor storage inconsistency**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15949). Further discussion may take place here.**
---
Some places in VTK use a C/row-major ordering of 2nd order tensors (vtkGradient...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15949). Further discussion may take place here.**
---
Some places in VTK use a C/row-major ordering of 2nd order tensors (vtkGradientFitler, vtkCell::Derivative()) and others assume a Fortran/column major ordering (vtkCellDerivatives, some of the numpy interface code). It's been decided that for consistency that VTK will go with C/row-major ordering. https://gitlab.kitware.com/vtk/vtk/-/issues/15962VTK 7.0.0.rc1 Java Dicom application keypress event handlers not working2018-10-23T16:42:01-04:00Kitware RobotVTK 7.0.0.rc1 Java Dicom application keypress event handlers not working**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15962). Further discussion may take place here.**
---
I am using Eclipse Mars.1 with Java 1.8 64 bit on Windows 10.
The attached zip...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15962). Further discussion may take place here.**
---
I am using Eclipse Mars.1 with Java 1.8 64 bit on Windows 10.
The attached zip file contains an Eclipse project folder with a java application that implements a sample program to display a stack of DICOM imasges. It works correctly except that the up/down keypress handlers are not firing, so it is not possible to step through the stack of images. I am new to VTK so I don't know if this is an implementation error on the Java side or something wrong on the VTK side.
The main method contains a path name to a folder containing DICOM images. Just replace this with your own path to run the demo.
Or just examine the code to see if you recognize the error. If it is an error on the Java side, it is probably obvious.
[VTKDicom.zip](/uploads/564f2dc0b1a789d48ccd08ed56b256b7/VTKDicom.zip)
Thanks,
Kenthttps://gitlab.kitware.com/vtk/vtk/-/issues/15966vtkInteractorStyleTrackballCamera changed after timer added2018-10-23T14:36:33-04:00Kitware RobotvtkInteractorStyleTrackballCamera changed after timer added**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15966). Further discussion may take place here.**
---
When I use the vtkInteractorStyleTrackballCamera, the object movement will stop...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15966). Further discussion may take place here.**
---
When I use the vtkInteractorStyleTrackballCamera, the object movement will stop when the mouse freezes ( with mouse button still down). After I added a timer, the object keep moving even when the mouse stop moving. Only after I release the mouse button, the movement stops.
reproduction code:
```python
#!/usr/bin/env python
import vtk
class vtkTimerCallback():
def __init__(self):
self.timer_count = 0
def execute(self,obj,event):
print(self.timer_count)
self.timer_count += 1
src = vtk.vtkCubeSource()
mapper = vtk.vtkPolyDataMapper()
mapper.SetInputConnection(src.GetOutputPort())
actor = vtk.vtkActor()
actor.SetMapper(mapper)
main_render = vtk.vtkRenderer()
main_render.AddActor(actor)
renWin = vtk.vtkRenderWindow()
renWin.AddRenderer(main_render)
iren = vtk.vtkRenderWindowInteractor()
iren.SetRenderWindow(renWin)
iren.SetInteractorStyle(vtk.vtkInteractorStyleTrackballCamera())
iren.Initialize()
cb = vtkTimerCallback()
cb.actor = actor
iren.AddObserver('TimerEvent', cb.execute)
timerId = iren.CreateRepeatingTimer(50);
iren.Start()
```
reference post:
http://vtk.1045678.n5.nabble.com/interaction-problem-after-timer-added-td5736076.html
https://gitlab.kitware.com/vtk/vtk/-/issues/15969vtkSMPContourGrid produces artifacts2018-10-23T16:43:21-04:00Kitware RobotvtkSMPContourGrid produces artifacts**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15969). Further discussion may take place here.**
---
Under certain conditions, the vtkSMPContourGrid filter produces isosurfaces tha...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15969). Further discussion may take place here.**
---
Under certain conditions, the vtkSMPContourGrid filter produces isosurfaces that are patchy and have buggy vertex connections. In these examples, I was using a composite dataset containing vtkUnstructuredGrids (disk_ref_out.ex2) and contouring at 0.000718448 in data array CH4.
The attached images show combinations of:
- MergePieces (merge)
- ScalarTree -- vtkSpanSpace (tree)
merge-off-tree-off produces the correct output.
merge-on-tree-off and merge-off-tree-on both have problems.
Additionally, some polygons flicker in-and-out as subsequent frames are rendered. Uninitialized memory access maybe?
![merge-off-tree-on](/uploads/3764c3f92a964910a89b7a4294ac41eb/merge-off-tree-on.png)
![merge-off-tree-off](/uploads/eb4db057f755eefd3c3fdb800f61313b/merge-off-tree-off.png)
![merge-on-tree-off](/uploads/c3fad29b3065f3f7ac4d3d242dde4eed/merge-on-tree-off.png)https://gitlab.kitware.com/vtk/vtk/-/issues/15983VTK crash with OpenFOAM2018-10-23T14:35:13-04:00Kitware RobotVTK crash with OpenFOAM**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15983). Further discussion may take place here.**
---
The simplest OpenFOAM (version 3.0) example (icoFoam.C) with included the simpl...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15983). Further discussion may take place here.**
---
The simplest OpenFOAM (version 3.0) example (icoFoam.C) with included the simplest VTK (version 6.3.0) example (Arrow.cxx) crashes with "Floating point exception" in window rendering if OpenFOAM functions are called before VTK.
It is enough, that OpenFOAM variable "args"
Foam::argList args(argc, argv, false);
is defined before renderWindow->Render().
It seems, that OpenFOAM's manager of exceptions intercepts something wrong (as division by 0) in VTK.
Crashing code example simplified as much as possible:
```
// ============================================================
// VTK includes
// ============================================================
#include <vtkAutoInit.h>
VTK_MODULE_INIT(vtkRenderingOpenGL);
VTK_MODULE_INIT(vtkInteractionStyle);
VTK_MODULE_INIT(vtkRenderingFreeType);
VTK_MODULE_INIT(vtkRenderingContextOpenGL);
#include <vtkArrowSource.h>
#include <vtkPolyData.h>
#include <vtkSmartPointer.h>
#include <vtkPolyDataMapper.h>
#include <vtkActor.h>
#include <vtkRenderWindow.h>
#include <vtkRenderer.h>
#include <vtkRenderWindowInteractor.h>
// ============================================================
// OpenFOAM includes
// ============================================================
#define WM_DP
#include "fvCFD.H"
// ============================================================
// MAIN
// ============================================================
int main ( int argc, char *argv[] )
{
// Create an arrow.
vtkSmartPointer<vtkArrowSource> arrowSource = vtkSmartPointer<vtkArrowSource>::New();
arrowSource->Update();
// Create a mapper and actor
vtkSmartPointer<vtkPolyDataMapper> mapper = vtkSmartPointer<vtkPolyDataMapper>::New();
mapper->SetInputConnection(arrowSource->GetOutputPort());
mapper->Update();
vtkSmartPointer<vtkActor> actor = vtkSmartPointer<vtkActor>::New();
actor->SetMapper(mapper);
// Visualize
vtkSmartPointer<vtkRenderer> renderer = vtkSmartPointer<vtkRenderer>::New();
vtkSmartPointer<vtkRenderWindow> renderWindow = vtkSmartPointer<vtkRenderWindow>::New();
renderWindow->AddRenderer(renderer);
vtkSmartPointer<vtkRenderWindowInteractor> renderWindowInteractor = vtkSmartPointer<vtkRenderWindowInteractor>::New();
renderWindowInteractor->SetRenderWindow(renderWindow);
renderer->AddActor(actor);
renderer->SetBackground(.1, .2, .3); // Background color dark blue
// ============================================================
// OpenFOAM
// ============================================================
Foam::argList args(argc, argv, false);
// ============================================================
// VTK
// ============================================================
renderWindow->Render();
renderWindowInteractor->Start(); // <-- 'Floating point exception' error in trying to manipulate with arrow
// ============================================================
// END
// ============================================================
return EXIT_SUCCESS;
}
```https://gitlab.kitware.com/vtk/vtk/-/issues/15999vtkCutter sometimes incorrectly cuts vtkQuadraticHexahedron when generating p...2018-10-23T16:43:56-04:00Kitware RobotvtkCutter sometimes incorrectly cuts vtkQuadraticHexahedron when generating polygons**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15999). Further discussion may take place here.**
---
The attached script demonstrates how cutting a quadratic hexahedron does not al...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15999). Further discussion may take place here.**
---
The attached script demonstrates how cutting a quadratic hexahedron does not always yield the expected rectangle, when vtkCutter::GenerateTrianglesOff().
[cutter.py](/uploads/63c4210c673b0f19145bd297234b72f6/cutter.py)https://gitlab.kitware.com/vtk/vtk/-/issues/16033vtkRenderingCoreCxx-TestFollowerPicking disabled for EGL dasbhoard2018-10-23T14:31:55-04:00Kitware RobotvtkRenderingCoreCxx-TestFollowerPicking disabled for EGL dasbhoard**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=16033). Further discussion may take place here.**
---
The vtkRenderingCoreCxx-TestFollowerPicking test has been disabled on Taanab fo...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=16033). Further discussion may take place here.**
---
The vtkRenderingCoreCxx-TestFollowerPicking test has been disabled on Taanab for the VTK EGL dashboard because it is failing. The failure is due to a regex check on the output which is:
ERROR: In /home/kitware/Dashboards/slave/vtk-taanab-linux-shared-release_mpi_python/source/Rendering/Core/vtkInteractorStyle.cxx, line 448
vtkInteractorStyleJoystickCamera (0x1e0e030): Timer start failed
https://gitlab.kitware.com/vtk/vtk/-/issues/16032vtkEGLRenderWindow (0x26eb350): Unable to eglMakeCurrent error2018-10-23T14:32:00-04:00Kitware RobotvtkEGLRenderWindow (0x26eb350): Unable to eglMakeCurrent error**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=16032). Further discussion may take place here.**
---
For the VTK EGL dashboard (Taanab) tests have been disabled due to the followin...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=16032). Further discussion may take place here.**
---
For the VTK EGL dashboard (Taanab) tests have been disabled due to the following error message:
ERROR: In /home/kitware/Dashboards/slave/vtk-taanab-linux-shared-release_mpi_python/source/Rendering/OpenGL2/vtkEGLRenderWindow.cxx, line 516
vtkEGLRenderWindow (0x26eb350): Unable to eglMakeCurrent
The tests that have been disable that fail with this ctest regex error are:
'vtkFiltersHybridPython-largeImageParallel',
'vtkFiltersHybridPython-largeImageGradientBackground',
https://gitlab.kitware.com/vtk/vtk/-/issues/16031vtkChartsCoreCxx-TestPropItem test fails with EGL2018-10-23T14:32:05-04:00Kitware RobotvtkChartsCoreCxx-TestPropItem test fails with EGL**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=16031). Further discussion may take place here.**
---
The vtkChartsCoreCxx-TestPropItem test on Taanab which is running EGL builds of...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=16031). Further discussion may take place here.**
---
The vtkChartsCoreCxx-TestPropItem test on Taanab which is running EGL builds of VTK is failing and has been disabled. This seems to be a stencil buffer issue with the EGL build of VTK where the contour lines shouldn't be shown behind the contour value labels in the test image.https://gitlab.kitware.com/vtk/vtk/-/issues/16041Missing vtkImageSliceMapper functionality for OpenGL2.2018-03-16T11:57:09-04:00Kitware RobotMissing vtkImageSliceMapper functionality for OpenGL2.**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=16041). Further discussion may take place here.**
---
Some functionality was lost when the vtkImageSliceMapper moved to OpenGL2:
...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=16041). Further discussion may take place here.**
---
Some functionality was lost when the vtkImageSliceMapper moved to OpenGL2:
1) ~~The clipping planes do not work.~~ ~~The clipping planes that are assigned to the slice mapper should be forwarded to the polydata mappers (will a transformation be required?)~~
2) Cubic interpolation no longer works (this is lower priority than the clipping, since vtkImageResliceMapper can be used if high-order interpolation is required)
3) The shader program for checkerboard rendering had to be removed, but it could be replaced with a new program. Perhaps, rather than replace it, it would be better to consider a solution that allows for custom fragment shaders.
David GobbiDavid Gobbihttps://gitlab.kitware.com/vtk/vtk/-/issues/16048vtk 7.0 multipass rendering framework not working on iOS2018-10-23T14:31:05-04:00Kitware Robotvtk 7.0 multipass rendering framework not working on iOS**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=16048). Further discussion may take place here.**
---
It requires vtkFramebufferObject in case of using multipass rendering. When usi...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=16048). Further discussion may take place here.**
---
It requires vtkFramebufferObject in case of using multipass rendering. When using vtkFramebufferObject, fbo.startNonOrtho() or fbo.createDepthBuffer() would call glRenderbufferStorgage(), which is not compatible with iOS stardard, thus would make multipass rendering framework in vtk not working on iOS.
the error message is like this : vtkFrameBufferObject: failed at glRenderbufferStorage 1 OpenGL errors detected 0:(1280) invalid enum.