mike h

Alright, so the "filterbyrange" node is working for me -- so thank you to all those who replied.

For those who may also be seeking an answer to this down the road there are 2 specific pieces to get the node working.

1. the wedge node has to have a range that is --larger-- than the filtered range.

So for example, if you want to filter range 10-20 like my example, the wedge node above it has to have a wedgecount of 20 or more. if you want to run range 21-40 then you will need a wedge count of 40 or more. If the wedgecount isn't high enough nothing will be output.

2. filterbyrange node adds a "range" attribute by default using the check box for "set range attribute", this isn't needed. Instead change "filter by" to "custom attribute" and set the attribute to "wedgeindex" then set the range that you would like to see.

Thank you for your replies, I'm not sure if they're working though.

@axelsp so the frame range node looks like it has similar paramaters to the wedge node's range, but it doesn't seem to connect to the wedge attribute, I think it's seeking a range like a frame range instead of a wedge range, unless there is a way to set it to do that, do you know how to set it?

@jurweer I'm trying to understand your naming convention a bit more, are you saying if I write @wedgenum.10 it will start from 10 and then do 11... 12 13.. or will it just go 0.10, 1.10, 2.10., 3.10 etc?

I'm trying to set my wedges so that I can run a range, let that range complete and then run a different range.

For example, I just want wedge 1-10, let that finish, then do 11-20 (testing with smaller numbers in the screenshot).

It seems the wedge node is set up for this, but whenever I run it the second range overwrites the first one, and it seems to start from wedge 0 even though I'm trying to set it to higher numbers.

I've set all my output nodes to use @wedgenum instead of @wedgeindex and I've checked "preserve wedge numbers" in the wedge node, but that didn't do it. What am I doing wrong? Can anyone help me out?