Tried that, report was discarded as it was unrepeatable.
Well, it’s not always repeatable for me, but today it’s there so I made a couple of quick animated gifs from some screenshots:
It’s not a major thing, but it’s is pretty annoying when you are tweaking a CP closeup and “zip!” your model dissapears from view and you have to find it again.
Of course posting about it here is a complete waste of time since no one from Hash is reading and it’ll never reach their eyes this way either… cough
Oh yeah. I have that too…the odd time. It’s gone since I followed Johns advice of closing the open chor (Thanks John). It looks like you have some open.
I have had this happen to me as well. But. . . its not really a show stopper so I never worried about it much. You should probably submit your findings to Hash directly though. Those are some pretty clear images describing the problem.
Something else I wonder if they’ll ever fix is the dimples caused by hooks in toon render
Obvious workaround: Don’t use hooks. 
I have had this happen too, the problem is if your hook is not directly in the middle of the two control points.
Right now your hook is closer to one than the other.
Just detatch and reattach closer tot he middle ofthat spline segment.
Mike Fitz
www.3dartz.com
Good call Mike. I can’t say I’ve ever noticed this dimple effect…but I usually put hooks in the center.
That’s strange - when I group select a section and turn the model, I find that my model finds another pivot.
BTW, I have only the modeling window open, and the model is centered exactly at the zero point.
Strangely enough, when I select a single CP, it stays centered. ( !?? )
Do any of you have advice for modeling with multiple ( modeling )windows open ? ( Front, side, top etc. )
When I do so, I find that moving a CP in one window causes totally erratic CP movement in the other views.
Has this been fixed in the current version ?
Thanks
Yeah, I believe the 4 window thing is fixed in the latest version. I had the erratic pivot point a while ago but not recently.
I realize that there will probably never be a Linux version of A:M, but have there been any mention of Netrender for Linux?
Ooo, so it is. Thank you, I have centered hooks that don’t cause this, but I’d never made the connection.
Cool.
Here’s a couple more little issues: When I render a frame range different from 0-end, say for example I render 0-40 then 40-90 the on screen playback for the rendered file does not work, AM sticks on 40 and will not playback. It’s simple enough to just open the file in mediaplayer, of course.
Then there’s some sort of focusing issue that is probably related, after I render the play button is greyed out. Actually, I think it’s related to the greyed out button, to get it to un-grey I have to click on a model window to “unfreeze” it, and when I go back to the choreography the playback is running through the timeline.
Anyone else get this?
No.
Of course Netrender has 3 components: Server, Messenger and Renderer. I assume you mean just the server component? I shouldn’t imagine it would be too difficult for a competant programmer to replicate the functions of the server but since the Renderer is still PC based - well what would the point be?
Cheers
No, I’m talking about the Messenger and Slave. The documentation is a little fuzzy imo, but I’m assuming that you can have unlimited Slaves for each Server? If so, I don’t want to buy copies of XP or 2000 simply to do one thing, which is render. I can buy the actual rendering hardware nowadays for less than a Windows license. Furthermore, all production network rendering has a Linux option it seems.
But then I read the Hash faq about Netrendering "Hash does not like to sell NetRender. Setting it up requires knowledge and experience well beyond the competence of most casual computer users. Also, fixing bugs in NetRender is our LOWEST priority. HOWEVER, NetRender is part of the “Big Picture”, (you know, someday we’re going to make another movie), so we continue to work on it.
Well, at least they're honest. :)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.