At this moment , I am free of working load, so I am happy to eleborate each topic in a bit of detail.
First let's begin on the uniting Hyperlynx DRC and Hyperlynx:
1 whatever you do DRC check or do simulation, first thing you need to translate you CAD database first.
This is common task for both HyperlynxDRC and Hyperlynx
2 after importing CAD database, you shoud do some setting for models or modifcations on stackup.
This is common task for both HyperlynxDRC and Hyperlynx
3 as you mentioned that Hyperlynx 9.3 now use Hyperlynx DRC to find similiar 3D areas automaticaly.
Why user have to run install and run a seperated applicaiton to find 3D areas?
So uniting Hyperlynx and Hyperlynx DRC can make this type of simulation more easy and in a straight way,isn' it?
4 a hiearchy tree for objects(contraints/netlcass/parts etc) make navigation of object more easy and fast.
Hyperynx do not support a hiearchy tree( and I have posted an idea for hiearchy object tree in Hyperlynx), but HyperlynxDRC do have hierachy tree.
5 to run batch simulaiton overnight, you need the scripts to support to setting models, selection nets and produce reports etc. For all of that, you ned the tool
have the APIs to make work done automaticallty.
Because Hyperlynx have rich APIs than Hyperlynx, so uniting Hyperlynx and HyperlynxDRC make it possible to run batch simulation by scripts.
So, uniting HyperlynxDRC and Hyperlynx provide much advatages for users and Mentor graphcis(saving your R/d resources). isn't It?
yanfeng