Hello,
Most of the assemblies that we would view would be the likes of fuselage skin panel assemblies, floor structure assemblies and systems clipping and routing models. As I said before, the amount of memory on the client directly affects how many instances you can load - so we coud load 500 models of cleats and AGS items into a 3D local viewer; but maybe only 140 models of stringers, frames and the skin panel. You can optimise the CGR's for size by switching off the "save lineic elements in the cache" option on the server and playing with the SAG values on the server. Another point to note is that we have found that CGR files produced with the CATIA V5 server are approx. 30% bigger than those created with the CATIA V4 server. The best advice I can give is for you to try it with your setup and parts and see what you think. But it works for us, and has allowed our methods people to create illustrated process plans using their normal PC, instead of a 4D nav workstation.
some problems that we have found include:
1. If you have a model file loaded that contains lots of AGS models, and you only want to see some of the AGS instances, you have to manually right-click on each AGS model and choose the "hide element" option. Very laborious for clipping runs.
2. If you move some of the models to perform an exploded view,the "Hidden line removal" function shows the models in their original position.
3. You cannot copy the current screen view straight to the clipboard like you can with 2D viewers. You have to perform a snapshot and then save the JPEG image from that to disk before opening it into powerpoint or similar. (IE has a bug that prevents a copy/paste being performed on the JPEG).
A very good guy to talk to in IBM UK is John Lawrie, email: lawrieJ<at>uk.ibm.com - or Paul Manton email: paul_manton<at>uk.ibm.com for techie stuff. Both these guys are very helpful, and have a lot of experience of 3Dcom via VPM.
I can email you some screenshots of assemblies that our Users have created if you like.
Finally, I would like to restate that we do not use VPM here, so there might be extra functionality (and bugs) that we do not know about. And.. Don't expect Dassault to be too helpful when you submit any APAR's - they seems to label all bugs relating to 3Dcom as a "permanent restriction" these days.
Hope this helps,
Gary.