How to unhide an ActorBody (and the rest)?

#1

Hello,

I have two questions about strange MotionBuilder 7.5 Extension 2 behaviors.

  1. I’ve hidden an ActorBody because it covered motion capture markers. Now I want to unhide the ActorBody (and other things I’ve hidden) by clicking in the Viewer window Display > Unhide unselected (or Unhide selected), but nothing happens.

Do you know how I can unhide everything?

  1. I’ve attached the markers to the marker set from my Actor. However, the animation playback is problematic. In many cases it plays well, but in other cases it just doesn’t play (only the timeline scrubber moves). And many times the timecode counter flies to absurd numbers (like 15879) while I only have 50 frames.

Does this sound familiar to you?

Thanks for any comments.

Fernando

#2

Hi fernando749845,

  1. U can control actor body visibility from Show context menu in Character Controls window.

  2. I think that your problems are connected to your hardware.

#3

Thanks Neill, that helped. I’m trying different nVidia drivers now, but without success yet.

If I switch on the ‘loop’ function, shouldn’t MotionBuilder repeat those 50 frames again and again? Can I assume that this works in your application?

Thanks,
Fernando

#4

I have tried working in MB on NoteBook (Acer, Core2Duo 1.66, NVidia 7300) and there was the playing problem like U has. So, It gives me possibility to think that CPU can make trouble in playing animation in MB.

#5

Hello, guys,
I’ve got the same problem with my book! Configuration is
Notebook Acer Extensa 5620G-1A1G12Mi
[size=2]Intel Core 2 Duo T5250 (1.5 GHz/ 2 Mb/ FSB 667), ATI Mobility Radeon HD 2400 XT with 256 Mb memory.
It demands Video driver [size=2]ATI Catalyst 7 and higher. And MB doesn’t play correctly with this driver. Animation is jerking and stopping in viewport. And I cannot select the rotation gizmos in the viewport by clicking them…
So, I guess, have to wait till either catalist or MB solve this problem.

Regards

[/size][/size]

#6

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.