jstrecker's picture

Jaymie (@jstrecker)

Groups

  • Vuo Founder
  • Team Vuo
jstrecker's picture
jstrecker's picture
+0

Interesting idea. This would make a straighter cut than Trim 3D Object, since it would be at the pixel level instead of the triangle level.

Since clipping is per-camera, one possibility would be to render your object to clip with one Render Scene to Window and the chosen clipping distances, and the rest of the scene with another Render Scene to Window and the default clipping distances, and combine them with Blend Images.

jstrecker's picture

OK. The only things that changed between 1.2.5 and 1.2.6-alpha1 were the Tree node set and the Sort nodes, nothing that could have affected Duet performance.

jstrecker's picture

I'd suggest doing some further testing of different Vuo versions with Duet, and different Duet versions too if you can. This would tell you if the problem is in Vuo or Duet and when it started.

jstrecker's picture
@jstrecker commented on @marioepsley's Bug Report, “texture mapping a .ply

@marioepsley, would you mind posting the .ply file that didn't work correctly, so we can figure out why? (Tried downloading from trn.io, but the download link was broken.)

jstrecker's picture
@jstrecker commented on @Kewl's Discussion, “Make Noise Image: how many bits?

It's 8bpc.

One reason that you might see banding is if your monitor supports fewer colors. If that's the problem, adding some noise (as in the attached composition) should help.

To check if you really are getting an 8bpc image, you can open it in an image editing application and check the number of unique colors. For example, in Photoshop, go to Image > Mode > Indexed Color. The maximum unique colors you could see with 8bpc is 256. If you see slightly fewer than that (like 246), it's fine. If you see a lot fewer, there's a problem.

Pages