I thought it would be more helpful to give the exact steps than to upload a composition here. The composition is at the link provided, along with the parabox node.
I’ll see if I can generate a new crash and get a crash report for you. It is extremely repeatable in the manner I specified, so it shouldn’t be a problem.
Thanks Jean!
It also is not personally a showstopper for me, but when I encountered it, I had a feeling it could possibly be linked to some other crashes people have experienced when loading vuo comps within various apps, or just in vuo itself.
If it was me, and I was attempting to reproduce, I’d want to go to the github, dl the package, install the node, open up a comp in the bin file located exactly as is. I think that is the best way to test the bug and keep most context in play. That said, I could upload the individual bits if it proves to be needed.
I’ll try to do the crash report by EOD, but I may just email it. :-) Â
The crash report excerpt is from Vuo 2.1.2. We tried to reproduce it in in 2.3.2, but haven’t been able to. Does it crash in Vuo 2.3.2? If so, can you e-mail us a crash report from the current version? We’ve seen some other crashes that implicate modules in the User Modules folder. Can you reproduce it if you temporarily move all the modules out of that folder?
So…the bug reports I sat down and filed recently were the result of going through a text doc where I had been writing them down. I just wanted to get them in because it’s kind of easy to procrastinate on (at least for me).
Obviously these were all against the incorrect version, so instead of being super duper helpful, it’s all kind of questionable.
I will go through each in the near future, test again, and follow up with response. Now, there are a some I felt should be filed as bugs and which would obviously still stand regardless of this version increment…so if there’s no follow up on those, it’s just meant to keep the signal to noise ratio a little better.
Well, unfortunately in the newest VUO I get messages like this when attempting to run these same parabox example compositions, save for showWireFrame…I believe likely relate to that composition not attempting to initialize a shader.
(This node is extremely important at the moment - at least to me, since vuo has no built in vertex shader customization on an in-editor level, or in the shader protocol for that matter. Otherwise one has to code a custom node to manipulate the vertex shader with custom code.)
Undefined symbols for architecture x86_64:
“_VuoSubmeshMesh_download”, referenced from:
_GetMeshValues in composite-RlQ8Ak-bc5c24.o
“__ZNKSs17find_first_not_ofEcm”, referenced from:
_VuoList_PbxShaderUniform_getSummary in composite-RlQ8Ak-bc5c24.o
“__ZNKSs5c_strEv”, referenced from:
_VuoList_PbxShaderUniform_getSummary in composite-RlQ8Ak-bc5c24.o
“__ZNKSs6lengthEv”, referenced from:
_VuoList_PbxShaderUniform_getSummary in composite-RlQ8Ak-bc5c24.o
“__ZNKSt19basic_ostringstreamIcSt11char_traitsIcESaIcEE3strEv”, referenced from:
_VuoList_PbxShaderUniform_getSummary in composite-RlQ8Ak-bc5c24.o
“__ZNSaIcEC1Ev”, referenced from:
_VuoList_PbxShaderUniform_getSummary in composite-RlQ8Ak-bc5c24.o
“__ZNSaIcED1Ev”, referenced from:
_VuoList_PbxShaderUniform_getSummary in composite-RlQ8Ak-bc5c24.o
“__ZNSolsEm”, referenced from:
_VuoList_PbxShaderUniform_getSummary in composite-RlQ8Ak-bc5c24.o
“__ZNSsC1EPKcRKSaIcE”, referenced from:
_VuoList_PbxShaderUniform_getSummary in composite-RlQ8Ak-bc5c24.o
“__ZNSsD1Ev”, referenced from:
_VuoList_PbxShaderUniform_getSummary in composite-RlQ8Ak-bc5c24.o
“__ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEEC1ESt13_Ios_Openmode”, referenced from:
_VuoList_PbxShaderUniform_getSummary in composite-RlQ8Ak-bc5c24.o
“__ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEED1Ev”, referenced from:
_VuoList_PbxShaderUniform_getSummary in composite-RlQ8Ak-bc5c24.o
“__ZSt20__throw_length_errorPKc”, referenced from:
_ZNSt6vectorI16PbxShaderUniformSaIS0_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS0_S2_EERKS0 in composite-RlQ8Ak-bc5c24.o
“__ZStlsISt11char_traitsIcEERSt13basic_ostreamIcT_ES5_PKc”, referenced from:
_VuoList_PbxShaderUniform_getSummary in composite-RlQ8Ak-bc5c24.o
“__ZStlsIcSt11char_traitsIcESaIcEERSt13basic_ostreamIT_T0_ES7_RKSbIS4_S5_T1_E”, referenced from:
_VuoList_PbxShaderUniform_getSummary in composite-RlQ8Ak-bc5c24.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation) Â
So, after some discussion with other users, it is my understanding that parabox nodes actually stopped working midway through version 1 of VUO.
It is history now, but it is concerning that a plugin would stop working midway through a major version of an app. I don’t think that should ever happen. I had a similar issue with a bunch of nodes I programmed. I think there is generally an expectation that a plugin standard does not shift in a way that breaks all plugins, within a major point version of an app. Who wants to spend time programming a bunch of things for a system without that expectation? If the developers of a system allow things to break within a point version update, it is a much much harder sell to convince outside developers to spend the time writing plugins for it.
I state this while understanding that sometimes hard decisions have to be made that are going to make someone unhappy, whatever route is taken. I would just hope that in the future, making changes that break all nodes within a major point version of VUO, is something that will not happen or happen very rarely with an understanding of just how inconvenient it is for outside developers as well as end users, sometimes creating truly impossible to solve situations.
That said, I am wondering if someone at VUO can give a head’s up about what may have changed that would then cause this plugin to be unusable. I don’t expect VUO to maintain this, though it would have been extremely useful if it had been integrated as a stock patch, and I really wonder why it wasn’t. But if someone could from the VUO team could give even a vague description of what changed so that this no longer works, it might be help to get it working again. Â
The Parabox nodes for 3D graphics stopped working with the Vuo 2.0.0 release due to improvements the team made for handling graphics.
Vuo 2.4.0 will include a new Get Mesh Values node, bringing the most-frequently-used Parabox functionality into Vuo core. If any community members want additional Parabox functionality in Vuo core, they are welcome to create feature requests and vote for them, fund them, or submit code contributions.
The parabox node set mended a lot of issues where it feels that there are gaps in VUO, aside from that node.
Another case that quickly comes to mind are the nodes to translate object to layer and vice versa. In VUO, a quad has been implemented as a layer, so there is a lack of interoperability with all of the scene object nodes.
It was lucky that someone had made all of these nodes to address major VUO issues.
Also, I think my request for a vague description may have been taken too literally :-)
The editor exception isn’t that helpful at pointing to what may need to be changed in the code. Â
The Parabox nodes for 3D graphics stopped working with the Vuo 2.0.0 release due to improvements the team made for handling graphics.
I was going to ask if the Vuo API somehow listed the changes from Vuo 1 to 2 (I usually see mostly the "new in Vuo 2.x.x notes in the API), but checking the release notes here of the Vuo versions on the website, scrolling down to the SDK version of Vuo 2.0.0 Release Version Notes I see changes are in fact written there.
Without being a coder, are all the changes that make the Paradox nodes crash in Vuo 2 listed there ? Or is it up to the developers to browse the API and search for the new functions instead ?