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.

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

Xflow: No operator with name 'xflow.add' found #100

Closed
j4yk opened this issue Feb 10, 2015 · 2 comments
Closed

Xflow: No operator with name 'xflow.add' found #100

j4yk opened this issue Feb 10, 2015 · 2 comments
Milestone

Comments

@j4yk
Copy link
Contributor

j4yk commented Feb 10, 2015

Xflow tells me that xflow.add could not be found (the issue title is the error message from the console) and I have no clue why. Below is a subset of my code which triggers this error (verified by removing everything else except html boilerplate). What could possibly cause this?

    <script src="http://www.xml3d.org/xml3d/script/xml3d.js" type="text/javascript"></script>
    <script src="http://www.xml3d.org/xml3d/script/tools/camera.js" type="text/javascript"></script>
    <!-- ... -->
        <dataflow id="createBoxesFromPointCloud" out="position">
            <float3 param="true" name="center"></float3>
            <float3 param="true" name="extent"></float3>
            <compute>
                position = xflow.add(center, extent);
            </compute>
        </dataflow>
        <mesh type="tristrips" style="shader: #boxInstancesShader">
            <data compute="dataflow['#createBoxesFromPointCloud']">
                <float3 name="center">0 0 0 0.463232 0.005 0.49296 ...</float3>
                <float3 name="extent">1 0.005 1 0.0374403 0.005 0.0130795 ...</float3>
            </data>
        </mesh>

PS. is there another active channel for questions about XML3D/Xflow that are not possibly bug reports or feature requests but rather calls for help? :-)

@csvurt
Copy link
Contributor

csvurt commented Feb 11, 2015

Well it looks like the xflow.add operator didn't make it into the last release build, which is interesting...

We're in the process of moving to a better build system right now so I'll leave this issue open until that's ready (release 4.9) to make sure this doesn't happen again. Until then you could register the operator yourself, just throw this into a .js file and include it after xml3d.js.

We have a public mailing list for questions and discussion and calls for help available here. I'd like to get some forums up at some point but until then that's your best bet.

@csvurt
Copy link
Contributor

csvurt commented Mar 31, 2015

I've double checked to make sure all the operators were included this time around, everything looks ok so I'll close this now.

@csvurt csvurt closed this as completed Mar 31, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants