question

What hardware are they using? A better graphics card might improve things - maybe Phil can tell us if a Quadro class would help with drawing so many line segments.

I would recommend putting the paths and control points inside a number of planes/containers and then you can set those as the viewfocus and only see the objects inside the plane - allowing you have good draw speed and edit the layout easily. (right click the plane and select View->Down). You can store the container view in Model Views as you would any other viewpoint.

You could also maybe build a number of smaller models containing just sections at the correct locations (based on a large CAD layout that is in the same position in each model) and then merge or reconstruct it in the main model by transferring the definition either through xml model maps and files or using the Properties tables. This way you can disable the drawing of the AGV nework in the main model entirely (except maybe to check the merge/reconstruction worked).

Here's an example of using properties - this works in a small test model, but it should scale well.

To record the definition:

Table.query("SELECT * FROM Objects()").cloneTo(Table("ModelDefinition"));
Table("ModelDefinition").deleteCol(1);  //Object
Table.query("DELETE FROM ModelDefinition WHERE Name='AGVNetwork'");
Table.query("DELETE FROM ModelDefinition WHERE Name='FlexsimModelFloor'");
// maybe remove records of other 'system' objects like the ConveyorSystem etc.

Then after loading the definition table(s) into the main model, build it using:

Table t=Table("ModelDefinition");
string headerString="(";
string comma="";
for (int n=1;n<=t.numCols;n++){
    headerString+=comma+t.getColHeader(n);
    comma=",";
}
headerString+=") ";
Table.query("INSERT INTO Objects() "+headerString+" SELECT * FROM ModelDefinition");

At the moment this doesn't seem to preserve the connection types between control points or to fixed resources, but they could be read into a different table, and reconstructed as part of the script.

Test model attached.

SQLstore_rebuild_model.fsm