Oh man, really??? Not a very nice thing to say to folks who actually spent time trying to help solve your problem here, and not encouraging for others to help you out… Yeah, times may be stressful now but let’s keep it civil over here please.
Looks like there is an issue with what the automated animated camera/target placement does that the Arctic and some other modes don’t like, but the above “investigation” pretty much nailed what the problem is - since Skylight shadows are View-based (somewhat generated from Zdepth information I think) then camera target being too close to the camera results in almost no shadows. And the path animations will not let you change that parameter. So 90% of the work has been done already, far from wasting time (thanks @Pascal - I had no idea that if we push the target far, the AO shadows get nicer and darker! good find…)
So in case anyone finds that useful, I wrote a script that may help with the above animation problem.
It uses the “ViewFrameNumber” command to manually iterate through the current animation frames, and pushes the target to user-defined distance to fix the shading issue. There is an option to just “Play” the animation or “Record” - in that case you will be asked for the base file name and location and frame numbers will be added to file name. Additionally the script lets you pick any display mode, not only the one picked when defining animation. Recorded frames will be saved using ViewCaptureToFile command, viewport size, but if you need larger sizes you can change the “Scale” parameter in the command prior to recording animation - it is sticky. Note (and I think this is the case with any recorded animation) that the lens will be used from what you currently have set, no matter what was set while defining the animation.
Maybe that helps, for now.
PlayRecordAnimation.rvb (3.3 KB)