FREQUENTLY ASKED QUESTIONS
We use quite a wide variety of tools. Our main development environment is CATIA based. We use customised configurations including CATIA-ICEM for high quaility surface development.
We convert CAD data using different translators depending on the type of model. We then assemble, rig and animate content using Maya as a hub. From here we can render images with a variety of different tools.
Yes certainly, and in some cases a bespoke model is the only option. But be aware that building any 3D geometry from scratch can be time-consuming and involve significant cost before any output has actually been produced from it.
This is why we try and build flexibility into our work so that it can be re-purposed and used as a basis for further content, helping to save cost in the future. Some of our models have been adapted, updated and reused over a 17 year period making the initial investment in them extremely cost-effective.
In many situations we work with existing customer CAD data, filling gaps, adapting or adding material to fit a particular requirement. This can help save significant time and cost.
We mainly work with models used for engineering applications and try to adapt and build models as solids wherever possible. Our prefered exchange option is the step file format (AP214 or AP203). However, we can accept a wide variety of file types.
The brief answer is yes, however it’s not quite as simple as just sending data in an appropriate file format. It might be that scale issues need to be addressed and appropriate support or fixing design considered. This applies to assemblies that are intended to be physically made in any form, not just 3D printed.
If you are interested in producing any type of physical model as part of a project, please get in touch and we can discuss your requirement in more detail.
Yes, low-polygon models can be generated but it is not always a straightforward process. It very much depends on what is meant by low-polygon.
Several times, we have been asked to adapt data for uses which require very low-polygon models. For example, an augmented reality app running on a smart phone where, because of limited graphics processing capability, the optimum polygon count for a model may be in the thousands of faces or even just a few hundred. In this situation, there is no way to simply turn down tessellation. The model will need to be simplified extensively to fit within the required polygon budget.
Here, the original model might be used as a template over which a highly simplified polygon model is custom built from scratch, perhaps using texture maps rendered from the original model to mimic detail. However, there are inevitably compromises and trade-offs to be considered with these approaches.
It very much depends on subject matter, the amount of research needed, level of detail and what the model is ultimately going to be used for. A very simple concept may take a few days to mock up, where as a detailed assembly could take many months to build and refine.
Again, in many situations we work with existing customer CAD data, filling gaps, adapting or adding material to fit a particular requirement. This can help save significant time and cost.