I'm getting much better results parsing the data by splitting the text than processing two X and Y lists and merging them. Up to almost 15fps which is ideal. Thanks again @Bodysoulspirit
Thanks @Kewl, it's really the inside Vuo stuff that I'm thinking about, how one would capture a 3d scene to wrap a cube without weird distortions and misalignments.
Would you build a kind of 6 camera setup? and how would that stitch together? What if the room wasn't perfectly cubed? Could we maybe stitch two 180degree fisheye cameras together and somehow use that to build the texture map?
Imagine you have a box room, and all the walls, the floor and the ceiling are edge to edge screens.
If we then created a 3D scene in vuo and wanted to project it onto those screens so it wraps around you seamlessly how do you think one would go about that?
Would it take a custom camera? Or is it possible to output a manipulated image of sorts? Bit of a mind bender. Thoughts welcomed ;)
Looks like I almost got there, omitting the get tree content node feels like its made it a little faster. I wonder if I could get better results if the coordinates were listed in a different way so we don't have to have so many processed list nodes. Will report back. Thanks again for the quick response!
Safeness&Greatness
M
