Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autodesk 2024 native support (ODA upgrade) #634

Closed
carmenfan opened this issue Aug 4, 2023 · 4 comments
Closed

Autodesk 2024 native support (ODA upgrade) #634

carmenfan opened this issue Aug 4, 2023 · 4 comments

Comments

@carmenfan
Copy link
Member

No description provided.

@carmenfan carmenfan changed the title 2023/2024 native support Autodesk 2024 native support (ODA upgrade) Aug 4, 2023
@sebjf
Copy link
Contributor

sebjf commented Sep 21, 2023

Things that changed this time round:

  1. BmViewType Enum has changed location
  2. The ParamDef Group Type has changed type
  3. The flags for the type of geometry in an OdNwFragment have been removed (the geometry itself must now be tested by casting to the different subclasses)
  4. The way the vertex data in an OdNwGeometry is accessed has changed.

Things to check extra carefully:

  1. That the built in parameter labels are correct
  2. That the view setup in RVT is still correct
  3. That both Lines and Meshes still import correctly from Navisworks

@sebjf
Copy link
Contributor

sebjf commented Sep 21, 2023

Hi @carmenfan, on staging, the Source File key contains the full filename for a Navisworks entry...

image

This line suggests that we intend to only include the filename itself:

setMetadataValue(OD_T("Item"), OD_T("Source File"), ItemSourceFile.filename().string(), metadata);

However, given the import I just performed, it seems this is not taking effect.

Do you know what the desired behaviour is? (I.e. whether the Source File metadata entry should display the full path or just the filename?)

@carmenfan
Copy link
Member Author

Hi @carmenfan, on staging, the Source File key contains the full filename for a Navisworks entry...

image

This line suggests that we intend to only include the filename itself:

setMetadataValue(OD_T("Item"), OD_T("Source File"), ItemSourceFile.filename().string(), metadata);

However, given the import I just performed, it seems this is not taking effect.

Do you know what the desired behaviour is? (I.e. whether the Source File metadata entry should display the full path or just the filename?)

@sebjf
I think we only want the file name here, afterall the path to the file isn't very useful in the cloud aimed for collaboration!

@sebjf
Copy link
Contributor

sebjf commented Sep 21, 2023

Differences accounted for:

  1. Some display names have more information, e.g. an entry called 327598 is now called Model Lines_327598.
  2. OdNwPartition::getDisplayName now includes the file path; bouncer has been updated to remove it when setting the layer, as this would affect the tree.
  3. The Item::Material metadata entry has different Color values. These are internal implementation details so no change is necessary.
  4. Two new items, Item::Source File Name and Item::File Name have been added, both of which include the full path. The metadata also sometimes includes Item::Source File too. A post-processing stage removes the path from the filename for all of these. Item::Source File is added explicitly based on the partition if not set elsewise. Item::Source File Name is ignored, since without the path it is identical to Item::Source File.
  5. The unicode characters for some units have changed (they both displayed correctly before in Chrome, but the new ones are "more correct").
  6. Some coordinates (e.g. Constraints::Colum Location Mark) are swapped (so, B.1-.5 becomes .5-B.1). This is an ODA implementation detail/we don't touch this directly in bouncer.

sebjf added a commit that referenced this issue Sep 21, 2023
…ta and tree, and ignored superfluous metadata entries
sebjf added a commit that referenced this issue Sep 25, 2023
sebjf added a commit that referenced this issue Sep 25, 2023
@carmenfan carmenfan added this to the v5.5.0 milestone Oct 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants