Bug Report: there are some bugs in Pipe::Create() API

Bug Report: there are some bugs in Pipe::Create() API

Anonymous
Not applicable
458 Views
1 Reply
Message 1 of 2

Bug Report: there are some bugs in Pipe::Create() API

Anonymous
Not applicable

Hi, 

 

When I use a PipeType to create a new pipe, and I use the biggest diameter of that PipeType, and ensure the biggest diameter is smaller than 152 mm.  I don't add insulation for this new pipe. 

 

Let's see the property of the new pipe in the following picture: the diameter is correct, but the overall size is not correct, so we see the shape of this new pipe is much big than it should be.

QQ截图20181205102031.png

In the picture, the left-top pipe is created by Revit ribbon drawing tool and it is correct. the right-bottom pipe is created by API and it is not correct

 

There is also some strange tips: 

  1. If I don't use the biggest diameter, it is always correct.
  2. If the biggest diameter is bigger than 152 mm, it is always correct.
  3. If the new pipe created by API is connected to other pipes, it is always correct.
  4. If I first add insulation for the new pipe, and then remove the insulation, then the shape of the new pipe become correct.

I guess there are something wrong of updating the overall size parameter value when setting diameter for the new pipe. 

 

The Pipe::Create() API I used is: 

public static Pipe Create(
Document document,
ElementId systemTypeId,
ElementId pipeTypeId,
ElementId levelId,
XYZ startPoint,
XYZ endPoint
)

 

 

Best Regards,

0 Likes
459 Views
1 Reply
Reply (1)
Message 2 of 2

JimJia
Alumni
Alumni

Dear Haibo Zhong,

 

Thanks for your query!

 

Can you provide a reproducible case for it?


In order to explore this matter further, we will need to provide a minimal reproducible case for the development team to analyse in depth.


In order to understand exactly what you mean and be able to research possible reasons for the discrepancy between the observed and expected behaviour, they require: 
· A short exact description of what you are trying to achieve.
· The behavior you observe versus what you expect, and why this is a problem.
· A complete yet minimal Revit sample model to run a test in.
· A complete yet minimal macro embedded in the sample model or Visual Studio solution with add-in manifest that can be compiled, loaded, run and debugged with a single click to analyse its behavior live in the sample model.
· Detailed step-by-step instructions for reproducing the issue, e.g. which element to pick, what command to launch etc.
· http://thebuildingcoder.typepad.com/blog/about-the-author.html#1b

 


Jim Jia
Autodesk Forge Evangelist
https://forge.autodesk.com
Developer Technical Services
Autodesk Developer Network
Email: Jim.Jia@autodesk.com
0 Likes