Version 3.0.0.3

Created by Steve Hill, Modified on Thu, 30 May at 8:54 AM by Steve Hill


Bug Fixes


General:

  • Due to issues in installing in an increasing number of environments, installation no longer has the settings in the user's documents folder, instead we have switched to using the user's AppData/Roaming folder. Example of the path is shown below
  • Additionally, we have named this folder a bit differently to help with scripting.
C:\Users\%<INSERT USER NAME>%\AppData\Roaming\Red_Transit_Consultants_LLC\Pipe Network Productivity Tools
  • Resolved a fatal error occurring when using the Settings file from an older version of Pipe Network Productivity Tools
  • Improved detection of faulty installations where Settings do not install correctly due to Windows permissions. New message appears to notify of the issue and how to manually remedy the issue. 
  • Additionally, product has default settings in the product installation. Improved the ability to use these settings in the event of faulty installation allowing for product to continue working.

Create Crossings Table:

  • Resolved an issue with overriding the Crossing table to allow for displaying data differently than the labels. With this fix, we have enhanced the settings page to allow for selecting the pipe elevations at any point for displaying in the table as desired.

Crossing Labels:

  • Resolved a separation error rounding issue that occurs in some situations.
  • When working in Civil 3D Metric, the option for Separation Feet / Inches no longer appears and defaults to false.

Slope Across Pipes Slope Catalogs:

  • Resolved an issue when apply slopes by catalog, the catalog slopes would not apply.




Enhancements:


General:

  • Added support for Civil 3D 2025
  • Added support for Child label styles wherever possible.
  • Part Filtering - added ability to filter Structure selection by Depth



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article