Home › Forum › SOFA › Using SOFA › [SOLVED] Cannot use ‘Add Node’
Tagged: 64_bits, SOFA_1912, using sofa, Windows_10
- This topic has 1 reply, 2 voices, and was last updated 4 years, 2 months ago by
Hugo.
-
AuthorPosts
-
10 June 2020 at 17:00 #16576
luong
BlockedHey everyone,
so I just started with SOFA and I followed the tutorials to get started and build SOFA in Windows. Everything so far works just fine, except that when I want to add a Node in the scene via the contextmenu/right-click the program crashes (even with the standard caduceus example) and I get following error:
########## SIG 11 - SIGSEGV: segfault ########## 64: sofa::helper::BackTrace::dump - 0x7fffd0152e8063: sofa::helper::BackTrace::sig - 0x7fffd0152fe062: seh_filter_exe - 0x7ff8125a0ca061: seh_filter_exe - 0x7ff8125a0ca060: _C_specific_handler - 0x7ffffe11e2c059: _chkstk - 0x7ff814b0ffd058: RtlRaiseException - 0x7ff814abb04057: KiUserExceptionDispatcher - 0x7ff814b0ebf056: QWidget::windowFilePath - 0x7fffa913313055: sofa::gui::qt::QSofaListView::RaiseAddObject - 0x7fffcc3a426054: QMetaObject::activate - 0x7fffa227b31053: QAction::activate - 0x7fffa90e82f052: QMenu::actionGeometry - 0x7fffa924819051: QMenu::actionGeometry - 0x7fffa924819050: QMenu::mouseReleaseEvent - 0x7fffa924d89049: QWidget::event - 0x7fffa911d7c048: QMenu::event - 0x7fffa9249a6047: QApplicationPrivate::notify_helper - 0x7fffa90f832046: QApplication::notify - 0x7fffa90f593045: QCoreApplication::notifyInternal2 - 0x7fffa225a8d044: QApplicationPrivate::sendMouseEvent - 0x7fffa90f97f043: QSizePolicy::QSizePolicy - 0x7fffa914429042: QSizePolicy::QSizePolicy - 0x7fffa914429041: QApplicationPrivate::notify_helper - 0x7fffa90f832040: QApplication::notify - 0x7fffa90f593039: QCoreApplication::notifyInternal2 - 0x7fffa225a8d038: QGuiApplicationPrivate::processMouseEvent - 0x7fffa26d7f1037: QWindowSystemInterface::sendWindowSystemEvents - 0x7fffa26c405036: QEventDispatcherWin32::processEvents - 0x7fffa22a45e035: CallWindowProcW - 0x7ff81321df4034: DispatchMessageW - 0x7ff81321db2033: QEventDispatcherWin32::processEvents - 0x7fffa22a45e032: qt_plugin_query_metadata - 0x7fffa9b216e031: QEventLoop::exec - 0x7fffa225657030: QMenu::exec - 0x7fffa9249e7029: sofa::gui::qt::QSofaListView::RunSofaRightClicked - 0x7fffcc3a45b028: QMetaObject::activate - 0x7fffa227b31027: QWidget::customContextMenuRequested - 0x7fffa911c02026: QWidget::event - 0x7fffa911d7c025: QFrame::event - 0x7fffa91c360024: QAbstractItemView::viewportEvent - 0x7fffa932745023: QCoreApplicationPrivate::sendThroughObjectEventFilters - 0x7fffa225cb2022: QApplicationPrivate::notify_helper - 0x7fffa90f832021: QApplication::notify - 0x7fffa90f593020: QCoreApplication::notifyInternal2 - 0x7fffa225a8d019: QSizePolicy::QSizePolicy - 0x7fffa914429018: QSizePolicy::QSizePolicy - 0x7fffa914429017: QApplicationPrivate::notify_helper - 0x7fffa90f832016: QApplication::notify - 0x7fffa90f593015: QCoreApplication::notifyInternal2 - 0x7fffa225a8d014: QGuiApplicationPrivate::processMouseEvent - 0x7fffa26d7f1013: QWindowSystemInterface::sendWindowSystemEvents - 0x7fffa26c405012: QEventDispatcherWin32::processEvents - 0x7fffa22a45e011: CallWindowProcW - 0x7ff81321df4010: DispatchMessageW - 0x7ff81321db209: QEventDispatcherWin32::processEvents - 0x7fffa22a45e08: qt_plugin_query_metadata - 0x7fffa9b216e07: QEventLoop::exec - 0x7fffa22565706: QCoreApplication::exec - 0x7fffa22597305: sofa::gui::qt::RealGUI::mainLoop - 0x7fffcc3b62c04: sofa::gui::GUIManager::MainLoop - 0x7fffebb732e03: sofa::gui::GUIManager::MainLoop - 0x7fffebb732e02: sofa::gui::GUIManager::MainLoop - 0x7fffebb732e01: BaseThreadInitThunk - 0x7ff8139e6fc00: RtlUserThreadStart - 0x7ff814abcea0
11 June 2020 at 17:24 #16598Hugo
KeymasterHi @anluong
Nodes cannot be directly added in runSofa.
runSofa is the GUI of SOFA and not a scene editor. A project is ongoing to have an editor for SOFA, and a first deliverable should be available end of this summer.
To modify the scene, please open the scene file (xml or python) and add the nodes and components you’d like.Best
Hugo
-
AuthorPosts
- You must be logged in to reply to this topic.