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

Unexpected relative path - document.importimage #244

Open
miquelronie opened this issue Apr 29, 2024 · 8 comments
Open

Unexpected relative path - document.importimage #244

miquelronie opened this issue Apr 29, 2024 · 8 comments
Labels
usage User issue in how to use the nodes/package

Comments

@miquelronie
Copy link

Revit: 2022.1
Dynamo: 2.12

I'm trying to import images to the image manager in Revit with dynamo. I use the node Document.ImportImage. I get an error : unexpected relative path or bad .

Captura
what I'm doing wrong?
Thanks in advance

@erfajo
Copy link
Owner

erfajo commented Apr 30, 2024

I have no idea... It works when I test
home
home2

@erfajo erfajo added the usage User issue in how to use the nodes/package label Apr 30, 2024
@miquelronie
Copy link
Author

With revit 2024 and dynamo 2.17 I even don't get it to work, even I got a different error message.
captura2
Any clue?

@erfajo
Copy link
Owner

erfajo commented May 7, 2024

The only thing I know will give an error is, that if you don't have the needed credentials in a folder, then will the node for sure fail. So I presume that "static12" is your username and not someone else's username and/or there is some ”reading” restrictions on that folder. My nodes and functions in general do respect credentials set in the overall operating system.

@Pylos08
Copy link

Pylos08 commented Dec 5, 2024

I am running to this issue as well. I have run testing and it appears that it throws this error when models are cloud shared. A model on my hard drive does not throw this error.
image

@Pylos08
Copy link

Pylos08 commented Dec 5, 2024

Here it is working.
image

@erfajo
Copy link
Owner

erfajo commented Dec 6, 2024

It is a well-known issue that ACC-driven files don't support relative paths, and paths need to have the characteristics that files have web addresses, as I remember it.
I don’t support ACC-driven documents besides those functions I have made where I turn the documents into normal Revit files. I don’t use ACC-driven documents and I don’t have access to ACC normally in my work. I am afraid I can’t help with such issues.

PS. why do you use "copyright Waithfor" node? I have a node named "Await" for that. In general, you should not need any other packages, since Orchid is the largest and most comprehensive package... unless it is very special cases!?

@Pylos08
Copy link

Pylos08 commented Dec 6, 2024

Thanks for the reply. We can make this work I believe after we run our script is to simple import the image. The goal was not to have to worry about links or pathing. We only work on ACC as my team is in a hybrid work model. We also work closely with other trades and designers.

Example here is I don't have these on my C drive but they do appear on the sheet.
image

These scripts I have made or added to over the last 5 or so years and only in the last year or so did I get Orchid working. Loving the nodes!

@erfajo
Copy link
Owner

erfajo commented Dec 6, 2024

First, please skip the slang term "script" since that is not what we are working with...
We work with DAG's --> Directed Acyclic Graph
https://erfajo.blogspot.com/2019/03/graphs.html

Next, I can take an ACC license from our pool, but only while no one else is using the licenses. These licenses are quite expensive, so we don't have an ACC license for everyone. We haven't seen any reason for me to start coding for ACC either, but we have started talking about it. This means that within the next year, I will be doing something with ACC-driven nodes.

I do know that the major issue is the web-based paths, and that is what I will solve first, when I start doing nodes for ACC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
usage User issue in how to use the nodes/package
Projects
None yet
Development

No branches or pull requests

3 participants