Tue, Nov 26, 5:03 PM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Nov 26 6:57 am)



Subject: Editing an Animation way point


surveyman ( ) posted Wed, 04 January 2012 at 2:51 AM · edited Sat, 23 November 2024 at 12:09 AM

file_477012.JPG

I'm just learning animation.  I'm getting it, but am having a problem changing the position "Z" (elevation) value of the animation path spline (blue line). 

Every time I try to lower/raise the elevation of the way point, it snaps back to its original location as soon as I finish the movement.  The "X" and "Y" spline positions (red & green) I can change/move without a problem.

The animation Wizard does not let you alter the elevation of the vertical spline path,. nor does it let you key in numerical elevation values.

I'm using xStream 10, but I found the same problem in xStream 9.5. 

Tx.


bruno021 ( ) posted Wed, 04 January 2012 at 3:10 AM

Why don't you do this in the viewport?



ShawnDriscoll ( ) posted Wed, 04 January 2012 at 3:25 AM

Is your camera's height locked or unlocked?  Kept level, or no?

www.youtube.com/user/ShawnDriscollCG


surveyman ( ) posted Wed, 04 January 2012 at 2:36 PM

Thanks Shawn - the camera was 'locked' - I guess that is the default setting.  As soon as I unlocked it, I could move the waypoints in three dimensions.

Bruno - when the camera is 'locked', the waypoints in the 3D views are locked in their vertical positions as well.  Thanks though.

 


bruno021 ( ) posted Wed, 04 January 2012 at 3:57 PM

Not if you're not going below the locked altitude... Actually, right now in Vue 10, you can even go under any locked altitude. Guess it's a bug!



surveyman ( ) posted Wed, 04 January 2012 at 4:25 PM

Bruno,

The altitude was not locked, the camera was.  However, I do not understand why with a locked camera I could alter the waypoint X & Y data but not the Z.  All I did was click on the camera 'lock' to unlock it and then it behaved like I expected it to.


ShawnDriscoll ( ) posted Wed, 04 January 2012 at 6:01 PM

surveyman,

Just be careful "when" you unlock the camera.  It's best to do it before even beginning a timeline.  Vue will gladly assist you with unlocking a camera if you are in the middle of a timeline, for instance, which will cause headaches.  The entire camera workflow in Vue is a kludge, so it's hard to spot a bug while using one.

www.youtube.com/user/ShawnDriscollCG


surveyman ( ) posted Thu, 05 January 2012 at 2:51 PM

LoL.  At this point, I'm not sure what is a 'bug' and what is 'designed bahavior'.  I'm just playing around, trying things and seeing what happens.  I did notice that I had to tweak the camera path a few times because 'things changed' on me.

I built a new computer for doing animations (i7-3930 w/ 32Gb ram & SSD) and it's still a 'bear' to render.  90 second animation @ 640x400 took 12+hrs to render.  Just a simple island w/ tropical eco.  But the time to render the same scene on my old Q6600 was estimated at 72+hrs. LoL.

Wish there were instructions on how to streamline the rendering options for best/fastest animation output.  I did notice that the new anti-flickering process adds about 45% to the render time, but really cuts down on the flickering.  Ran 2 animations & compared.

Tx for the warning - I'll keep an eye out for those 'features'.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.