Having installed MX SS3 I now have to go back and work on a project that was initially developed in SS2 and all input file based. The cross sections are generated by a command macro provided by the local road authority (who are still on SS2) and that has worked fine up until now. When using it in SS3 some unusual things start happening, including:
What should be the first section on the second sheet is placed as the last section on the last sheet;
If I set dpf pages to single drawing as multiple sheet models trying to go to the start or end of the sheets (with the pages toolbar) leads to crashes and even just changing sheets can sometimes crash. If dpf pages are set to separate drawings it is much more stable.
Anyone else had any issues with draw commands / macros in SS3?
This behaviour isn't one I can repeat here. Can you tell me what seed files are set in the File Management tab of the MX Configuration panel.
Hi Jason, sorry for the delay responding. Seed files are as shown in the screen capture in the attached zip file. I have also included dpf & dgn cross section files generated using the same code in both SS2 and SS3. The dpf files appear similar (although a check with UltraCompare suggests they are certainly not identical) but the dgn are significantly different in size. Opening the dgn's in uStn SS3 (08.11.09.397) the MX SS2 generated version provides access to all 7 pages, whereas the MX SS3 version seems stuck on Page 2. Although the other sheets are listed as models. Assuming MX Draw code is first written to the dpf and then to the dgn it appears to me that something has changed in the dgn writing process between SS2 and SS3.
There is a known issue in MX v8i SS3 where dpf pages set to single drawing as multiple sheet models page 1 of the cross sections won't load, it only shows page 2 onwards. Using dpf pages set to separate drawings is recommended for now. When you get a crash are you seeing an error message?
In MX v8i SS3 the dgn is set as the priority file over the dpw/dpf so that may account for the changes you are seeing.
Answer Verified By: Grant Stewart
No error message but Bentley pop-up to send error log back to Bentley (which I have on a nuber of occassions). Have reverted to using SS2 for belting out the section sheets for now. Trust the "known issue" will addressed in the next release.
Has this issue been resolved? One of our plan presentation macros relies on the x sections being separate pages in one dgn. Running build 08.11.09.494 and still have this problem.