Results 1 to 7 of 7

Thread: DPKit MDD Pointer: time input ???

  1. #1
    Axes grinder- Dongle #99
    Join Date
    Jul 2003
    Location
    Seattle
    Posts
    14,726

    DPKit MDD Pointer: time input ???

    An enveloped scalar input on the Time input to MDD Point should work just fine, right? And it's in frames, not seconds?

    tnx!
    They only call it 'class warfare' when we fight back.
    Praise to Buddha! #resist
    Chard's Credo-"Documentation is PART of the Interface"
    Film the cops. Always FILM THE COPS. Use this app.

  2. #2
    Registered User
    Join Date
    Oct 2006
    Location
    London
    Posts
    1,013
    It's in seconds NOT frames.

    so a scalar value of 1 = 1 second


    Just did a quick test on demo of LW11 and seems to work as expected.

    Are you having difficulties?
    Last edited by littlewaves; 08-03-2012 at 08:39 AM.

  3. #3
    Red Mage Celshader's Avatar
    Join Date
    Feb 2003
    Location
    Burbank, California
    Posts
    1,817

    Lightbulb

    Quote Originally Posted by jeric_synergy View Post
    An enveloped scalar input on the Time input to MDD Point should work just fine, right? And it's in frames, not seconds?

    tnx!
    As an alternate in LW10+, try this Michael Wolf trick:

    1. Use the native MDD Displacement node or MD Reader.
    2. Set the Time Scale to 0%.
    3. Envelope the Frame Offset.


    With this method, a value of 1 means "frame 1" and a value of 100 means "frame 100." So you can envelope the playback using the native toolset.
    Jen's 3D -- LightWave stuff.
    Jen's 2D -- my comic book.

    Python is my smashing board. LightWave is my S.M.A.K.

  4. #4
    Axes grinder- Dongle #99
    Join Date
    Jul 2003
    Location
    Seattle
    Posts
    14,726

    Lightbulb Fracture> Bullet> ClothFX> MDD_Pointer> bed :+DPKIt feature request

    Quote Originally Posted by littlewaves View Post
    It's in seconds NOT frames.
    so a scalar value of 1 = 1 second
    Just did a quick test on demo of LW11 and seems to work as expected.
    Are you having difficulties?
    Ahhh, thanks for that clarification.

    Feature request! (of course!): a frames input.*

    I was having difficulties, but it was late. Using Bullet for the first time, I dropped some letters to shatter. Used ClothFX to scan their motion, playback thru ClothFX, with Bullet disabled, seemed to work great, but although I thought there would be a simple envelope in the ClothFX mdd playback panel, I couldn't find it.

    So, I loaded up the (native) Displacement node editor, added DPKit MDD_Pointer, and ran that, ClothFX disabled. Everything still seemed to work, so I added a Scalar node and tried to run it backwards. Things fell apart there, and I had to hit the hay.

    My misunderstanding of the TIME input is no doubt part of the problem, I'll try again today. Thanks!

    RE: the feature request: as an animator/video guy/dog sitter, I just naturally think in FRAMES rather than seconds. It would be awesome if, over the course of his maintaining and upgrading his nodes, Denis added FRAME inputs alongside all the DPKit TIME inputs. I'm sure it would simplify/clarify some node networks and effects too.

    Basically, anywhere a TIME input exists on any plugin, not just Denis' work, I'd like to see a FRAMES input.
    Last edited by jeric_synergy; 08-03-2012 at 10:14 AM.
    They only call it 'class warfare' when we fight back.
    Praise to Buddha! #resist
    Chard's Credo-"Documentation is PART of the Interface"
    Film the cops. Always FILM THE COPS. Use this app.

  5. #5
    Axes grinder- Dongle #99
    Join Date
    Jul 2003
    Location
    Seattle
    Posts
    14,726

    backwards MDD via DPKit: like a charm

    Thanks, Jen, didn't see your post last time! That's good to know: it's conceivable that I'd have to do this (ha!) effect somewhere without DPKit in their arsenal. (I wish.)

    The whole "1=100" thing sets my teeth on edge. Oh well.

    Littlewaves: correcting for my previous blunder, worked like a charm. Thanks! And thanks to Denis for making such awesome nodes!

    ++++
    EDIT: wouldn't you know it: when back in, halved the gravity, scanned it, crash!
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	backwardsMDD.jpg 
Views:	72 
Size:	118.0 KB 
ID:	105941  
    Last edited by jeric_synergy; 08-03-2012 at 09:50 AM.
    They only call it 'class warfare' when we fight back.
    Praise to Buddha! #resist
    Chard's Credo-"Documentation is PART of the Interface"
    Film the cops. Always FILM THE COPS. Use this app.

  6. #6
    Red Mage Celshader's Avatar
    Join Date
    Feb 2003
    Location
    Burbank, California
    Posts
    1,817
    Quote Originally Posted by jeric_synergy View Post
    The whole "1=100" thing sets my teeth on edge. Oh well.
    That's not what I wrote:

    Quote Originally Posted by Celshader View Post
    With this method, a value of 1 means "frame 1" and a value of 100 means "frame 100." So you can envelope the playback using the native toolset.
    1 does not equal 100. 1 equals 1, and 100 equals 100.
    Jen's 3D -- LightWave stuff.
    Jen's 2D -- my comic book.

    Python is my smashing board. LightWave is my S.M.A.K.

  7. #7
    Axes grinder- Dongle #99
    Join Date
    Jul 2003
    Location
    Seattle
    Posts
    14,726
    Quote Originally Posted by Celshader View Post
    That's not what I wrote:
    My apologies: I was just going back to delete what I wrote 'cuz I saw I got it perfectly backwards, but ya beat me there.

    That's a very slick trick. Thank you!
    They only call it 'class warfare' when we fight back.
    Praise to Buddha! #resist
    Chard's Credo-"Documentation is PART of the Interface"
    Film the cops. Always FILM THE COPS. Use this app.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •