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/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/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/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/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)https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/54Vertices of Polylines ignore point size material property.2017-05-04T12:33:26ZHans-Christian EbkeVertices of Polylines ignore point size material property.The radius of the vertices of polylines should be equal to the point size material property. Right now they have constant size and the point size material property has no effect.
# Screen Shots
## Exhibit A
![bug1](/uploads/262558e1...The radius of the vertices of polylines should be equal to the point size material property. Right now they have constant size and the point size material property has no effect.
# Screen Shots
## Exhibit A
![bug1](/uploads/262558e153debb6d94d221775aee6d5e/bug1.png)
## Exhibit B
![bug2](/uploads/ab4dcbe91bd24e5ec021a77e604c68d1/bug2.png)https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/52Mysterious Progress Dialog Pops Up and Occasionally Crashes OpenFlipper2017-05-04T12:33:26ZHans-Christian EbkeMysterious Progress Dialog Pops Up and Occasionally Crashes OpenFlipperOn a vanilla OpenFlipper-Free build, without ~/.OpenFlipper folder (i.e. no stale settings), when you open the File -> Options dialog and wait for 3-5 seconds an unlabeled progress dialog pops up (see screen shot). When you close it by c...On a vanilla OpenFlipper-Free build, without ~/.OpenFlipper folder (i.e. no stale settings), when you open the File -> Options dialog and wait for 3-5 seconds an unlabeled progress dialog pops up (see screen shot). When you close it by clicking the "Cancel" button on roughly 1 out of 3 instances OpenFlipper crashes.
# Crash Log
<pre>
=====================================================
OpenFlipper or one of its plugins caused a Segfault.
This should not happen,... Sorry :-(
=====================================================
Trying a backtrace to show what happened last:
Stack frames: 20
0: ./Build/bin/OpenFlipper(_Z9backtracev+0x1e) [0x45f05e]
1: ./Build/bin/OpenFlipper(_Z16segfaultHandlingi+0x2da) [0x45f4fa]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x350e0) [0x7f89559710e0]
3: ./Build/bin/OpenFlipper(_ZN13OptionsWidget14cancelDownloadEv+0x65) [0x561bb5]
4: ./Build/bin/OpenFlipper() [0x5a1e85]
5: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Core.so.5(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x8ee) [0x7f89572e235e]
6: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(+0x36bc75) [0x7f89584e8c75]
7: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Core.so.5(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x8ee) [0x7f89572e235e]
8: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(_ZN15QAbstractButton7clickedEb+0x32) [0x7f895865c282]
9: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(+0x24f195) [0x7f89583cc195]
10: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(+0x24fd29) [0x7f89583ccd29]
11: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(_ZN15QAbstractButton17mouseReleaseEventEP11QMouseEvent+0xd4) [0x7f89583ccec4]
12: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(_ZN7QWidget5eventEP6QEvent+0x2b8) [0x7f89583131d8]
13: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x8c) [0x7f89582d24cc]
14: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(_ZN12QApplication6notifyEP7QObjectP6QEvent+0xb65) [0x7f89582d7e15]
15: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Core.so.5(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0xc3) [0x7f89572b4663]
16: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb+0x3a2) [0x7f89582d6aa2]
17: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(+0x1b0bdd) [0x7f895832dbdd]
18: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(+0x1b2efb) [0x7f895832fefb]
19: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x8c) [0x7f89582d24cc]
Backtrace completed, trying to abort now ...
Trying to get additional information (This might fail if the memory is corrupted).
DrawMode Viewer 0 Solid (smooth shaded)
DrawMode Viewer 1 Solid (smooth shaded)
DrawMode Viewer 2 Solid (smooth shaded)
DrawMode Viewer 3 Solid (smooth shaded)
Aborted (core dumped)
</pre>
# Screen Shot
![bug](/uploads/b5fa81fb0889a8187b2f126c72c5ffe9/bug.png)Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/51Vertices in Polyline not Rendered Correctly in Shader Pipeline Renderer2017-05-04T12:33:26ZHans-Christian EbkeVertices in Polyline not Rendered Correctly in Shader Pipeline RendererThe vertices of polyline objects do not get rendered in the Shader Pipeline Renderer.
# Steps to reproduce
1. Start OpenFlipper, load any mesh, draw a PolyLine.
2. Set Point-Size of PolyLine in material properties to something b...The vertices of polyline objects do not get rendered in the Shader Pipeline Renderer.
# Steps to reproduce
1. Start OpenFlipper, load any mesh, draw a PolyLine.
2. Set Point-Size of PolyLine in material properties to something big (i.e. 5).
3. Toggle Between Shader Pipeline Renderer and Default Classical Renderer.
The vertices of the polyline get drawn in the default classical renderer but not in the shader pipeline renderer.
# Screenshots
## Default Classical Renderer
![Default Classical Renderer](/uploads/eaa868868d44a11f57c554403fc5084b/bug1.png)
## Shader Pipeline Renderer
![Shader Pipeline Renderer](/uploads/95c773d943fdfda467ca3b474f76873f/bug2.png)https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/50Qt5.6 VS 2015 Update2 issues2017-09-11T16:46:45ZMartin SchultzQt5.6 VS 2015 Update2 issuesI see a few internal compiler errors when compiling wih Visualstudio 2015 Update 2.
A lot of Vec3f or Vec2f array declarations seem to cause an Internal Compiler Error (e.g. GLPrimitives.cc : 608).
Not shure if it is the same problem...I see a few internal compiler errors when compiling wih Visualstudio 2015 Update 2.
A lot of Vec3f or Vec2f array declarations seem to cause an Internal Compiler Error (e.g. GLPrimitives.cc : 608).
Not shure if it is the same problem, but may be related:
in SplatCloudExtensions.hh : 56 also causes an ICE, seems like a problem with the instantiation of arrays of templated classes in Visualstudio.https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/49QT 5.5 No OpenGL Toolbars in Mainview visible2017-09-11T16:46:45ZJan Möbiusmoebius@cs.rwth-aachen.deQT 5.5 No OpenGL Toolbars in Mainview visibleE.g. Selection toolbox
Might be OSX onlyE.g. Selection toolbox
Might be OSX onlyMartin SchultzMartin Schultzhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/48Viewer snapshot triggered from code does not respect the given aspect ratio.2017-09-11T16:46:45ZIsaak LimViewer snapshot triggered from code does not respect the given aspect ratio.@adielen does merge request !88 fix this (especially in combination with the origin/viewerSnapshot branch)?
Please test this so we can determine if !71 is obsolete.@adielen does merge request !88 fix this (especially in combination with the origin/viewerSnapshot branch)?
Please test this so we can determine if !71 is obsolete.Alexander DielenAlexander Dielenhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/47Viewer Snapshots triggered through Menu (or F2 hotkey) are always 1x12016-05-11T09:23:39ZHans-Christian EbkeViewer Snapshots triggered through Menu (or F2 hotkey) are always 1x1https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/46saving objects fails if any path component other than the filename contains a...2016-05-11T09:23:39ZHans-Christian Ebkesaving objects fails if any path component other than the filename contains a dotThe menu item "File" -> "Save Objects To" (indirectly) uses `LoadWidget::saveFile()` to save all objects. However, `LoadWidget::saveFile()` has a crude and severely broken ad-hoc implementation to check whether the path picked in the sav...The menu item "File" -> "Save Objects To" (indirectly) uses `LoadWidget::saveFile()` to save all objects. However, `LoadWidget::saveFile()` has a crude and severely broken ad-hoc implementation to check whether the path picked in the save dialog contains a filename with an extension: `filename.contains(".",Qt::CaseSensitive)` Note: `filename` contains the entire path here.
If the filename does not contain a dot but another component of the path does, this check returns a false positive, causing the file type detection to wreck havoc.https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/45Commit e4bef69e5596f5c89b62167e15ea712615deca04 breaks Plugin-Scissor2016-05-07T19:39:59ZHans-Christian EbkeCommit e4bef69e5596f5c89b62167e15ea712615deca04 breaks Plugin-ScissorConcerning commit e4bef69e5596f5c89b62167e15ea712615deca04:
Plugin-Scissor doesn't compile anymore since update method of MeshObjectT is private. Please revert.Concerning commit e4bef69e5596f5c89b62167e15ea712615deca04:
Plugin-Scissor doesn't compile anymore since update method of MeshObjectT is private. Please revert.Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/44Qt 5.6 support2016-05-13T15:12:55ZMartin SchultzQt 5.6 supportSo i tried compiling with Qt 5.6.
on our linux machines i only need to change some cmake script and everything else works as expected.
I tried to compile with the Windows machine using Visualstudio 2015. Unfortunately i get a lot of ...So i tried compiling with Qt 5.6.
on our linux machines i only need to change some cmake script and everything else works as expected.
I tried to compile with the Windows machine using Visualstudio 2015. Unfortunately i get a lot of errors when the moc files are compiled because qopenglextrafunctions.h cannot resolve qopenglfunctions.
I also noticed a lot of warnings regarding the ionclusion of map and other c++ std headers when compiling acg.
I attached the out and error list from the compilation. My guess right now is that this might be a problem caused by isualstudio 2015 rather than by qt 5.6.
[compileout.txt](/uploads/45043c0c3af71d1e502955272e1e8599/compileout.txt)[compileerrors.txt](/uploads/5b3ce26420182eeb40bf7edb04b9c9f2/compileerrors.txt)Martin SchultzMartin Schultz