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

Export Family Config Fails #1732

Closed
DarkElephantDesignTech opened this issue Feb 14, 2023 · 4 comments · Fixed by #1793
Closed

Export Family Config Fails #1732

DarkElephantDesignTech opened this issue Feb 14, 2023 · 4 comments · Fixed by #1793
Assignees
Labels
API Change Revit API change that breaks pyRevit [class->Upgraded #{number}: {title}] Prioritize The issue is planned to be resolved in the next version

Comments

@DarkElephantDesignTech
Copy link

DarkElephantDesignTech commented Feb 14, 2023

Describe the bug
Export Family Config fails with errors.

To Reproduce
Steps to reproduce the behavior:

  1. Open a door family
  2. Click on Family drop-down, then "Export Family Config"
  3. Select location and parameters to export
  4. See error

Expected behavior
A YAML file generated with family parameters

Screenshots
image

Desktop (please complete the following information):

  • OS: Windows 11
  • pyRevit Version 4.8.12.22247
  • pyRevit Environment:
    ==> Registered Clones (full git repos) ==> Registered Clones (deployed from archive/image) master | Deploy: "basepublic" | Branch: "master" | Version: "4.8.12.22247+0031" | Path: "C:\Users\ykaranfil\AppData\Roaming\pyRevit-Master" ==> Attachments master | Product: "Autodesk Revit 2023" | Engine: IPY277 (277) | Path: "C:\Users\ykaranfil\AppData\Roaming\pyRevit-Master" | AllUsers master | Product: "Autodesk Revit 2020" | Engine: IPY277 (277) | Path: "C:\Users\ykaranfil\AppData\Roaming\pyRevit-Master" | AllUsers ==> Installed Extensions ==> Default Extension Search Path C:\Users\ykaranfil\AppData\Roaming\pyRevit\Extensions ==> Extension Search Paths ==> Extension Sources - Default https://github.com/eirannejad/pyRevit/raw/master/extensions/extensions.json ==> Extension Sources - Additional ==> Installed Revits Autodesk Revit 2023 | Version: 23.0.20.21 | Build: 20220726_1500(x64) | Language: 1033 | Path: "C:\Program Files\Autodesk\Revit 2023\" Autodesk Revit 2020 | Version: 20.2.90.12 | Build: 20220517_1515(x64) | Language: 1033 | Path: "C:\Program Files\Autodesk\Revit 2020\" ==> Running Revit Instances Error: Object reference not set to an instance of an object. Run with "--debug" option to see debug messages
    pyrevit env

Choosing different parameters doesn't seems to make a difference.

@jmcouffin
Copy link
Contributor

@DarkElephantDesignTech revit 2023

@jmcouffin jmcouffin added Bug Bug that stops user from using the tool or a major portion of pyRevit functionality [class] Prioritize The issue is planned to be resolved in the next version labels Feb 15, 2023
@jmcouffin jmcouffin self-assigned this Feb 15, 2023
@DarkElephantDesignTech
Copy link
Author

@DarkElephantDesignTech revit 2023

Correct, seems to work OK on Revit 2020.

@jmcouffin
Copy link
Contributor

working on it right now jmcouffin@3e8f2a0
It took me some time to figure out a few things.
I still have to fix the import part.

@jmcouffin jmcouffin added API Change Revit API change that breaks pyRevit [class->Upgraded #{number}: {title}] and removed Bug Bug that stops user from using the tool or a major portion of pyRevit functionality [class] labels Feb 20, 2023
@jmcouffin jmcouffin linked a pull request Apr 8, 2023 that will close this issue
jmcouffin added a commit that referenced this issue May 6, 2023
Fix #1732 import export family config
@jmcouffin
Copy link
Contributor

jmcouffin commented May 6, 2023

Fixed by #1793
Might require some extensive testing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Change Revit API change that breaks pyRevit [class->Upgraded #{number}: {title}] Prioritize The issue is planned to be resolved in the next version
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants