Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

No crash/errors in Solaris, but also no render #66

Open
BrianHanke opened this issue Mar 22, 2023 · 20 comments
Open

No crash/errors in Solaris, but also no render #66

BrianHanke opened this issue Mar 22, 2023 · 20 comments

Comments

@BrianHanke
Copy link

I've got everything set up according to the instructions in the docs. All the MoonRay nodes and parameters are showing up in Houdini and MoonRay is listed in the choice of renderers. But, when I select it, the viewport goes blank and there is no rendering happening. Right now I have HOUDINI_PATH pointing to MoonRay in houdini.env and all the other MoonRay variables (PXR_PLUGINPATH, etc) are in .bashrc.
@rgwilson68
Copy link
Contributor

Does MoonRay remain in the list of renderers? (a link error will cause it to be removed)
Do any messages appear in the terminal or the viewport messages after selecting MoonRay?

@BrianHanke
Copy link
Author

@rgwilson68 Yes, it remains in the list.

I did some more troubleshooting and I can confirm that MoonRay standalone is working 100%, including XPU.

I juggled around some environment variables trying to narrow down the problem with Houdini and I finally was able to get this in the console after trying to launch a MR render in Solaris. Any ideas how to fix? I also attached a pic showing my houdini.env and .bashrc and what it looks like after selecting a MR render (empty viewport with just object manipulators).

Traceback (most recent call last):
  File "/opt/hfs19.5.534/python/lib/python3.9/site-packages-forced/shiboken2/files.dir/shibokensupport/__feature__.py", line 142, in _import
    return original_import(name, *args, **kwargs)
ModuleNotFoundError: No module named 'pxr.MoonrayShaderParser'
Traceback (most recent call last):
  File "/opt/hfs19.5.534/python/lib/python3.9/site-packages-forced/shiboken2/files.dir/shibokensupport/__feature__.py", line 142, in _import
    return original_import(name, *args, **kwargs)
ModuleNotFoundError: No module named 'pxr.MoonrayShaderDiscovery'

moonray

@vvzen
Copy link

vvzen commented Mar 23, 2023

@BrianHanke There might be a few reasons why python isn't pickup your env variables. How are you running houdini? Are you sure that everything is making its way to the PYTHONPATH in houdini ?

Can you run a hython shell and print the sys.path that you get in that session ? And do the same from a python shell in a normal houdini UI session ?

@rgwilson68
Copy link
Contributor

MoonrayShaderParser and MoonrayShaderDiscovery are plugins that don't have Python modules. I've seen usdview issue a warning about them, but I haven"t seen this cause an error in Houdini before. I don't know if this error is causing the empty render, or if it's something else. You could try creating empty Python modules for them (under pxr) and adding these to PYTHONPATH : that should get rid of the module load error at least.

@BrianHanke
Copy link
Author

Thanks @vvzen and @rgwilson68, I rebuilt MoonRay with Python 3.9.0 on the off chance that was the problem. Build successful and warning gone, but still no render. Attached is a video showing what's happening. There are no errors or warnings in the terminal or the Houdini viewport.

sys.path gives the following, both in hython and in the Houdini GUI:

['/opt/hfs19.5.534/bin', '/opt/hfs19.5.534/bin', '/opt/hfs19.5.534/python/lib/python3.9/site-packages-ui-forced', '/opt/hfs19.5.534/python/lib/python3.9/site-packages-forced', '', '/opt/hfs19.5.534/python/lib/python39.zip', '/opt/hfs19.5.534/python/lib/python3.9', '/opt/hfs19.5.534/python/lib/python3.9/lib-dynload', '/opt/hfs19.5.534/python/lib/python3.9/site-packages', '/installs/openmoonray/plugin/houdini/python3.9libs', '/opt/hfs19.5.534/packages/kinefx/python3.9libs', '/opt/hfs19.5.534/houdini/python3.9libs', '/opt/hfs19.5.534/packages/kinefx/viewer_states', '/opt/hfs19.5.534/houdini/viewer_states', '/opt/hfs19.5.534/packages/kinefx/viewer_handles', '/opt/hfs19.5.534/houdini/viewer_handles', '/opt/hfs19.5.534/python/lib/python3.9/site-packages']

moonray_1.mp4

@rgwilson68
Copy link
Contributor

Hmm... Are you able to bring up the render settings for MoonRay when it is selected? (You should see 'debug mode', 'restart', 'reload textures' etc...)

@BrianHanke
Copy link
Author

@rgwilson68 Where are those options located?

@rgwilson68
Copy link
Contributor

Right side of the solaris view, near the bottom : it looks like an eye and has tooltip 'Open display options...'

@BrianHanke
Copy link
Author

Ah yep, that's there, lists all options for MoonRay.

@rgwilson68
Copy link
Contributor

If the options are listed, that suggests that the plugin is loaded and running, but not producing a render for some reason.
Can you try turning on 'debug mode'? - if nothing happens immediately, try switching away from moonray and back again...

@BrianHanke
Copy link
Author

BrianHanke commented Mar 23, 2023 •
edited
Loading

It def appears to be running. The little pencil icon is active, showing rendering is happening.

If there is geometry in the scene Debug mode causes a segmentation fault. It does not if there's no geo. Here's the crash log:

Crash report from brian; Houdini FX Version 19.5.534 [linux-x86_64-gcc9.3]
Uptime 123 seconds
Thu Mar 23 19:51:38 2023
Caught signal 11

Traceback from 4576 ThreadId=0x7f325cbff700
AP_Interface::si_CrashHandler::handledSignal(UTsignalHandlerArg) <libHoudiniUI.so>
signalCallback(UTsignalHandlerArg) <libHoudiniUT.so>
UT_Signal::UT_ComboSignalHandler::operator()(int, siginfo_t*, void*) const <libHoudiniUT.so>
UT_Signal::processSignal(int, siginfo_t*, void*) <libHoudiniUT.so>
L_unlock_13 <libpthread.so.0>
pxrInternal_v0_22__pxrReserved_::HdSceneIndexAdapterSceneDelegate::InvokeExtComputation(pxrInternal_v0_22__pxrReserved__::SdfPath const&, pxrInternal_v0_22__pxrReserved__::HdExtComputationContext*) <libpxr_hd.so>
hdMoonray::Geometry::getDirtyPrimvars(pxrInternal_v0_22__pxrReserved__::HdSceneDelegate*, hdMoonray::RenderDelegate&, unsigned int*) <hdMoonray.so>
hdMoonray::Mesh::Sync(pxrInternal_v0_22__pxrReserved__::HdSceneDelegate*, pxrInternal_v0_22__pxrReserved__::HdRenderParam*, unsigned int*, pxrInternal_v0_22__pxrReserved__::TfToken const&) <hdMoonray.so>
pxrInternal_v0_22__pxrReserved__::(anonymous namespace)::SyncRPrims::Sync(unsigned long, unsigned long) <libpxr_hd.so>
void tbb::interface9::internal::dynamic_grainsize_mode<tbb::interface9::internal::adaptive_modetbb::interface9::internal::auto_partition_type >::work_balance<tbb::interface9::internal::start_for<tbb::blocked_range, void pxrInternal_v0_22__pxrReserved_::WorkParallelForN<std::Bind<void (pxrInternal_v0_22__pxrReserved_::(anonymous namespace)::SyncRPrims::*(pxrInternal_v0_22__pxrReserved_::(anonymous namespace)::SyncRPrims, std::Placeholder<1>, std::Placeholder<2>))(unsigned long, unsigned long)> >(unsigned long, std::Bind<void (pxrInternal_v0_22__pxrReserved::(anonymous namespace)::SyncRPrims::*(pxrInternal_v0_22__pxrReserved::(anonymous namespace)::SyncRPrims, std::Placeholder<1>, std::Placeholder<2>))(unsigned long, unsigned long)>&&, unsigned long)::Work_ParallelForN_TBB, tbb::auto_partitioner const>, tbb::blocked_range >(tbb::interface9::internal::start_for<tbb::blocked_range, void pxrInternal_v0_22__pxrReserved::WorkParallelForN<std::Bind<void (pxrInternal_v0_22__pxrReserved::(anonymous namespace)::SyncRPrims::*(pxrInternal_v0_22__pxrReserved::(anonymous namespace)::SyncRPrims, std::Placeholder<1>, std::Placeholder<2>))(unsigned long, unsigned long)> >(unsigned long, std::Bind<void (pxrInternal_v0_22__pxrReserved::(anonymous namespace)::SyncRPrims::*(pxrInternal_v0_22__pxrReserved::(anonymous namespace)::SyncRPrims, std::Placeholder<1>, std::Placeholder<2>))(unsigned long, unsigned long)>&&, unsigned long)::Work_ParallelForN_TBB, tbb::auto_partitioner const>&, tbb::blocked_range&) <libpxr_hd.so>
tbb::interface9::internal::start_for<tbb::blocked_range, void pxrInternal_v0_22__pxrReserved::WorkParallelForN<std::Bind<void (pxrInternal_v0_22__pxrReserved::(anonymous namespace)::SyncRPrims::*(pxrInternal_v0_22__pxrReserved::(anonymous namespace)::SyncRPrims, std::Placeholder<1>, std::Placeholder<2>))(unsigned long, unsigned long)> >(unsigned long, std::Bind<void (pxrInternal_v0_22__pxrReserved::(anonymous namespace)::SyncRPrims::*(pxrInternal_v0_22__pxrReserved::(anonymous namespace)::SyncRPrims, std::Placeholder<1>, std::Placeholder<2>))(unsigned long, unsigned long)>&&, unsigned long)::Work_ParallelForN_TBB, tbb::auto_partitioner const>::execute() <libpxr_hd.so>
tbb::internal::custom_schedulertbb::internal::IntelSchedulerTraits::process_bypass_loop(tbb::internal::context_guard_helper&, tbb::task*, long) (custom_scheduler.h:474)
tbb::internal::custom_schedulertbb::internal::IntelSchedulerTraits::local_wait_for_all(tbb::task&, tbb::task*) (custom_scheduler.h:636)
tbb::internal::generic_scheduler::local_spawn_root_and_wait(tbb::task*, tbb::task*&) <libtbb.so.2>
pxrInternal_v0_22__pxrReserved::WorkDispatcher::InvokerTask<pxrInternal_v0_22__pxrReserved::HdRenderIndex::SyncAll(std::vector<std::shared_ptr<pxrInternal_v0_22__pxrReserved_::HdTask>, std::allocator<std::shared_ptr<pxrInternal_v0_22__pxrReserved__::HdTask> > >, std::unordered_map<pxrInternal_v0_22__pxrReserved__::TfToken, pxrInternal_v0_22__pxrReserved__::VtValue, pxrInternal_v0_22__pxrReserved__::TfToken::HashFunctor, std::equal_to<pxrInternal_v0_22__pxrReserved__::TfToken>, std::allocator<std::pair<pxrInternal_v0_22__pxrReserved__::TfToken const, pxrInternal_v0_22__pxrReserved__::VtValue> > >)::{lambda()#2}::operator()() const::{lambda()#1}>::execute() <libpxr_hd.so>
tbb::internal::custom_schedulertbb::internal::IntelSchedulerTraits::process_bypass_loop(tbb::internal::context_guard_helper&, tbb::task*, long) (custom_scheduler.h:474)
tbb::internal::custom_schedulertbb::internal::IntelSchedulerTraits::local_wait_for_all(tbb::task&, tbb::task*) (custom_scheduler.h:636)
pxrInternal_v0_22__pxrReserved__::WorkDispatcher::Wait() <libpxr_work.so>
pxrInternal_v0_22__pxrReserved__::WorkDispatcher::~WorkDispatcher() <libpxr_work.so>
pxrInternal_v0_22__pxrReserved__::HdRenderIndex::SyncAll(std::vector<std::shared_ptr<pxrInternal_v0_22__pxrReserved__::HdTask>, std::allocator<std::shared_ptr<pxrInternal_v0_22__pxrReserved__::HdTask> > >, std::unordered_map<pxrInternal_v0_22__pxrReserved__::TfToken, pxrInternal_v0_22__pxrReserved__::VtValue, pxrInternal_v0_22__pxrReserved__::TfToken::HashFunctor, std::equal_to<pxrInternal_v0_22__pxrReserved__::TfToken>, std::allocator<std::pair<pxrInternal_v0_22__pxrReserved__::TfToken const, pxrInternal_v0_22__pxrReserved__::VtValue> > >)::{lambda()#2}::operator()() const <libpxr_hd.so>
tbb::interface7::internal::isolate_within_arena(tbb::interface7::internal::delegate_base&, long) <libtbb.so.2>
pxrInternal_v0_22__pxrReserved__::HdRenderIndex::SyncAll(std::vector<std::shared_ptr<pxrInternal_v0_22__pxrReserved__::HdTask>, std::allocator<std::shared_ptr<pxrInternal_v0_22__pxrReserved__::HdTask> > >, std::unordered_map<pxrInternal_v0_22__pxrReserved__::TfToken, pxrInternal_v0_22__pxrReserved__::VtValue, pxrInternal_v0_22__pxrReserved__::TfToken::HashFunctor, std::equal_to<pxrInternal_v0_22__pxrReserved__::TfToken>, std::allocator<std::pair<pxrInternal_v0_22__pxrReserved__::TfToken const, pxrInternal_v0_22__pxrReserved__::VtValue> > >) <libpxr_hd.so>
pxrInternal_v0_22__pxrReserved__::XUSD_ImagingEngineGL::DispatchRender(UT_StringHolder const&, pxrInternal_v0_22__pxrReserved__::UsdPrim const&, pxrInternal_v0_22__pxrReserved__::XUSD_ImagingRenderParams const&) <USD_UI.so>
HUSD_Imaging::updateRenderData(UT_Matrix4T const&, UT_Matrix4T const&, UT_Rect<UT_DimRectImpl> const&, bool) <libHoudiniUSD.so>
tbb::internal::function_task<HUSD_Imaging::launchBackgroundRender(UT_Matrix4T const&, UT_Matrix4T const&, UT_Rect<UT_DimRectImpl> const&, UT_StringRef const&, UT_Options const*, bool)::{lambda()#1}>::execute() <libHoudiniUSD.so>
tbb::internal::custom_schedulertbb::internal::IntelSchedulerTraits::process_bypass_loop(tbb::internal::context_guard_helper&, tbb::task*, long) (custom_scheduler.h:474)
tbb::internal::custom_schedulertbb::internal::IntelSchedulerTraits::local_wait_for_all(tbb::task&, tbb::task*) (custom_scheduler.h:636)
tbb::internal::arena::process(tbb::internal::generic_scheduler&) (arena.cpp:196)
tbb::internal::market::process(rml::job&) (market.cpp:667)
tbb::internal::rml::private_worker::run() (private_server.cpp:266)
tbb::internal::rml::private_worker::thread_routine(void*) (private_server.cpp:219)
start_thread <libpthread.so.0>
__clone <libc.so.6>

Traceback from 4576 ThreadId=0x7f328e242f40
AP_Interface::coreDumpChaser(UTsignalHandlerArg) <libHoudiniUI.so>
AP_Interface::si_CrashHandler::chaser(UTsignalHandlerArg) <libHoudiniUI.so>
signalCallback(UTsignalHandlerArg) <libHoudiniUT.so>
UT_Signal::UT_ComboSignalHandler::operator()(int, siginfo_t*, void*) const <libHoudiniUT.so>
UT_Signal::processSignal(int, siginfo_t*, void*) <libHoudiniUT.so>
_L_unlock_13 <libpthread.so.0>
_GI_ppoll <libc.so.6>
qt_safe_poll(pollfd*, unsigned long, timespec const*) <libQt5Core.so.5>
QEventDispatcherUNIX::processEvents(QFlagsQEventLoop::ProcessEventsFlag) <libQt5Core.so.5>
QXcbNativeInterface::dumpNativeWindows(unsigned long long) const <libQt5XcbQpa.so.5>
UI_QtGeneratorThread::processEvents(QFlagsQEventLoop::ProcessEventsFlag) <libHoudiniUI.so>
UI_QtGeneratorThread::waitForRawEvents() <libHoudiniUI.so>
UI_Queue::waitForGenerators(int) <libHoudiniUI.so>
UI_Queue::waitForEvents() <libHoudiniUI.so>
UI_Queue::generateEvents(bool, bool) <libHoudiniUI.so>
UI_Queue::eventLoop() <libHoudiniUI.so>
main <libHoudiniUI.so>
__libc_start_main <libc.so.6>
main

@vvzen
Copy link

vvzen commented Mar 24, 2023 •
edited
Loading

* adds joke on Rust and memory safe languages *

Jokes aside, I’m curious to know more myself since I wanted to try Moonray on Houdini! If you could make a MRE and attach a simple scene so that maybe someone else could try to reproduce it?

@BrianHanke
Copy link
Author

I suppose I could, but it's essentially 1) Load Houdini Solaris 2) Enable MoonRay 3) Doesn't work. :P

I haven't heard of a single person getting Open MoonRay working in Houdini, so I'm wondering if there's a bug somewhere. This seems unnecessarily complicated. The actual standalone renderer is working fine and everything is there in Houdini. Just no rendering...

@BrianHanke
Copy link
Author

Here's another clue. I tried rendering a simple scene to MPlay with MoonRay. (The scene works in Karma/MPlay.) Got this in the console:

"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_DEBUG_REGISTRY'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_DISCOVERY_TERSE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_DISCOVERY_DETAILED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_DLOPEN'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_DLCLOSE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_SCRIPT_MODULE_LOADER'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_TYPE_REGISTRY'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_ATTACH_DEBUGGER_ON_ERROR'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_ATTACH_DEBUGGER_ON_FATAL_ERROR'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_ATTACH_DEBUGGER_ON_WARNING'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_LOG_STACK_TRACE_ON_ERROR'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_LOG_STACK_TRACE_ON_WARNING'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_ERROR_MARK_TRACKING'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_PRINT_ALL_POSTED_ERRORS_TO_STDERR'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PLUG_LOAD'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PLUG_REGISTRATION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PLUG_LOAD_IN_SECONDARY_THREAD'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PLUG_INFO_SEARCH'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'AR_RESOLVER_INIT'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDF_LAYER'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDF_CHANGES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDF_ASSET'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDF_ASSET_TRACE_INVALID_CONTEXT'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDF_FILE_FORMAT'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'NDR_DISCOVERY'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'NDR_PARSING'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'NDR_INFO'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'NDR_STATS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'NDR_DEBUG'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDR_TYPE_CONFORMANCE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
Traceback (most recent call last):
File "/opt/hfs19.5.534/python/lib/python3.9/site-packages-forced/shiboken2/files.dir/shibokensupport/feature.py", line 142, in import
return original_import(name, *args, kwargs)
ModuleNotFoundError: No module named 'pxr.MoonrayShaderParser'
Traceback (most recent call last):
File "/opt/hfs19.5.534/python/lib/python3.9/site-packages-forced/shiboken2/files.dir/shibokensupport/feature.py", line 142, in _import
return original_import(name, args, kwargs)
ModuleNotFoundError: No module named 'pxr.MoonrayShaderDiscovery'
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_DEBUG_REGISTRY'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_DEBUG_REGISTRY'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_DISCOVERY_TERSE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_DISCOVERY_TERSE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_DISCOVERY_DETAILED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_DISCOVERY_DETAILED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_DLOPEN'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_DLOPEN'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_DLCLOSE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_DLCLOSE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_SCRIPT_MODULE_LOADER'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_SCRIPT_MODULE_LOADER'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_TYPE_REGISTRY'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_TYPE_REGISTRY'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_ATTACH_DEBUGGER_ON_ERROR'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_ATTACH_DEBUGGER_ON_ERROR'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_ATTACH_DEBUGGER_ON_FATAL_ERROR'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_ATTACH_DEBUGGER_ON_FATAL_ERROR'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_ATTACH_DEBUGGER_ON_WARNING'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_ATTACH_DEBUGGER_ON_WARNING'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_LOG_STACK_TRACE_ON_ERROR'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_LOG_STACK_TRACE_ON_ERROR'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_LOG_STACK_TRACE_ON_WARNING'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_LOG_STACK_TRACE_ON_WARNING'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_ERROR_MARK_TRACKING'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_ERROR_MARK_TRACKING'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_PRINT_ALL_POSTED_ERRORS_TO_STDERR'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_PRINT_ALL_POSTED_ERRORS_TO_STDERR'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PLUG_LOAD'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PLUG_LOAD'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PLUG_REGISTRATION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PLUG_REGISTRATION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PLUG_LOAD_IN_SECONDARY_THREAD'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PLUG_LOAD_IN_SECONDARY_THREAD'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PLUG_INFO_SEARCH'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PLUG_INFO_SEARCH'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'AR_RESOLVER_INIT'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'AR_RESOLVER_INIT'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDF_LAYER'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDF_LAYER'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDF_CHANGES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDF_CHANGES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDF_ASSET'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDF_ASSET'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDF_ASSET_TRACE_INVALID_CONTEXT'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDF_ASSET_TRACE_INVALID_CONTEXT'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDF_FILE_FORMAT'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDF_FILE_FORMAT'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PCP_CHANGES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PCP_CHANGES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PCP_DEPENDENCIES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PCP_DEPENDENCIES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PCP_PRIM_INDEX'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PCP_PRIM_INDEX'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PCP_PRIM_INDEX_GRAPHS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PCP_PRIM_INDEX_GRAPHS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PCP_NAMESPACE_EDIT'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'PCP_NAMESPACE_EDIT'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_AUTO_APPLY_API_SCHEMAS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_AUTO_APPLY_API_SCHEMAS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_CHANGES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_CHANGES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_CLIPS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_CLIPS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_COMPOSITION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_COMPOSITION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_DATA_BD'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_DATA_BD'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_DATA_BD_TRY'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_DATA_BD_TRY'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_INSTANCING'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_INSTANCING'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_PATH_RESOLUTION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_PATH_RESOLUTION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_PAYLOADS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_PAYLOADS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_PRIM_LIFETIMES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_PRIM_LIFETIMES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_SCHEMA_REGISTRATION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_SCHEMA_REGISTRATION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_STAGE_CACHE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_STAGE_CACHE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_STAGE_LIFETIMES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_STAGE_LIFETIMES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_STAGE_OPEN'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_STAGE_OPEN'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_STAGE_INSTANTIATION_TIME'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_STAGE_INSTANTIATION_TIME'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_VALIDATE_VARIABILITY'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_VALIDATE_VARIABILITY'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_VALUE_RESOLUTION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USD_VALUE_RESOLUTION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDGEOM_EXTENT'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDGEOM_EXTENT'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDGEOM_BBOX'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDGEOM_BBOX'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'NDR_DISCOVERY'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'NDR_DISCOVERY'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'NDR_PARSING'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'NDR_PARSING'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'NDR_INFO'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'NDR_INFO'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'NDR_STATS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'NDR_STATS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'NDR_DEBUG'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'NDR_DEBUG'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDR_TYPE_CONFORMANCE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'SDR_TYPE_CONFORMANCE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_BPRIM_ADDED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_BPRIM_ADDED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_BPRIM_REMOVED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_BPRIM_REMOVED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_BUFFER_ARRAY_INFO'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_BUFFER_ARRAY_INFO'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_BUFFER_ARRAY_RANGE_CLEANED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_BUFFER_ARRAY_RANGE_CLEANED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_CACHE_HITS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_CACHE_HITS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_CACHE_MISSES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_CACHE_MISSES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_COUNTER_CHANGED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_COUNTER_CHANGED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_DIRTY_ALL_COLLECTIONS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_DIRTY_ALL_COLLECTIONS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_DIRTY_LIST'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_DIRTY_LIST'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_DISABLE_MULTITHREADED_RPRIM_SYNC'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_DISABLE_MULTITHREADED_RPRIM_SYNC'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_DRAWITEMS_CULLED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_DRAWITEMS_CULLED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_ENGINE_PHASE_INFO'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_ENGINE_PHASE_INFO'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_EXT_COMPUTATION_ADDED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_EXT_COMPUTATION_ADDED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_EXT_COMPUTATION_REMOVED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_EXT_COMPUTATION_REMOVED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_EXT_COMPUTATION_UPDATED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_EXT_COMPUTATION_UPDATED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_EXT_COMPUTATION_EXECUTION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_EXT_COMPUTATION_EXECUTION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_FREEZE_CULL_FRUSTUM'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_FREEZE_CULL_FRUSTUM'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_INSTANCER_ADDED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_INSTANCER_ADDED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_INSTANCER_CLEANED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_INSTANCER_CLEANED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_INSTANCER_REMOVED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_INSTANCER_REMOVED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_INSTANCER_UPDATED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_INSTANCER_UPDATED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_RENDER_SETTINGS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_RENDER_SETTINGS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_RPRIM_ADDED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_RPRIM_ADDED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_RPRIM_CLEANED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_RPRIM_CLEANED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_RPRIM_REMOVED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_RPRIM_REMOVED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_RPRIM_UPDATED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_RPRIM_UPDATED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_SAFE_MODE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_SAFE_MODE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_SELECTION_UPDATE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_SELECTION_UPDATE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_SHARED_EXT_COMPUTATION_DATA'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_SHARED_EXT_COMPUTATION_DATA'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_SPRIM_ADDED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_SPRIM_ADDED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_SPRIM_REMOVED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_SPRIM_REMOVED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_SYNC_ALL'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_SYNC_ALL'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_TASK_ADDED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_TASK_ADDED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_TASK_REMOVED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_TASK_REMOVED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_VARYING_STATE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:05] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'HD_VARYING_STATE'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_CHANGES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:06] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_CHANGES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_COLLECTIONS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:06] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_COLLECTIONS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_COMPUTATIONS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:06] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_COMPUTATIONS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_COORDSYS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:06] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_COORDSYS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_INSTANCER'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:06] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_INSTANCER'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_PLUGINS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:06] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_PLUGINS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_POINT_INSTANCER_PROTO_CREATED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:06] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_POINT_INSTANCER_PROTO_CREATED'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_POINT_INSTANCER_PROTO_CULLING'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:06] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_POINT_INSTANCER_PROTO_CULLING'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_POPULATION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:06] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_POPULATION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_SELECTION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:06] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_SELECTION'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_SHADERS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:06] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_SHADERS'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_TEXTURES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:06] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_TEXTURES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
"[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_UPDATES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration."
[20:18:06] USD Fatal Error[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'USDIMAGING_UPDATES'. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
terminate called after throwing an instance of 'arras4::client::DefinitionLoadError'
what(): Couldn't find definition file for 'hd_single' in search path
6635: (sent by pid 6635)
-- TRACEBACK BEGIN --
Traceback from karma 19.5.534 (Compiled on linux-x86_64-gcc9.3):
stackTrace(UTsignalHandlerArg) <libHoudiniUT.so>
signalCallback(UTsignalHandlerArg) <libHoudiniUT.so>
UT_Signal::UT_ComboSignalHandler::operator()(int, siginfo_t, void) const <libHoudiniUT.so>
UT_Signal::processSignal(int, siginfo_t, void) <libHoudiniUT.so>
__GI_raise <libc.so.6>
__GI_raise <libc.so.6>
__GI_abort <libc.so.6>
__gnu_cxx::__verbose_terminate_handler() <libstdc++.so.6>
std::rethrow_exception(std::__exception_ptr::exception_ptr) <libstdc++.so.6>
std::terminate() <libstdc++.so.6>
__cxa_throw <libstdc++.so.6>
arras4::client::SessionDefinition::load(std::string const&, std::string const&) [clone .cold] <libclient_api.so>
hdMoonray::ArrasSettings::ArrasSettings() <hdMoonray.so>
hdMoonray::ArrasRenderer::ArrasRenderer(scene_rdl2::rdl2::SceneContext) <hdMoonray.so>
hdMoonray::RenderDelegate::getRendererApplySettings() <hdMoonray.so>
hdMoonray::RenderBuffer::Allocate(pxrInternal_v0_22__pxrReserved_::GfVec3i const&, pxrInternal_v0_22__pxrReserved__::HdFormat, bool) <hdMoonray.so>
pxrInternal_v0_22__pxrReserved__::HdRenderBuffer::Sync(pxrInternal_v0_22__pxrReserved__::HdSceneDelegate*, pxrInternal_v0_22__pxrReserved__::HdRenderParam*, unsigned int*) <libpxr_hd.so>
pxrInternal_v0_22__pxrReserved__::Hd_PrimTypeIndex<pxrInternal_v0_22__pxrReserved__::HdBprim>::RenderDelegateDestroyPrim(pxrInternal_v0_22__pxrReserved_::HdRenderDelegate*, pxrInternal_v0_22__pxrReserved__::HdBprim*) <libpxr_hd.so>
pxrInternal_v0_22__pxrReserved__::HdRenderIndex::SyncAll(std::vector<std::shared_ptr<pxrInternal_v0_22__pxrReserved__::HdTask>, std::allocator<std::shared_ptr<pxrInternal_v0_22__pxrReserved__::HdTask> > >, std::unordered_map<pxrInternal_v0_22__pxrReserved__::TfToken, pxrInternal_v0_22__pxrReserved__::VtValue, pxrInternal_v0_22__pxrReserved__::TfToken::HashFunctor, std::equal_to<pxrInternal_v0_22__pxrReserved__::TfToken>, std::allocator<std::pair<pxrInternal_v0_22__pxrReserved__::TfToken const, pxrInternal_v0_22__pxrReserved__::VtValue> > >) <libpxr_hd.so>
pxrInternal_v0_22__pxrReserved__::HdEngine::Execute(pxrInternal_v0_22__pxrReserved__::HdRenderIndex*, std::vector<std::shared_ptr<pxrInternal_v0_22__pxrReserved__::HdTask>, std::allocator<std::shared_ptr<pxrInternal_v0_22__pxrReserved__::HdTask> > >*) <libpxr_hd.so>
pxrInternal_v0_22__pxrReserved__::XUSD_HuskEngine::doRender() <libHoudiniUSD.so>
pxrInternal_v0_22__pxrReserved__::XUSD_HuskEngine::Render(double) <libHoudiniUSD.so>
std::runtime_error::what() const
std::runtime_error::what() const
__libc_start_main <libc.so.6>
std::runtime_error::what() const
-- TRACEBACK END --

@BrianHanke
Copy link
Author

  1. Launch Houdini 19.5.534 from the console in CentOS 7.
  2. Load attached scene and click Render to MPlay in rendersettings1.
  3. Check console for above errors.
    moonray_error.zip

@panda1100
Copy link
Contributor

@BrianHanke When you build MoonRay with Python3.9, Do you have MoonrayShaderParser and MoonrayShaderDiscovery Python modules? or There are no Python module for them but just warning messages gone?

@panda1100
Copy link
Contributor

Please ignore my above message. #64 (reply in thread) MoonrayShaderParser and MoonrayShaderDiscovery does not have Python modules.

@solomon-s2020
Copy link

I have the same error problem, is there a solution? No rendering,but moonray appears in the rendering list.

@solomon-s2020
Copy link

@BrianHanke I have the same error problem. what is the solution? thanks
Traceback (most recent call last): File "/opt/hfs19.5.534/python/lib/python3.9/site-packages-forced/shiboken2/files.dir/shibokensupport/__feature__.py", line 142, in _import return original_import(name, *args, **kwargs) ModuleNotFoundError: No module named 'pxr.MoonrayShaderParser' Traceback (most recent call last): File "/opt/hfs19.5.534/python/lib/python3.9/site-packages-forced/shiboken2/files.dir/shibokensupport/__feature__.py", line 142, in _import return original_import(name, *args, **kwargs) ModuleNotFoundError: No module named 'pxr.MoonrayShaderDiscovery'

@BrianHanke
Copy link
Author

@solomon-s2020 For me the solution was to build MoonRay using the Houdini USD libraries. A standard MoonRay build using the official build guide won't work in Houdini.

jlanz pushed a commit that referenced this issue Jul 29, 2024
Update submodues (#66)
9d1615f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@panda1100 @vvzen @BrianHanke @solomon-s2020 @rgwilson68