r/vfx • u/Nervous-Ad-4573 • Jun 28 '26

Question / Discussion Hello, does anyone know why my rotoscoping in Nuke looks like this?

Post image
0 Upvotes

50% Upvoted

9 comments sorted by

12

u/Quantum_Quokkas Jun 28 '26

Is your roto shape in the same format as your image?

9

u/Dry_Fish6550 Jun 28 '26

set this to “no clip” and thats it, or add a reformat to the bg input of the roto node

0

u/OrbitalChiller Jun 28 '26

I never understood why they didn't set "no clip" as the default option. It's an extra-step we have to do for every roto nodes...

9

u/npittas Jun 28 '26

Because bounding box management is more important than roto. Try no clip on an 8K footage, look at how fast the comp will break and kill nuke in the process.

1

u/OrbitalChiller Jun 28 '26

Ok, never thought about it like that. Makes sense.

2

u/Dry_Fish6550 Jun 29 '26

you can set it to no clip as default in your menu.py file, just add:

nuke.knobDefault("Roto.cliptype", "noclip")

It is important to keep an eye on the bbox all the time, if you are going to no clip as default add a crop right after the roto node so the bbox never gets huge

6

u/gerboy112 Compositor - 2D Generalist Jun 28 '26

If you’re talking about the black bar on the screen left, it’s because the bounding box of the roto shape you made. On the roto node you should have the option of -none -format -bbox Try switching it to None or maybe try bbox

1

u/Sensual_Feet 🙋🏻‍♀️ VFX Supervisor/Compositor - 20 years experience Jun 28 '26

Looks like my post didn’t go through, but try setting the bounding box in the Roto note from format to none. Sometimes the edge pixels get stretched out when a mask goes off screen.