Hi.
I have a character that I created, complete with actions, in it's own Moho file.
Is there any difference or preferred way to bring it into a new file? Should I import it or save it to the library and then bring it into the new file?
Will one work better than the other. And will they bring in actions?
Thanks.
Importing a character vs. Library
Moderators: Víctor Paredes, Belgarath, slowtiger
Importing a character vs. Library
M1 Mac Mini.
Moho Pro 14
Moho Pro 14
Re: Importing a character vs. Library
I don't think there's much difference. The Library is just a way to store and organize assets internally. It can be convenient if you work exclusively in Moho and don't need to access the files in other programs very much, or share them with other users on a network.
I took a quick look just now to make sure nothing was missing when importing from the Library. Library's Import window looks the same, but I noticed I don't get the option for Unlink Shared Styles; that seems to appear only when I import via the Import command. That would be a deal killer for me, but if you don't use Shared Styles, maybe that's okay.
Personally, I prefer story in my own folders on my hard drive. This way, I can organize them exactly how I want, and they are fully shareable and accessible by all the programs I use in a production (audio, editing, compositing, 3D animation, etc.,)
At one time, I used the Library to store Moho-specific elements, like Styles. Nowadays, I just save my Styles as vector tiles in a document and store them in an assets folder on my drive. When I need the Styles, I import them and sample them in the workspace like regular artwork. This method is easier for me to manage, and it's also easier to share the file with other artists when I need to.
Hope this helps.
I took a quick look just now to make sure nothing was missing when importing from the Library. Library's Import window looks the same, but I noticed I don't get the option for Unlink Shared Styles; that seems to appear only when I import via the Import command. That would be a deal killer for me, but if you don't use Shared Styles, maybe that's okay.
Personally, I prefer story in my own folders on my hard drive. This way, I can organize them exactly how I want, and they are fully shareable and accessible by all the programs I use in a production (audio, editing, compositing, 3D animation, etc.,)
At one time, I used the Library to store Moho-specific elements, like Styles. Nowadays, I just save my Styles as vector tiles in a document and store them in an assets folder on my drive. When I need the Styles, I import them and sample them in the workspace like regular artwork. This method is easier for me to manage, and it's also easier to share the file with other artists when I need to.
Hope this helps.
Animations, Tutorials, and Cats (Oh, My!) Little Green Dog Channel on YouTube!
D.R. Greenlaw
Artist/Partner - Little Green Dog
Little Green Dog Channel | Greenlaw's Demo Reel Channel
D.R. Greenlaw
Artist/Partner - Little Green Dog
Little Green Dog Channel | Greenlaw's Demo Reel Channel
Re: Importing a character vs. Library
And yes, Actions carry over either way.
Another way to move assets from one project to another is to use the Copy Layer and Paste Layer commands. When you use this on a Group, it copies all the child layers in the Group. When you already have the project files open, this can be more convenient than using Import. However, you won't get the Unlink Shared Style or the Import As Reference options this way. You do get Actions this way.
Word of warning: Lately, I've seen a few cases where I get double actions with the same identical names, and this can cause a conflict. I'm not exactly sure how I'm creating this error yet. One theory is that it's from using Copy Layer/Paste Layer to move items to another project, mirror the actions and artwork, then using Copy Layer/Paste Layer to send the mirrored versions back to the original project. Or, it might be through the use of a third-party tool to modify and mirror actions. I need to look into this later, so TBD.
But Copy Layer/Paste Layer works fine if you're not trying anything too tricky with it, like I am. Just understand the limitations.
Another way to move assets from one project to another is to use the Copy Layer and Paste Layer commands. When you use this on a Group, it copies all the child layers in the Group. When you already have the project files open, this can be more convenient than using Import. However, you won't get the Unlink Shared Style or the Import As Reference options this way. You do get Actions this way.
Word of warning: Lately, I've seen a few cases where I get double actions with the same identical names, and this can cause a conflict. I'm not exactly sure how I'm creating this error yet. One theory is that it's from using Copy Layer/Paste Layer to move items to another project, mirror the actions and artwork, then using Copy Layer/Paste Layer to send the mirrored versions back to the original project. Or, it might be through the use of a third-party tool to modify and mirror actions. I need to look into this later, so TBD.
But Copy Layer/Paste Layer works fine if you're not trying anything too tricky with it, like I am. Just understand the limitations.
Animations, Tutorials, and Cats (Oh, My!) Little Green Dog Channel on YouTube!
D.R. Greenlaw
Artist/Partner - Little Green Dog
Little Green Dog Channel | Greenlaw's Demo Reel Channel
D.R. Greenlaw
Artist/Partner - Little Green Dog
Little Green Dog Channel | Greenlaw's Demo Reel Channel
Re: Importing a character vs. Library
Thanks, Greenlaw.
Very helpful, as always.
Very helpful, as always.
M1 Mac Mini.
Moho Pro 14
Moho Pro 14