Revit 2015 Update Release 3


Revit 2015 Update Release 3
has
been published.

It includes a large number of important new enhancements, as well as the improvements provided by the update releases 1 and 2.

I count the following numbers of bullet items in the

release notes
:

  • Architecture: 45
  • MEP: 18
  • Structure 7
  • API: 9

Here is the full list of Revit API enhancements:

  • Improves retention of device connections when using Wire.Create to create new wire connecting to a device.
  • Improves display of wire connection points when using Wire.ConnectTo and Connector.Connect.
  • Enable changes to MEPSystemType.CalculationLevel via public API.
  • Level parameter correctly set when elements are placed via NewFamilyInstance().
  • Improves retention of parameters in line boundary condition objects.
  • Improves stability when using CompoundStructure.SetLayers.
  • Allows proper assignment of a Phase Created value when using DirectShapes.
  • Improves alignment of text created via API.
  • Improves stability when the API is in Automatic TransactionMode.

The second to last item, especially, is one that many developers encountered and reported, e.g. like this:

NewTextNote Text Wrapping

Question: When I call the NewTextNote method to create a new text note in Revit 2015, it does not fill the text box, but wraps the text around the middle of the text box.

Here is a simple code example:


  XYZ origin = XYZ.Zero;
  XYZ baseVec = XYZ.BasisX;
  XYZ upVec = XYZ.BasisY;
 
  Transaction trans = new Transaction( doc );
  trans.Start( "Create text" );
 
  TextNote note = doc.Create.NewTextNote(
    view, origin, baseVec, upVec, 0.3,
    TextAlignFlags.TEF_ALIGN_BOTTOM | TextAlignFlags.TEF_ALIGN_LEFT,
    "Why is this line too long for the text box!" );
 
  //doc.Regenerate();
  //note.Width = 25;
 
  trans.Commit();

This worked fine in Revit 2014, just as it should, but in Revit 2015 it fails.

I tried to regenerate and set the width after the note creation, but it does not help.

If you click on such a text note manually it fixes.

Answer: Install

Revit 2015 Update Release 3
.


Comments

7 responses to “Revit 2015 Update Release 3”

  1. Dear Jeremy,
    I want to set System Type (System Air,Exhust Air) To duct. But i am not getting. how to do this using Code. Plz help me ASAP.
    Thanks in Advance.

  2. Dear John,
    Thank you for your query.
    I have also just grabbed your associated ADN case 09691948 [Unable to change a duct’s System Type in an Add-in].
    I am very sorry that the initial reply provided by my colleagues was completely beside the point and that nothing has happened since then.
    They are all very busy right now, all with exciting stuff, and so am I :-)
    Still, I’ll take a look at this as soon as I can.
    Thank you for your patience!
    Cheers, Jeremy.

  3. Dear John,
    The quickest answer I can provide to your query is this:
    Look at the AdnRme HVAC sample:
    http://thebuildingcoder.typepad.com/blog/2012/05/the-adn-mep-sample-adnrme-for-revit-mep-2013.html
    Search the source code for some permutation of ‘air’ and ‘supply’.
    The most up-to-date version that I have provided of it is for Revit 2014:
    http://thebuildingcoder.typepad.com/blog/2013/06/the-adn-sample-adnrme-for-revit-mep-2014.html
    I am working on a version for Revit 2015 for you at this very moment.
    Thank you for your patience!
    Cheers, Jeremy.

  4. Dear John,
    I created a GitHub repository for the AdnRme sample to share it with you more easily:
    https://github.com/jeremytammik/AdnRme
    I then migrated it to Revit MEP 2015 for you:
    https://github.com/jeremytammik/AdnRme/releases/tag/2015.0.0.0
    Have you found the solution to your query in there yet?
    Please let us know how it works out for you.
    Thank you.
    Cheers, Jeremy.

  5. Dear John,
    I now searched for the answer to your question in the AdnRme sample.
    I initially implemented what you need using standard generic Revit element parameter functionality.
    However, there is a newer and simpler way to do is using MEP specific API functionality as well.
    Wisely, I stored that answer in the code:
    “You should be able to just use RBS_SYSTEM_CLASSIFICATION_PARAM instead of RBS_SYSTEM_TYPE_PARAM if you like.
    The former System Type property on duct and piping systems (RBS_SYSTEM_TYPE_PARAM) has been renamed to System Classification (RBS_SYSTEM_CLASSIFICATION_PARAM). We are renaming it for clarify and to avoid confusion with the new duct and piping system type elements. This naming also goes in line with other similar parameters like Load Classification.
    The former System Type property on duct and pipe connectors to has been renamed to System Classification. The associated parameters RBS_DUCT_SYSTEM_TYPE and RBS_PIPE_SYSTEM_TYPE has been renamed to RBS_DUCT_CONNECTOR_SYSTEM_CLASSIFICATION_PARAM and RBS_PIPE_CONNECTOR_SYSTEM_CLASSIFICATION_PARAM.
    Another more ‘correct’ way to do this would be to get the Autodesk::Revit::DB::ElementType::MEPSystemType using the new RBS_DUCT_SYSTEM_TYPE_PARAM param from the family instance as above. You should then be able to check the system classification enum (Autodesk::Revit::DB::MEPSystemClassification) in the duct system type element to identify what kind of air system it is (Supply, Return, Exhaust etc). This would also work for piping system components using the RBS_PIPING_SYSTEM_TYPE_PARAM param.”
    Please let us know how you make use of this.
    Actually, please add it to the AdnRme sample yourself and let me know so I can integrate it into the master branch.
    Thank you!
    I hope this helps.
    Cheers, Jeremy.

  6. Hi Jeremy,
    Can you clarify please what does mean ‘Improves retention of parameters in line boundary condition objects.’ in the Revit API enhancements list?
    Thanks,
    Victor.

  7. Dear Victor,
    I believe there was an issue with the parameters passed in to the boundary condition constructor. Their values were lost, so you had to set their values (again) using parameters after calling the constructor. Now the values passed in to the constructor are retained, as they should be. I think.
    Cheers, Jeremy.

Leave a Reply to Jeremy TammikCancel reply

Discover more from Autodesk Developer Blog

Subscribe now to keep reading and get access to the full archive.

Continue reading