This has been incredibly frustrating. I've been a MicroStation user and champion of the software for about two decades now, but this facet of its operation has left me with a very sour taste in my mouth. I've done several animations in MicroStation, and I'm being hamstrung by something that has come up in a few cases previously. For some confounding reason, certain frames render poorly. Various elements just don't fully render, and it happens at various locations along my fly-through. I've tried moving all the elements closer to (0,0,0), merging references into the active file, and dropping mesh elements to shapes. These drastic approaches have helped in many cases, but as you can see in the animation link provided below, it's still haunting me.
Please, dear Lord, somebody give me some helpful guidance as to how to resolve this. It's completely mind-boggling to me that I've invested this much time and effort into making a robust model to animate, only to be left endlessly troubleshooting the rendering functionality of the software I'm using.
Thanks for your time and attention.
-Chris
Hi Chris,
Sorry you are having this issue it looks like you are saving frames using smooth shading and not Luxology is this correct? It would be best for you to post the data set for us to have a look. It appears to be camera clipping issue which could be the cause and that could happen based on where the camera target is at the point in the animation where the geometry disappears, Are you animating just the camera and not having the camera follow a animated target? When you script a animation camera without placing and animating a target the focal distance is fixed at the time you create the animation camera and it could be that distance is too short.
Jerry
Thanks for taking the time to reply, Jerry. I really appreciate you sharing your expertise on this forum. Yes, I'm saving the frames using smooth shading (I'd love to use Luxology, but it either takes way too long or more frequently just crashes). Yes, I initially setup the camera to simply follow a path without defining an animated target, but I tried your suggestion and that seems to be resolving the issue so far (I'm 56% into a 29 hour rendering process). Fingers-crossed...