PlantSpecDriven has a more modern user interface for the configurations.

When switching the language, the labels for the proxy settings are not updated, but all other labels.

When AttributeFlow gets triggered by copying values through OPC Manager the Port properties won't be updated through AttributeFlow.
 

When inserting an OLET through the PSD Tree, dialog #01269 appears if if it is the correct pipe (line).

This was due to the fact, that PlantSpecDriven always considered the port names starting with S (e.g., S1, S2), but OLETs using D1, D2.

When inserting a flange with no pipe on its port 1 and the flange is connected to another flange, then the inserted flange was not linked to the PID flange symbol. Now the flange will be considered as being inserted in to blank space and then linked.
 

Sometimes it happened, that apparently for no particular reason during some regular function like substituting a PID symbol another drawing became active.

The reason behind it was, that multiple PlantTools listened for changes in the drawing (e.g., changing the size of a line segment) and then the various PlantTools functions had to be processed one at a time. However, PlantSpecDriven didn't have a function to restore the active drawing in case some other PlantTools changed the active drawing).
 

PlantTools now support AutoCAD Plant 3D 2025.

PlantTools support AutoCAD Plant 3D 2020 - 2025 now.

Updated DevExpress controls and tools to version 23.2.6 in all PlantTools.
 

The reducer symbol in the tree is oriented in a way to show whether it reduced or expands.

P&ID Fasteners such as Gaskets weren't linked to their 3D counter parts anymore.
 

Sometimes the P&ID Fasteners were linked to the wrong counter parts.
 

When changing size or spec on a line segment connected to another drawing, then the dialog asking about whether to propagate the data appeared, but then nothing happened. The connected drawing wasn't opened.

This is also in combination with PlantExpressTools OPC Manager.
 

When selecting the option to Open, Propagate, and Close the connected drawing after AttributeFlow did its job, the drawing stayed open.

This is also in combination with PlantExpressTools OPC Manager.
 

PlantExpressTools and PlantSpecDriven created an ACPlantTools folder in the documents folder.
 

All functions which opened drawings (e.g., Zoom onto P&ID Symbol, or Copy P&ID to 3D in the Inconsistency Palette) are not downloading or checking out the drawings before opening them.

What is missing are the function in PlantSpecDriven which change the project setup (creation of properties) and pipe specs (adding missing properties which are used in the configuration)
 

When retrieving information from the registry about the installed version we disregard ACAD versions which the installed PT don’t support.

E.g. a customer has 2025 installed, but the installed PTs support only 2019-2024.
 

There is a new setting for PlantSpecDriven to be able to suppress the AttributeFlow notification when opening a drawing. This is sometimes used when for example making a bulk import of data changes with Data Manager or PlantDataManager and the AttributeFlow task is not supposed to open and ask for every drawing.

If you check the box Do not show this dialog again when opening a drawing and then click on either Run AttributeFlow or Close, the tasks will either be executed for each following drawing you open, or the will never be executed.

In the PlantSpecDriven settings you can disable the suppression if you want to get the Task Dialog again. You can also switch between Don't run Tasks and Run Tasks.

PlantSpecDriven linked the pipe spec which was selected in the spec driven configuration under the Related Files\ACPlantTools\Spec Sheets.

No this link will be removed because it is confusing since it is already referenced in P3D’s Spec Sheets folder already.
 

The relationship types are stored in a the ACPRelationshipTypes table in the ProcessPower database. This has been changed to be stored in an xml files which is easier to handle for collaboration projects. This new approach will also be used for Non-Collaboration projects.

In certain views there is no single top level node which would allow using e.g. Expand All. Therefore we need the menu also when no node is selected.

This is the case when the DWG nodes are hidden.

There are some use cases where there is the need to still insert Reducers from the PlantSpecDriven tree even if it means it isn’t necessarily the correct Reducer.

We deactivated the Reducer to to the issue, that sometimes the wrong reducer was on the mouse pointer.

The recommended workflow can be seen here Inserting P&ID Reducers and Tees (3D).
 

Is was possible to insert a P&ID symbol from the PlantSpecDriven tree into the wrong Pipe Line Segment.

Now there will be a dialog which asks you how to proceed in such a case. You can Cancel. Then nothing will happen. Or you click OK and the 3D valve which was assigned to the P&ID symbols will be inserted into the wrong line, but it will not be linked.

The Relationship Type which could be extended through PlantDataManager and PlantSpecDriven are now stored under \ACPlantTools\PIDRelationshipTypes.xml and not the ACPRelationshipTypes table in the ProcessPower.dcf. It is also handled for Collaboration projects.
 

An error appeared when trying to copy a value between P&ID and 3D of a Pipe Line Group.

An error appeared when trying to zoom onto a P&ID or 3D Pipe Line Group. The zoom options are deactivated now.

When Autopipe is executed, the default EndType is set to CL instead of FL. This causes the flanges on the fitting to be swapped out. The reason for this is that in the PSD configuration under "Opposing Flanges", CL is defined before FL under "Symbol end types that need a flange". The default is then set to CL in the code because it is queried alphabetically.

If PlantTools download/check out, check in, or remove one of its configuration files we now show a progress panel with the file name and path to see which file is handled.

The PlantSepcDriven was finally updated. In addition you will find Sample project for metric, imperial and mixed-metric projects.
 

When using the AttributeFlow Task List the xml file with the pending tasks will be handled also when using Collaboration projects. This also includes handling of the AttributeFlow through OPC Manager in PlantExpressToools.

PlantTools for Collaboration projects are available only for AutoCAD Plant 3D 2023 or higher. This is due to the fact, that the API PlantTools rely on were improved in 2023.

Some functions may still work, but it is not supported. Make sure you install Plant 3D 2023 or higher.

We introduced a new method where the reducer isn’t required to be inserted separately. Instead the user draws the second line segment and Plant 3D automatically inserts the 3D reducer. PlantSpecDriven will then link the 3D reducer automatically with the P&ID reducer.
 

We introduced a new method where the tee isn’t required to be inserted separately. Instead the user draws the second (branch) line segment and Plant 3D automatically inserts the 3D reducer. PlantSpecDriven will then link the 3D tee automatically with the P&ID tee.
 

This new option allows zooming onto an object which is xrefered into the active drawing.

Before PlantSpecDriven zoomed onto the 3D object in the drawing on object originates from.
 

PlantSpecDriven doesn't require to open the P&ID drawing anymore when routing or inserting a line segment or symbol from the PlantSpecDrivern tree.

The only exceptions are the connection between the flanges in 3D and the flanges in P&ID. If you don't use the AutoPipe option of PlantSpecDriven, then this doesn't concern you.
 

When PlantSpecDriven was used with the AutoPipe function for example to insert flange symbols for a flanged valve, then using the space or return key put the last inserted symbol (which was the flange) on the mouse, but not the previously selected valve symbol.

Now the inserted symbols will stay on the mouse (auto repeat). With ESC you can terminate the inserting. With Return/Space key you have the symbols on your mouse again.
 

When using Zoom onto 3D object from the context menhu of a PID PipeLineSegment node, then all linked objects are considered.
 

When using a mixed-metric project where the P&ID uses inch (e.g. 4”), but the pipe spec used mm, then PlantSpecDriven doesn’t find any catalog data.
 

When manually linking a P&D line segment to one or more 3D pipes (they are the representatives for the P&ID line segments), then the P&ID Line Group is not linked to the 3D Line Group.

Additionally, you can now unlink the 3D Line Group from the P&ID Line Group with the context menu of the P&ID Line Group.
 

With the new Data Grid control of DevExpress (see PT-2211 above) you can now also multi-select rows to execute the same function.
 

With the new Data Grid control of DevExpress (see PT-2211 above) any fitlers and sorting will be stored when closing the Inconsistency Palette and will be restored when opening the Palette again. When changing to another project the stored settings will be deleted.
 

These is now a Expand All and Collapse All menu item in PlantSepcDriven tree's context menu.
 

The Part Selector dialog only shows the port property columns which are needed for the part. In the example below you see that Nominal Diameter 2 and End Type 2 are hidden.

The column header use the localized display names now.

When using Imerpial or Mixed-Metric projects, the size columns in the Part Selector dialog will show imperial units instead of decimal formatting (e.g. 2.5).

When routing a P&ID Line Segment in 3D only the pipes where linked with the P&ID Line Segment. Now the Elbows are linked as well.
 

With PlantTools version 6.0.0.2267 (first support for Plant 3D 2023) we linked the PlantTools files (located under [PROJECT]\ACPlantTools) into the MISC.dcf database so the PlantTools files appear under the Related Files folder in Project Manager. However, this cause a problem with Vault projects when we started to check in/out/download the PlantTools files for Collaboration projects in later versions.

Now the PlantTools files are still linked into the MISC.dcf, but they are not checked in/out/downloaded anymore if current project is using Vault.

You can now just copy PlantTools files from another project or template project into your Vault project and open the project in Plant 3D again. Alternatively, you can follow the Workflow with Vault and PlantTools.
 

When switching between AutoCAD Workspaces the PlantTools palettes weren't restored to the previous setting. For example, if a palette was open before, it may be closed after the switch. Now the palettes will be opened again if they were open before.

This applies to the following Palettes:

1.PlantSpecDriven Tree

2.PlantSpecDriven - Inconsistency

3.PlantDataManager Plugin - Data Import

4.PlantExpressTools - PlantProjectManager

5.PlantExpressTools - PropertiesPalette

6.PlantExpressTools - SymbolsPalette
 

Especially with pump nozzles it was often impossible to link a P&ID nozzle to the correct 3D nozzle.
 

We replaced the grid control of the Inconsistency Palette with the grid control of DevExpress (also used in PlantDataManager or PlantLink). This way there are more options for grouping and filtering.
 

If the user wanted to link a 3D pipe with a P&ID Line Segment which is already linked to other 3D pipes, then the option Link with 3D object was disabled and the additional pipe(s) couldn't be linked anymore. Now Link with 3D object will stay enabled.
 

The images for the PlantSpecDriven tree where previously installed under C:\ProgramData\ACPlant Consult\PlantTools\General\ClassImages, Now the files are included in the C:\ProgramData\ACPlant Consult\PlantTools\General\Libraries\AqaPlantToolResources.5.0.dll with all the other texts and images.
 

The texts in the Wizard have been changed.

The texts in the Inconsistencies context menu have been changed.

The setting for Different Values in the AttributeFlow settings was ignored and the property values were always propagated between connected line segments.

Connected lines are line segments which belong to the same line group and where the start and end points of two line segments are connected.

The Property Mismatch dialog didn't always use the localized display names.

In the dialog where you can define the condition for Fasteners, parts of the info texts were missing.

The label on page 14 of the PlantSpecDriven Wizard wasn't added to the resources. That resulted in an untranslated text when setting PlantTools to German.

When deleting a segment breaker symbol like a reducer...

... and the property of the other line segment of the segment breaker symbol changes...

...then the property value will not only be propagated to the immediately connected line segment, but will also be propagated down the line and branches.

In this example the 100 will not only flow to the right line segment, but also to the branch.

When inserting symbols (e.g. Flanges, Tees) PlantSpecDriven assumed, that the class name was also the symbol name. Now PlantSpecDriven uses the real symbols name.
 

When inserting an InlineAsset/InlineInstrument into a line segment which has a Gap created with SLEDIT an error appeared.

When using Assign Tag on a line segment with a Gap an error appeared.
 

Depending of a P&ID reducer is size1 larger than size2 or vice versa, inserting a reducer can fail when inserted from the PlantSpecDriven tree into the 3D model.

We now changed the workflow completely. Instead of inserting the reducer separately, you now simple start routing with the next line segment. Plant 3D will then insert the reducer automatically. We then link the 3D reducer with the P&ID reducer.
 

When Copying between P&ID and 3D sometime an error appeared.

.

When creating a new project using the Project Manager function, then Plant 3D will create a second ACPlantTools folder.

We provide a function which removes the unneeded ACPlantTools folder. Use the following command:

AQAPTRemoveDuplicateACPlantToolsFolder
 

We forgot to update the new digital certificate in the Setup.exe and Update.exe. This is necessary to let Windows and AutoCAD know, that our files are trustworthy.
 

For Collaboration projects we need to know which PlantTools settings files still need to be downloaded in case they don't yet exist locally.
 

We watch PlantTools folder and configuration files in order to recognize changes (made by another user) in those folders and files. If files change, we need to invalidate the cached PlantTools settings in the Plant 3D session to ensure, the PlantTools use the latest settings.
 

To add an existing configuration file you can now use the Import button. This will will then be copied into the appropriate PlantTools folder, will be added to the collection file and if it is a Collaboration project, the configuration will also be checked in.

When using the Refresh button we check if all configuration files are also listed in the Collection file and if not, we added the missing configuration files.

Now the configuration files which are not in the Collection file will be deleted.

In case you want to add a existing configuration file you can now use the Import button.

The SpecDrivenLinkConfiguration.Collection.xml was saved even if no changes were made (added or removed PlantSpecDriven Configurations).
 

PlantTools now support AutoCAD Plant 3D 2024.

PlantTools support AutoCAD Plant 3D 2019 - 2024 now.
 

We updated DevExpress controls and tools to the latest version 22.2.5 in all PlantTools.
 

The Log files are written into the %programdata%\ACPlant Consult\PlantTools\Log folder.

Existing log files will be moved from the old folder to the new folder.

For convenience there is a folder junction in the old location %appdata%\ACPlant Consult\PlantTools\Log

Up until PlantSpecDriven 6.0.1.2318 inserting 3D Relief Valve through the PlantSpecDriven tree worked. But when starting to use 6.1.0.2575 it fails.

Since a Relief Valve is a segment breaker in PID, using a Relief Valve creates 2 Line Segments where the Relief Valve is showing up under the outgoing Line Segment. When transitioning the two Line Segments with the Relief Valve to 3D, the flanges and gaskets weren't linked to their PID counterparts.
 

AutoPipe isn't executed on drawing save if one of the options (flanges and/or branch symbols) is check.

Full integration of PlantSpecDriven and its configuration files for Collaboration projects.
 

As part of the strategy to move all PlantTools settings into PlantProjectSetup, we started moving the common settings Language, DevExpress Skin, Update Check, and Proxy Settings into PlantProjectSetup and make it accessible through all Desktop PlantTools (PC, PDM, PR) and Plugins (PCD, PDM Plugin, PET, PL, PS, PSD).

Details can be found under: PlantProjectSetup
 

As part of the move of the common PlantTools settings (Language, DevExpress Skin, Proxy Settings) we also updated the Update Installer.

Details can be found under: Update Installer
 

As part of the adaptation of PlantTools for collaboration projects, we moved the PlantSpecDriven settings into the project folder under \ACPlantTools\PlantSpecDriven\PlantSpecdriven.xml.

The Syncronize ACP database function isn't needed anymore due to the migration of the ACPProcessPower.dcf in PSD 5.0.0.2090.

PlantSpecDriven checks if the pipe specs and catalogs need additional columns used in the configuration of the SDC file. However, some customers experienced slow performance, because catalogs couldn't be found which delays the loading of the project.

To suppress the check for required columns, the check can be deactivated in the Settings dialog.

Making sure, that the PlantTools ribbons in AutoCAD Plant 3D use the current language.
 

The AutoCAD language code for French Plant 3D wasn't supported in PlantTools. This effected all PlantTools.
 

When trying to insert an InlineAsset or InlineInstrument from the PlantSepcDriven tree, nothing happend. The reason was the use of the quotation character for the Inch unit which was written in a temporary XML file which caused a line like:

<Size Value="4"" />

And with the three quotation characters the function get an error. Which didn't show in the command line, but in the log file.
 

When changing the Tree Settings for the PlantSpecDriven tree in the PaletteSettings and then open the tree settings UI, the UI doesn't use the settings from the PaletteSettings.xml, but from memory of the previously loaded settings.

When changing the configuration in the Wizard of PlantSpecDriven, the changes weren't used right away and a project reload was necessary.
 

The SymbolsPaletteCustomClasses.xml which is used for the PlantExpressTools SymbolsPalette was created by every PlantTool Plugin (PlantClashDetection, PlantDataManager. PlantLink, PlantSpecDriven, PlantSync) and not just be PlantExpressTools.
 

If PlantSpecDriven AND PlantExpressTools are installed, the sdc file name in the SpecDrivenLinkConfiguration.Collection.xml was removed when closing Plant 3D.
 

The AttributeFlowTaskList.xml file is still using PnPIDs instead of PnPGUIDs which is a problem when using Vault or Collaboration projects.
 

When selecting a template pipe spec in the PlantSpecDriven wizard, a backslash was missing when the wizard adapted the path to use variables.

For example, when selecting C:\AutoCAD Plant 3D 2023 Content\CPak DIN\10HC01.pspc

it resulted in [SC]CPak DIN\10HC01.pspc, but it should be [SC]\CPak DIN\10HC01.pspc.

There is a \ missing after [SC].
 

When using ‘Link with 3D Object’ or ‘Unlink from 3D Object’ the change isn’t registered by ACAD and therefore the user isn’t asks to save the drawing when closing the drawing. So when opening the drawing again the PID and 3D objects are still linked/unlinked.

This is actually a sort of bug in the 3D part of Plant 3D, because changing data in P&ID drawings will automatically trigger a change status, but not in 3D.
 

Some files had a wrong path to the Development Express DLLs in the PlantToolsCommon project, which potentially could could error for some controls. However, that apparently never became an issue.
 

We added SC and AD as variables on page 2 of the wizard, but forgot to mention them in the info box.

To avoid issues with different build versions of PlantTools, we now force users to update all installed PlantTools to avoid any issues with shared files between PlantTools.

After installing one PlantTool and not updating others you will see the following dialog which allows you to individually download PlantTools or to download all available updates at once (green arrow).

The updates will be downloaded and stored in the download folder.

After closing the desktop PlantTools (PlantCenter, PlantDataManager, PlantReporter) or closing Plant 3D the downloaded updates will be installed automatically.
 

So far PlantSpecDriven had two options if it comes to find appropriate AutoPipe symbols. Either ‘Use FL end type’ to find symbols. This works ok if users use AutoPipe exclusively for getting flanges. Or ‘Use symbol end type’. In this case AutoPipe uses the EndCode of the symbol (e.g. a valve) to find an appropriate symbol to insert.

Now you can define except EndCodes in the Wizard to let PlantSpecDriven know, that instead of using the Symbol's EndCode to use FL.

At the top you see an example how the symbol looks like. Below you see, that the WF AttachmentPoint1 and 2 get Flanges (this is the selected under 'Except for those'). AttchmentPoint3 and 4 have TC and AutoPipe will search for EndCode TC to find a suitable symbol.

Because AttachmentPoint1 and 2 have WF, AutoPipe is supposed to ignore that and search for FL.

In addition to this new feature we changed the controls, which now allow only the selection of existing EndCodes to avoid Type-Os.

The selection list for the Exceptions shows only the EndCodes selected under 'Symbol end types that need a flange'.

When AutoPipe inserts symbols on AttachmentPoints it can happen, that the Annotation of the symbol breaks a Line Segment which is close by (see green arrow).

Now the Annotation will be mirrored to the other side of the symbol, so the symbol on the other AttachmentPoint can be inserted too.

When line segments are setup to get flow arrows it conflicted with the placement of flanges through AutoPipe.

Now AutoPipe will remove those flow arrows to avoid issues with the placement of the flanges.

The various dropdown lists in PSD’s Wizard are often showing the properties are database fields in the order the were created and not in alphabetical order. Now they show ordered on all pages of the Wizard.

When entering properties in a Line Segment which trigger AutoPipe, then PlantSpecDriven also tries to assign catalog data to the Equipment the Line Segment is connected to.

Now PlantSpecDriven check if a symbol has the Spec property to evaluate whether it gets Catalog Data or not.

When selecting a class with an existing filter expression, the expression was shown only in text mode, but not in visual mode.

When opening a project where the MISC database doesn't exist you get an error.

This applies typically to old projects where the MISC database didn't exists from project creation on. Only when you added files or folders under 'Related Files' was the MISC database created.

The Plugins like PlantClashDetection, PlantDataManager, PlantExpressTools, PlantLink, PlantSpecDriven and PlantSync will create the file on project load.

PlantDataManager and PlantReporter show the following dialog as an info. The project will be loaded anyway.

If you extend the dialog you get information on how to create the MISC database.

When using different flanges in PID...

... PlantSpecDriven will check if the correct flanges are inserted by Plant 3D in 3D. If not, then PlantSepcDriven will substitute to the correct flanges as assigned in PID.

If the folder PnPPersistentCache or its content gets deleted (e.g. by PnPLocalDataCachePurger.exe), an existing AttributeFlow Task Lists gets deleted on project open.

This is due to the fact, that the deletion of the local data cache results in NULL values for connected Off-Page Connectors. Then the IDs in the task list will be marked as invalid (not needed anymore) and the whole task list gets deleted.
 

PlantTools now support AutoCAD Plant 3D 2023.

PlantTools support AutoCAD Plant 3D 2018 - 2023 now.
 

We updated DevExpress controls and tools to the latest version 21.2.6 in all PlantTools.
 

The ACPAssetOwnership table in the ProcessPower.dcf (P&ID Database) isn't needed anymore and therefore will be removed. The relationships stored in that table between Placed Objects and Not-Placed Objects used in PlantSpecDriven as already stored
 

The property in 3D which stored the PnPID of the P&ID object for the link between a 3D object and its P&ID counterpart when using PlantSpecDriven, was changed from using PnPIDs to PlantTools' PET_GUID value as a preparation for BIM360/ACC and Vault projects. We now migrated the PET_GUID value to Plant 3D's own PnPGuid value to ensure a streamlined process when using BIM360/ACC or Vault project.
 

For example, Raster-Design uses relative URIs for the ribbons which caused a FATAL ERROR when hovering over a button in the Raster-Design ribbon.
 

If the Windows user name contains an apostrophe it cause error when PlantTools tried to access one of its databases (PDMDataCache.dcf, ACProject.db, ACPChangeLog.dcf, ACPProcessPower.dcf)
 

Because of duplicate PnPIDs in ACPProcessPower and ProcessPower databases the migration failed.
 

When editing drawing properties in Project Manager or PlantProjectManager it took very long.
 

While migrating ACPProcessPower into ProcessPower it could happen that both databases contain the same PnPID. If this PnPID is used inside relationships it happened that the wrong PnPId (the one from ProcessPower and not the one from ACPProcessPower) got converted.

This resulted in a silent exception and therefore wasn't obvious to the user.
 

The ACPRelationships table can contain owner PnPIDs where the PnPID doesn’t exist (anymore). Those relationships will be ignored, but written into the log file if you see the following dialog:

Not-Place Objects that are not linked to a drawing were ignored while migration of the NPOs from the ACPProcessPower to the ProcessPower database, if this object does not have a relationship.
 

With version 5.0 all PlantTools will be updated to that version. Because of shared resources and code is mandatory that all PlantTools on a machine are updated. If this is not the case the following dialog will appear and lists all the installed PlantTools on a machine and which ones require an update.

The PlantTools with the red arrow require an update. The dialog will appear until all PlantTools are updated to the required version.

The language of PlantTools can be set globally now. In the Plugins (PlantClashDetection, PlantDataManager Plugin, PlantExpressTools, PlantLink, PlantSpecDriven, PlantSync) you can select AutoCAD, English, or German. AutoCAD tells the PlantTools to use the AutoCAD language. If you change the setting, the PlantTools Plugins will change the language of the user interfaces and ribbons instantly.

If you select English or German in the Plugins, the Desktop Apps (PlantCenter, PlantDataManager, PlantReporter, MigrationTools and PlantProjectCreate will use this language.

If you select a language in one of the Desktop App Settings, all Desktop Apps will use this language and not the AutoCAD language.

The ACPProcessPower.dcf database hosted the Not-Placed Objects (NPOs) which were created by PlantSpecDriven or PlantDataManager, and also used by PlantReporter.

The NPOs will now be stored in the ProcessPower.dcf (P&ID database) directly. This applies to SQL Server projects as well.

The advantage is, that when using Vault or ACC/BIM projects, those NPOs will also be check in/out.

The first time you open a project PDM, PDM-Plugin, PET, PL, PR, or PSD will migrated an existing ACPProjectPower.dcf and its content into PID's ProcessPower.dcf.

If you are updating any of the following PlantTools (PlantDataManager, PlantExpressTools, PlantLink, PlantReporter, PlantSpecDriven) you MUST make sure, that the other PlantTools you have installed are also updated to version 5.0.0.x.
 

Since it is possible to create multi-connections of OPCs (1:n, n:1) with PlantExpressTools' OPC Manager, PlantSpecDriven must be able to support AttributeFlow also for these cases.
 

There can be cases, where the pipe spec file in your project isn't valid anymore (e.g. file size of 0 KB). in this case we show th following dialog which can then be suppressed.

When trying to execute AutoPipe from the drawing or pipe line group node in the PSD tree or the context menu of the line segment PlantSpecDriven->AutoPipe PipeLineGroup AutoPipe wasn't executed. This happened when there was no definition for Branch Symbols.

When having multiple PlantTools Plugins (PlantClashDetection, PlantDataManager Plugin, PlantExpressTools, PlantLink, PlantSpecDriven, PlantSync) installed and they are set for different languages then Plant 3D crashed if the tooltips for the PlantTools ribbon buttons are supposed to be shown.
 

When using 'All 3Ds' or 'Project' or 'Current Drawing' views for the PlantSpecDriven tree, you either got an error message or an empty tree.

In some PlantTools the URL to the online documentation pointed to the old location.
 

When opening a drawing one of the two error messages appeared.

Before:

After:

Part of the AttributeFlow is the ability to write property values of the connected line segments into the (port) properties of the Inline Assets. This worked correctly till version 4.0.0.1441. After that, the number of connected line segments didn't match the number of ports of the symbols which left some port properties empty.

Before:

After (Port 3 properties are empty):

Now it works again.
 

When opening a drawing one of the two error messages appeared.

This was an unexpected return value to out code which creates the GUIDs for the PET_GUID property when opening a drawing.
 

PlantSpecDriven is now supporting the use of the InlineInstruments class in P&ID as well.

In addition to selecting 'Inline Assets' class, you can now add the 'Inline Instruments' class. The properties which are used by the Wizard on the following pages, will be automatically be created also for the 'Inline Instruments' class.

Line Segments which are separated by reducers or other segment breaker symbols, will be ordered according to their flow direction. Also Inline Assets and Inline Instruments will be ordered according to the order they are placed on a line segment.

Here is an example of line segments separated by a reducer.

And here is an example of Inline Assets and Inline Instruments being in order of the flow.

In the PSD Tree Settings you will find a new checkbox where you can disable the flow order to get the previous order.

Up until now, PlantSpecDriven stored the PnPID of the PID symbol in the corresponding 3D object to link them. As a preparation for having PlantSpecDriven work with Vault and BIM360 projects, it was necessary to switch to a GUID based link, because when checking drawing in the PnPIDs of objects can change which breaks the link between PID symbol and 3D object. Existing PnPIDs in the 3D object will be migrated automatically.
 

Up until now, PlantSpecDriven used the PnPID of the PID symbol to link NPO (Not-Plaved Objects) like Gaskets, StubEnds to the PID symbol. As a preparation for having PlantSpecDriven work with Vault and BIM360 projects, it was necessary to switch to a GUID based link, because when checking drawing in the PnPIDs of objects can change which breaks the link between PID symbol and NPO object. Existing PnPIDs in the ACPProcessPower database will be migrated automatically.
 

Up until now, only the PlantExpressTools Change Log function created an additional property "PET_GUID". Since more and more PlantTools and functions require this property, the property will now be created on project load if it doesn't exist yet.

It will be created for all 'Base Classes' like Pipe Line Group, Signal Line Group, Engineering Items, and Non Engineering Items. It will now also be created for 3D (P3d Line Group, Piping and Equipment, Steel Structure, and Pulled Pipe Bend.

The PET_GUID will be filled (if empty) on drawing load.

The PET_GUID will also be filled right away as soon as an object is created. In addition of filling the PET_GUID with a new value if PET_GUID is empty, there are two rules which apply:

1.Copying (copy, array, mirror, CTRL+C/CTRL+V, using grips for copying, and more)
The copied objects will get a new PET_GUID because not two objects can have the same GUID.

2.Move (move, using grips for moving, rotate, CTRL+X/CTRL+V, and more)
The moved objects will keep their GUID.

The two rules apply also when copying and moving between drawings.
 

Sometimes the wizard opened always in the upper left hand corner of the screen. We now store the location of the wizard and restore this position when the wizard is opened again.
 

If the SymbolStyleName in project Setup isn't set. The dialog will not appear anymore if the symbolStyleName is null.

If a filter is set for PipeLineSegments in the Tree Settings (e.g. filtering PipeLineSegments with Size less or equal than 50)...

And you then clicked on the filter toggle button Plant 3D froze and eventually crashed.

In some instances it was possible, that the PlantSpecDriven tree didn't show all nodes, because it ran into end endless loop.
 

When having only PlantSpecDriven installed, then the following error appears multiple times when closing Plant 3D.

Because of localization issues, sometimes the Class Property for the Part Family Check wasn't displayed even if it was selected and stored in the sdc file.

The Spec property from page 5 of the Wizard is also localized now.

The Inconsistency check indicated inconsistencies, because the sizes in P&ID and 3D weren't handled properly.

For example, In P&ID a Reducer can show 100x80 or 80x100 depending on the direction of the symbol. In 3D however, the Reducer always shows 100x80. If the P&ID reducer shows 80x100 and 3D showed 100x80 it led to an inconsistency.
 

Various dialogs which appear when PlantSpecDriven wants to assign catalog data or insert connecting objects (e.g. flanges) through AutoPipe can be suppressed now.

The reason behind all the suppressible dialog is, that some customers want to use PlantSpecDriven with a different workflow, where the designer is not supposed to be interrupted by dialogs when drawing.

The dialog which appears if PlantSpecDriven finds multiple suitable records in the pipe spec can be suppressed now.

The dialog which appears if PlantSpecDriven wants to insert Default Flanges can be suppressed now.

The dialog which appears if PlantSpecDriven cannot find a suitable record in the pipe spec can be suppressed now.

The dialog which appears if the spec property is empty in the line segment can be suppressed now.

When installing PlantCenter, PlantDataManager, PlantReporter on a PC a a dialog informed the user about denied access when starting the PlantTools from the Desktop. PlantClashDetection, PlantLink, PlantSync, PlantSpecDriven had to be activated everytime Plant 3D was started, because the registration information couldn't be written either. This happened only when installing the PlantTool for the first time or after uninstalling previous installations. desktop shortcut.

When switching between work spaces Plant 3D gets very slow all of a sudden. Also the memory consumption increases. For example when switching between "3D Piping" and "PID ISO" 10 times. In Task Manager you can see "Not responding". Eventually Plant will react and you can close it.

It looks like this:

If PCD, PDM Plugin, PET, PL, PS and PSD cannot acquire a network license when Plant 3D starts, the performance became very slow. This was due to the fact, that these PlantTools Plugins checked for a network license multiple times a second.

If no network license was available you get the next two dialogs.

Now these PlantTools check just on startup.

The dropwown list of previous fitler expressions didn't include the previous expressions.

When entering a filter expression the the PlantSpecDriven palette, the filtering was executed only on the second try.

When routing a branch with a different line number (Line Group) than the main line, the main line got the line number of the branch line. This all lead to wrong connections and inconsistencies.

Sometimes the following dialog appears when saving a drawing in a project using PlantSpecDriven:

Those errors are triggeres by Plant 3D and it is hard to catch them. We checked the code to catch more of those exceptions.
 

When using AutoPipe with PlantSpecDriven and the P&ID Symbol property isn't set in the SDC file, you get a warning now.

In addition you see a warning in the PSD main dialog.

If AutoPipe is enabled and "P&ID symbol property" isn't selected, you cannot use "Next" to jump to the next page.

If it is filled out the "Next" button will be enabled.

When changing the "Update Type" in the wizard and then clicking in another row, the change setting will be reverted to the previous setting.

We now support AutoCAD Plant 3D 2022.

The new "Project Compare" is included in PlantProjectManager also.
 

PlantTools trigger the "Update License" check of the network license in auxaliaLicenseServer service on your server.

auxaliaLicenseServer is checking the license every 15 min to ensure, that your license information (e.g. number of license, expiration dates) are updated automatically without your need for involvement.

There is no need to keep the auxaliaLicenseManager open.

If a PlantTools is started and it finds an older CADSTUDIOLicenseManager or auxaliaLicenseManager installed on the server, the following dialog shows up.

You can decide when you want to be reminded again. The maximum is 2 weeks. After that, you will have a maximum of another week, then another 4 days and so on. That gives you a grace period of 4 weeks till auxaliaLicenseManager must be updated. If you don't do this, you will be reminded every time the PlantTools is asking for a license.
 

The PlantSpecDriven tree can now also use auto-filtering to search for nodes in the tree.

Just type in the value and press return.

Since it may take a while to filter the tree, we show a Progress Panel so you see what is happening.

Using longer filter strings works fast.
 

We updated DevExpress controls and tools to the latest version 20.2.6 in all PlantTools.
 

We discontinue the support for AutoCAD P&ID 2016/2017 and AutoCAD Plant 3D 2016/2017.

Typically we only removed only one version when adding the newest AutoCAD Plant 3D version, but since hardly any customer is using AutoCAD P&ID 2017 or AutoCAD Plant 3D 2017 anymore we decided to cut off the two oldest versions. Another argument was, that there is no migration needed between 2018 and 2022 which makes it more convenient for customers t use those newer versions.
 

PlantTools will run run 14 days in trial period before they stop working.

Several dialogs informing about anything related to licensing (expiration dates, rental dates, issues with activation and more) have been improved to make it clearer what the dialog is all about.
 

The images for the Part Selection and AutoPipe dialogs are now read directly from the Plant 3D content folder's metadata.zip.

The setup of PlantSpecDriven will not install those images anymore and existing images will be removed from: C:\ProgramData\ACPlant Consult\PlantTools\General\Images.

We started to put more information in our Message Boxes to give you more background details to reduce support questions or the need to look into the online documentation.

Also, all dialog boxes have a number which helps with support.

When using F1 in PlantCenter, PlantDataManager, PlantReporter, MigrationTool, PlantCenter or any button in the PlantTools or PlantExpressTools ribbon we open our own browser window.

When NPOs (e.g. gaskets) are inserted and then the user opens the PSD Main Form, any new NPOs inserted after that, well not be stored.
 

When enabling "Insert Branch Symbols on Drawing Save" no Branch Symbols (e.g. Tees) weren't inserted in existing branch connections. Only after restarting Plant 3D were the Branch Symbols inserted.

When inserting a symbol the "No catalog data found" dialog appeared twice.

After PlantProjectSetup has been entered and closed again, the style of the "Update Bolt Calculation" dialog had the wrong style and looked like this:

Now it looks as it is supposed to:

When "Run AutoPipe on drawing save (Flanges only)" is deactivated, then missing flanges won't be inserted when trying to use AutoPipe from the PlantSpecDriven tree or the context menu of the Pipe Line Segment.

This happened if the settings of PlantSpecDriven have the insertion of branch symbols enabled, but no branch symbols were needed. In this case missing flanges weren't inserted either.

When the branch symbol is inserted, the flow arrows appear only when running AutoPipe a second time.

This is how it looks after the first saving:

Here the branch symbol in more detail:

The following dialog didn't have a title.

When having FlowArrows for PipeLineSegments enabled, the auto-inserted Branch Symbols (AutoPipe) didn't work correctly

When using a LISP function in a tool palette and having branch symbols inserted on drawing save, the LISP function was call again after saving the drawing.

When inserting a branch symbols manually, the following message appeared.

When saving a drawing sometimes the following message appeared.

[PlantSpecDriven] Value cannot be null.
Parameter name: key
 

This was ordered by a customer who needs a symbol which is automatically inserted so calculations can be done on the symbol.

Another use case are automatically inserted Tees.

In the PSD Wizard you can define the classes which should be considered.

You must define the condition under which the symbol is supposed to be inserted.

Lastly, there is a checkbox which checks and inserts missing branch symbols OnDrawingSave.

When there is no spec value in the PipeLineSegment/InlineAsset you will now get this modified dialog. You can choose to suppress it for future cases.

If you want to turn it back on again you can do so in the PSD settings.

When routning a P&ID PipeLineSegment in 3D, the P&ID PipeLineGroup wasn't linked to the 3D PipeLineGroup.