Dear Peter,
Thank you for your patience.
The development team are analysing your issue REVIT-115510 [different result setting CropBox for a 3D view with Revit 2018 -- 13049014] and say so far:
- This may be a side effect to the adjustments made in January 2016 which were not seen by users until 2018 released.
I hope we can find a workaround or advice for Peter regarding what setting produces the effect he wants, and perhaps we need to add some API coverage for different scenarios.
- From a UI behaviour perspective, I don't see a different in behaviour between 2017 and 2018 (when I run the embedded macro).
We will need to assess this issue.
Can you provide more detailed information on the difference in behaviour between 2017 and 2018 that I can pass on to them to clarify the problem?
Remember that the development team does not have an add-in development environment at hand, or RevitLookup installed.
Maybe your macro could include a couple of lines of code to print out the problematic values and ensure that they are not overlooked.
Thank you!
Cheers,
Jeremy