![]() Hopefully support will shed more light on this. This was posted about 5 years ago, I don't think that things have changed. Hi Jonathan, in this article Yessios explains that it uses a mix of ACIS and proprietary modelling engine developed in-house. This one is a bit beyond the Tech Support arena alone, so we have forwarded your question to those that can answer that and expect something back soon. It's one of the reasons I'm digging deep with my assessment of FormZ, because ACIS is the backbone of many important architectural CAD technologies and with that forming a large part of both my existing and future client base it's an import aspect of my software Tech I thought it was open knowledge that the underlying geometry engine in FormZ was Spacial ACIS technology. If you have a policy of not discussing your technology implementation that's fine just let me know. ![]() Noticed that you seem to have gracefully ignored this question. If they're a bespoke set of tools linked via API's to the underlying Spatial code base that must complicated matters when attempting to provide a seamless transition across the different tools. ![]() ![]() I ask because it helps clarify in my mind the development task you have when building the subdivision tools. As I understand it the Solids, Surface & NURBS engine are all driven by Spatial but reading through Spatial's latest documentation I couldn't find any reference to subdivision surfaces. I was wondering if the SubD stuff in FormZ is part of Spatial's code base of something that you've built and linked to the Spacial engine via API's. Is the SubD technology in FormZ part of Spatial ACIS code base? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |