Hello,
Using the Trace VOP, I attach a Parameter set to List of Objects to the Scope input. When I try to use it, however, I notice a couple of unfortunate things. Blank means everything, which IMHO is wrong (should be * means everything!) and I cannot do /obj/nothing as a workaround, it also gives me everything!
Strangely, if I set my ROP to have Visible Objects set to only the obj with the raytrace shader on it, I can use another object that is not in the Visible Objects list, and that will effectively set the Trace scope to none.
Cheers,
Peter B
BUG: Scoping raytracing in VOPs
4471 6 2- pbowmar
- Member
- 7025 posts
- Joined: July 2005
- Offline
- rafal
- Staff
- 1449 posts
- Joined: July 2005
- Offline
- pbowmar
- Member
- 7025 posts
- Joined: July 2005
- Offline
- rafal
- Staff
- 1449 posts
- Joined: July 2005
- Offline
- pbowmar
- Member
- 7025 posts
- Joined: July 2005
- Offline
- lisux
- Member
- 581 posts
- Joined: July 2005
- Offline
- jason_iversen
- Member
- 12485 posts
- Joined: July 2005
- Offline
Whats interesting about the VEX trace calls is that the instant you specify the “scope” argument that it'll ignore the Scope parameter in Object's parameters and use only what is specified to VEX. I personally wish the masks would be combined but what you can do is use the renderstate() function to find out what the object level mask should be and optionally use it instead. To this end it'd be great to have the Raytrace VOP support using the renderstate() functionality too.
Jason Iversen, Technology Supervisor & FX Pipeline/R+D Lead @ Weta FX
also, http://www.odforce.net [www.odforce.net]
also, http://www.odforce.net [www.odforce.net]
-
- Quick Links