What about this bug then?

[3DArtZ]

what keys do you have activated at the bottom of the screen when you do this cut?
If you have key model, bones, muscle and all then all that stuff will be cut. If you only have specific ones activated then only these elements will be affected by the cut,copy,paste functions.
Mike Fitz

[Bugle]

That's the whole point - the bone rotation , scale & etc keys are greyed out when you are in muscle mode, they're not supposed to be affected, and I'm pretty sure that's how it used to be in 8.0 but now you have to tick them off on purpose before going into muscle mode to do a cut or copy operation involving CPs

At least that's how it works in an action window, I just tried it - muscle mode, bones not affected by cut, choreography, bones are affected by cut.

[3DArtZ]

Hmmm, well maybe it is infact a bug or an oversight by the programmers. Send it in and you'll get your name in lights.... or at least on the upgrade bugs fixed page!
Mike Fitz

[Bugle]

Been there a few times, but I'm afraid the Sappington aversion therapy makes emailing them a chore. Be my guest. Or whoever wants the "glory"...

[3DArtZ]

Want Steve's attention? Go and drop an email bomb on the hash forum a-la Mike Fitz style and they'll be intouch real soon.
Mike Fitz

[Bugle]

You did what now?

[3DArtZ]

Usually happens after an evening hanginout with Captn Morgan, I would go and drop a "ruff" email voicing my displeasure with some feature or another. Usually would be a good way to get your point noticed. However I have refrained from that stuff as of late, really cause I think hash is doing a good job at getting the app up and running strong.
I compared the speed of it's render to that of RayDream studio, once in a forum email, putting things into a negative light.
Mike Fitz

[JBarrett]

Originally posted by Bugle
At least that's how it works in an action window, I just tried it - muscle mode, bones not affected by cut, choreography, bones are affected by cut.
Personally, I avoid cutting any kind of motion data. I prefer to copy it, then paste it at the target time, then go back and delete the old version if I really didn't want it there.

Yeah, I know, you *should* be able to cut and not have problems. So bite the bullet and send in a bug report. I've never had a problem with bug reports, in terms of getting a harsh response or anything. Personally, I feel the key to bug reports is to remove all emotion from them. Simply list the facts as specifically as you can, in as much detail as you can, after making several tests to make sure you know exactly what causes the problem. Just say, "Here's my system setup, here are the steps I take, and here's what happens." If there's any name calling or rough language (even simply venting frustration), you're less likely to get help.

Treat folks with respect, and they'll most likely do the same in return. Not trying to imply that you don't do this already, but I'm merely pointing out what has worked for me.

[Bugle]

Oh I do that, I even try to convince myself that "suport@hash.com" is an independent entity with no relation to human beings. What killed my enthusiasm this time round was getting reports rejected because there were more than one bug per email. Cue biting of fingers to avoid typing things like "I'll report bugs one at a time when I only find one bug per session" or suchlike.

So that's why I'd rather post them here, get some human simpathy from fellow users (Or at least confimation that I alone experience 'em). And let someone else get the "glory".

Mike> You're a brave man :)

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.