Avimator and Qavimator responding slowly

Hi, this is a weird question and I am not sure if anyone has seen it. Recently both avimator and qavimator are responding slowly to mouse clicks. When I click on a body part it takes about 10 seconds for it to become selected and turn green. When I try to click on the background to rotate the avatar there are a few seconds of delay before it allows the mouse to rotate the avatar. Everything still works but it makes animating a lot more annoying now. Any ideas on what is causing this? All my other programs work fine. I just recently upgraded my ATI software. I've reinstalled both avimator and qavimator and still have the same problem.

Wow, SL's performance is getting so bad it's even lagging offline tools.

Hi Bree,
I use avimator to make poses and it has been extremely laggy lately and the poses I have uploaded have been twitchy or shift often into other poses. It is quite frustrating. The program stalls, i can't move the av around as easily as I used to be able to. I'm surprized you are still able to make poses, I am not as patient.
I have unistalled it/reinstalled..cleaned my comp, rebooted etc. nothing seems to help.
It seems to work on the other computer in my house, but the uploaded poses are shifty there as well. and i dont always have access to that puter.
Are there any other free pose programs to use besides avimator and qavimator?

thanks,
hazel

well there's SLAT and there's DAZ. I haven't used either but I might try them. I think I might just put avimator on my older computer here. I really have no clue why it's running this way. It's as if the mouse is not being tracked properly. When I click on a limb in qavimator the mouse pointer will jump to the center of the avatar's body an then jump back to the limb I clicked.

I've never tried SLAT, but I can wholeheartedly recommend DAZ. I've been using it for my own animations for well over a year now, and while it's not perfect (nor arguably as powerful as Poser) it's quite capable and has several useful features that QAvimator doesn't. Active Pose and Puppeteer alone make it extremely useful, and you just can't beat the price (free, just like QAvimator).

I've used QAvimator, I think it's great for what it is, and I think it's wonderful that someone was willing to spend the time and effort to make it, but it's pretty limited.

.

So... any chance for making a tutorial for how to animate using Daz? Active pose and puppeteer? Sounds interesting.

Actually, I have noticed that same slowness in QAvimator recently. It's odd.

Hey Bree,

I just had this problem a few weeks ago and it seems to be related to video drivers. QAvimator became laggy when I updated my drivers for the new SL client. I rolled back the drivers and AQvimator started working again but now the SL client glitchs. It seems that that you have to make a choice one or the other but not both...I choose QAvimator.

I am running a RADEON x300/x550 Series card...also ATI based so you maybe having the same problem.

I was afraid someone would say it was the drivers. I guess there's not much that can be done unless the driver's get updated again and avimator magically starts working again. I have a 2nd computer and avimator runs perfectly there. I'll be using that for now.

oops, sorry, I missed your question...

I've been meaning to make a tutorial, I just haven't found the time. There's a small tutorial, not really in-depth but covers the very basics, at http://secondlife.dolphpun.com/daz3d/

If I can find the time to make my own tutorial in the near future, I'll come back and update this thread.

I find this is generally an OpenGL window issue.... that somehow tangles with Second Life.

You can generally solve it by running your animation/3D application first, and then Second Life.

You'll find both will run perfectly well together as long as Second Life is not running before you start either. If you start them with Second Life running first, many will be choppy or respond very slowly. Sometimes, re-starting the application a few times will help as well..... but it's just easier to close Second Life, run your program, then run Second Life.