This version seems slower than previous versions when to access the back stage or recent files. Perhaps a 1-2 sec delay. This should be instantaneous!!
Max place a # in front of this variable and restart CE. see if the speed improves, if not remove the #
Thanks Ian - can't say there's an improvement.
From explorer, using right click> Open with>testfile.dgn...
CE (10.09.00.23) takes 26 seconds to open a file.
v8i (08.11.09.829) takes 16 seconds to open the file (and all commands/ functions/ features, now buried in a laggy CE backstage, are instantly available in V8i).
When CE7 or 8 was released Bentley included a new variable called
MS_WORKSETMISMATCH_ALERT_EXCLUDE_VARS_ALLLEVEL
This variable is set at the system level so its not one that is obvious. However, this variable does or did have an impact of the speed of CE (CE( should have it fixed)
With this new variable there are several switches that are set by default;
MS_CELLOUT;MS_CELL;MS_CELLLIST;MS_DGNLIBLIST;MS_DEF;MS_DGNLIBLIST_CLASH;MS_DGNLIBLIST_LINKS;MS_DGNLIBLIST_PRINTING;MS_DGNLIBLIST_RENDER;MS_GUIDGNLIBLIST;MS_SEEDFILES
The switch that I have discovered to be directly related to speed is the switch MS_DEF.
So I now set this variable at the Organization level and define it as;
MS_WORKSETMISMATCH_ALERT_EXCLUDE_VARS_ALLLEVEL = MS_CELLOUT;MS_CELL;MS_CELLLIST;MS_DGNLIBLIST;MS_DGNLIBLIST_CLASH;MS_DGNLIBLIST_LINKS;MS_DGNLIBLIST_PRINTING;MS_DGNLIBLIST_RENDER;MS_GUIDGNLIBLIST;MS_SEEDFILES
ie the MS_DEF has been removed.
Give it a try and see what you think
Ian
Ian/Max,
The MS_CELLLIST Variable has a small impact on speed, depending on how many/how large cell libraries you have. The more/larger, the slower. (I set this primarily to list cell libraries in the cell manager drop downs and also is required if setting any cells to standards or tools)
The properties window actually has the greatest impact. Close down properties and open cell libraries, they are now as fast as V8.
Ian,
What is his (hidden)variable supposed to achieve. From it's name it would suggest something if you are opening a file in the wrong workset, so if opening a file in the correct workset, surely it should have no effect?
Anyway, nice to see us users trying to solve bentleys problems, again...
Duncan
True, but if you were to scan the files being access on CE startup, the paths are being reviewed and need to be processed. The one that was a shock was MS_DEF.