OpenFlipper-Free issueshttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues2024-02-05T12:34:09Zhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/186Build issue: System-wide install of pybind11 interferes2024-02-05T12:34:09ZMartin HeistermannBuild issue: System-wide install of pybind11 interferesHi, my system has pybind11 installed in a global include dir, which apparently takes precedence over the local copy of pybind11.
It leads to this sort of compile error:
```
[...]
In file included from /Users/mh/src/OpenFlipper-IGM/OpenFl...Hi, my system has pybind11 installed in a global include dir, which apparently takes precedence over the local copy of pybind11.
It leads to this sort of compile error:
```
[...]
In file included from /Users/mh/src/OpenFlipper-IGM/OpenFlipper/PythonInterpreter/PyLogHook.h:32:
In file included from /opt/homebrew/include/pybind11/pybind11.h:13:
[...]
In file included from /opt/homebrew/include/pybind11/detail/../attr.h:13:
/opt/homebrew/include/pybind11/detail/common.h:479:16: error: redefinition of 'ssize_t_cast'
inline ssize_t ssize_t_cast(const IntType &val) {
^
/Users/mh/src/OpenFlipper-IGM/OpenFlipper/libs_required/ACG/../pybind11/include/pybind11/detail/common.h:483:16: note: previous definition is here
inline ssize_t ssize_t_cast(const IntType &val) {
```
## Why does it happen - include folder precedence
At least with gcc and clang, the specified include dirs have left-to-right preference, i.e., earlier has precedence.
The corresponding commandline includes ` -isystem /opt/homebrew/include `, and later `-isystem /Users/mh/src/OpenFlipper-IGM/OpenFlipper/libs_required/pybind11/include`. Folders specified by `-I` take precedence, which is probably what we would like to use for the vendored copy of pybind11.
The cause for CMake to use `-i system` instead of `-I` is the combination of
```
# Check if pybind11 is being used directly or via add_subdirectory
if(CMAKE_SOURCE_DIR STREQUAL PROJECT_SOURCE_DIR)
[...]
else()
set(PYBIND11_MASTER_PROJECT OFF)
set(pybind11_system SYSTEM)
endif()
```
and
```
target_include_directories(
pybind11_headers ${pybind11_system} INTERFACE $<BUILD_INTERFACE:${pybind11_INCLUDE_DIR}>
```
in `OpenFlipper/libs_required/pybind11/CMakeLists.txt`.
## Fix?
Patching that file to just `set(pybind11_system "")` results in a successful build for me, but I'm not certain this is the best kind of fix.Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/185Feature edge rendering broken in colored-edges rendering2023-03-17T09:15:30ZMartin HeistermannFeature edge rendering broken in colored-edges renderingWhen visualizing an edge property using edge colors on a mesh that also has feature edges, feature edges are drawn randomly across the space, not even along mesh edges. Every time I click "Visualize" in propvis, the random mess changes, ...When visualizing an edge property using edge colors on a mesh that also has feature edges, feature edges are drawn randomly across the space, not even along mesh edges. Every time I click "Visualize" in propvis, the random mess changes, so I'd guess uninitialized memory - however once in a blue moon, I actually get a rendering that looks like I would expect.
![bad](/uploads/166aacb87d04eada58431db4315b4544/fail.png)
![good](/uploads/c281f02da8ab6c9eba05339210aff37a/ok.png)
Btw, a while ago, I had fixed (or maybe not entirely fixed :/) some bug with similar symptoms, I wouldn't be surprised if this is in similar code paths:
https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper/-/merge_requests/188Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/184Add Toolbox icons2022-12-05T10:15:02ZJan Möbiusmoebius@cs.rwth-aachen.deAdd Toolbox icons![image](/uploads/46c8c3ad9003ead7de1e76e0d8957089/image.png)![image](/uploads/46c8c3ad9003ead7de1e76e0d8957089/image.png)Edwin ÖzdemirEdwin Özdemirhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/183Search-field for plugin list2023-01-25T11:01:41ZJulius Nehring-WirxelSearch-field for plugin listIf there are a lot of plugins it is sometimes quite tedious to find the correct one quickly. It would be nice to have a small search field above the plugin list that can be used to filter the plugins by name and does so while typing.
Li...If there are a lot of plugins it is sometimes quite tedious to find the correct one quickly. It would be nice to have a small search field above the plugin list that can be used to filter the plugins by name and does so while typing.
Like this mockup:
![Mock](/uploads/c9e13f4113af990b3d476e82c734dca5/Mock.png)https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/182File loading race condition leads to crashes2022-05-25T14:13:01ZMartin HeistermannFile loading race condition leads to crashes[Update 2022-05-25: added more details to clarify the race]
1. A file loading operation calls the plugins's `load()` function called in a new thread
1. `load()` uses `addEmptyObject()` is used to create an object to hold the loaded file...[Update 2022-05-25: added more details to clarify the race]
1. A file loading operation calls the plugins's `load()` function called in a new thread
1. `load()` uses `addEmptyObject()` is used to create an object to hold the loaded file.
1. This emits the `emptyObjectAdded` signal, which is connected to `Core::slotEmptyObjectAdded`
1. `Core::slotEmptyObjectAdded` emits `signalObjectUpdated(_id)` and `signalObjectUpdated(_id, UPDATE_ALL)`
Now these two things can happen in parallel:
- In the loading thread, file loading (e.g. OM or OVM) occurs
- Other plugins get notified vis `slotObjectUpdated` and can operate on this unfinished object at the same time
In particular, `PropertyVisPlugin::slotObjectUpdated` does cause crashes for me, but likely is not the only problematic plugin.
With OM, this can lead to a crash while properties are loaded from the file with the following order of execution:
- Main thread, propvis' `OMPropertyModel<...>::gatherProperties()` calls `mesh_->fprops_begin()`
- File load thread: `OpenMesh::PropertyCreator::create_property()`, this invalidates the fprops_begin iterator
- Main thread: The Property iterator is dereferenced -> crash
I attached the output of an ASAN instrumented build that runs into this with detailed backtraces:
[of-load-om-race-condition-asan-output.txt](/uploads/1621a94f55aea9a81e8dab0596e5bc21/of-load-om-race-condition-asan-output.txt)
How should we go about solving this? Maybe just putting a mutex around mesh access from objects? This would also prevent similar issues when performing mesh processing in a worker thread.Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/181CI error on Windows: "error: cannot spawn git: Read-only file system"2020-12-02T13:17:34ZMartin HeistermannCI error on Windows: "error: cannot spawn git: Read-only file system"https://www.graphics.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/jobs/117773
```
[...]
Cloning into 'E:/gitlab/builds/cu6mRa6g/0/OpenFlipper-Free/OpenFlipper-Free/Plugin-PrimitivesGenerator'...
WARNING: Failed to terminate pr...https://www.graphics.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/jobs/117773
```
[...]
Cloning into 'E:/gitlab/builds/cu6mRa6g/0/OpenFlipper-Free/OpenFlipper-Free/Plugin-PrimitivesGenerator'...
WARNING: Failed to terminate process: exit status 1
WARNING: Failed to force-kill: exit status 1
Cloning into 'E:/gitlab/builds/cu6mRa6g/0/OpenFlipper-Free/OpenFlipper-Free/Plugin-Print'...
Cloning into 'E:/gitlab/builds/cu6mRa6g/0/OpenFlipper-Free/OpenFlipper-Free/Plugin-PropertyVis'...
Cloning into 'E:/gitlab/builds/cu6mRa6g/0/OpenFlipper-Free/OpenFlipper-Free/Plugin-Remesher'...
Cloning into 'E:/gitlab/builds/cu6mRa6g/0/OpenFlipper-Free/OpenFlipper-Free/Plugin-Ruler'...
Cloning into 'E:/gitlab/builds/cu6mRa6g/0/OpenFlipper-Free/OpenFlipper-Free/Plugin-Scripting'...
Cloning into 'E:/gitlab/builds/cu6mRa6g/0/OpenFlipper-Free/OpenFlipper-Free/Plugin-SimpleSmoother'...
Cloning into 'E:/gitlab/builds/cu6mRa6g/0/OpenFlipper-Free/OpenFlipper-Free/Plugin-SkeletalAnimation'...
error: cannot spawn git: Read-only file system
fatal: clone of 'https://www.graphics.rwth-aachen.de:9000/OpenFlipper-Free/Plugin-SkeletalAnimation.git' into submodule path 'E:/gitlab/builds/cu6mRa6g/0/OpenFlipper-Free/OpenFlipper-Free/Plugin-SkeletalAnimation' failed
Failed to clone 'Plugin-SkeletalAnimation'. Retry scheduled
error: cannot spawn git: Read-only file system
```Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/180Panning broken when zooming in?2021-09-07T10:07:48ZJan Möbiusmoebius@cs.rwth-aachen.dePanning broken when zooming in?In V4.1 (Windows), panning the view by holding the middle mouse/scroll
wheel no longer works after double-clicking on a mesh to change the
center of rotation. Panning works before double-clicking. This is a
regression from V4.0 (Windows)...In V4.1 (Windows), panning the view by holding the middle mouse/scroll
wheel no longer works after double-clicking on a mesh to change the
center of rotation. Panning works before double-clicking. This is a
regression from V4.0 (Windows).
I looked at this behavior more and have a correction and clarification.
The behavior is the same in 4.0 and 4.1. The pan behavior appears to be
scaled by the zoom level, so after double-clicking to focus/zoom a
couple times, the pan scaling is effectively zero. That is the realJan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/179Chek Windows Installer from artifacts2020-11-24T08:47:04ZJan Möbiusmoebius@cs.rwth-aachen.deChek Windows Installer from artifactsJohannes LenzenJohannes Lenzenhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/178Include what you use job for OpenFlipper2021-02-01T12:07:40ZJan Möbiusmoebius@cs.rwth-aachen.deInclude what you use job for OpenFlipperPlease create a new build job which uses include what you use (Linux only):
Maybe we need to include a mapping file to handle Qt 5 correctly
Beispiel:
cmake -DCMAKE_CXX_INCLUDE_WHAT_YOU_USE="iwyu" ../OpenFlipper-FreePlease create a new build job which uses include what you use (Linux only):
Maybe we need to include a mapping file to handle Qt 5 correctly
Beispiel:
cmake -DCMAKE_CXX_INCLUDE_WHAT_YOU_USE="iwyu" ../OpenFlipper-FreeJohannes LenzenJohannes Lenzenhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/177Plugin Smoother: Test is failing with python support disabled #1083732020-10-30T11:50:11ZJohannes LenzenPlugin Smoother: Test is failing with python support disabled #108373The PLUGIN-SMOOTHER-smoother_c0_normal_10.ofp-cube_sharp.off test fails when disabling python support for OpenFlipper with -DDISABLE_OPENFLIPPER_PYTHON_SYSTEM=TRUE
Running the PLUGIN-SMOOTHER-smoother_c0_normal_10.ofp-cube_sharp.off whi...The PLUGIN-SMOOTHER-smoother_c0_normal_10.ofp-cube_sharp.off test fails when disabling python support for OpenFlipper with -DDISABLE_OPENFLIPPER_PYTHON_SYSTEM=TRUE
Running the PLUGIN-SMOOTHER-smoother_c0_normal_10.ofp-cube_sharp.off while python support is switched off results in the following error: Job [#108373](https://www.graphics.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/jobs/108373) failed for 9ca922b688ae5b02796a0e9c28c6a8ff970fd696:Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/176Intermittent UIC related compile failures with CMake 3.18 on Windows2020-11-20T09:13:02ZMartin HeistermannIntermittent UIC related compile failures with CMake 3.18 on WindowsWith the following setup, in many compile runs, some `ui_*.h` files are not found, i.e. UIC is not run:
- Windows 10
- MSVC 2019
- Qt 5.15
- CMake 3.18
Sometimes, regenerating the project, switching between release/debug types ...With the following setup, in many compile runs, some `ui_*.h` files are not found, i.e. UIC is not run:
- Windows 10
- MSVC 2019
- Qt 5.15
- CMake 3.18
Sometimes, regenerating the project, switching between release/debug types and full solution rebuilds actually yield a success, but I haven't been able to figure out any pattern.
Not all `ui_*.h` files are missing (the build results in an incomplete OF that works, but is without the DataControl plugin), however I also couldn't make out what makes the failing ones special. The following ones 'tend' to fail:
- `ui_QtMaterialDialogUi.h`
- `ui_lightWidget.h`
With CMake 3.14 (everything else unchanged), the issues do not seem to appear.
This behavior occurs both on my machine and on the machine of one of our students.https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/175Bad remesh and .stl export2021-09-07T10:07:57ZValentin NigolianBad remesh and .stl exportConcerns the master branch.
Remeshing the attached file with the Uniform Remesher results in a bad .stl export.
I used the "Estimate Parameters" button to get the remeshing parameters.
All faces were selected
[octopus-2.stl](/uploa...Concerns the master branch.
Remeshing the attached file with the Uniform Remesher results in a bad .stl export.
I used the "Estimate Parameters" button to get the remeshing parameters.
All faces were selected
[octopus-2.stl](/uploads/491cbabf39a6d5f4bfad584d62a2be2c/octopus-2.stl)Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/174Uniform Remeshing produces degenerate patches using vertex selection2021-09-07T10:08:05ZZain SelmanUniform Remeshing produces degenerate patches using vertex selectionWhen using the Remesher Plugin (Uniform) on a simple mesh (cube1.off) the remesher produces broken patches.
Steps to reproduce:
- Open the cube1.off in `/path/to/OpenFlipper-Free/OpenFlipper/`
- Select a large proportion of a side of the...When using the Remesher Plugin (Uniform) on a simple mesh (cube1.off) the remesher produces broken patches.
Steps to reproduce:
- Open the cube1.off in `/path/to/OpenFlipper-Free/OpenFlipper/`
- Select a large proportion of a side of the cube
![cube1](/uploads/1d548a7445a3a352eb37bec779754220/cube1.png)
- Set the edge length (0.02 here)
![cube2](/uploads/bae851765546d0efdf239759b4813d37/cube2.png)
- Remesh
![cube3](/uploads/c6732e3c195e6a84c5ead22456f6f3e2/cube3.png)
- Close up of degenerate path
![cube4](/uploads/852e034c57c253475f7e6ac2b91e335e/cube4.png)
If you compare the result to the input and edge length of 0.02 is not too small compared to the average. Starting with a value of 0.025 and then choosing 0.02 also results in this kind of behavior.Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/173Loading Objects moves progressbar behind filepicker2020-08-13T13:11:32ZZain SelmanLoading Objects moves progressbar behind filepickerAs apparent in the screenshot the filepicker hovers above the progressbar window. Not knowing whether it is loading the file or not, can be confusing if not aware of this and the progressbar is completely covered (as it is default).
![im...As apparent in the screenshot the filepicker hovers above the progressbar window. Not knowing whether it is loading the file or not, can be confusing if not aware of this and the progressbar is completely covered (as it is default).
![image](/uploads/faf24a3d0d42a2e16ac17979aeae9802/image.png)https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/172Selection Line Width2021-02-16T10:40:26ZMax Lyonlyon@cs.rwth-aachen.deSelection Line WidthSetting Line Width in the material properties of a mesh has no effect on the red and purple lines rendered for edges marked as selected or feature.
Similarly, Point Size has no effect on vertices marked as selected or feature.Setting Line Width in the material properties of a mesh has no effect on the red and purple lines rendered for edges marked as selected or feature.
Similarly, Point Size has no effect on vertices marked as selected or feature.Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/171CMake 3.17 Policy CMP0100 Problem2020-04-30T10:56:09ZMartin HeistermannCMake 3.17 Policy CMP0100 ProblemWhen running the CI pipeline for current master, that successfully passed in the past <https://www.graphics.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/pipelines/13920>, now it fails on mac: <https://www.graphics.rwth-aachen.de...When running the CI pipeline for current master, that successfully passed in the past <https://www.graphics.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/pipelines/13920>, now it fails on mac: <https://www.graphics.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/pipelines/14006>
```
[ 31%] Building CXX object OpenFlipper/libs_required/ACG/CMakeFiles/ACG.dir/QtWidgets/QtClippingDialog.cc.o
In file included from /Users/jenkins/builds/8dfb9a4a/0/OpenFlipper-Free/OpenFlipper-Free/OpenFlipper/libs_required/ACG/QtWidgets/QtClippingDialog.cc:55:
/Users/jenkins/builds/8dfb9a4a/0/OpenFlipper-Free/OpenFlipper-Free/OpenFlipper/libs_required/ACG/QtWidgets/QtClippingDialog.hh:60:10: fatal error: 'ui_QtClippingDialogUi.h' file not found
#include "ui_QtClippingDialogUi.h"
^
1 error generated.
```Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/170Assertion fails in GLMatrixT when zooming to triangle2020-11-23T06:02:47ZMax Lyonlyon@cs.rwth-aachen.deAssertion fails in GLMatrixT when zooming to triangleSteps to reproduce:
- Build in debug mode
- Add triangle:
```
int id;
emit addEmptyObject( DATA_TRIANGLE_MESH, id);
auto& mesh_obj = *PluginFunctions::triMeshObject(id);
auto& mesh = *PluginFunctions::triMesh(id);
mesh.add_ver...Steps to reproduce:
- Build in debug mode
- Add triangle:
```
int id;
emit addEmptyObject( DATA_TRIANGLE_MESH, id);
auto& mesh_obj = *PluginFunctions::triMeshObject(id);
auto& mesh = *PluginFunctions::triMesh(id);
mesh.add_vertex(TriMesh::Point(0,0,0));
mesh.add_vertex(TriMesh::Point(1,0,0));
mesh.add_vertex(TriMesh::Point(0,1,0));
mesh.add_face(OpenMesh::VertexHandle(0), OpenMesh::VertexHandle(1), OpenMesh::VertexHandle(2));
```
- Right click mesh in DataControl widget and click "zoom to object"https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/169Infinite loop in DrawMeshT when deleted elements are present2020-02-14T10:29:50ZMax Lyonlyon@cs.rwth-aachen.deInfinite loop in DrawMeshT when deleted elements are presentCode to reproduce:
```
int id;
emit addEmptyObject( DATA_TRIANGLE_MESH, id);
auto& mesh = *PluginFunctions::triMesh(id);
mesh.add_vertex(TriMesh::Point(0,0,0));
mesh.add_vertex(TriMesh::Point(1,0,0));
mesh.add_vertex(TriMes...Code to reproduce:
```
int id;
emit addEmptyObject( DATA_TRIANGLE_MESH, id);
auto& mesh = *PluginFunctions::triMesh(id);
mesh.add_vertex(TriMesh::Point(0,0,0));
mesh.add_vertex(TriMesh::Point(1,0,0));
mesh.add_vertex(TriMesh::Point(0,1,0));
mesh.add_vertex(TriMesh::Point(1,1,0));
mesh.add_face(OpenMesh::VertexHandle(0), OpenMesh::VertexHandle(1), OpenMesh::VertexHandle(2));
mesh.add_face(OpenMesh::VertexHandle(1), OpenMesh::VertexHandle(3), OpenMesh::VertexHandle(2));
mesh.delete_face(OpenMesh::FaceHandle(0));
```https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/168Current 4.0 release does not work with Qt > 5.9 and starts with black screen2020-03-17T16:43:11ZMartin HeistermannCurrent 4.0 release does not work with Qt > 5.9 and starts with black screenThe current 4.0 release still has a long-fixed bug in the cmake scripts that breaks it for Qt > 5.9 (broken regex that assumes 1 character for the minor release number).
The other big issue is #164 that causes users to be greeted with a...The current 4.0 release still has a long-fixed bug in the cmake scripts that breaks it for Qt > 5.9 (broken regex that assumes 1 character for the minor release number).
The other big issue is #164 that causes users to be greeted with a black screen unless they figure out to change the renderer.
Maybe we could have a new release soon?Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/167Edge property visualization with property visualizer plugin2020-11-20T09:13:02ZNicolas Gallego-OrtizEdge property visualization with property visualizer pluginSystem: macOS 10.14.6, c++ compiler clang-1000.11.45.5, cmake 3.14.5,
Debug mode, using Qt Creator 4.9.2
Shader: pipeline render plugin, (although changing it does not change the behavior)
Hi all,
I just observed this unexpected be...System: macOS 10.14.6, c++ compiler clang-1000.11.45.5, cmake 3.14.5,
Debug mode, using Qt Creator 4.9.2
Shader: pipeline render plugin, (although changing it does not change the behavior)
Hi all,
I just observed this unexpected behavior when visualizing edge properties of meshes (OpenMesh) with the property visualization plugin. I the provided file there is a triangle mesh of a plane, and an edge property saved from it.
I get this error message on the console, and the mesh is rendered as a tube on the z-direction as shown in the image. The plane mesh can be seen after clicking on the object for a short time but the edges shown are not those of the original mesh.
I would be happy to help solve this issue, for now just let me know if you can reproduce it in other systems and some hints on where to start the debugging process.
Thanks,
Nicolas
```
GLError /Users/nicolas.gallego-ortiz/projects/OpenFlipper-072019/OpenFlipper/libs_required/ACG/ShaderUtils/GLSLShader.cc:650 - 1282
GLError /Users/nicolas.gallego-ortiz/projects/OpenFlipper-072019/OpenFlipper/libs_required/ACG/ShaderUtils/GLSLShader.cc:704 - 1282 - inColor
```
[mesh2.om](/uploads/7d19640750d0d63bac96123c433397d2/mesh2.om)
[kappa.eprop](/uploads/85cb68a117b9b3876525ecc5ce580307/kappa.eprop)
![screenshot](/uploads/086c07c3b29a4618be864f85cb6e206e/screenshot.png)Nicolas Gallego-OrtizNicolas Gallego-Ortiz