RE: Family Table Driven and will use pre-Wildfire3 replace functionality?
Here is a little more "meat" regarding this topic.
In WF 3.0 we merged two different replace "engines" (that had different pros and cons) into a combined "engine". This was done to resolve a number of technical issues that had lead to SPR's. The result is stable replacements and consistency.
However, because we don't want to rev bump existing models, we are NOT converting legacy data automatically. The config (although it has a somewhat misleading description) does not either facilitate an automatic conversion of the componentsonce set to the value "Yes" as this would "bump the assembly). The config will make the "Update" RMB command available enabling a user to manually update the models component placement feature to the new replace method.
Note 1. If you have not had any instability issues with the replacement there is really no reason to convert.
Note 2. A new replacement (in WF 3.0 or later) will automatically "convert" the component to the new replace method. For those wanting more information about the replace changes, I have attached a file describing these changes.
Below please also find some more info I copied from the WF 3.0 help center.
About Component Replacement and Legacy DesignsLegacy designs (pre Wildfire 3.0) containing family table replacement functionality, must be manually updated to Wildfire 3.0 replacement functionality.
Because packaged components are automatically replaced when updating a legacy design, all instances are also updated, including those in which the component being replaced is a packaged component.
To update to Wildfire 3.0:
Set the convert_to_wf3_replace configuration option to yes.
Update the generic design to use Wildfire 3.0 replace functionality: