nTopology 3.7 - What's New

Version 3.7

nTopology 3.7 is here! This release features a new overload to the Cell Map between CAD Faces block in our new lattice pipeline, which automatically creates a lattice without self-intersections, so you don’t have to think about the face parameterization or UV origins. As with every release, nTopology’s dedicated support team is ready to answer your questions. Please visit support.ntopology.com to gain access to helpful tutorials and support articles.

Overload: Cell Map between CAD Faces (Beta)

  • The Cell Map between CAD Faces (beta) block has been simplified. The advanced block inputs prior to the 3.7 release are now available as an overload. This simplified block allows you to quickly create a Cell Map between two CAD faces without thinking about the face parameterizations or UV origins.
  • When you add the Cell Map Between CAD Faces (beta) block to a notebook, you’ll see the simplified block with only three inputs: the first CAD face, the second face, and a Vector for the UVW cell count. Internally, nTopology will reparameterize the second CAD face as needed to ensure that the resulting Cell Map is free of self-intersections. You can switch to the advanced overload by clicking the dropdown next to the block name. The advanced overload lets you manually manipulate the face parameterizations or UV origins if needed. Below is an outline of the new default, simplified block.
  • Name: Cell Map between CAD Faces (Beta)
  • Location: Beta > Lattices - Cell Map
  • Description: Constructs volumetric lattice cells between two CAD faces.
  • Input 01: First face
    • Type: CAD Face
    • Description: First CAD surface to apply the cell map.
  • Input 02: Second face
    • Type: CAD Face
    • Description: Second CAD surface to apply the cell map.
  • Input 03: UVW count
    • Type: Vector
    • Description: Number of cells in three directions.
  • Output: Cell Map

Usage Improvements

  • Error messages now include the name of the input that causes the error. In previous releases, error messages would display the input position number where an error was stemming from, as opposed to the name of the input.

Bug Fixes

  • We fixed an issue where CAD edges weren’t correctly bound. When used for boundary selection, all elements along the edge’s directions were selected, but now they can be used for selection as intended.
  • We fixed a tolerance issue in the Trim Cell Map (beta) block that was causing cells to remain that should have been trimmed.
  • We fixed an issue where the lattice result of running the Periodic Lattice Body (beta) block with a Cylindrical Cell Map and Body Centered Cubic Unit Cell wasn’t correctly tessellated.
  • We resolved an issue that was preventing the use of the precise render option for custom implicit Unit Cells.
  • We resolved an issue where entering invalid inputs into either the Cylindrical Cell Map (beta) or the Cell Map on Quad Mesh (beta) block would cause nTop to unexpectedly exit.
  • We resolved an issue where blocks in the input section were not providing you with the ability to add a comment.
  • We resolved an issue where input variables were not triggering the block level build buttons to appear on their associated blocks when the autobuild button was turned off.
  • We resolved an issue where Japanese characters were getting clipped and becoming illegible in variable chips.
  • We resolved an issue where the Gimbal value box was remaining in the scene after closing the section cut or field viewer.
  • We resolved an issue with the extrude constraint. If the curve is significantly longer than the element size in a topology optimization, or the curve is unbound, the computational time may increase significantly. In these cases a warning will be issued and the user will be able to cancel the operation in progress bar.


 new whats 3.7 
Was this article helpful?