Welcome to od|forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

eddgarpv

Members
  • Content count

    13
  • Joined

  • Last visited

Community Reputation

1 Neutral

About eddgarpv

  • Rank
    Peon
  • Birthday August 16

Personal Information

  • Name
    Edgar
  • Location
    Mexico
  1. Thanks Matt, it is even more clear (I'm right now at the orient, matrices, quaternions and stuff ) Fuat: works good too, I'll see how much it changes within the dop network and constraints
  2. Hello, I'm trying to do the same (get rotation) following Matt's suggestion but for some reason, there is a weird flip at some point in my orient attribute. I know I'm missing something, it's just I'm not really familiar with vex. Already tried a couple alternatives but this one looks more clear to me. I just wanted to create constraints and one thing leads to another I guess . test_constraint.zip
  3. I know this is an old post, but just recently had the same problem with a fresh centos 7 install (debian was working perfectly, but had to switch). Anyway, the problem was I had a firewall running in centos. Disabling this solved that 'Unicode: need string' error. I can't restart nodes using the web interface but I can ssh to the nodes. There may be another security option that may be causing this but I still have to find out. Hope this helps somebody in the future.
  4. Cool example! adding a trail for velocity makes it look super sexy.
  5. Ah, that was the problem. Adding that option solves the issue... thanks John!
  6. from support: The issue that was causing the incorrect shading was related to ray continuation. Some of the tracking of ray distances was off, resulting in ray continuation beyond the far clipping plane. This issue has been resolved for our Houdini 15 release.
  7. Submitted to support. I tried using deep comp but for this particular shot, it was too much (of disk space and nuke script setup). I've found that this problem happens when there is no density field in the volume. If I create a primitive called density and copy heat to it, it will clip the volume just fine. http://i.imgur.com/zrODQKX.png I ended up using matte objects for the front, but now I know how to solve it.
  8. That is amazing. You guys have been busy. Congrats.
  9. Hello, I'm trying to use near/far clipping planes on a camera to render a volume and comp something in the middle.. the problem is, when the far clipping plane is in the middle of the volume (i.e. the front part of the fire), the far clipping plane is ignored. If the volume is hidden, I can get the front part clipped. Right section of the image is using the same far clipping plane as the left part, just with a hidden volume. I'm not really sure if I should add something else to the ROP, so any hint is appreciated Here is the indie file and bgeo. thanks!
  10. cool videos, thank you!
  11. https://www.youtube.com/watch?v=x-_-uNhnXQU
  12. I have the same problem: a crashing mantra render at random frames when reading bgeo files but without compression. Already reported (using 13.0.582). An alternative could be caching sim files instead (probably this is the correct way to do it?)
  13. Thanks for the scene, Ian. I thought I could get a continuous motion using the ocean spectrum's Loop Over Time checkbox