Maniphest T93307

Poses Cannot be found
Closed, Archived

Assigned To
None
Authored By
Neni Tzima (HWWO)
Nov 22 2021, 7:01 PM
Tags
  • BF Blender
Subscribers
Aaron Carlisle (Blendify)
Neni Tzima (HWWO)
Philipp Oeser (lichtwerk)
Richard Antalik (ISS)

Description

Operating system: Windows 10
Graphics card: RTX2080

Blender 3.0 Beta, Update November 22 , 02:39:14

I am using a rigged character from Human Generator in Pose Mode. I have created my pose, I selected the whole skeleton/all bones and then I created a Pose Asset with this pose.

Before that I made sure to create a New File Path in the Asset Libraries. But even though my poses appear inside the Editor and the Asset Browser and I can apply them perfectly onto the character when I am in this project, they do not seem to appear anywhere inside the File Path/folder that I created or even after a deep search in my drivers. When I start a new project and I try to find and apply the poses onto a new character from Human Generator the poses do not appear at all.

Exact steps for others to reproduce the error

  1. Open Blender
  2. Go to Human Generator
  3. Create a new human
  4. Finish Creation Phase
  5. Chose Skeleton
  6. Go to Pose Mode
  7. Open the Animation in Pose Library
  8. Go to Preferences - File Paths - Asset Libraries. Add a new Asset Library. New Name (Fantasy Poses) and a New Directory
  9. Go to Animation (Pose Library), chose User Library (not used by the Asset Browser)
  10. While in Pose Mode, I create a new pose with my character. ( Something simple, limoving her arm front)
  11. With the bone being selected I press Create Pose Asset - Pose Name - Click on the Activate New Action
  12. On the Asset Browser my new Pose has been added. I see the thumbnail and I can load it onto my character in this project.
  13. Close Blender - Start a new project.
  14. Create a new Human from Human Generator. A female again. - Finish Creation Phase
  15. Chose skeleton
  16. Go to Pose Mode
  17. Open Animation in Pose Library
  18. Chose Fantasy Poses ( My new library used by the Asset Browser) or User Library
  19. Go to Browser Assets nothing appears. No saved pose.

The same process I have tried with other fbx characters with a rig, not just with the characters from the Human Generator and the result was the same.

After a deep search into my local disks for the Poses I created , nothing appeared.

Thanks for all your work. I love this new feature and I cannot wait to work with it properly :)

Event Timeline

Neni Tzima (HWWO) created this task.Nov 22 2021, 7:01 PM
Neni Tzima (HWWO) updated the task description.Nov 22 2021, 7:03 PM
Neni Tzima (HWWO) updated the task description.Nov 22 2021, 7:09 PM
Neni Tzima (HWWO) updated the task description.
Philipp Oeser (lichtwerk) changed the task status from Needs Triage to Needs Information from User.Nov 23 2021, 2:04 PM
Philipp Oeser (lichtwerk) added a subscriber: Philipp Oeser (lichtwerk).

Seems like you have not specified the asset library in the Asset Browser (yet)?

Can you see your poses when you change it to Fantasy Poses (or whatever you called your library)?

Neni Tzima (HWWO) added a comment.Nov 23 2021, 4:11 PM
In T93307#1258705, @Philipp Oeser (lichtwerk) wrote:

Seems like you have not specified the asset library in the Asset Browser (yet)?

Can you see your poses when you change it to Fantasy Poses (or whatever you called your library)?

I have specified the Asset Library and the poses do not appear in my Library.

This is how I have done it :

  1. I have created this new Directory

  1. Then I save the pose by choosing the directory of my Library and the Current File in the Asset Browser. Here the Pose is showing as if it has been saved.

When I start a new project with a new character trying to find a pose that I supposedly have saved in my Fantasy Poses Library nothing appears. In fact no pose appears anywhere in the Asset Browser.

  1. This is the way I am doing it so far , because if I try to choose the User Library in the Pose Library and the Fantasy Poses in the Asset Browser, it does not allow me to create a pose asset.

Am I doing it wrong?

Thank you

PS. I am wondering why does it feel so complicated and not as simple as how DAZ or Poser are saving Poses or Assets, for example (?) :)

Philipp Oeser (lichtwerk) changed the task status from Needs Information from User to Needs Triage.Nov 23 2021, 4:24 PM
Richard Antalik (ISS) added a subscriber: Richard Antalik (ISS).Nov 24 2021, 6:45 AM

If you hold mose over buttons of pose library tab, it describes it works in different way than expected here. Dropdown menu defines where poses are to be found, not where they are saved. Create Pose Asset will save pose only in current file. If you choose user library as "destination", Create Pose Asset will be inactive.

So I think this works as designed currently.

Philipp Oeser (lichtwerk) changed the task status from Needs Triage to Needs Information from User.Nov 24 2021, 8:50 AM

Not totally sure I understand correctly.

@Neni Tzima (HWWO) : dou you save the poses while having the original file (the library file) open?
as @Richard Antalik (ISS) said, you can only save to the current file, you cannot save to a library file that is not open currently.

Neni Tzima (HWWO) added a comment.EditedNov 24 2021, 9:21 PM

Hello,

After many trial testing, I discovered that the poses in order to be saved, I had to save the project where I am creating them inside the same folder as I have my custom Library.

For instance I created a new folder for my Library '' Fantasy Poses '' and I saved the project where I created the new pose asset in the same folder as the Fantasy Poses library.
Only then the poses appeared on a new project. They have to be in the same folder as the Library that we create.

I did not see that being mentioned in any of the tutorials I have watched. ( Unless I have missed it ), but it was not known to me.

After this, everything works fine.

Thank you ! :)

Richard Antalik (ISS) added a subscriber: Aaron Carlisle (Blendify).Nov 25 2021, 1:53 AM
In T93307#1259584, @Neni Tzima (HWWO) wrote:

Hello,

After many trial testing, I discovered that the poses in order to be saved, I had to save the project where I am creating them inside the same folder as I have my custom Library.

For instance I created a new folder for my Library '' Fantasy Poses '' and I saved the project where I created the new pose asset in the same folder as the Fantasy Poses library.
Only then the poses appeared on a new project. They have to be in the same folder as the Library that we create.

What pose library does is just create action and mark it as asset. AFAIK you can't save asset from current file into library in different path. Having current file saved in path for library you want to use makes your current file as the library, that works as expected.

So I think this is issue with workflow - if you want to make library, then you should consider your current file as the library and save it to library path.
If you want to use library, just choose one you want and apply pose. But you can't modify or add poses. For that you have to open library .blend file and do changes there.

Not sure if documentation has been updated from previous pose library version, I am not familiar with how that was implemented at all, but looks like it was very similar, just asset browser streamlined work with library .blend files.

So I think code-wise things work correctly here. @Aaron Carlisle (Blendify) do you know if docs are sufficiently up to date for this feature? Or if there is other task for missing docs?

Neni Tzima (HWWO) added a comment.Nov 25 2021, 7:17 PM

I figured it out eventually, that the poses/assets are saved in the blend file, not as separate files in the folder. It was really difficult for me to find this information in the documentation, and eventually got help from my partner to sort it out. Thanks for your help, time and patience!

Philipp Oeser (lichtwerk) closed this task as Archived.Nov 26 2021, 8:42 AM

Thx @Neni Tzima (HWWO) for your own investigations (yes, this is how it works).
Documentation might still improve here, but will close then (since this is not really a bug).