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.

XRM

Members
  • Content count

    40
  • Joined

  • Last visited

Community Reputation

7 Neutral

About XRM

  • Rank
    Peon

Contact Methods

  • Skype ranadeep.vfx

Personal Information

  • Name Ranadeep
  • Location India

Recent Profile Visitors

2,248 profile views
  1. Maybe your source node has time limited by expression. Check your source node. If that is not the case share your file here. I can have a look. Ranadeep FX TD @dNeg
  2. Hi everyone,I was trying to achieve a bullet passing through high viscous gel. I started with a keyframed bullet which passes through a flip cube. I am using the suction force option to make the flip particles retain shape. I can't get it right at all. Always particles are bursting out. I am attaching an youtube link to the reference. Ranadeep FD TD Dneg
  3. Hi fellow FX artists. I was recently doing a sim which required viscous liquids. I wanted to try the opencl option with helps to calculate pressure and viscosity on a graphics card. I am getting this error c:\workarea\16.15.2211\stream\opencl\compiler\clc2\ocl-headers\build\wNow64a\B_rel/opencl12_builtins.h:14603:36: note: candidate function not viable: no known conversion from 'const __global fpreal *' (aka 'const __global float *') to 'const __local half *' for 2nd argument half __attribute__((overloadable)) vload(size_t offset, const __local half *p); ^ c:\workarea\16.15.2211\stream\opencl\compiler\clc2\ocl-headers\build\wNow64a\B_rel/opencl12_builtins.h:14609:36: note: candidate function not viable: no known conversion from 'const __global fpreal *' (aka 'const __global float *') to 'const half *' for 2nd argument half __attribute__((overloadable)) vload(size_t offset, const __private half *p); ^ error: Clang front-end compilation failed! Frontend phase failed compilation. Error: Compiling CL to IR clBuildProgram (-11) OpenCL Exception: C:\Users\Ranadeep\AppData\Local\Temp\\OCL9128T41.cl:286:27: error: no matching function for call to 'vload' fpreal dq_blend_weight = vload(i, dqLW); My version of Houdini is 15.0.244.16 This use to work fine on houdini 14. Graphics info is below OpenCL Platform AMD Accelerated Parallel Processing Platform Vendor Advanced Micro Devices, Inc. Platform Version OpenCL 2.0 AMD-APP (2004.6) OpenCL Device Hawaii OpenCL Type GPU Device Version OpenCL 2.0 AMD-APP (2004.6) Frequency 947 MHz Compute Units 40 Device Address Bits 64 Global Memory 4096 MB Max Allocation 2880 MB Global Cache 16 KB Max Constant Args 8 Max Constant Size 64 KB Local Mem Size 32 KB 2D Image Support 16384x16384 3D Image Support 2048x2048x2048 OpenCL Platform Extensions: cl_khr_icd cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_amd_event_callback cl_amd_offline_devices OpenCL Device Extensions: cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_khr_gl_depth_images cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_khr_image2d_from_buffer cl_khr_spir cl_khr_subgroups cl_khr_gl_event cl_khr_depth_images cl_khr_mipmap_image cl_khr_mipmap_image_writes Please if someone has a workaround let me know. Thank you
  4. Check the attached image. Turn that option on. It shows the collision sdf volume. I am sure the volume is not correct. Cheers!
  5. Asus AMD R9 290 4GB opencl - 01:09:51 Intel i7 4930k - 01:37:53 Rest configuration 256Gb SSD Gigabyte x79 UP5 64 GB DDR3 2133MHz
  6. you were right edward. My graphics drivers were set to autoupdate. Reverting back to the previous drivers fixed it.
  7. The scene files are opening fine in the other systems. There is not problem with it I am sure of it. Even if I just add a box and then connect it to a vdb to polygons node, I can see this problem. I am on windows 7, Houdini 13.0.547, AMD R290 with latest drivers. It was working fine. I can only think of formatting and installing everything fresh again.
  8. Nothing. It just started happening all of a sudden. I even tried restoring and also deleted the houdini13 preferences folder from my documents folder. I even re installed the graphics drivers. All in vain.
  9. Hi, recently I am facing this issue. The display of sdf and distance vdb is always corrupted in the viewport. I've attached an image. Does anyone know how to fix this?
  10. Yes I am talking about point renders not mesh.
  11. That will again will be waste of time as the combined cache size per frame is more than 10 Gb. If I have to load everything why wouldn't I just render it instead of saving. You see delayed load is used to cut down the RAM usage.
  12. Hi all, I've this huge FLIP sim which I've distributed on 10 farm systems to sim. Now I am able to load them using the loadslice node that houdini creates for distributed sim cache loading. What it does is it basically loads each and every slice and delete repetitive particles. It ia basically using a for each. Now my question is, can we do all of this using a delayed load shader or a instance shader? That will actually use less ram than loading the cache in a file node. Thanks for your help.
  13. Hi Florian, This a common thing in Houdini Scaling camera and light can cause this thing. Use the below mention expressions to fix it Unhide scale in camera and origin(opinputpath(".",0), "", "SX") for x origin(opinputpath(".",0), "", "SY") for y origin(opinputpath(".",0), "", "SZ") for z that should do it. Cheers!
  14. Liked your post for the last line
  15. Thank you D K for the tip. It works fine now.