AccuRender nXt

advanced rendering for AutoCAD

Roy, is this a small bug?

I've noticed that nXt doesn't render the last frame of an animation.  If my animation is 100 passes, I do get 100 rendered frames.  Its just that the last one doesn't correspond with the ends of my paths.  I need to set up a camera using the endpoints of both my camera and target paths, and render it with the same FOV in order to catch that last view.

Views: 218

Replies to This Discussion

Not really a bug (I don't think.)  It currently divides the path into n pieces, where n is the number of frames.  This will make it stop one frame length before the path end.  Is that what you're experiencing?  I can change this behavior easily by dividing the path into n-1 lengths-- obviously that imposes a two frame minimum-- not a big deal.
Thanks for the help.  I figured that was the problem.  That last frame is important if I want to add a new path from the end of the last one.  Without it the animation has a little jump because of the missing frame.
Not really-- if I add it back you'll have the equally (probably) annoying problem of a repeated frame.

That's true.  I suppose that's not the problem I was thinking it was.  The first frame of the second animation path equals the last frame of the first - which is probably the ideal way of dealing with it.  I suppose the issue I was having was trying to frame that last view exactly how I want it and then not actually getting that view rendered.  I suppose this issue is probably easier to deal than having to deal with the annoying repeated frame.

 

As an aside, is it possible to batch render multiple animation paths?  You seem to have set a limit of 1000 frames on a single path.  That means that I am limited to only 1000 rendered frames over night.

The 1000 frame limitation is a mistake-- I'll fix it in the next build.

RSS

Search

Translate

© 2026   Header image courtesy Peter Milner   Powered by

Badges  |  Report an Issue  |  Terms of Service