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

Materials lost when transform a SnapshotDb to another by using core-transform #5307

Closed
fatalstar opened this issue Mar 29, 2023 · 4 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@fatalstar
Copy link

Describe the bug
I try to transform a SnapshotDb to another, but materials lost.
And then, I try to transform it to an empty SnapshotDb,materials get lost and error.

To Reproduce
Steps to reproduce the behavior:

  1. Convert House_Model.dgn to a local house.bim file. And do same thing with testY1.dgn.
  2. Build an iModelTransformer with core-transformer@3.4.4
  3. Excute iModelTransformer.processAll( house.bim, testY1.bim, no options),
  4. When transform done, excute targetDb.saveChanges( )
  5. Open the targetDb in view, and could see the materials lost.

Expected behavior
Materials exist and be correct.

Screenshots
The house.bim view :
image

The result.bim view: (materials get lost)
image

If transform to an empty db, and view: (roof material lost, wall and steps meterial error)
image

Desktop (please complete the applicable information):

  • iTwin.js Version [3.4.4]

Additional context

@pmconne
Copy link
Member

pmconne commented Mar 29, 2023

Did you try with the latest version (3.6)?
@MichaelBelousov

@pmconne pmconne added the bug Something isn't working label Mar 29, 2023
@fatalstar
Copy link
Author

fatalstar commented Mar 29, 2023

Did you try with the latest version (3.6)? @MichaelBelousov

I have tested core-transformer@3.6.3 just now and materials still get lost.

@MichaelBelousov
Copy link
Contributor

@fatalstar I'm sorry for missing this. The transformer has moved to a separate repository, so I will make an issue there and close this one if that's OK. Texture loss should have been fixed by #5059.

@fatalstar
Copy link
Author

@fatalstar I'm sorry for missing this. The transformer has moved to a separate repository, so I will make an issue there and close this one if that's OK. Texture loss should have been fixed by #5059.

Sure, thanks for that!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants