OpenFlipper-Free issueshttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues2017-05-04T12:33:26Zhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/75PropertyVisualizer histograms?2017-05-04T12:33:26ZMartin HeistermannPropertyVisualizer histograms?For me it would be quite useful to compute histograms for property values and on the suggestion of @dbommes I'm currently trying to add support for this to the property visualizer.
Would that be appreciated? I'm asking now, as otherwise...For me it would be quite useful to compute histograms for property values and on the suggestion of @dbommes I'm currently trying to add support for this to the property visualizer.
Would that be appreciated? I'm asking now, as otherwise, I'd save some effort by implementing it in a standalone plugin and wouldn't have to restrict myself to C++98 & Qt4 compat.
I'm currently adding a "show histogram" button to the bottom of the toolbox for appropriate properties (for my purposes, double is enough, but int and bool seem very reasonable too), which would then add a Qwt based histogram inline below, possibly with some controls over bin sizes etc. However I'm very open to suggestions here.
@moebius : If you're interested in this feature, is there some way I could use the CI infrastructure for my own dev branch, so I don't have to duplicate it? (I noticed the CI fails on my PRs as it apparently can't access the git refs in my clone?)https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/74ShaderPipeline: Overlay Flag Handling Buggy2017-07-26T08:09:31ZHans-Christian EbkeShaderPipeline: Overlay Flag Handling BuggyThe shader pipeline renderer supports the overlay flag of render objects. If it is set, the object is rendered in a second pass above everything of the first pass. This sort of works, but not always.
The following screen shots show one g...The shader pipeline renderer supports the overlay flag of render objects. If it is set, the object is rendered in a second pass above everything of the first pass. This sort of works, but not always.
The following screen shots show one good case and one failure case:
![bug1](/uploads/c720132cba7ab509488043cbfbc333b5/bug1.png)
![bug2](/uploads/a28439aa97a6f7a6171ddc071d4a6124/bug2.png)
If I had to guess, I'd say it is some issue with the Z-Buffer. Maybe it's not cleared properly before the second pass?https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/73Plugin Convert Meshes2017-05-04T12:33:26ZJan Möbiusmoebius@cs.rwth-aachen.dePlugin Convert MeshesConvert between tri and polymesh preserving properties.Convert between tri and polymesh preserving properties.Martin SchultzMartin Schultzhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/72Plugin-MergeMeshes2017-05-04T12:33:26ZJan Möbiusmoebius@cs.rwth-aachen.dePlugin-MergeMeshesPlugin-MergeMeshes
Toolbox icon:
Merge all Target meshes into one mesh.
Ask for new name
Checkbox if old ones should be removed
Preserve properties if possible.
Copy Property function (in OpenMesh)
Ask if different typesPlugin-MergeMeshes
Toolbox icon:
Merge all Target meshes into one mesh.
Ask for new name
Checkbox if old ones should be removed
Preserve properties if possible.
Copy Property function (in OpenMesh)
Ask if different typesMartin SchultzMartin Schultzhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/71More efficient PrincipalAxisNode rendering2017-05-04T12:33:26ZHans-Christian EbkeMore efficient PrincipalAxisNode renderingPrincpialAxisNode (ACG/Scenegraph/PrincipalAxisNode.cc) is rendered in a rather inefficient manner: Axis nodes consist of only 3 colors but every vertex has its individual color. That's some major waste of GPU memory. At the point of thi...PrincpialAxisNode (ACG/Scenegraph/PrincipalAxisNode.cc) is rendered in a rather inefficient manner: Axis nodes consist of only 3 colors but every vertex has its individual color. That's some major waste of GPU memory. At the point of this writing, the file in question is not yet merged into master but in branch move_principal_axis_node_from_physim.https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/70Crash when rendering poly lines w/ default internal renderer2017-05-04T12:33:26ZHans-Christian EbkeCrash when rendering poly lines w/ default internal rendererOpenFlipper immediately crashes when displaying poly lines with the default internal renderer. Using the shader pipeline, everything appears to work smoothly.
# Steps to Reproduce
* start OpenFlipper
* set renderer to *Shader Pipe...OpenFlipper immediately crashes when displaying poly lines with the default internal renderer. Using the shader pipeline, everything appears to work smoothly.
# Steps to Reproduce
* start OpenFlipper
* set renderer to *Shader Pipeline*
* open the attached [test.pol](/uploads/ced0dcb7ed7d0f69fcc1209cc9dc0f1f/test.pol)
* the poly line is displayed normally
* switch renderer to *Default Internal*
* *crash*https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/69Broken Shading at Shininess 02017-05-04T12:33:26ZHans-Christian EbkeBroken Shading at Shininess 0Shading of faces is broken if shininess is set to 0.
# Steps to Reproduce
* Open the attached [ra.obj](/uploads/ab67f40db62f4371201751c8a914dd3c/ra.obj) in OpenFlipper.
* Select Shader Pipeline Renderer
* Select Flat Shaded Visuali...Shading of faces is broken if shininess is set to 0.
# Steps to Reproduce
* Open the attached [ra.obj](/uploads/ab67f40db62f4371201751c8a914dd3c/ra.obj) in OpenFlipper.
* Select Shader Pipeline Renderer
* Select Flat Shaded Visualization Mode
* Set Shininess to 1. Result: ![bug1](/uploads/788d10832b72b8ad53391c98f9fb7a13/bug1.png)
* Set Shininess to 0. Result: ![bug2](/uploads/27afff821a2655b4ff4ccb3be17dc38c/bug2.png)https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/68Qt 5.7.0 Crash2017-05-04T12:33:26ZChristopher TenterQt 5.7.0 CrashOpenFlipper compiled with qt 5.7.0 crashes at startup
[trace.txt](/uploads/9950667a4e91ea16176fa0e00450d095/trace.txt)OpenFlipper compiled with qt 5.7.0 crashes at startup
[trace.txt](/uploads/9950667a4e91ea16176fa0e00450d095/trace.txt)https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/67Command line parsing on windows seems to be broken2017-05-04T12:33:26ZJan Möbiusmoebius@cs.rwth-aachen.deCommand line parsing on windows seems to be brokenOptions except the filename are ignored. No log output with -cOptions except the filename are ignored. No log output with -cOpenFlipper 3.1Martin SchultzMartin Schultzhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/65Slice plugin not working with new shaders2017-05-04T12:33:26ZJan Möbiusmoebius@cs.rwth-aachen.deSlice plugin not working with new shadersOpenFlipper 3.1https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/64VS2013 Build error2017-05-04T12:33:26ZJan Möbiusmoebius@cs.rwth-aachen.deVS2013 Build error61>Time Elapsed 00:00:00.05
8>E:\JB\workspace\OF-Staging-Win-Gitlab-master\3ea7a0db\OpenFlipper/BasePlugin/PluginFunctions.hh(583): warning C4520: 'PluginFunctions::ObjectReferenceIterator' : multiple default constructors specified
8>E...61>Time Elapsed 00:00:00.05
8>E:\JB\workspace\OF-Staging-Win-Gitlab-master\3ea7a0db\OpenFlipper/BasePlugin/PluginFunctions.hh(583): warning C4520: 'PluginFunctions::ObjectReferenceIterator' : multiple default constructors specified
8>E:\JB\workspace\OF-Staging-Win-Gitlab-master\3ea7a0db\OpenFlipper/BasePlugin/PluginFunctions.hh(583): error C2668: 'PluginFunctions::ObjectReferenceIterator::ObjectReferenceIterator' : ambiguous call to overloaded function
8> E:\JB\workspace\OF-Staging-Win-Gitlab-master\3ea7a0db\OpenFlipper/BasePlugin/PluginFunctions.hh(536): could be 'PluginFunctions::ObjectReferenceIterator::ObjectReferenceIterator(BaseObjectData *,PluginFunctions::IteratorRestriction,DataType)'
8> E:\JB\workspace\OF-Staging-Win-Gitlab-master\3ea7a0db\OpenFlipper/BasePlugin/PluginFunctions.hh(531): or 'PluginFunctions::ObjectReferenceIterator::ObjectReferenceIterator(PluginFunctions::IteratorRestriction,DataType)'
8> while trying to match the argument list '()'
8> This diagnostic occurred in the compiler generated function 'void PluginFunctions::ObjectReferenceIterator::__dflt_ctor_closure(void)'
8> PluginFunctionsBSplineCurve.cc
8>E:\JB\workspace\OF-Staging-Win-Gitlab-master\3ea7a0db\OpenFlipper/BasePlugin/PluginFunctions.hh(583): warning C4520: 'PluginFunctions::ObjectReferenceIterator' : multiple default constructors specified
8>E:\JB\workspace\OF-Staging-Win-Gitlab-master\3ea7a0db\OpenFlipper/BasePlugin/PluginFunctions.hh(583): error C2668: 'PluginFunctions::ObjectReferenceIterator::ObjectReferenceIterator' : ambiguous call to overloaded function
8> E:\JB\workspace\OF-Staging-Win-Gitlab-master\3ea7a0db\OpenFlipper/BasePlugin/PluginFunctions.hh(536): could be 'PluginFunctions::ObjectReferenceIterator::ObjectReferenceIterator(BaseObjectData *,PluginFunctions::IteratorRestriction,DataType)'
8> E:\JB\workspace\OF-Staging-Win-Gitlab-master\3ea7a0db\OpenFlipper/BasePlugin/PluginFunctions.hh(531): or 'PluginFunctions::ObjectReferenceIterator::ObjectReferenceIterator(PluginFunctions::IteratorRestriction,DataType)'
8> while trying to match the argument list '()'
8> This diagnostic occurred in the compiler generated function 'void PluginFunctions::ObJanis BornJanis Bornhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/63ACG::SceneGraph::BaseNode should implement children_ with std::vector instead...2017-05-04T12:33:26ZHans-Christian EbkeACG::SceneGraph::BaseNode should implement children_ with std::vector instead of std::liststd::list is almost certainly slower than std::vector in any realistic use case.std::list is almost certainly slower than std::vector in any realistic use case.Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/62Plugin-HoleFilling: Selection in toolbox not possible anymore2017-05-04T12:33:26ZHans-Christian EbkePlugin-HoleFilling: Selection in toolbox not possible anymoreIt's not possible anymore to select holes in the table widget of the toolbox. Consequently, it's not possible to use the plugin at all right now.It's not possible anymore to select holes in the table widget of the toolbox. Consequently, it's not possible to use the plugin at all right now.Martin SchultzMartin Schultzhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/61Stop rendering to back buffer2017-07-26T08:09:32ZChristopher TenterStop rendering to back bufferStop rendering directly to back buffer from qt widget. Use an intermediate fbo and blit the color buffer to Qt afterwards. Hardware stereoscopic 3D mode needs some adjustment, as GL_BACK_LEFT / GL_BACK_RIGHT won't be available anymore. A...Stop rendering directly to back buffer from qt widget. Use an intermediate fbo and blit the color buffer to Qt afterwards. Hardware stereoscopic 3D mode needs some adjustment, as GL_BACK_LEFT / GL_BACK_RIGHT won't be available anymore. An fbo with 2 color buffers has to be used in that case.
in QtGLGraphicsScene::drawBackground there is a QPainter with native-painting mode used. Maybe the intermediate framebuffer should be bound here instead.
OpenFlipper/widgets/glWidget/QtGLGraphicsScene.cchttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/60Tesselation Shader based Subdivision Surface rendering of Polymeshes2017-07-26T08:09:32ZHans-Christian EbkeTesselation Shader based Subdivision Surface rendering of PolymeshesThis is a feature request for a (possibly tesselation shader based) rendering mode for polyline meshes.
A Catmull-Clark refinement operator should be applied with a configurable number of steps. Ideally, the smoothing operator should ...This is a feature request for a (possibly tesselation shader based) rendering mode for polyline meshes.
A Catmull-Clark refinement operator should be applied with a configurable number of steps. Ideally, the smoothing operator should be configurable as well (bilinear, biquadratic, bicubic) but the most important one is definitely bilinear, so for a first version it's ok if this is fixed.
What's important is that wireframe rendering as well as "edges (colored)" must still work in the sense that the line segments of the wireframe get refined and smoothed but the wireframe mesh does not become finer.Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/59Supersampling2019-02-07T14:54:31ZChristopher TenterSupersamplingImplement supersampling for high resolution rendering and high quality anti aliasing. Feature should be used for snapshots mostly.Implement supersampling for high resolution rendering and high quality anti aliasing. Feature should be used for snapshots mostly.https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/58OpenFlipper Main Window doesn't remember maximized state2017-05-04T12:33:26ZHans-Christian EbkeOpenFlipper Main Window doesn't remember maximized stateIf OpenFlipper is closed in maximized state, the main window is restored in normal state when starting OpenFlipper again. The maximized state should be restored instead.If OpenFlipper is closed in maximized state, the main window is restored in normal state when starting OpenFlipper again. The maximized state should be restored instead.Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/57Picking of polylines2017-05-04T12:33:26ZJan Möbiusmoebius@cs.rwth-aachen.dePicking of polylinesPolyline picking is not consisten. Sometimes switching beteween renderers (classic, shader) causes the picking polylines to be removed (Switch to picking renderer and no polylines are visible anymore.)
Furthermore the rendering of li...Polyline picking is not consisten. Sometimes switching beteween renderers (classic, shader) causes the picking polylines to be removed (Switch to picking renderer and no polylines are visible anymore.)
Furthermore the rendering of lines in picking sometimes does not contain the spheres
@ebke : CCOpenFlipper 3.0https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/56Crash in Script Editor2017-05-04T12:33:26ZHans-Christian EbkeCrash in Script Editor# Steps to Reproduce
1. Start OpenFlipper
2. Menu "Scripting" -> "Show script editor"
3. Inside the script editor, select any entry in the "Function List". (No need to do anything further. Just any entry has to be selected.)
...# Steps to Reproduce
1. Start OpenFlipper
2. Menu "Scripting" -> "Show script editor"
3. Inside the script editor, select any entry in the "Function List". (No need to do anything further. Just any entry has to be selected.)
4. Close the script editor.
5. Menu "Scripting" -> "Show script editor"
6. *CRASH*Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/55Shader Pipeline Renderer: Messed up Shading when rendering Wireframe2017-05-04T12:33:26ZHans-Christian EbkeShader Pipeline Renderer: Messed up Shading when rendering WireframeIn "Solid (flat shaded)" rendering mode, shading is ok. If "Wireframe" is activated _in addition_, shading of faces becomes weird. See attached screen shots. Model seen in screen shots is attached as well.
Does not happen in Default R...In "Solid (flat shaded)" rendering mode, shading is ok. If "Wireframe" is activated _in addition_, shading of faces becomes weird. See attached screen shots. Model seen in screen shots is attached as well.
Does not happen in Default Renderer, only in Shader Pipeline.
# Screen Shots
![bug1](/uploads/5a76f7f7ef0aa64043a75bd043ec1028/bug1.png)
![bug2](/uploads/b92a5e8247d1e016fef95a2f727d8744/bug2.png)
# Used Rocker Arm Model
[rocker-arm_2806.off](/uploads/df603b9518c3cdc3eecdeafaab5cffb8/rocker-arm_2806.off)