Mapping members from Tekla Structural Designer into Revit 2024 -Revit not recognizing members

[ben.coxCV6BW]

I am importing a .cxl file from Tekla Structural Designer into Revit 2024 via the Tekla Integrator Plugin within Revit 2024 and Revit is not recognising the steel members which are typical steels UC/UBs etc from Tekla Structural Designer.

I have attached three screen shots hopefully illustratrating clearly the issue.

I note the Mapping members "AutoDesk Revit guidance" however this does not inform or clearly indicate what file to map and where from. We have tried the revit/libraries/uk but this does not seem to have any effect.

(I am looking to add connections within Revit to the structure once imported from Tekla SD)

I look forward to Autodesks or anyones replies on this matter

[jay_colcombe]

Hi, this could be down to simple small anomalies in Revit and the Tekla Integrator, it was only released very recently and this could be a little buggy as Tekla have to make changes inline with what Revit has done in the background.

As regards the mapping files etc. these are simply the Revit Families loaded with the software

You may have to a little work in the Tekla Integrator to point it at the correct folders.  

In the past i pointed it to older versions of Revit content (2022/2021/etc.) as i knew this worked and all it does is bring those families into the model.

I would also ensure you let Tekla know of the difficulties you are facing as it may be an issue that needs to resolved their end.

[ben.coxCV6BW]

Hi Jay

Many thanks for your response

Could it be the the Beam names/descriptions simply do not match accurately enough ; see attached screen shot and where I have marked in red , it looks like the import Beams contain a space after the UKB whereas the Revit 2024 beam names do not contain this space? (I have checked with CHS, UB and UC and the same applies)

Revit Beam    UKB610x229x101

Import Beam UKB 610x229x101

[jay_colcombe]

I doubt it as the 2021/22/23 section would have been just reused in this version i think it could be something a little more and I'm sure Tekla would have picked that up prior to release.  

Could you try and map to an older library and see if it works or you get the same issue?

Other than this i would suggest you use Tekla Support and post the response here for other if it happens to them