Jump to content

Hey, you need a renderfarm? If that's the case, make sure you check this topic for more info! 


jed

Bronze Supporter
  • Content count

    1,167
  • Joined

  • Last visited

  • Days Won

    12

jed last won the day on July 7

jed had the most liked content!

Community Reputation

320 Excellent

3 Followers

About jed

  • Rank
    jed
  • Birthday 12/22/1949

Profile Information

  • First Name
    Gerald
  • Last Name
    Scruton
  • C4D Ver
    19.053 Studio
  • Location
    Manchester, UK
  • Interests
    building + repairing computers, C4D
  1. Not sure why your baking went wrong. Did you disable any XPresso or Python after baking ? My usual method is to drag everything into the dope sheet, and with all items selected go Functions, bake objects, select all parameters, disable make a copy, click OK to bake the keyframes. Then I disable anything and everything that can move stuff - like dynamics, Python, aim constraints etc. If the anim scrubs forwards and backwards, I assume it's OK.
  2. Xpresso, iterate points problem

    I think the 1st point node that you're using to get the count is somehow messing things up (possibly because it's set to point_0). If you set the iteration manually to 1 - 5, you can move point_0 in X, Y and Z. spline_points.c4d
  3. Just a name mix-up. I think you were using set driver, which puts the XPresso tag on the object in question. This is OK for a one-off, but when you want to control many things, you end up with a lot of separate XPresso windows. Better to write your own XPresso as per @HSrdelic's reply. Also, with complex scenes, you sometimes get priority issues (lag etc). You can often solve this by moving things around in the object manager - things at the top are processed first. This can be a problem when the set driver tags move with their objects - it also changes the order the XPresso is calculated.
  4. I also noticed that 'feature' when the new cog tool was released (a few versions ago). I guess that's just how it works.
  5. Which scene are we talking about ? If you mean how to do the speed thing on the math version in python - piston-trig2.c4d
  6. Do you mean setting the rotating part to 0 deg ? Sometimes you need the animation to start at a certain position, but for things that don't really matter like helicopter blades, you can leave out the 'zero at F0' part of the XPresso. When you rewind the time to F0, the rotation will 'stick' from the last position. C4D don't seem to mind if rotation is 0 or 30,000 deg. BTW I made a piston scene using the math. I used Python because it's easier to type in the equation, compared to hooking up a load of nodes in XPresso - less chance of errors. piston-trig.c4d.
  7. @natevplas - it's good for helicopter blades @ryantscott - your method of moving the pistons using rangemap is linear, which is incorrect - that's why the conrods drift with respect to the pistons. The actual math uses sin, cos and Pythagoras, but as 3DKiwi says in the video, using his constraint method does the same job (but is still accurate). That's why I described his method as 'clever'. Here's the math 3DKiwi refers to - I think I'll change my username to Mr Pedantic ...
  8. @natevplas is correct - use addition to generate rotation. The amount added per frame is the 'speed' - small value = slow, large value = faster, zero = stop. Will slow down without going backwards. Due to addition, the rotation sticks when you rewind the timeline, so I put a zero @ F0 bit in. You can also use this zero part to set the start position. Pistons_ForCafe2.c4d edit - this clever method by @3DKiwi to get piston movement might interest you https://www.dropbox.com/s/3wgfna8ju5s91yl/3DKiwipiston.zip?dl=1
  9. I had a go at making the perpetual motion desktop toy from Iron Man 2 - you can buy them from Swinging Sticks. Here's an explanation of my approach here's a render scene sticks.c4d might amuse someone
  10. Xpresso workflow speed up

    I don't use set driver, but I understand the nodes in the generated XPresso somehow get their name from what the XP tag is attached to - which means copy and pasting all your various bits of set driven XP into one window would probably break things. Much better to write your own XP and put the tag on its own null. This way you can also fix priority problems by re-arranging the object manager order. Re: names - if you rename an object in the OM, the resulting node takes that name. Tags can be renamed in attribute manager basic > name, which shows up in the XP window eg change 'Align to Spline' to 'Camera 1 align to spline'. You can also rename some (not all) of the XP operators in the AM eg change Compare to 'Compare != 0'. I also recommend using remark nodes (under general) for comments.
  11. Nice deal for future tutorial creators

    On the subject of cheap, I have Camtasia and for audio I use a Microsoft USB LifeChat headphone + boom mic. Has an inline amp so you can hear your voice through the cans without any delay (a common Windows problem). Amazon UK do them for about £22 link. I've only used them on Windows - can't vouch for Mac.
  12. AFAIK set driver, set driven gives a 1:1 linear mapped correspondence between the 2 angles in question. I think your assumption that you can do this and the distance between the 2 levers (the connector rod) will remain constant is incorrect.
  13. Looping a Set Driver/Driven

    @BLSmith see pm about 719 degrees
  14. Looping a Set Driver/Driven

    My gut reaction is that the cogs will both next be in their start positions when the 39T cog has turned 28X and the 28T cog has turned 39X. At your speeds this will be at 2800F. If the small cog is symmetrical, so that 0 deg and 180 deg are identical, they'd line up at 1400F. I made a rig to test this. If you drag the timeline slider (it's keyframed), you may find a lower frame position where align is acceptable within limits. cogs2.c4d edit - if the large 39T cog has no irregular stuff attached ie it's just symmetrical with respect to the teeth, you could maybe drive the thing from the smaller cog. One rotation of the 28T cog is a whole number of teeth on the 39T cog, so would appear to loop. In this file, the 28T rotates 716.4 deg in 199F (would also work for 99F). https://www.dropbox.com/s/51fl0jnzfa3mgle/cogs4.c4d?dl=1 (BTW - I'm not too sure about your 719 degree thing) one of my cog experiments
  15. Creating an audio spectrum

    I used to play around with audio spectrum analyzer, using various methods - XPresso + Python. I used to make one channel, and just duplicate it say 8 times, setting the channel frequency and width individually and using count to drive the number of LEDs etc. I see you're on R15 (which has inferior sound effector to R19), so here's some things to bear in mind - Graphic EQ + spectrum analyzers have the frequency in octaves eg the freqs will be 32Hz, 64Hz, 125Hz, 250Hz, 500Hz, 1KHz, 2KHz ... etc. This is how the human ear hears music ie middle C to top C (8 notes on a piano) is a double of frequency - one octave. The sound effector display in AM is linear, so if you arrange bands equally using the effector panel, all the music will be in the 1st channel. The standard method of cloner and scale (on older versions of C4D) doesn't represent what a real graphic display looks like - it just somehow jumps around in time to the music. R19 is better in this respect. In old R15 sound effector, the freqs in the panel are way out - often by as much as 2X ie 1K in sound effector is 2K in real life. I made some test tones to calibrate the channels (you can download test tones also). When you have say 8 bands ready for testing, disable the sound from all but one, else you'll get scrambled audio. The upper freq ranges work OK in the sound effector, but the bass end is very flaky - needs careful tweaking. A display looks best when there's widely separated chunks of music - bass, space, treble, space etc. Most pop music is so compressed and levelled out, there's nothing interesting to see. I used to use dub reggae as a sound source. Here's one I made using the cloner count method and a reggae tune -

×