VTK issueshttps://gitlab.kitware.com/vtk/vtk/-/issues2020-03-25T21:03:11-04:00https://gitlab.kitware.com/vtk/vtk/-/issues/17804Add wheel building docs to build.md instructions2020-03-25T21:03:11-04:00Ben BoeckelAdd wheel building docs to build.md instructionsInstructions for how to build a wheel are not included in the build documentation.
Cc: @tjcoronaInstructions for how to build a wheel are not included in the build documentation.
Cc: @tjcorona9.0Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/vtk/vtk/-/issues/7440Adding vtkXYPlotActor with an additional renderer causes error in output of v...2016-08-12T06:57:27-04:00Kitware RobotAdding vtkXYPlotActor with an additional renderer causes error in output of vtkRenderLargeImage**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=7440). Further discussion may take place here.**
---
Adding a vtkXYPlotActor to an exisiting view and trying to capture a hi-res imag...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=7440). Further discussion may take place here.**
---
Adding a vtkXYPlotActor to an exisiting view and trying to capture a hi-res image causes the output to be corrupt. The plot is incorrectly copied to each subimage of the output.https://gitlab.kitware.com/vtk/vtk/-/issues/18537AddressSanitizer builds failing on macos2022-05-05T11:59:20-04:00Cory Quammencory.quammen@kitware.comAddressSanitizer builds failing on macosI encounter an error when linking VTK with AddressSanitizer enabled (options `VTK_ENABLE_SANITIZER:BOOL=ON` and `VTK_SANITIZER:STRING=address`). I get this error
```bash
==10572==ERROR: Interceptors are not working. This may be because ...I encounter an error when linking VTK with AddressSanitizer enabled (options `VTK_ENABLE_SANITIZER:BOOL=ON` and `VTK_SANITIZER:STRING=address`). I get this error
```bash
==10572==ERROR: Interceptors are not working. This may be because AddressSanitizer is loaded too late (e.g. via dlopen). Please launch the executable with:
DYLD_INSERT_LIBRARIES=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/12.0.0/lib/darwin/libclang_rt.asan_osx_dynamic.dylib
"interceptors not installed" && 0/bin/sh: line 1: 10572 Abort trap: 6 /usr/local/Frameworks/Python.framework/Versions/3.9/bin/python3.9 -m vtkmodules.generate_pyi -p vtkmodules -o /Users/cory.local/build/vtk-debug/lib/python3.9/site-packages/vtkmodules vtkCommonCore vtkCommonMath vtkCommonTransforms vtkCommonDataModel vtkCommonExecutionModel vtkCommonMisc vtkFiltersCore vtkRenderingCore vtkInteractionStyle vtkRenderingContext2D vtkFiltersGeneral vtkFiltersSources vtkInteractionWidgets vtkViewsCore vtkViewsInfovis vtkCommonColor vtkViewsContext2D vtkTestingRendering vtkPythonContext2D vtkImagingCore vtkImagingMath vtkRenderingHyperTreeGrid vtkRenderingUI vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkRenderingFreeType vtkRenderingLabel vtkRenderingLOD vtkRenderingImage vtkRenderingContextOpenGL2 vtkParallelMPI4Py vtkIOVeraOut vtkIOTecplotTable vtkIOImage vtkIOSegY vtkIOXMLParser vtkIOXML vtkIOParallelXML vtkIOCore vtkIONetCDF vtkIOParallelNetCDF vtkRenderingParallel vtkIOPLY vtkIOPIO vtkIOMovie vtkIOOggTheora vtkIOMotionFX vtkIOLegacy vtkIOGeometry vtkIOParallel vtkIOMPIParallel vtkIOMPIImage vtkIOMINC vtkIOLSDyna vtkIOInfovis vtkIOImport vtkParallelCore vtkIOIOSS vtkIOHDF vtkIOVideo vtkRenderingSceneGraph vtkRenderingVtkJS vtkIOExport vtkIOExportPDF vtkRenderingGL2PSOpenGL2 vtkIOExportGL2PS vtkIOExodus vtkIOEnSight vtkIOCityGML vtkIOChemistry vtkIOCesium3DTiles vtkIOCONVERGECFD vtkIOCGNSReader vtkIOAsynchronous vtkIOAMR vtkInteractionImage vtkImagingStencil vtkImagingStatistics vtkImagingGeneral vtkImagingMorphological vtkImagingFourier vtkIOSQL vtkImagingSources vtkInfovisCore vtkGeovisCore vtkInfovisLayout vtkRenderingAnnotation vtkImagingHybrid vtkImagingColor vtkFiltersTopology vtkFiltersSelection vtkFiltersSMP vtkFiltersPython vtkFiltersProgrammable vtkFiltersModeling vtkFiltersPoints vtkFiltersVerdict vtkFiltersParallelVerdict vtkFiltersStatistics vtkFiltersImaging vtkFiltersExtraction vtkFiltersGeometry vtkFiltersHybrid vtkFiltersTexture vtkFiltersParallel vtkFiltersParallelImaging vtkCommonSystem vtkParallelMPI vtkFiltersParallelGeometry vtkFiltersParallelDIY2 vtkFiltersGeneric vtkCommonComputationalGeometry vtkFiltersFlowPaths vtkFiltersAMR vtkDomainsChemistry vtkDomainsParallelChemistry vtkFiltersParallelMPI vtkIOParallelExodus vtkDomainsChemistryOpenGL2 vtkFiltersHyperTree vtkCommonPython vtkChartsCore
ninja: build stopped: subcommand failed.
hihat~/build/vtk-debug(:|✔) %
```
Setting the environment variable `DYLD_INSERT_LIBRARIES` in the shell as directed does not resolve the problem.
This started happening after ~8868 was merged.https://gitlab.kitware.com/vtk/vtk/-/issues/18458Adios VTX reader (VTU) doesn't support CellData2023-07-07T05:14:16-04:00Garth N. WellsAdios VTX reader (VTU) doesn't support CellDataThe VTX reader for unstructured grids (VTU) doesn't support cell data. This isn't stated in the limited available docs, but there is a TODO comment in the reader code (https://gitlab.kitware.com/vtk/vtk/-/blob/master/IO/ADIOS2/VTX/schema...The VTX reader for unstructured grids (VTU) doesn't support cell data. This isn't stated in the limited available docs, but there is a TODO comment in the reader code (https://gitlab.kitware.com/vtk/vtk/-/blob/master/IO/ADIOS2/VTX/schema/vtk/VTXvtkVTU.cxx#L87).
Obviously this means cell data can't be visualised, but it also means the `vtkOriginalCellIds` field can't be set.https://gitlab.kitware.com/vtk/vtk/-/issues/18004ADIOS2: VTK build system incompatible with ADIOS2 2.6.0 release2020-10-30T15:32:46-04:00Brad KingADIOS2: VTK build system incompatible with ADIOS2 2.6.0 release
The problem is that [this code](https://gitlab.kitware.com/vtk/vtk/-/blob/2ccb36f5e7536e0a287539fb9cb75cd5b2a433e5/IO/ADIOS2/CMakeLists.txt#L64) in VTK causes [this other code](https://gitlab.kitware.com/vtk/vtk/-/blob/2ccb36f5e7536e0a2...
The problem is that [this code](https://gitlab.kitware.com/vtk/vtk/-/blob/2ccb36f5e7536e0a287539fb9cb75cd5b2a433e5/IO/ADIOS2/CMakeLists.txt#L64) in VTK causes [this other code](https://gitlab.kitware.com/vtk/vtk/-/blob/2ccb36f5e7536e0a287539fb9cb75cd5b2a433e5/CMake/vtkModule.cmake#L1549-1551) in VTK to set the [IMPORTED_GLOBAL](https://cmake.org/cmake/help/v3.18/prop_tgt/IMPORTED_GLOBAL.html) target property on the `adios2::adios2` target. This makes it globally visible after the import [here](https://gitlab.kitware.com/vtk/vtk/-/blob/2ccb36f5e7536e0a287539fb9cb75cd5b2a433e5/IO/ADIOS2/CMakeLists.txt#L1-3). However, other targets like `adios2::core` are not made globally visible. That means when VTK later import ADIOS2 again in [this code](https://gitlab.kitware.com/vtk/vtk/-/blob/2ccb36f5e7536e0a287539fb9cb75cd5b2a433e5/IO/ADIOS2/Testing/Cxx/CMakeLists.txt#L1), ADIOS2's [de-duplication guard](https://github.com/ornladios/ADIOS2/blob/v2.6.0/cmake/adios2-config-common.cmake.in#L162-L168) on `adios2::core` does not trigger, so it tries creating `adios2::adios2` again.https://gitlab.kitware.com/vtk/vtk/-/issues/17663ADIOS2: VTX VTI3D test segfaults in libadios22019-09-11T08:42:10-04:00Chuck AtkinsADIOS2: VTX VTI3D test segfaults in libadios2https://open.cdash.org/testDetails.php?test=793649410&build=6057047https://open.cdash.org/testDetails.php?test=793649410&build=6057047https://gitlab.kitware.com/vtk/vtk/-/issues/17662ADIOS2: VTXHelper.cxx build failure on MSVC and macOS2021-02-03T18:56:55-05:00Cory Quammencory.quammen@kitware.comADIOS2: VTXHelper.cxx build failure on MSVC and macOSThe ADIOS2 module fails to build in the ParaView superbuild. Relevant failure output from the [full log](https://open.cdash.org/viewNotes.php?buildid=6053744) included below:
```
[7866/19749] Building CXX object VTK\IO\ADIOS2\CMakeFiles...The ADIOS2 module fails to build in the ParaView superbuild. Relevant failure output from the [full log](https://open.cdash.org/viewNotes.php?buildid=6053744) included below:
```
[7866/19749] Building CXX object VTK\IO\ADIOS2\CMakeFiles\IOADIOS2.dir\VTX\common\VTXHelper.cxx.obj
FAILED: VTK/IO/ADIOS2/CMakeFiles/IOADIOS2.dir/VTX/common/VTXHelper.cxx.obj
C:\PROGRA~2\MICROS~1.0\VC\bin\amd64\cl.exe /nologo /TP -DIOADIOS2_EXPORTS -DIOADIOS2_HAVE_MPI -DMPICH_SKIP_MPICXX -DOMPI_SKIP_MPICXX -DVTK_MODULE_ENABLE_VTK_ParallelMPI=1 -DVTK_MODULE_ENABLE_VTK_mpi=1 -DVTK_MODULE_ENABLE_VTK_pugixml=1 -DVTK_MODULE_ENABLE_VTK_vtksys=1 -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS -D_MPICC_H -D_SCL_SECURE_NO_DEPRECATE -D_SCL_SECURE_NO_WARNINGS -IVTK\IO\ADIOS2 -IC:\bbd\cf096d1e\source-paraview\VTK\IO\ADIOS2 -IVTK\Common\Core -IC:\bbd\cf096d1e\source-paraview\VTK\Common\Core -IVTK\Utilities\KWIML -IC:\bbd\cf096d1e\source-paraview\VTK\Utilities\KWIML -IVTK\Utilities\KWSys -IC:\bbd\cf096d1e\source-paraview\VTK\Utilities\KWSys -IC:\bbd\cf096d1e\build\install\include -IVTK\Common\ExecutionModel -IC:\bbd\cf096d1e\source-paraview\VTK\Common\ExecutionModel -IVTK\Common\DataModel -IC:\bbd\cf096d1e\source-paraview\VTK\Common\DataModel -IVTK\Common\Math -IC:\bbd\cf096d1e\source-paraview\VTK\Common\Math -IVTK\Common\Transforms -IC:\bbd\cf096d1e\source-paraview\VTK\Common\Transforms -IVTK\Parallel\Core -IC:\bbd\cf096d1e\source-paraview\VTK\Parallel\Core -IVTK\Parallel\MPI -IC:\bbd\cf096d1e\source-paraview\VTK\Parallel\MPI -I"C:\Program Files (x86)\Microsoft SDKs\MPI\Include" -IVTK\ThirdParty\pugixml\vtkpugixml -IC:\bbd\cf096d1e\source-paraview\VTK\ThirdParty\pugixml\vtkpugixml -IVTK\ThirdParty\pugixml -IC:\bbd\cf096d1e\source-paraview\VTK\ThirdParty\pugixml /DWIN32 /D_WINDOWS /W4 /GR /EHsc -DBOOST_ALL_NO_LIB /MD /O2 /Ob2 /DNDEBUG /showIncludes /FoVTK\IO\ADIOS2\CMakeFiles\IOADIOS2.dir\VTX\common\VTXHelper.cxx.obj /FdVTK\IO\ADIOS2\CMakeFiles\IOADIOS2.dir\ /FS -c C:\bbd\cf096d1e\source-paraview\VTK\IO\ADIOS2\VTX\common\VTXHelper.cxx
C:\bbd\cf096d1e\source-paraview\VTK\IO\ADIOS2\VTX\common\VTXHelper.cxx(359): error C2893: Failed to specialize function template 'std::vector<T,std::allocator<_Ty>> vtx::helper::StringToVector(const std::string &) noexcept'
C:\bbd\cf096d1e\source-paraview\VTK\IO\ADIOS2\VTX\common\VTXHelper.cxx(359): note: With the following template arguments:
C:\bbd\cf096d1e\source-paraview\VTK\IO\ADIOS2\VTX\common\VTXHelper.cxx(359): note: 'T=std::size_t'
```
There is also a linking failure on `bigmac`.
```
Undefined symbols for architecture x86_64:
"vtkSmartPointer<vtkDataArray> vtx::helper::NewDataArray<long long>()", referenced from:
void vtx::VTXSchema::InitDataArray<long long>(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, unsigned long, unsigned long, vtx::types::DataArray&) in VTXSchema.cxx.o
"vtkSmartPointer<vtkDataArray> vtx::helper::NewDataArray<unsigned long long>()", referenced from:
void vtx::VTXSchema::InitDataArray<unsigned long long>(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, unsigned long, unsigned long, vtx::types::DataArray&) in VTXSchema.cxx.o
```
/cc @chuck.atkins @williamfgchttps://gitlab.kitware.com/vtk/vtk/-/issues/17892AggregateDataSet filter runs into MPI size constraint2020-05-19T11:30:41-04:00Boonthanome NouanesengsyAggregateDataSet filter runs into MPI size constraintThere have been occasions where an mpi error is encountered where mpi is trying to send a message that is too large. The error looks like "This operation not yet supported for more than <x> bytes".
This error was last encountered with t...There have been occasions where an mpi error is encountered where mpi is trying to send a message that is too large. The error looks like "This operation not yet supported for more than <x> bytes".
This error was last encountered with the AggregateDataSet filter, in which Bob Kares was going from 30K procs to 200 procs. I've also encountered this error in the past, too. Bob has got it working now, but I'm not sure what he is doing differently.
@patchett2002 @cory.quammen @utkarsh.ayachithttps://gitlab.kitware.com/vtk/vtk/-/issues/15998Alloc-dealloc mismatch in vtkOpenGLImageSliceMapper::RenderTexturedPolygon2017-10-27T08:52:58-04:00Kitware RobotAlloc-dealloc mismatch in vtkOpenGLImageSliceMapper::RenderTexturedPolygon**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15998). Further discussion may take place here.**
---
The unsigned char *data of MakeTextureData is allocated with a new operator but...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=15998). Further discussion may take place here.**
---
The unsigned char *data of MakeTextureData is allocated with a new operator but will be deallocated with a free because SetArray method use VTK_DATA_ARRAY_FREE as default but in this case we need VTK_DATA_ARRAY_DELETE.https://gitlab.kitware.com/vtk/vtk/-/issues/17897Allow compiler-specific preprocessor operators in wrapped headers2020-05-14T08:45:52-04:00David GobbiAllow compiler-specific preprocessor operators in wrapped headersThe wrappers can handle a broad variety of compiler-specific predefined macros, but they can't handle predefined operators like the following:
```
// gcc and clang
#if __has_attribute(x)
#if __has_cpp_attribute(x)
#if __has_builtin(x)
#...The wrappers can handle a broad variety of compiler-specific predefined macros, but they can't handle predefined operators like the following:
```
// gcc and clang
#if __has_attribute(x)
#if __has_cpp_attribute(x)
#if __has_builtin(x)
#if __has_include(x)
// clang
#if __has_include_next(x)
#if __has_feature(x)
#if __has_extension(x)
#if __has_warning(x)
#if __has_c_attribute(x)
#if __has_declspec_attribute(x)
#if __is_identifier(x)
```
The wrappers can implement some of these (like `__has_feature()` and `__has_attribute()`) to simply return zero. Others like `__has_include()` and `__is_identifier()` are trickier and should probably be left unimplemented.https://gitlab.kitware.com/vtk/vtk/-/issues/18542Allow each VTK module to specify variable to export for use in either build o...2022-07-26T14:30:38-04:00Jean-Christophe Fillion-RobinAllow each VTK module to specify variable to export for use in either build or install treeEach VTK modules should be able to specify variables to export, this would allow to remove the hard-coded value listed in [vtkInstallCMakePackageHelpers.cmake](https://gitlab.kitware.com/vtk/vtk/-/blob/master/CMake/vtkInstallCMakePackage...Each VTK modules should be able to specify variables to export, this would allow to remove the hard-coded value listed in [vtkInstallCMakePackageHelpers.cmake](https://gitlab.kitware.com/vtk/vtk/-/blob/master/CMake/vtkInstallCMakePackageHelpers.cmake).
Variables could be associated with only the build tree (e.g PATH variables) and some could be associated with both build and install trees.
Related issues:
* https://gitlab.kitware.com/vtk/vtk/-/issues/18299
* https://gitlab.kitware.com/vtk/vtk/-/issues/17925
* https://gitlab.kitware.com/vtk/vtk/-/issues/18338
* https://gitlab.kitware.com/vtk/vtk/-/issues/18339
* https://gitlab.kitware.com/vtk/vtk/-/issues/18563https://gitlab.kitware.com/vtk/vtk/-/issues/11134Allow graphs to be colored by a vtkUnsignedCharArray2016-08-12T07:18:23-04:00Kitware RobotAllow graphs to be colored by a vtkUnsignedCharArray**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=11134). Further discussion may take place here.**
---
vtkGraphLayoutView does not currently support coloring vertices with a vtkUnsig...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=11134). Further discussion may take place here.**
---
vtkGraphLayoutView does not currently support coloring vertices with a vtkUnsignedCharArray. You currently must use an array with normal scalar values (e.g. a vtkIntArray) and then use vtkViewTheme's point lookup table to set up the proper mapping of integers to colors. This is awkward in some cases.https://gitlab.kitware.com/vtk/vtk/-/issues/3345Allow parallel to be built without rendering2016-08-12T06:35:58-04:00Kitware RobotAllow parallel to be built without rendering**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=3345). Further discussion may take place here.**
---
The only classes in vtkParallel that require rendering are:
vtkCompositeRenderM...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=3345). Further discussion may take place here.**
---
The only classes in vtkParallel that require rendering are:
vtkCompositeRenderManager
vtkParallelRenderManager
and the function that takes a vtkPolyDataMapper in vtkPipelineSize if these were handled with ifdefs and subclassing vtkParallel could be built independently.https://gitlab.kitware.com/vtk/vtk/-/issues/16818Allow Plot3D function files to be imported with user defined names2017-10-17T00:45:38-04:00Michael NucciAllow Plot3D function files to be imported with user defined namesThis issue is a feature request coming from the ParaView mailing list. Currently when importing Plot3D function files into ParaView, the variables are automatically named **Function0**, **Function1**, etc. It would be useful to be able t...This issue is a feature request coming from the ParaView mailing list. Currently when importing Plot3D function files into ParaView, the variables are automatically named **Function0**, **Function1**, etc. It would be useful to be able to point the vtkPlot3DMetaReader to a text file that defines the names of the variables contained. This is similar to how the Plot3D function file readers for Ensight and Tecplot work. For example, if my function file contains the variables **density**, **velocity-x**, **velocity-y**, **velocity-z**, and **pressure** the accompanying text file may look something like this:
5 1
0 density
1 velocity-x
2 velocity-y
3 velocity-z
4 pressure
1 2 3 velocity
In the above format, the first line contains the number of scalar variables (5) and vector variables (1). The next five lines list a variable ID number followed by a variable name. The last line indicates that a vector should be created from variable IDs 1, 2, & 3, and it should be named **velocity**.https://gitlab.kitware.com/vtk/vtk/-/issues/18273Allow Python path objects for filenames2021-08-20T16:00:28-04:00Carlos A. Michelén StröferAllow Python path objects for filenamesThe different readers (e.g. STL, VTK, etc.) only accept a string path. It would be a good addition to accept path objects from the `pathlib` Python standard library.
The following is a minimal example:
```python
from pathlib import Pa...The different readers (e.g. STL, VTK, etc.) only accept a string path. It would be a good addition to accept path objects from the `pathlib` Python standard library.
The following is a minimal example:
```python
from pathlib import Path
import vtk
reader = vtk.vtkSTLReader()
path = Path()
filename = path / "mesh.stl"
reader.SetFileName(filename)
```
which gives the error:
```python
TypeError: SetFileName argument 1: string or None required
```https://gitlab.kitware.com/vtk/vtk/-/issues/19256Allow to also blit back the depth buffer from the internal framebuffer2024-03-13T19:39:34-04:00Uwe SiemsAllow to also blit back the depth buffer from the internal framebufferIn an OpenGL application that we recently ported to VTK 9.3.0 (www.MeVisLab.de), we use vtkExternalOpenGLRenderWindow to render into an existing OpenGL context (which already is a FramebufferObject). The VTK scene is rendered inbetween o...In an OpenGL application that we recently ported to VTK 9.3.0 (www.MeVisLab.de), we use vtkExternalOpenGLRenderWindow to render into an existing OpenGL context (which already is a FramebufferObject). The VTK scene is rendered inbetween other render items, thus the content of the external framebuffer needs to be copied to the internal framebuffer, and then back to the external framebuffer.
This blitting back to the external framebuffer is implemented, but only copies the color buffer, not the depth buffer, though in our case more external rendering might occur, which would need the depth information from the VTK scene to render correctly.
I propose to add either a flag or another enum value for FrameBlitMode to control if the depth buffer should be copied too (in vtkOpenGLRenderWindow::Frame)https://gitlab.kitware.com/vtk/vtk/-/issues/16988Ambient color not working in VTK7.1.0, while fine in VTK6.3.02018-10-23T13:48:39-04:00xzfnAmbient color not working in VTK7.1.0, while fine in VTK6.3.0The ambient color composition seems broken in VTK7.1.0, but OK in VTK6.3.0.
The attached python script can demonstrate that.
An actor that has non-zero ambient, zero diffuse and zero specular is created.
There's no light, but the render...The ambient color composition seems broken in VTK7.1.0, but OK in VTK6.3.0.
The attached python script can demonstrate that.
An actor that has non-zero ambient, zero diffuse and zero specular is created.
There's no light, but the renderer's ambient is set to green.
The result should be green, since global green ambient shine on white actor.
While in VTK6.3.0, it shows green, in VTK7.1.0, it shows grey.
I'm using Win7 x64, both versions of vtkpython are downloaded from the official release page.
Run this:
`vtkpython.exe test_light.py`
[test_light.py](/uploads/ab42bc56a23a1c18859cf3df038dc476/test_light.py)https://gitlab.kitware.com/vtk/vtk/-/issues/17337Ambient lighting/colour issues with vtkOBJImporter2023-01-09T10:54:20-05:00DanielAmbient lighting/colour issues with vtkOBJImporterHello,
I've been working using the OBJImporter example (but without textures, just the .mtl file) and I'm finding that consistently the ambient light/colour is "blown out" (too bright). I've attached a very simple code example to descri...Hello,
I've been working using the OBJImporter example (but without textures, just the .mtl file) and I'm finding that consistently the ambient light/colour is "blown out" (too bright). I've attached a very simple code example to describe the issue.
If I change the ambient coefficient manually on each actor down to 0 the models look fine, but if let the importer set the coefficient it does a terrible job. In the example provided it completely whites out the models, but in other tests it just generally appears far far too bright (I'm not really in a position to share the other models publicly I'm afraid).
If you toggle the commented out line 45 in my code you will be able to see the dramatic difference as shown in the examples.
I'm happy because I have a "solution" (line 45) - but something seems a bit fundamentally off?
Any suggestions on fix this? Happy to help work on a solution if needs be.
Platform wise: macOS High Sierra, using VTK 8.1.1 (complied from homebrew, with QT support)
[main.cpp](/uploads/521e583b714bdbd81254ea9c99eef579/main.cpp)
![wrong](/uploads/763d5092c98e03d61dfc442ee6ed6ff5/wrong.png)
![correct](/uploads/85a6a252ce758965cdbe6a16a5adeb79/correct.png)
[simple-test.mtl](/uploads/21ca730ca343b3c1ab77f625d43d7ef1/simple-test.mtl)
[simple-test.obj](/uploads/81bd0b5164cd3e34e08b2ed77439a6e5/simple-test.obj)
[CMakeLists.txt](/uploads/97a9d08142235141593e36e660d67a19/CMakeLists.txt)https://gitlab.kitware.com/vtk/vtk/-/issues/512ambiguous Byte Order setting in EnSight Reader2019-01-20T21:36:51-05:00Kitware Robotambiguous Byte Order setting in EnSight Reader**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=512). Further discussion may take place here.**
---
I have a binary EnSight6 file which VTK fails to read with either Little or Big E...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=512). Further discussion may take place here.**
---
I have a binary EnSight6 file which VTK fails to read with either Little or Big Endian set.
The heuristic in vtkEnSight6BinaryReader.cxx seems to fail for large grid size.
I can supply Debug output to help debug and the file can also be made available (94 Mbytes geom file).
I have been able to read the file by changing the source code around line 2630:
// If they are both valid, use the larger one.
if (tmp > 0 && tmp > *result)
I changed "tmp > *result" to "tmp < *result" and it allows VTK to continue without errors. This is only a work-around for the particular file, not a solution to the problem.https://gitlab.kitware.com/vtk/vtk/-/issues/511ambiguous Byte Order setting in EnSight Reader2019-01-20T21:36:51-05:00Kitware Robotambiguous Byte Order setting in EnSight Reader**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=511). Further discussion may take place here.**
---
I have a binary EnSight6 file which VTK fails to read with either Little or Big E...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=511). Further discussion may take place here.**
---
I have a binary EnSight6 file which VTK fails to read with either Little or Big Endian set.
The heuristic in vtkEnSight6BinaryReader.cxx seems to fail for large grid size.
I can supply Debug output to help debug and the file can also be made available (94 Mbytes geom file).
I have been able to read the file by changing the source code around line 2630:
// If they are both valid, use the larger one.
if (tmp > 0 && tmp > *result)
I changed "tmp > *result" to "tmp < *result" and it allows VTK to continue without errors. This is only a work-around for the particular file, not a solution to the problem.