![]() New Feature - Bolex Log and Bolex Wide Gamut.New Feature - RED Gamma 1 and RED Gamma 2 using data from.Bugfix - Gamut Limiter tool was blocking LUT generation.Bugfix - Fixed Javascript policies which stopped LUTCalc working on Internet Explorer / Edge browser.Feature Change - Improved interpretation of Canon EOS Standard and Normal gammas.Feature Change / Bugfix - Extensive rewrite of 'Custom Colour Space' code.Feature Change - New code for estimating the gamut triangle on the 'xy / uv chromacity' preview.Feature Change - Reworked 1D interpolation code for speed and efficiency.Feature Change - Extensive rewrite of LUTAnalyst code for improved accuracy.Feature Change - Complete rewrite of 3D interpolation / extrapolation code for efficiency, accuracy, clarity and maintainability.New Feature - Custom Colour Space can now set primaries from a matrix and white point / illuminant.New Feature - 'DaVinci Resolve 12+ auto' preset option, to reflect that Resolve 12's default 'auto' clip range setting.Where LUTs appear to have been clamped (ie the maximum output value is exactly 1.0 and or the minimum exactly 0.0), the declip process will attempt to extrapolate the clipped values, then limit them within a sensible range without hard clipping. New Feature - 'Declip' button on the LUTAnalyst tool.Clicking it creates a LUT title containing input and output gamma and gamut details, plus basic info of customisation (currently black level and saturation). New Feature - Sony Standard Gammas STD 1-6.New Feature - P3 Colourspace now available with DCI, D60 and D65 white points.Legalises colours and fixes potential LUT overshoots when going from a wide Gamut such as S-Gamut3 to a narrow one such as Rec709. New Feature - Completely new gamut limiter algorithm and code.New Feature - Choice of tricubic, tetrahedral and trilinear interpolation for analysis and use in LUTAnalyst.Its BoundingBox worked well but I still don’t know how to collect all of them. I thought it should be simpler because I used Select Model Element to pick that “Unknown” element as the outmost frame. ![]() # View.CropBox returns a boundingboxXYZ, converting them to Dynamo Geometry, ToProtoType() Method ![]() # Unwrap views to make it work with Revit API # RevitNodes, ToDSType method, Geometry conversionĬlr.ImportExtensions(Revit.Geometr圜onversion) I am getting most of the information from the sdk 2018 here ( )įrom import *įrom RevitServices.Persistence import DocumentManagerįrom RevitServices.Transactions import TransactionManager I am right now trying understand how to use the ‘getcurvesinview’ command for the grids correctly. For all other grids we reduce the the points by a certain distance (Magic No.) using the extend and trim curve by distance option. If the X,Y of the points coincide we filter out those grids cause they are not being trimmed in view. Also get the default 3D start point and end point of the same Grids. Use GetCurvesInView to get the start point and end points of the Grids in the view. Since from Revit 2016, the Grid class provides the methods GetCurvesInView and `SetCurveInView. Also the intersection when eventually done for some 700 sheets is going to be very task intensive so I was thinking of other ways to deal with the same issue. Hi Jeff, I was having issues with intersection and getting the exact cropbox aswell. ![]() Have not tested it though, I hope nothing goes wrong when it comes to batch process. dyn just operate on a single view, the next step is to propagate it to all views / viewports on sheets. So the “0.9” theory still holds true for the rest of views. It makes sure that grids on other views still “remain unsolved” instead of having a new length due to the changes in current view. Getting the original curves from GetCurvesInView(), shrinking it with the difference.Ībout SetCurveInView(), DatumExtentType.ViewSpecific is another key to this case since I think as long as it is ViewSpecific, change happend in the current view won’t affect other views. So I just use dynamo to calculate the difference between the orginal curves and new curves. After excluding reasons stated in exception message, I think it could be precision issue. Since the method requires curves, I was thinking about generating new curves for grids using dynamo lines and turn them to Revit lines but it throw an “Not Coincident with Original Grid Line” exception when applied them to SetCurveInView(). I was wondering why Grid class has just a SetVerticalExtent() without a SetHorizontalExtent().īut the method I need reside in its base class which has a SetCurveInView(). Notice that I am using the shrunk boundingbox (a new box) to intersect with grids to generate a series of new ends, not actually apply the new box to the view.
0 Comments
Leave a Reply. |