Netfabb known issues
This is a selection of issues present in the 2025.1 release.
Note: Issues being listed here but not listed for previous releases does not necessarily mean they were introduced with this release. They may have existed before and were just not listed then.
Netfabb
Cutting
| Note |
Key |
| Using a custom cutting depth of the exact depth of the part itself may lead to artifacts at the far cutting surface. As a workaround, avoid depths and orientations that make the cutting surface exactly coplanar to the far surface of the part to cut. |
NC-12409 |
| The option Cutting depth is only available for arbitrary polygon cuts. Even though the control is present for circular/cylindrical and rectangular/cuboid cuts, it does nothing for these modes. |
NC-15334 |
| The command Modify > Cut > Plane cut does not do anything and also gives no feedback while none of the clipping planes are actually intersecting with any part on the platform. |
NC-15012 |
Back to top
Lattice Commander
| Note |
Key |
The Void role of a body currently voids lattices, skins, and meshes where it should only void lattices.
As a workaround, generate the meshes separately, with the roles applied appropriately, then merge the generated meshes on the regular part platform using Boolean unify. |
NC-10998 |
| Generating a volume lattice on bodies with fully enclosed and closed cavities can generate a separate piece of lattice inside those cavities, too. |
NC-11062 |
| For lattice components imported from 3MF file, Netfabb always assumes millimeters as units, ignoring any specifications in the file saying otherwise. |
NC-12427 |
| Exporting a 3S structure simulation or surface structure simulation to Lattice Commander fails if the base structure has no contour defined for its bars, even though LC ignores bar contour information. |
NC-15411 |
Back to top
Labeling
| Note |
Key |
| In rare cases, a text label on a part in a location that is undercut by another section of the same part as seen along the text projection can partially or fully appear on the undercut as well. |
NC-13435 |
Back to top
Lua
| Note |
Key |
System object properties screenwidth and screenheight always report values for primary screen regardless which screen Netfabb currently sits on. |
NC-14524 |
The Slice object's methods createdownskin and createupskin are inverted. They generate the opposite of what their names suggest. |
NC-15934 |
When the tray:setclipplane(axis, halfspace, space, distance, contour) method is used to position a custom clip plane at a depth along the view axis (with axis = 2 and space = 2), subtract 1000 from the value for distance before calling the method. |
NC-15597 |
The exportpngmulticore method of the SliceImageExporter object ignores the solidness of solid support and always draws them open, with a line at a thickness configured by the supportthickness property. |
NC-13617, NFL-54 |
Back to top
Machine workspaces
| Note |
Key |
| Segments stenciled out of closed contours by the hatchcutting filter are turned into hatches instead of continuing to be contours. This makes them appear as $$HATCHES statements in the CLI export instead of $$POLYLINE ones. This is currently by design. |
NC-15390 |
| The Recalculate button in the slice analysis view produces an unexpected or empty result when the slice analysis was launched out of HP machine workspace. This is currently by design. To recalculate a slice analysis from HP machine workspaces call the analysis from the context view again. |
NC-15568 |
| Stripe hatching in powderbed toolpathing contains a left-over parameter, Unidirectional hatching. This switch is the inverse of Alternating hatch direction but actually does nothing and should not be used. |
NC-16138 |
| Using a Renishaw EBPA configuration with multilaser mode enabled leads to an error message, "EBPA Error 32 (ReferenceError: l_iter is not defined)". As a workaround, choose the Stripe-wise strategy or disable multilaser mode entirely and assign lasers explicitly via Current part > Laser index in the machine's context view. |
NFL-272 |
Back to top
Measurement
| Note |
Key |
| Placing a measurement probe on internal surfaces uncovered using clip planes fails. You can only start measuring from a surface that is visible in the current perspective without the clip plane's hiding function active. |
NC-14994 |
Back to top
Mesh manipulation
| Note |
Key |
| In Mesh manipulation, volumetric remeshing does not do anything when Stop when target is reached is unchecked. There is no workaround other than using it with the option checked. The results are generally comparable, if slightly more rounded than if the option was unchecked. |
NC-15631 |
Back to top
Part library
| Note |
Key |
| Part Library part Screw generates with overlapping triangles when values for Radius and Wrench size are chosen too close to each other. |
NC-12885 |
Back to top
Product name
| Note |
Key |
| Autodesk Netfabb Premium misses the "Premium" name bit in various places |
none |
Back to top
Project tree
| Note |
Key |
| Drag & drop of multiple parts in the project tree only works when grabbing the selection by the focused entry. The focused entry is the one with the dotted box around it. |
NC-15659 |
Back to top
Repair
| Note |
Key |
| The Mesh status on the Status tab in the Repair context view shows correct status only exactly once after freshly opening Repair on a part or after changing the mesh through a script or a manual action like deleting a triangle. As a workaround, visually inspect the part more closely and make use of the Highlighting functions on the Status tab. |
NFL-468 |
Back to top
Slicing
| Note |
Key |
| The displayed drawing order of slices is incorrect when some slices are in groups. |
NC-13175 |
| Reduce points does not always delete points even when they should be eligible. |
NC-15208 |
| Buttons in the slice export may initially be off-center, possibly truncating their text labels. This is a cosmetic issue only. Switching to a different slice format and back to the current one should recenter the buttons. |
NC-15610 |
| Slicing > Stripe hatching contains a left-over parameter, Unidirectional hatching. This switch is the inverse of Alternating hatch direction but actually does nothing and should not be used. |
NC-16137 |
Back to top
Small parts and triangles
| Note |
Key |
| Parts loaded from STL, PLY, and other unitless formats can appear very small or very large. This happens due to a mismatch of units that are assumed during writing and reading the files as these types contain no reliable indicator of units, only plain numbers. This is not a bug or shortcoming of Netfabb but an ambiguity inherent in these file formats. |
NC-15332 |
At very small triangle sizes, some functions stop working reliably, such as placing the camera pivot (Shift+Middle-click) or some repair functions.
As a workaround, scale the part to the correct size, then launch Repair, then click Apply repair without actually modifying the mesh in any way. If the part is already at the desired size, and the problem is still occurring, temporarily scale it up for the required actions, then scale it back down afterwards. |
NC-15333 |
Back to top
Supports
| Note |
Key |
In rare cases, a separate cluster is detected around undercuts or sharp splits for otherwise no apparent reason.
The hollowed-out GE bracket with surfaces requiring support. Cluster detection found a separate cluster on an otherwise continuous surface
This happens when triangles are found to qualify for support multiple times. To help with detection along such conflicting contours, use Texture and color to define facegroups that create artificial segmentation of the downskin.
The Downskin where facegroups have been applied to enforce cluster segmentation. The darker area is a separate facegroup. |
NC-10955 |
| On re-entering the active support editor after generating bar supports with baseplates for bar groups and moving or rotating the part, choosing to refresh supports, rather than replay any support actions, refreshes the bars but not the baseplates. This is currently by design. |
NC-15599 |
Touching the order of support scripts in Netfabb 2025 and newer produces an Access Violation error for Netfabb versions 2024.0 and earlier upon opening the support script list or the support editor. This is caused by lack of forwards compatibility and cannot be fixed. The only workaround to this is to delete %APPDATA%\netfabb\script_order.xml and to avoid reordering scripts in the list with newer Netfabb versions while the older Netfabb installations are still needed. |
NC-15875 |
| Cluster detection by face group name breaks when the name contains a space character |
NC-16251 |
| Volume support set to observe distance to other supports fails to do so with those generated by Polyline on cluster contour when those are set to generate as open polyline walls. The distance is only properly kept when the polylines are generated as closed-volume walls. |
NFL-343 |
Back to top
Texture and color
| Note |
Key |
| Updating Netfabb from 2024.0 to 2025.0 or later with default keyboard shortcuts causes some double mapping of multiple functions to the same key, F8. This must be rectified manually in Settings > Settings > Keyboard shortcuts > Texture and color. |
NC-15782 |
Back to top
UI
| Note |
Key |
| Renaming using keyboard shortcuts (F2 by default) after selecting a part in the 3D view is unreliable and may attempt to rename the associated platform or machine workspace instead. To reliably rename a part in the 3D view, use the Rename command in the part's context menu. Renaming by shortcut after selecting the part in the project tree is not affected by this issue, as should renaming by shortcut in places like the 2D slice view, Lattice Commander, and other views. |
NFL-148 |
| Various numerical input fields do not accept typing a minus sign even though they should. As a workaround, copy&paste the negative value, or manipulate the associated element in the 3D view as and where available until the field shows a negative value itself, then select the numerical value without the minus sign and type the desired value. |
NFL-164 |
| Renaming of a machine workspace in the project tree is not preserved during saving and loading the FABBPROJECT file. There is currently no workaround for this. |
NFL-205 |
Back to top
Simulation Utility, Local Simulation
| Note |
Key |
| When using a build plate STL in a part scale powder bed simulation, a crash occurs if the results are filtered and then the Thermal Gradient result type is selected. |
ANFB-3186 |
| Simulation crashes upon trying to simulate too many distinct and separate meshes at once. This is not typically encountered but may happen when using the import option Split support volumes with individual density on parts with individual bar supports, for example. There is no immediate workaround for this. Try to reduce the amount of individual meshes. For example, connect and merge their volumes, either into one volume or into few volumes that group many individual volumes. |
NC-15011 |
| If Simulation Utility or the Local Simulation GUI was opened previously on a screen that is no longer available, trying to access dialogs like Solver settings and Mesh settings causes them to open on inaccessible screen space, resulting in the main window to apparently freeze. As a workaround, attempt to switch to extended or external-only modes using Win+P while the GUI appears frozen. This should bring the dialogs back into view. When they are, change their position briefly. This should open them properly on the remaining screen for the next session at the latest. |
ANFB-3259 |
Back to top
Optimization Utility
| Note |
Key |
| The lattice of a component may be rendered in thin blue lines. This means that the specification of your lattice is not suitable for the creation of a lattice. The angles between beams are to small or there are too many beams in the component. Modify the size of the unit cell of your lattice. In particular try to avoid a very high aspect ratios of the unit cell. |
NC-3615 |
| When multiple versions of Netfabb Ultimate are installed side-by-side, Optimization Utility fails to open for any version except for the one installed last, producing error messages about missing DLL files. As a workaround, in the respective Netfabb installation folder, copy everything from the atf subfolder, as well as tspline<…>.dll (where *<…>* is a number) from the reform folder, to the base installation folder. |
NC-15561 |
| On very fresh installations of Windows, you may get an error in Optimization Utility by "FEACSCommandLine.exe" saying "VCOMP110.DLL was not found". This is caused by Visual C++ Runtimes being missing or corrupted. Follow advice at https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/vcomp110-dll-is-missing-from-your-computer.html to rectify. |
NC-15582 |
Back to top
