-
Posts
28,095 -
Joined
-
Last visited
-
Days Won
365
Content Type
Profiles
Forums
Events
Everything posted by robcat2075
-
Can you explain a bit about what you are wanting to do?
-
Prehistoric! Image Contest! Deadline December 20!
robcat2075 replied to robcat2075's topic in Animation:Master
Two months to go on... Prehistoric! -
-
We were talking about overlapping motion in DavidDenzill's recent thread. This PRJ lets you experiment with overlapping motion and quickly see the result. HeadBanger03.prj open the PRJ open Action2 and look at it from a side view. I have keyframed the two extremes of a head-banging motion on Rabbit... up-down-up-down-up-down... play it! It's motion but it's stiff! Next, grab the keyframes for Head and Neck and slide them a couple frames later. (Hold down the SHIFT key and drag a bounding box around the keyframes you want to move.) play it! Suddenly, what was stiff is now flexible! Try three frames... four... five... how floppy can you make it? Keep going until you go too far! What happens if you go in the opposite direction? There's lots of places for overlap in a motion like this, the head/neck is just the start. Notice how the ears, which are not animated at all, look stiff as a board on that flexible head!
-
3D printed animatronic characters! That interests me greatly! I shall be eager to see updates on this.
-
Planes Trains Automobiles Image Contest Results!
robcat2075 replied to robcat2075's topic in Contests/Challenges
They're in the Mail! The High-5 and Top-10 certificates-so-suitable-for-framing-that-you-get-a-dollar-to-buy-a-frame are in the mail. Now I need to figure out the medal! -
Hi David, I enjoyed your videos! Don't feel bad about having to cut corners. Animation is a daunting endeavor. An L.A. studio owner once said "The worst animations are the ones that don't get done." Is that your band? Your songs? Are those characters caricatures of the band members? "stiffness" is more a matter of animation than a rig. When a motion appears stiff it is usually due to a lack of overlapping motion. For example there are lots of "head banging" motions in your videos. The head and torso are starting and stopping at the same time but if the head motion lagged the torso by a few frames it would appear more flexible and more weighty. Think of it as the head being lead around by the torso but always a bit behind. The whole body is like that, things being led by other things and alwasy trying to catch up. BTW, i noticed the mention of "paleo" diet. You might be interested in the current "Prehistoric" Image contest. See the link in my signature!
-
Here's what i don't understand. This same window popsup in Netrender to choose a network location of IO plugins but it is also going to assign a drive letter, unlike the window where a network location for slaves was assigned. You can set this alternate path but how do you get the slaves to use it?
-
Oh cool. It turns out someone else just had this problem...
-
-
For simplicity of maintaining the system. You only need to ever update the main computer if everything comes from there. That was the premise of Jody's PDF. If it can work that would be the way to go.
-
Finding plugins (especially Image IO plugins, needed to save a render) seems to be problem for slaves on machines that don't have an actual directory of A:M installed. Is there some way using "folder paths" (?) or shortcuts to make the slave look across the network to the A:M folder installed on the main machine for additional items it needs? If C:\Program Files\Hash Inc\V19.0\ImageIOS doesn't exist on the slave machine can we make it look to \\MainComputer\AMRoot\ImageIOS ? There is an "override plugin folders" option in Netrender but that doesn't seem to work the same as the "override slaves" option, which was able to get the Render Messengers to pull their slaves from the main computer instead of needing them locally.
-
New problem... They render but they don't save the image. 😀 I'm sure there's a solution.
-
The test i did last night was when i still had A:M installed on the remote PC. But according to the plan in Jody's PDF everything is supposed to come from the server, So I uninstalled A:M from the remote computer. With A:M gone from the remote computer, The rendermessengers are still properly pulled from the main server and run on the remote computer, according to plan. However, the RenderMessengers are still looking for RenderSlaves on a hard-coded path to a C drive, which won't exist on the remote computer. How do I get the messengers to properly look for RenderSlaves in the network shared folder \AMRoot? Update.... I can on the remote slave in Netrender and choose "Change slave exe" and choose RenderSlave.exe from the networked folder. Now it renders! But what do i need to do to make this happen automatically, so i don't need to rechoose every slave every time I run Netrender?
-
It's a very simple test project. It is baffling because the same project worked before I changed it to render with AO. IT has to be the same version of Netrender since everything is coming from the AMRoot directory on the server
-
If a Project loads and renders OK in A:M, what makes a render node decide it is "Invalid"? The nodes that are on my server computer still render it fine, but the remote node can not. On the Render Server display the nodes is just perpetually stuck at "Loading frame" with no error reported.
-
Hold everything... I think it's working! I've got some manually started nodes doing something on both computers. Thank you Gerald, Steve and Jason for your suggestions. I think there were three cascading problems... p2p services not getting started when my computer booted up each computer had it's own "HomeGroup" although Netrender can see nodes on a remote computer that were started from one of the remote computer's folders, those nodes can't seem to understand paths to PRJs. If i navigate from the remote computer to the AM folder on the main computer and start a RenderMessenger, that will load/run on the remote computer AND be able to load PRJs via a network path.
-
I got the p2p services "started" The problem with Homegroups seemed to be that each computer had one established but they were not the same Homegroup. I killed one of them and joined the other and now I can indeed see shared folders remotely. However, my remote Netrender node still is "unable to load Project." I did this and now there is a user named "Remote01" on my main computer but... that doesn't seem to change anything about my remote computer.
-
My account name on the remote computer(named "Brent-PC)" is "Remote01". I changed it to that because my account on my main computer was already "Robert" On my main computer , when i try to "Share with" the folder i want to share, I am unable to add anything from the remote computer. It does not appear in a search of the network, even though it does appear in the "network" in Windows explorer.
-
When i run the Windows Networking "troubleshooter" on my remote computer, it says I don't have permissions to access the folder I have shared. What more permissions can i give than the everything and everyone I have already given?
-
I've made a folder on my main computer (Q6600) on the C drive called "Frames" It is shared with the name "AMData" Its permissions are set so that anyone can do anything to it... NetRender aside... I should now at least be able to see that shared folder on "Q6600" over the network from my remote computer "BRENT-PC" From my remote computer "Brent-PC" the network can see that there is computer named Q6600, but I can't access anything in it, not even the folder that is shared. This is true even if I turn off the Firewall on both computers. What is missing?
-
The core problem seems to be that if i browse the "network" from my remote computer, I can see my server computer on the network but can't see any of the public/shared folders it contains. It's some sort of permissions problem.
-
So far, all of my remote nodes are still "unable to open project"
-
The hair... sort of reminded me of hair on a porcelain figurine. It is like the exterior volume of the hair without being every strand. That is neither good nor bad, I saw it as a style choice.