Bone Minion problems for anyone else?

Dartanbeck

BTW, I'm sorry (for you) that you are apprehensive about using control dials (to make key frames). It's a Magical way to work - and it's Really Freaking Fun!!!

WendyLuvsCatz

Dartanbeck said:

BTW, I'm sorry (for you) that you are apprehensive about using control dials (to make key frames). It's a Magical way to work - and it's Really Freaking Fun!!!

each to their own, I rather dislike AniBlocks too!

I never liked it in 3DU's figures among others

I have installed your freebies BTW it's just not my preffered way of doing stuff, I use puppeteer a lot then prune out the keyframes and save animated part poses 

Dartanbeck

Wow. We are So Different!

aniBlocks and aniMate 2 along with the ability to easily (and quickly) create custom dials are the magic that makes animation possible in Studio - and a Lot more Powerful!!!

Just to name some of the more Major reasons, we can:

• Set the Starting point of the motion
• Reverse the motion
• Manipulate the motion path of the various limbs and/or hip while in aniBlock form
• Change the speed and/or duration of the motion
• Mirror the animation
• Change the direction of the motion
• Apply Partial aniBlocks to the motion
• Add or Remove High Heels to or from the motion
• Combine this motion with others or even repeat this one again without the need of graph editing
• Preview the motion using the target figure of choice

We can also use the aniMate 2 Parent Constraint system, which allows for parenting and unparenting along the timeline.

This example shows picking up a phone and talking on it, then slamming it back down, letting go of it.

Note: We don't have to be using aniMate 2 at the time, or be using aniBlocks to use aniMate 2's Parent Constraints. It just works.

Dartanbeck

...and the Bone Minion Bundles are the Magic that allow us to use our work on Any Figure Generation!!!

Thanks Riversoft Art!!!

WendyLuvsCatz

Dartanbeck said:

 

We can also use the aniMate 2 Parent Constraint system, which allows for parenting and unparenting along the timeline.

This example shows picking up a phone and talking on it, then slamming it back down, letting go of it.

Note: We don't have to be using aniMate 2 at the time, or be using aniBlocks to use aniMate 2's Parent Constraints. It just works.

well that's something I didn't know

there is nothing wrong with dial up poses and if you like them use them

I use partial dial up correctives like arms up and down, legs up, the dial up foot pose fits for shoes (usually I need to make those from the single loads much the same way you create your dial ups)   etc myself 

I just don't usually animate them, I use them more to correct posture as one animation does not work on all figure shapes

often the graph editor moving the whole range of selected keys works too

I don't pretend to be much of a character animator, I am more into moving scenes the people are incidental

Dartanbeck

I love what you do.

And, yeah... those Arms Up/Down, etc., are essentially what I create. Just more possibilities. A Lot more.  alot of the times I might not need to animate them but, since their key frames go on an otherwise empty line, using them to assist in animations is true magic! Easy! Fun!

 

Trust me, I'm not trying to change your ways! You truly have a workflow and you have been a real inspiratio to me ever since I started in on all of this and we became fast friends - but I'm loving the debate! :)

Cheers Sis! 

Dartanbeck

Arms twist was HUGE for me. I could dial that one on the first frame of animation and correct an entire arm/torso cropping issue.

That's how it all began. 

 

Then I decided to ask Rosie if she could do This using those dials - and she complied. Amazed, I asked her if she could do more. She just never says no.

She keeps reminding me of the real Rosie more and more! :)

 

Loves me my real Rosie! 

RiverSoft Art

NotAnArtist said:

RiverSoftArt said:

It worked fine for me (just tested).  No secret sauce.  Are you turning off the limits on the G8 before applying poses?

Yes sir, I turned off limits each time as per the instructions.
But I've been thinking, I did this on an old machine I built in 2012, with DS4.15 now installed, and it may have its own problems.

I should try the same procedure on my newly-built machine and see what happens. It's sort of 'on the shelf' due to a cooling problem and I'm waiting for a chance to add more fans.

I'll try again there without rendering. It shouldn't be a problem.

Thanks for responding! It was a frustrating situation and I just wanted to confirm that what I was trying to do was possible. You have confirmed it for me. Really appreciate your work all together, and this one product right now is proving to be a huge timesaver in filtering down my loads of poses and anims. I just need to stop 'experimenting' and get back to work:-)
Cheers,
Ken

An old version like that probably does fail somewhere. 

RiverSoft Art

Dartanbeck said:

...and the Bone Minion Bundles are the Magic that allow us to use our work on Any Figure Generation!!!

Thanks Riversoft Art!!!

You're very welcome!  Thank you for all the kind words and sharing your workflow with everyone!

Dartanbeck

'Tis my pleasure. I want Everyone to have Fun!!! :)

Dartanbeck

1. Genesis 2 Female to G2F_Mixamo_Upload_FBX
2. Mixamo Download to G2F_FBX
3. Set Daz Studio as the thing to open FBX files
4. Open Mixamo Downloaded G2F_FBX files
5. Run 3DU's Body2Hip Script
6. Save as Animated Pose DUF
7. Open Rosie 8 Base Scene
8. Apply Bone Minion for G2F Poses
9. Run three of my nine Skateboarding animations
10. Load in my Cyberpunk'd Urban Sprawl 3

Get this:

Dartanbeck

I'll actually be demonstrating Bone Minion and how I use it - how much Power it gives us - in an upcoming webinar:

RiverSoft Art

Dartanbeck said:

I'll actually be demonstrating Bone Minion and how I use it - how much Power it gives us - in an upcoming webinar:

Looks interesting!  You make really amazing videos using Daz Studio.  Good luck!

crosswind

I'm also a heavy user of Bone Minion like Dartanbeck. However, it'll be great if both RiverSoftArt and ManFriday are in this thread... Up to date, that "conflict error" is still there in b/t Bone Minion and dForce Companion...

I cannot live on with DS without these 2 products but I don't know if there's any possibility this issue could be fixed or not...

The issue is : with a Minion and dForce item(s) on the figure, each item when switching to dForce Companion pane, this error pops up... (from a certain time I remember... but definitely not from very beginning when I started to use both Minion and Companion at the same time..)

PS1: I have to click Ignore (the 3rd button in the dialogue box) each time otherwise, DS session will crash...

PS2: I've not sent any ticket for this issue as I still can skip it by clicking the button. I hate sending ticket... In most of the issue cases, I fixed them by myself but this one relates to both Plug-in and Script, I could not...

RiverSoft Art

crosswind said:

I'm also a heavy user of Bone Minion like Dartanbeck. However, it'll be great if both RiverSoftArt and ManFriday are in this thread... Up to date, that "conflict error" is still there in b/t Bone Minion and dForce Companion...

I cannot live on with DS without these 2 products but I don't know if there's any possibility this issue could be fixed or not...

The issue is : with a Minion and dForce item(s) on the figure, each item when switching to dForce Companion pane, this error pops up... (from a certain time I remember... but definitely not from very beginning when I started to use both Minion and Companion at the same time..)

PS1: I have to click Ignore (the 3rd button in the dialogue box) each time otherwise, DS session will crash...

PS2: I've not sent any ticket for this issue as I still can skip it by clicking the button. I hate sending ticket... In most of the issue cases, I fixed them by myself but this one relates to both Plug-in and Script, I could not...

It looks like ManFriday's product does not like Bone Minion.  You see the assertion is coming from an "MF" (ManFriday) DLL.  I don't know what connection his DLL is looking for but I guess Bone Minion does not provide it.  This is something he would have to fix.

crosswind

RiverSoftArt said:

crosswind said:

I'm also a heavy user of Bone Minion like Dartanbeck. However, it'll be great if both RiverSoftArt and ManFriday are in this thread... Up to date, that "conflict error" is still there in b/t Bone Minion and dForce Companion...

I cannot live on with DS without these 2 products but I don't know if there's any possibility this issue could be fixed or not...

The issue is : with a Minion and dForce item(s) on the figure, each item when switching to dForce Companion pane, this error pops up... (from a certain time I remember... but definitely not from very beginning when I started to use both Minion and Companion at the same time..)

PS1: I have to click Ignore (the 3rd button in the dialogue box) each time otherwise, DS session will crash...

PS2: I've not sent any ticket for this issue as I still can skip it by clicking the button. I hate sending ticket... In most of the issue cases, I fixed them by myself but this one relates to both Plug-in and Script, I could not...

It looks like ManFriday's product does not like Bone Minion.  You see the assertion is coming from an "MF" (ManFriday) DLL.  I don't know what connection his DLL is looking for but I guess Bone Minion does not provide it.  This is something he would have to fix.

Yes, that was my thought as well. Thanks,  RiverSoftArt.

As Companion will check each item in the scene to acquire dForce related properties, however, it seems that Companion cannot get the info. from Minion(s) or cannot list Minion(s) in to its list of Figures, haha ~~

Anyway, just let you guys know about that...

RiverSoft Art

crosswind said:

RiverSoftArt said:

crosswind said:

I'm also a heavy user of Bone Minion like Dartanbeck. However, it'll be great if both RiverSoftArt and ManFriday are in this thread... Up to date, that "conflict error" is still there in b/t Bone Minion and dForce Companion...

I cannot live on with DS without these 2 products but I don't know if there's any possibility this issue could be fixed or not...

The issue is : with a Minion and dForce item(s) on the figure, each item when switching to dForce Companion pane, this error pops up... (from a certain time I remember... but definitely not from very beginning when I started to use both Minion and Companion at the same time..)

PS1: I have to click Ignore (the 3rd button in the dialogue box) each time otherwise, DS session will crash...

PS2: I've not sent any ticket for this issue as I still can skip it by clicking the button. I hate sending ticket... In most of the issue cases, I fixed them by myself but this one relates to both Plug-in and Script, I could not...

It looks like ManFriday's product does not like Bone Minion.  You see the assertion is coming from an "MF" (ManFriday) DLL.  I don't know what connection his DLL is looking for but I guess Bone Minion does not provide it.  This is something he would have to fix.

Yes, that was my thought as well. Thanks,  RiverSoftArt.

As Companion will check each item in the scene to acquire dForce related properties, however, it seems that Companion cannot get the info. from Minion(s) or cannot list Minion(s) in to its list of Figures, haha ~~

Anyway, just let you guys know about that...

I am curious.  Does it fail on Heavyweight Bone Minions or regular Bone minions?  It might be the Heavyweight Bone Minions, since they are real figures, might work.

crosswind

RiverSoftArt said:

crosswind said:

RiverSoftArt said:

crosswind said:

I'm also a heavy user of Bone Minion like Dartanbeck. However, it'll be great if both RiverSoftArt and ManFriday are in this thread... Up to date, that "conflict error" is still there in b/t Bone Minion and dForce Companion...

I cannot live on with DS without these 2 products but I don't know if there's any possibility this issue could be fixed or not...

The issue is : with a Minion and dForce item(s) on the figure, each item when switching to dForce Companion pane, this error pops up... (from a certain time I remember... but definitely not from very beginning when I started to use both Minion and Companion at the same time..)

PS1: I have to click Ignore (the 3rd button in the dialogue box) each time otherwise, DS session will crash...

PS2: I've not sent any ticket for this issue as I still can skip it by clicking the button. I hate sending ticket... In most of the issue cases, I fixed them by myself but this one relates to both Plug-in and Script, I could not...

It looks like ManFriday's product does not like Bone Minion.  You see the assertion is coming from an "MF" (ManFriday) DLL.  I don't know what connection his DLL is looking for but I guess Bone Minion does not provide it.  This is something he would have to fix.

Yes, that was my thought as well. Thanks,  RiverSoftArt.

As Companion will check each item in the scene to acquire dForce related properties, however, it seems that Companion cannot get the info. from Minion(s) or cannot list Minion(s) in to its list of Figures, haha ~~

Anyway, just let you guys know about that...

I am curious.  Does it fail on Heavyweight Bone Minions or regular Bone minions?  It might be the Heavyweight Bone Minions, since they are real figures, might work.

It's a regular Bone Minion.... You're right that there's no problem at all if it's a Heavyweight one. However, I only use regular Minion...

Dartanbeck

Bone Minion!!! 

Dartanbeck

Dartanbeck said:

I'll actually be demonstrating Bone Minion and how I use it - how much Power it gives us - in an upcoming webinar:

Corrected the (backwards! LOL) times I had on the video!

RiverSoft Art

crosswind said:

RiverSoftArt said:

crosswind said:

RiverSoftArt said:

crosswind said:

I'm also a heavy user of Bone Minion like Dartanbeck. However, it'll be great if both RiverSoftArt and ManFriday are in this thread... Up to date, that "conflict error" is still there in b/t Bone Minion and dForce Companion...

I cannot live on with DS without these 2 products but I don't know if there's any possibility this issue could be fixed or not...

The issue is : with a Minion and dForce item(s) on the figure, each item when switching to dForce Companion pane, this error pops up... (from a certain time I remember... but definitely not from very beginning when I started to use both Minion and Companion at the same time..)

PS1: I have to click Ignore (the 3rd button in the dialogue box) each time otherwise, DS session will crash...

PS2: I've not sent any ticket for this issue as I still can skip it by clicking the button. I hate sending ticket... In most of the issue cases, I fixed them by myself but this one relates to both Plug-in and Script, I could not...

It looks like ManFriday's product does not like Bone Minion.  You see the assertion is coming from an "MF" (ManFriday) DLL.  I don't know what connection his DLL is looking for but I guess Bone Minion does not provide it.  This is something he would have to fix.

Yes, that was my thought as well. Thanks,  RiverSoftArt.

As Companion will check each item in the scene to acquire dForce related properties, however, it seems that Companion cannot get the info. from Minion(s) or cannot list Minion(s) in to its list of Figures, haha ~~

Anyway, just let you guys know about that...

I am curious.  Does it fail on Heavyweight Bone Minions or regular Bone minions?  It might be the Heavyweight Bone Minions, since they are real figures, might work.

It's a regular Bone Minion.... You're right that there's no problem at all if it's a Heavyweight one. However, I only use regular Minion...

Interesting.  Well, at least you have a workaround to use both until ManFriday can fix his tool