ADN Developer Days 2011 Connecting the Pieces.

ADN Developer Days 2011 Connecting the Pieces

Revit Quasar 2013 Image Courtesy : ESO/M. Kornmesser (

Connecting the Pieces

Connecting the Pieces The whole is greater then the parts
The parts are increasingly not viable on their own

Today’s Agenda Revit 2013 Features APIs The Rice (must do)
The Wine (value add) Timing Image courtesy of Harmonix Music Systems, Inc.

Nondisclosure Agreement
Today’s discussion is covered under your ADN Agreement with Autodesk. The information we will be providing is highly confidential, and is to be shared within your company on “need to know basis” and to no one outside your company. Autodesk makes no guarantees that anything presented or discussed will actually appear in the future.

Revit 2013 Features

Revit 2013 Projects Design for: Construction/Fabrication/Engineering
Construction Modeling Fabrication Platform Precast Elements Reinforcement Detailing Point Clouds Piping & System Routing Customer Requests Platform Scalability Revit Server Performance Countrification Stairs & Railings MEP Centerlines IFC API Suites & Interoperability First Experience Revit One Box Consistent Visualization Translation Fidelity Add-In Integration View API Visualization API Suites Visualization Workflows Inventor Interoperability API Analysis & Simulation Physical Properties Structural Analysis in BIM Structural Code Checking Analysis Visualization Analytical Volumes MEP Calculations There are 5 general categories as listed on the slides.

Design for: Construction / Fabrication / Engineering

Design for: Construction/Fabrication/Engineering
Construction Modeling (Creation of Parts) Benefits: Derive construction insight by working with multi- disciplinary design model Deliverables: Merge Parts for concrete pour planning Create Parts from loadable structural families and in- place walls Linked model object splitting and manipulation Empty layer Additional parameters export to Navisworks/QTO Merge part also has an API to it. The broader goal with these enhancements is to prepare models for pre-construction stage.

Precast Elements (Modeling + Assemblies + Shop Drawings) Benefits: Precast fabrication platform Enable partners to supply countrification Deliverables: Split with gaps and profile Allow more view types on Assembly sheets Schedule API for external development Manual transfer of Assembly sheets during deletion Dividing with profiles, we can represent pre-cast elements. Schedule API is in it nascent stages still.

Reinforcement Detailing Benefits: Extending BIM lifecycle from Design to Construction through Detailing and Fabrication Deliverables: Area/path reinforcement to host real rebar and set Welded wire mesh Reinforcement to be aware of fillets and hooks Additional reinforcement units Reinforcement detailing is a new topic. We have welded wire mesh in Revit 2012, with API included. We also have some APIs around fillets and hooks.

Piping & System Routing Benefits: Improve ease of routing duct and pipe systems Deliverables: Enhanced system routing Routing preferences for ease of content selection Foundation work for construction level pipe content Image courtesy of Hazen & Sawyer, (Phil Nower)

Point Clouds 2.0 Benefits: Streamlines as-built BIM authoring process for Existing Building Renovation and Retrofits Enhanced ability to connect Construction Planning & Execution to BIM. Deliverables: Improved assistance in authoring from point clouds Improved visual fidelity Improved performance Customer feedback response There are some minor enhancements around it. Memory management should be better.

Customer Requests Benefits: Provide enhancements with high customer value Remove barriers to meeting local standards Deliverables: Dimension Improvements Multi-segmented Grids View References Guide Grid Improvements Void Cut Improvements Divide & Repeat Worksharing Enhancements Dimension Improvements are: Diameter Delete Dimension in Chain Equality Dimension Improvements A lot of customers would be happy about multi-segmented grids around which we also have an API. Void Cuts Improvements allow for the cutting of Casework, Furniture, Furniture Systems and Specialty Equipment with Voids hosted in families

Platform Scalability

Platform Scalability Revit Server Benefits:
Geographically dispersed teams can collaborate on shared Revit models across the WAN Ability to connect to multiple central servers Compatibility with Vault AEC Server Deliverables: Side-by-side install with earlier RS versions Hyper-V virtualization support Multiple Host network Improved file lock management Unified project data management with Vault Model Search / Open / Link / Archiving Revit Server has some enhancements around robustness and ability to create a network of servers. There is a REST API which allows us to perform some administrative tasks programmatically. We do have a document on the REST API by Adam Nagy on the ADN Extranet and the capabilities of Revit 2013 will be primarily the same as of Revit 2012 REST API.

Platform Scalability Performance Benefits: Deliverables:
Significant performance improvements leading to a smoother experience using Revit on large projects. Deliverables: Performance improvements for: Large, complex models Stacked Walls Zones Rebar Cover Flex Piping Graphics Frameworks for: Multi-Threaded Family Regeneration Multi-Processed Model Regeneration Deferred System Propagation Continuously working on improving performance and have done some changes under the hood which should not have any changes to the API as such.

Countrification

Countrification Stairs & Railings Benefits:
Users will be able to easily model, edit and document their stair & railing designs Deliverables: Stair Modeling Improvements Component based stair and railing assemblies Annotation & Representation Improvements to meet industry and firm standards Continuous handrail with extensions API access to customize for unaddressed needs Stair Modeling Improvements Include: Winder Stairs, T-Shaped Stairs, Circular Stairs greater than 360 degrees, Notched connections between stair runs and landings/floors Annotation & Representation improvements include: Stair Path and cut mark customization, Tread/Riser numbering, and greater control of element visibility. Old New

Suites & Interoperability

Revit (One Box) Benefits: Support multi-discipline workflows Easier to manage multiple Autodesk solutions Deliverables: New product combining RAC, RST, and RME Available in Premium & Ultimate Building Design Suites. A unified and customizable product to support cross disciplinary use. Configure available tools before or after deployment. We are creating a unified Revit – one box. This will show up on the user experience side as tabs with the Systems tab being comprising of the M, E and P. The upper right screenshot is the configuration dialog which shows what functionality should be included with the different disciplines. For example, you will now be able to turn off the structural analysis capability for enhanced performance until you need this feature.

Consistent Visualization Benefits: Increased options for rendering Support for most current visualization technologies Deliverables: Improved interoperability with Showcase Cloud-Based Rendering (Project Neon) Microsoft Warp support DirectX 11 support Interactive rendered views Graphics performance improvements Continuous improvements with Visualizations. We now have included Microsoft Warp support for windows 7 and windows vista SP 2. We will also have interactive rendered views. Improved Anti-aliasing

Analysis & Simulation

Analysis & Simulation Structural Analysis in BIM Benefits:
Deliver Structural analysis in the cloud Support partner ecosystem growth Deliverables: Results Storage in RST (early Q3/TBD) Results Exploration in RST (early Q3/TBD) Improved analytical models for surface elements Seamless workflow between RST/RSA Improved rigid links

Analysis & Simulation Structural Analysis Web Service
Benefits: Democratize Analysis Increase Competitive Differentiator and show Thought Leadership in Structural Analysis Make Analysis Easy to Use and Sell Deliverables: Static Analysis Results visualization RST Results storage in RST (Q3) Ability to have structural analysis done on a cloud. In near future a lot of the services will be delivered from the cloud. With respect to the API, it is currently under discussion.

Analysis & Simulation Analysis Visualization Benefits:
Deliver Structural analysis in the cloud Support partner ecosystem growth Deliverables: Support for deformation analysis Support for Modal analysis Enhanced results visualization

Analysis & Simulation Physical Properties 2.0 Benefits:
Centralize analysis workflows around BIM data. Improve efficiency of BIM-based analysis workflows. Deliverables: Extended thermal and structural properties of building envelope Material authoring and library management workflows Foundation for material ecosystem Data flow with key Building Performance and Structural Analysis applications Continued focus on Physical Properties. Primary goal is to have the physical parts of the materials as available as the visual aspects to have applications use them.

Analysis & Simulation MEP Calculations Benefits:
Ability to validate calculation results Ability to customize calculations Support for international calculation methods Deliverables: Improved accuracy of HVAC and Piping calculations Pressure loss report for duct and pipe systems Calculations API Ability to use physical properties from architectural elements in heating/cooling calculations Image courtesy of Hazen & Sawyer, (Phil Nower) Created a framework in the API so that specialized calculations can be plugged in including calculations for MEP. Internally work is in progress to have the product calculations sit on top of the API and be called when regeneration or updates are required. This is an open framework for you to countrify MEP depending on your preferred standards.

Revit 2013 APIs

Revit 2013 API Themes Add-In Integration Analysis
Construction Workflows Interoperability …and more!

APIs and Porting The Rice The Wine Making sure your application runs
Steps to support the next release The Wine Opportunities to add value Using the new features and APIs to increase the value of your and our products

The Rice .NET 4.0 VSTA Removal & Replacement with SharpDevelop
Revit.ini registration disabled Document.Element properties replaced Updates to Idling event Platform deprecations IFC API removals Construction modeling changes MEP changes PointCloud engine API changes Obsolete API cleanup Revit is compiled on .NET 4.0. Revit ini registrations for plugins was deprecated last year and now is disabled.

.NET 4.0 for compilation Revit API dlls are built with .NET 4.0 compiler All add-in projects must set as .NET 4.0 projects All add-ins should be compiled with .NET 4.0

VSTA Removal VSTA does not support 4.0
Access to VSTA through Revit UI has been removed Replaced with SharpDevelop platform and IDE* VSTA does not support 4.0 and so we have not included it in Alpha 2. We are going to replace it with a open source component SharpDevelop.

Revit.ini registration disabled
Add-ins will no longer be read from INI file Revit will look for .addin files from machine-wide and user-specific locations only.

Document.Element properties
Old existing indexed properties removed… Document.Element[ElementId] Document.Element[String] …and replaced with: Document.GetElement(ElementId) Document.GetElement(String) This is a cosmetic change only for improved .NET compatibility

Idling Event Idling event can be invoked with no active document
Idling event offers two modes of behavior: In default mode, single raise of event is made each time Revit gets into idle mode. If user is not active at all, Revit may not invoke calls to subscriber until user is active again. In non-default mode, application makes repeated calls to event subscriber even if user is totally inactive. IdlingEventArgs.SetRaiseWithoutDelay() Helps indicate the preference for non-default idling Also wine, performance increase for use of Idling in attended Revit sessions (e.g. modeless dialogs) In the default mode, a single raise of the event will be made each time Revit begins an idle session. Note that when the user is active in the Revit user interface, idle sessions begin whenever the mouse stops moving for a moment or when a command completes. However, if the user is not active in the user interface at all, Revit may not invoke additional idling sessions for quite some time; this means that your application may not be able to take advantage of time when the user leaves the machine completely idle for a period of time. In the non-default mode, your application forces Revit to keep the idling session open and to make repeated calls to your event subscriber. In this mode even if the user is totally inactive the Revit session will continue to make Idling calls to your application. However, this can result in performance degradation for the system on which Revit is running because the CPU remains fully engaged in serving Idling events during the Revit application's downtime.

Platform deprecations
ElementArray and ElementSet have been replaced with ICollection><ElementId> in many methods Batch element creation methods have been marked deprecated but not replaced directly ItemFactoryBase.NewTextNotes() Creation.Document.NewRooms(List<RoomCreationData>) Creation.Document.NewWalls() (all overloads) Instead of these batch creation methods, use single element creation method in loop and then call Regenerate() method Some of these changes are simple, others will require some work to use replacements (e.g. batch creation methods). GeometryElement.Objects also replaced, GeometryElement is now IEnumerable<GeometryObject> The batch creation methods previously were created since there was no control over regeneration and so it was best to batch create elements and then regenerate in one step. Now with regeneration being in the control of API users, it is best to call element creation methods in loop and then call regeneration when required. Thus batch creations methods have been deprecated.

Platform deprecations
GeometryElement.Objects replaced: GeometryElement is now IEnumerable<GeometryObject> Wall creation methods on Autodesk.Revit.Creation.Document replaced: Now part of Wall class: Wall.Create (5 overloads) Couple of small changes – geometry object replaced to now be a enumerable. The wall creation API comes off the wall class instead and there are various overloads for that.

IFC API removals Many APIs introduced in Revit 2012 to support the Open Source IFC exported have been removed in this release. Autodesk recommends beginning any IFC export customization from the current release source code, which uses a new more generic and more extensible API (instead of attempting to port code written for Revit 2012).

Construction Modeling changes and deprecations
Following methods have changed Part.GetDividedParents - replaced with: Part.GetSourceElementIds PartMaker.GetDividedElementIds - replaced with: PartMaker.GetSourceElementIds PartMaker.IsElementDivided - replaced with: PartMaker.IsSourceElement PartMaker.SetDividedElementIds - replaced with: PartMaker.SetSourceElementIds PartUtils.IsMaxDivisionDepthReached - the limitation on maximum # of divisions has been removed Following methods are marked obsolete: Part.OriginalDividedElementId Part.ParentDividedElementId PartUtils.GetDividedParents Interface clean ups and obsoleting some previously exposed methods. also wine, related to merge parts capability in Revit 2013.

MEP changes and deprecations
ConnectorElement Subclasses of ConnectorElement are obsolete IsPrimary, AssignAsPrimary and LinkedConnector moved to ConnectorElement Creation methods in FamilyItemFactory obsolete Connector.Create functions added for all disciplines New methods for cable tray/conduit connector creation ConnectorProfileType enums have been renamed from InvalidProfile -> Invalid RoundProfile -> Round RectProfile -> Rectangular OvalProfile -> Oval PartType has been renamed from UndefinedPartType -> Undefined also wine, ConnectorElement creation allows cable tray/conduit. Some nomenclature changes as listed on the slide

Point cloud engine API changes
New methods have been added to the interface IPointCloudAccess: Free() – allows your engine to release memory when the point cloud type is unloaded or deleted GetOffset() – gets the offset to the origin for the point cloud points (used for placement “origin to origin” or “relative to last”) CreatePointSetIterator() – a second overload with an additional argument – density – the desired number of points per unit area. Area is computed in native units of the point cloud

Obsolete API Cleanup APIs marked obsolete in Revit 2012 have been removed: MaterialConcrete, MaterialOther, MaterialSteel, etc Autodesk.Revit.DB.ConstructionType SuspendUpdating Document members like Move(), Rotate(), etc Reference members Face.MaterialElement PointOnEdge members ControlledApplication.LibraryPaths PipingSystem members ObjectType on Element Space.Boundary these were all previously marked Obsolete.

The Wine (value add) Timing Hopefully the rice section is back to half a day of update work instead of two days as it was from Revit 2010 to Revit But that change was to prepare for future footing. Image courtesy of Harmonix Music Systems, Inc.

The Wine Integration Analysis Modeling Interoperability …and more!

Integration

UI API enhancements Ribbon items can now provide contextual help:
RibbonItem.SetContextualHelp() API commands can be assigned Keyboard shortcuts API commands can be moved to QAT Ability to replace existing Revit command: RevitCommandId Embed Revit Views as WPF controls inside a dialog: PreviewControl Drag & Drop API Options dialog custom extensions Primary goal is to expose the UI API to such a level where add-ins are indistinguishable from Revit features as you might have noticed with updater, idling event. One important step in this is to add help for your plug-ins contextually. Addin can be assigned keyboard shortcuts, moved to QAT. And you can replace an existing Revit command implementation with your own. If you are working with Revit views and want to show a part of the model in a dialog box. We can now use the drag and drop api to control the way we drop things into Revit from your applications (not yet included in the API but plan on including it in the API soon). We now can also add our own page to the options dialog.

View API enhancements New UIView class now represents a View window
View Creation: Duplicate Views Read Plan View Regions Read Plan View Range Lock and unlock 3D Views New enums added to API: DisplayStyle ViewDetailLevel PlanViewDirection Plans 3D Sections Elevations Detail Callout Reference Rendering View creation: Plans (renovation/enhancement), 3D views (renovation/enhancement), Sections (detail/callout/reference), Elevations, ImageView (rendering view) UIView capabilities include identification of open views, pan and zoom to volume in area Duplicate views Read PlanView regions Bunch of small enhancements If we are listing future capabilities, schedule support will also cover placing schedules on sheets (basic capabilities) and read/creation/manipulation of schedule fields and filters

View API enhancements New ViewSchedule class added to API*
Place Schedules on Sheets Create / Read / Edit Schedule Fields & Filters Export schedule to text file A new API for some capability around schedules but not included yet in the API. There are plans for further investment in this API in future too.

Rendering Settings Settings in Rendering Options dialogs exposed:
New methods: View3D.GetRenderingSettings View3D.SetRenderingSettings New class offers properties and methods corresponding to options in UI dialog: RenderingSettings Render capability is not present, this just accesses stored settings. So cannot kick off a rendering yet but is in the plans for future.

External Events Framework
New API for asynchronous processes (like for supporting modeless dialogs) Steps for using this framework: Implement an external event derived from the interface: IExternalEvent Create an ExternalEvent with: ExternalEvent.Create() When an event happens in your modeless UI where a Revit action needs to be taken, call: ExternalEvent.Raise() Revit will wait for an available Idling timecycle and call the implementation of your event: IExternalEvent.Execute()

Document and Worksharing changes
New overloads for OpenDocumentFile() and OpenAndActivateDocument() OpenOptions and OpenOptionsForUI Help specify how Revit document should be opened OpenOptions.DetachFromCentralOption and OpenOptionsForUI.DetachFromCentralOption Provide ability to detach opened file from central New class called BasicFileInfo Provides information without opening the file Worksharing status Revit version Username Central path Last saved locale New overloads for open documents include detach from central. Hopefully this will be valuable to you. This is a wine feature. BasicFileInfo entirely new and provides some information about a file without actually opening the file.

Analysis

MEP improvements New Routing Preferences API supports selecting:
Pipe sizes Materials Fitting types New interfaces to calculate Pipe & Duct friction factors New class MEPSection is base of duct/pipe section New class FluidTemperature represents viscosity and density at specified temperature Additional MEP Calculations to come…* other MEP calculations still planned Some APIs for routing preferences which is a feature for this release. With the analysis part, friction factors, viscosity and more to come in respect to the framework related to MEP calculations that we discussed before.

Physical Properties New ThermalProperties class exposed
Structural family instances support additional structural material element Material assets (Structural and Thermal) can be shared and set on materials Ability to indicate if thermal information is included in GBXML export GBXML export for work with energy analysis.

Structural Analytical Model
New element type AnalyticalLink can be created between two other Analytical Elements, e.g. an analytical beam and analytical column There are two kinds of Links: user defined and automatically generated Links have properties like "fixity state" that can be accessed via the API

Analysis Visualization Framework
Support for deformed shapes as part of AVF display: AnalysisDisplayStyleDeformedShapeTextLabelType AnalysisDisplayDeformedShapeSettings A new override to CreateAnalysisDisplayStyle accepts an input argument of AnalysisDisplayDeformedShapeSettings

Light and Light Group API
New classes added to get and set photometric data LightType LightFamily Access includes family instances in projects and family types in family documents Exposed parameters include: Initial Color Initial Intensity Loss Factor Color Filter Dimming Color New classes to manage light groups: LightGroupManager – create and delete LightGroup LightGroup – get name, rename, add light, remove light and turn lights on & off for rendering Some control over lights and light groups, rendering aspects, and some ability to manage light groups.

ReferenceIntersector
New class ReferenceIntersector allows ray-cast selection of elements with a point and direction Similar to FindReferencesWithContextByDirection() but additionally supports filtering of output for better performance Supports filtering elements, meshes, edges, curves and faces Also Wine. Allows better performance looking for certain types of output (e.g. find only “walls” instead of all elements). So you can know filter out what you get from the results.

Modeling

Stairs New classes to create / read / modify stairs: Stairs StairType
New classes access Stair annotations: StairsPath StairsPathType CutMarkType capabilities: create/read/modify of new stairs (not older stairs). Associate railing with stairs. Revit 2013 will have two types of stairs – the older ones and new ones has API access for most parts of them and work will continue on this. We should be able to control the geometry and the annotations on the stairs.

Stairs Access to the subcomponents and subcomponent types of the new Stairs elements: StairsLanding StairsLandingType StairsRun StairsRunType Older stair elements identified using built-in category Stairs now are componentized so there are various components that can be accessed programmatically. Can use the built in category to distinguish between new stairs in 2013 and legacy stairs from prior releases. User will still be able to create the old and new stairs and this can be considered as a transition for that.

Railings New classes access Railings: Railing RailingType
Railings can be associated to a host Can be continuous or non-continuous Rail subcomponents:* ContinousRail HandRail TopRail Limited access for non-continuous railings ContinousRail/HandRail/TopRail are special subcomponents being exposed (not in Alpha 2) Ability to associate a railing with a host.

Welded Wire Mesh FabricArea FabricSheet FabricSheetType FabricWire
FabricWireType Revit 2013 provides a welded wire mesh object that will provide access to these properties. (not completely included in Alpha 2)

Reinforcement New class RebarInSystem, representing a bar in a system:
AreaReinforcement PathReinforcement New members in AreaReinforcement to: Retrieve system members Retrieve curve boundaries Remove element and convert its bars into standard rebar New members on PathReinforcement to: More access to rebars in a system in both area reinforcements and path reinforcements.

Reinforcement Rebar.GetCenterlineCurves(Boolean, Boolean, Boolean) controls: Adjustment for self-intersection Including hooks Including bend radius curves (fillets) New methods and properties: RebarShapeMatchesCurvesAndHooks() checks if RebarShape matches curves and hooks CreateFromCurvesAndShape() creates a new instance of a Rebar element with default shape parameters from the RebarShape GetBarPositionTransform() GetBarExistsAtPosition() GetHookTypeId() SetHookTypeId() ScheduleMark property Programmatic access to hooks and fillets and number of functions around that capability.

Construction Modeling
Part merging PartUtils.ArePartsValidForMerge() PartUtils.CreateMergedPart() PartUtils.FindMergeableClusters() PartUtils.GetChainLengthToOriginal() PartUtils.GetMergedParts() PartUtils.IsMergedPart() Part.Excluded property identifies and assigns parts to be excluded AssemblyViewUtils.AcquireAssemblyViews() transfers assembly views owned by a source assembly instance to a target sibling assembly instance of the same assembly type AssemblyInstance.Location returns consistent location for AssemblyInstance elements Quite a lot of work has been done is providing capability around merging of parts – from providing access to parts that are eligible to become a part to the merged parts. You can also exclude parts from a merge AcquireAssemblyViews(): This is helpful when we have to delete an assembly from which views have been created but not have deleted all the views that were created by that assembly.

Interoperability

IFC Export IFC export implementation in Revit has switched to a more generic toolkit Many of the APIs introduced in Revit 2012 to support customized IFC export have been marked obsolete and will be removed in Revit Quasar New interfaces introduced allowing more flexibility in writing the IFC file IFC Exporter source code now available on SourceForge Plan to remove obsolete IFC APIs (specialized workflow, we prefer you start from our 2013 implementation) As you all might be aware already, IFC export was moved to Open source. There is the possibility of customizing it and it is being greatly enhanced. Older export API interfaces are going to be removed.

Data Exchange API enhancements
DGN / DWF / DWG Settings API DGN V8 Import & Export New method to import DGN files into Revit views: Document.Import(string, DGNImportOptions, View) New options for DGN Export DWG / DXF Import & Export New method to support DXF import: Document.Import(string, DWGImportOptions) New options for DWG / DXF Export This supports DGN v8 (import and export). Also offers access to stored export settings in document (create/read/modify)

Revit Link Creation Revit 2013 API provides the ability to create Revit links RevitLinkType.Create(Document, ModelPath, RevitLinkOptions) will create a new Revit link type and load the associated linked file into the document. RevitLinkInstance.Create(Document, ElementId) will create a new instance of an already-loaded RevitLinkType. ability to create Revit links and so now we can take a revit model and link it into a host Revit model programmatically.

…and more!

Filled Region FilledRegion extended to provide ability to
Create filled regions Get boundaries of regions Apply linestyle to all boundary segments New class FilledRegionType Provides access to all visible properties of filled region type API to manage Filled regions to display analysis results or some expression of geometry in a particular view.

Elements and Filtering
New SelectionFilterElement accesses filter type New PhaseFilter class creates / reads / writes phase filters SelectionFilterElement has been part of RST and is now showing up in one box Revit.

Geometry and Sketching
New method SolidUtils.SplitVolumes() to take multiple disjointed enclosed volumes and return solids representing each volume The new method SolidUtils.TessellateSolidOrShell() returns TriangulatedSolidOrShell, a single triangulated structure for the input Solid (one or more fully closed volumes, or a shell of faces which do not form a closed volume). allowing access to the stored triangulated components and triangles. API read/modify/create for DividedPath (supported in the massing environment consisting of a set of points distributed along a connected set of curves and edges). SplitVolumes take a multi-body solid and split it into individual solids. One usage currently is the IFC export besides others. TessellateSolidOrSolid takes a whole solid or shell and do a tessellation such that we are not tessellating each face but rather aligned with each side of the solid.

Geometry and Sketching
NewSketchPlane(Document, Reference) overload in ItemFactoryBase creates a sketch plane from a Reference representing a planar face. CylindricalHelix curve type for Stairs and Railings New Ellipse properties to provide unit vectors for X and Y axes New GeometryElement.GetBoundingBox() reads bounding box CurveLoop as IEnumerable<Curve> traverses curve loop members CurveElement.CenterPointReference returns the center of a curve to allow dimensioning ModelCurve.ChangeToReferenceLine now for all family types If you want to create an extrusion element, and wanted to reference an existing plane, the new sketch plane is the best to use since the reference will be preserved from one end to another rather than getting the geometry of the plane and then passing it as a plane and then there is no reference preserved. And so if the original plane is changed, the sketch element (extrusion) is not changed accordingly. CylindricalHelix is a first time complete 3D ellipse and is only intended for use in stairs and railings and cannot be used elsewhere. CurveElement.CenterPointReference is useful for annotations – if you want to dimension to a center of a curve, we need a special reference that is not there in regular geometry.

Detailing and Annotations
Diameter Dimensions FamilyItemFactory.NewDiameterDimension() creates DimensionShape enumeration contains a new Diameter member DimensionSegment overrides: DimensionSegment.Prefix DimensionSegment.Suffix DimensionSegment.Above DimensionSegment.Below DimensionSegment.ValueOverride The class DetailElementOrderUtils has been added providing the ability to affect the draw order of detail elements (including FilledRegions) Revit will have a diameter dimension and an API for that. We also have some further control over dimension segments. And the ability to change the draw order coupled with filled region and so more graphic control in this case.

Families and Content New SpatialElementCalculationPoint class creates / reads / modifies graphical location point marker AssetType enum now contains a value "Content“ to enumerate RPC assets in the Revit session Family.PlacementType property returns placement type for instances of the given family. PlacementType roughly maps to the overloads of NewFamilyInstance Certain content is going to have calculation points and this will help it make clear about which room a piece of content should be counted. So Revit will use this instead of any arbitrary point mentioned in the family of the content for this graphical locations. And this can be manipulated from the API. API now has access to RPC assets. PlacementType will help identify if a family is 2D family or 2D line based family or face or host based. This will then help decide the right overload to use for the create family instance method.

…and even more! ProgressChanged event returns progress bar data
ProgressChangedEventArgs Caption: name of current transaction / subtransaction Stage: Type of progress event (Started, RangeChanged, PositionChanged, CaptionChanged, UserCancelled, Finished) Position: Numerical index between zero and UpperRange showing number of completed steps of current transaction / subtransaction UpperRange: Number of steps in current transaction / subtransaction Cancel: Cancels the current transaction in progress, if possible Cancellable: indicates if the current transaction can be cancelled MultiSegmentGrid class to support multi-segment grids SiteLocation.PlaceName provides place name of the site location Application.DefaultProjectTemplate - full path to default template file Many new units have been added to UnitType, DisplayUnitType and ParameterType. ProgressChanged to help get more information on a current process that is on-going in Revit and take some actions on it including cancelling the current transaction in progress. API access to multi-segment grid, Added more units to the UnitTypes, etc.

Revit Quasar Timing Beta 1 Early December Beta 2 Late January Beta 3 Early March RTM Early March FCS Late March

Nondisclosure Agreement
Today’s discussion is covered under your ADN Agreement with Autodesk. The information we will be providing is highly confidential, and is to be shared within your company on “need to know basis” and to no one outside your company. Autodesk makes no guarantees that anything presented or discussed will actually appear in the future.

Connecting the Pieces The whole is greater then the parts
The parts are increasingly not viable on their own

Connecting the Pieces

Autodesk, AutoCAD, Alias, Autodesk Inventor, Inventor, Maya, Mudbox, and 3ds Max are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. Academy Award and Oscar are registered trademarks of the Academy of Motion Picture Arts and Sciences. mental ray is a registered trademark of mental images GmbH licensed for use by Autodesk, Inc. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document. © 2011 Autodesk, Inc. All rights reserved.

ADN Developer Days 2011 Connecting the Pieces.

Similar presentations

Presentation on theme: "ADN Developer Days 2011 Connecting the Pieces."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

ADN Developer Days 2011 Connecting the Pieces.

Similar presentations

Presentation on theme: "ADN Developer Days 2011 Connecting the Pieces."— Presentation transcript:

Similar presentations

About project

Feedback