Export DXF fails constantly

[PCully]

Hi,

I've asked some of our consultants who use the Export DXF feature (I never have) if they have had any similar problems or can provide guidance based on experience so will post back here with any tips.

IndusPro and PiscesPro don't have a Collision Detection feature, sorry.

It's not a straightforward to compare <VE> MicroFlo to other CFD software but some general points to note are that MicroFlo uses a non-uniform Cartesian mesher (with the downside being that it can be harder to model complex shapes or concentrate cells in sections of the geometry) while Star-cd can use an unstructured mesh (with more options for different cell shapes and regional mesh refinement).

Some benefits that <VE> MicroFlo offers is speed as the Cartesian mesh is very efficient regarding memory and processor use. Even better now, in fact, since <VE> version 6 offers Parallel processing on multi-core machines for no extra licensing cost! (**shameless advertising**). MicroFlo is also easier to use so will have a lower learning curve for new users.

Within the <Virtual Environment> you have the option to link the CFD model to the Dynamic Thermal model and import Apache simulation results to import such data as surface temperatures, airflows through openings and internal loads.

IES Technical support will be better placed to comment on specific projects and whether the problem could be tackled using MicroFlo but hopefully this gives you some food for thought and perhaps other users on this forum who have experienced different CFD packages could comment also?

Phil