michaelb
07-30-2003, 12:57 AM
Hi,
I was hoping someone could shed some light on a problem I’m having with LW’s Targeting function. I put together two quick scene files in a .zip archive that will demonstrate it:
http://yourpage.blazenet.net/michaelbarnes/Targeting.zip
What I basically want to do is have a light on a hinge point at a target, but the light and the target are both children of separate nulls that rotate. In the “TargetOK” scene, everything is fine as long as I keep everything in its original zeroed out orientation. In the “TargetTwisted” scene, just keep your eyes on the light as it rotates. I moved the TargetBase null a meter off the 0 position, and it’s all thrown out of alignment. The light should remain centered above the LightHinge null and pointed at the Target null, but it’s off in space pointing a whole different direction. It’s almost like the Targeting function is additive, and it affects children more and more the deeper it progresses into an object hierarchy. Am I just doing something wrong here, or is it really supposed to be this way? Is there a way around this by using expressions, counter angled nulls parented to the target nulls, etc.? Any and all help or suggestions would be appreciated!
Thank you,
Michael A. Barnes
I was hoping someone could shed some light on a problem I’m having with LW’s Targeting function. I put together two quick scene files in a .zip archive that will demonstrate it:
http://yourpage.blazenet.net/michaelbarnes/Targeting.zip
What I basically want to do is have a light on a hinge point at a target, but the light and the target are both children of separate nulls that rotate. In the “TargetOK” scene, everything is fine as long as I keep everything in its original zeroed out orientation. In the “TargetTwisted” scene, just keep your eyes on the light as it rotates. I moved the TargetBase null a meter off the 0 position, and it’s all thrown out of alignment. The light should remain centered above the LightHinge null and pointed at the Target null, but it’s off in space pointing a whole different direction. It’s almost like the Targeting function is additive, and it affects children more and more the deeper it progresses into an object hierarchy. Am I just doing something wrong here, or is it really supposed to be this way? Is there a way around this by using expressions, counter angled nulls parented to the target nulls, etc.? Any and all help or suggestions would be appreciated!
Thank you,
Michael A. Barnes
