HiWe're using Microstation Connect Edition Update 4 - Version 10.04.00.46 on a desktop that has an Intel Xeon CPU @3.40 GHz with 32GB of RAM. We're trying to create some fly through videos. Our preferred method is to create JPG files then we use other software to compile them into a video. Our issue is that the memory on the machines gets slowly filled up until it's full at which point MS either disappears with no notice or it slows the machine to a crawl then disappears. We can do about 3800 frames (It seems to differ from machine to machine, probably because different machines are running different applications). We need almost 40000 frames for our video so it means we can't run the video creation over night as it needs to be re-started 10 or more times. Other factors that might be important: We record our JPGs at a resolution of 1920x1080 with zero anti-alias.
My question is: Is there a setting that might affect this?
T.I.A.
Maybe I'm getting your description wrong, but why not script this and do a work with smaller parts? Say like frame 0 to 500 and so on? Each frame will get it's number so no problem there. Send everthing to the same folder and when reach the last frame you can use you're other program to merged them. Probably you're aware, but Microstation also does this in a simpler way without many possibilities that others can do.
Regards
José
Hi Jose
We're still trying to work the way we did in V8, which could produce 40000 frames over night without crashing. I get your point about scripting the work. I could see it working. At the moment we don't really have that capability in the office and, really, Microstation shouldn't be crashing because it's filled the RAM on my machine. The last time I tried to get Microstation to produce a video from the JPGs we had, it couldn't produce the video at the same resolution as the JPGs. I haven't tried using the Connect edition to create the video, we have Adobe and it works.
Paul
Hi Paul,
I understand your vision upon this issue. We all fell the same, but as you are aware, Microstation is becoming more complex upon each release. Working in a daily base you'll see that are some things that can't be done exactly the same way as once before. This a good example. Another issue is you haven't told which render are you using, I'm guessing Luxology? This is heavier duty compare to the old raytracing or others. Are you comparing the same render settings? Resolution output? It's completely wrong to compare the render engine from that far version to the new ones. Obviously you can't get the same result with the same time in the new version. If using the same render engine as the earlier version, and all the other settings are the same, then you can compare.
Another issue could be, are you referencing DWG files?
At least you'll get by with smaller parts. In other issues (not about visualization) we have to go back to previous versions to get the work done.