PCS behaves differently if I try to use it within ABD within ProjectWise managed workspace or within ABD outside Projectwise...
The library paths I define in standalone ABD load correctly, no matter if the content of the folders are .pac, .paw or .paz.
In managed workspace, only the folders containing .paz material show, and then when trying to load a component library, nothing happens anyway...
Identical folders & files in the managed workspace and the unmanaged workspace...
Anyone?
Hi Steve, well that's kinda reassuring, I have also tried adding PCS as an application in PW Admin with the relevant file extensions but still no joy...
Hi Chris,
The parametric tools now available (and that will continue to be developed further) in MicroStation CONNECT Edition will be "consumed", as we call it here, by ABD and other Bentley applications that are based on the MicroStation platform. It is intended to replace PCS and FrameBuilder with tools based on the platform parametrics. Exactly what will emerge and how it will relate to GC I don't know and am not going to speculate. However GC also has a long term future, here is one possible use for GC in ABD: GC SS6 - Creating and Modifying ABD Floors
Regards
Marc
Marc has nicely covered the future of parametric content creation for ABD CONNECT and beyond. So I will just add that File > Open and File > Save are the only two commands that are ProjectWise enabled in PC Studio.
Hi Steve, thanks for the PCS info, I have tried various locations without success.
When choosing a library path in the PCS options, PW does list folders containing .paz files, but not those containing .pac or .paw files. Regardless of where those folders are.
But when it comes to loading components, it just won't do it anyway, even if the folder to be loaded shows up in the list.
Yes I know we can create parametric content, my comment was more about the lingering uncertainty surrounding the future of either of those tools, PCS and FB... You will I am sure agree that it's kinda hard to be motivated by a product which you yourself describe as being replaced in the future... Mark's comments in that respect are all very well but really give us zero indication as any sort of timeline. Hopefully content already created will be editable with any future new product...?