Hi Aussie, thanks for your videos! Regarding what you mentioned in the video about maintaing Packages, do you know if it is possible to "pass the reins" to somebody else without giving him the keys of the user. E.g. a friend of mine created a package. He is no more interested. Is it possible for me to update it?
Hrm I don't believe so - from what I recall the package rights are tied to the author's autodesk account. Maybe ask the query on dynamo forums also, someone there will know the specifics.
Aussie is it possible for you to please please take us through creating a revit template from scratch: A lot is hidden and i really want to know the software inside out. Thank you
I found trying to develope a project within a blank template file and creating all families yourself excellent for uncovering a lot of the hidden workings of Revit.
I can do a few videos eventually on what there is to develop in a template. Building an entire template can take weeks though so it'll probably not cover it all in detail.
I tried to change the top path location in the three-dot button. The change didn't get saved. So I deleted the top path and moved the correct path up from the list below. I need to test several more times to make sure the package publish procedure work. Create and publish packages are the most confusing tasks in Dynamo. It allows me more than one way to do it but it doesn't mean those are the correct ways.
Yes I feel this feature is a bit misfunctional sometimes. I've had similar issues when I changed from the default setting so I rarely change it. I've also found that pointing to a server location is problematic as well, and that it sometimes reverts back to the appdata folder anyway.
When I published the package in the C:, it created an extra 'Packages' folder where the location I chose. Then the actually Custom Node package folder is created within the extra 'Package' folder. Also, I had trouble to add additional custom nodes to the package. Would you mind creating another video to show the procedures?
There are a few reasons this may happen, but most likely your default path has been changed or is incorrect. Make sure in 'settings > manage nodes and package paths' that the top path does not end with packages folder, but the next level up (e.g. 2.6).
Hi Aussie, thanks for your videos!
Regarding what you mentioned in the video about maintaing Packages, do you know if it is possible to "pass the reins" to somebody else without giving him the keys of the user. E.g. a friend of mine created a package. He is no more interested. Is it possible for me to update it?
Hrm I don't believe so - from what I recall the package rights are tied to the author's autodesk account. Maybe ask the query on dynamo forums also, someone there will know the specifics.
Aussie is it possible for you to please please take us through creating a revit template from scratch: A lot is hidden and i really want to know the software inside out. Thank you
I found trying to develope a project within a blank template file and creating all families yourself excellent for uncovering a lot of the hidden workings of Revit.
I can do a few videos eventually on what there is to develop in a template. Building an entire template can take weeks though so it'll probably not cover it all in detail.
Great advice David, I agree!
@@parked32 Thanks man. i will definitely give this a try
@@AussieBIMGuru This would really be great. Thank you sir
I tried to change the top path location in the three-dot button. The change didn't get saved. So I deleted the top path and moved the correct path up from the list below. I need to test several more times to make sure the package publish procedure work. Create and publish packages are the most confusing tasks in Dynamo. It allows me more than one way to do it but it doesn't mean those are the correct ways.
Yes I feel this feature is a bit misfunctional sometimes. I've had similar issues when I changed from the default setting so I rarely change it. I've also found that pointing to a server location is problematic as well, and that it sometimes reverts back to the appdata folder anyway.
When I published the package in the C:, it created an extra 'Packages' folder where the location I chose. Then the actually Custom Node package folder is created within the extra 'Package' folder. Also, I had trouble to add additional custom nodes to the package. Would you mind creating another video to show the procedures?
There are a few reasons this may happen, but most likely your default path has been changed or is incorrect.
Make sure in 'settings > manage nodes and package paths' that the top path does not end with packages folder, but the next level up (e.g. 2.6).
@@AussieBIMGuru I couldn't find out the reason and it keeps screwing up the folder structure. Is there a way I can change the default path?
@@AussieBIMGuru Let me try tomorrow. I shared your channel with my company. Hope the channel can generate more attaentions.
Yes if you click the 3 dots next to the path it should be changable.
What if I click publish (new package or this custom node) and nothing happens? - there is no window to fill in.
Weird. My guess is a firewall blocking it maybe. Best to check in on dynamo forums for detailed help
@@AussieBIMGuru Hmm I can search for the packages so it shouldn't be blocked. Also when I click sign in nothing happens. I will try on forum.
One question :
If we accidentally publish online then how to delete?
Do we have delete option?
I believe the author can only deprecate their package as opposed to remove it altogether; github.com/DynamoDS/Dynamo/issues/2999