Jump to content

tricecold

Members
  • Content count

    120
  • Joined

  • Last visited

  • Days Won

    2

tricecold last won the day on July 25 2015

tricecold had the most liked content!

Community Reputation

16 Good

About tricecold

  • Rank
    Initiate

Contact Methods

  • Website URL
    http://www.timucinozger.com

Personal Information

  • Name
    Tim
  • Location
    Montreal

Recent Profile Visitors

3,692 profile views
  1. Is AMD potentially risky? (Threadripper)

    no no, i tried it inside Houdini with the environment flag on and off and with opencl ticket on and off, its almost twice as fast with the flag on, without the flag on in houdini.env and openCL ticket , its more than twice the speed, i will run the command once i get back also
  2. Is AMD potentially risky? (Threadripper)

    Hey, so it works here, I am on Ubuntu 16.04 cliinfo ICD loader properties ICD loader Name OpenCL ICD Loader ICD loader Vendor OCL Icd free software ICD loader Version 2.2.8 ICD loader Profile OpenCL 1.2 Device Name GeForce GTX 970 Device Vendor NVIDIA Corporation Device Vendor ID 0x10de Device Version OpenCL 1.2 CUDA Driver Version 375.66 Device OpenCL C Version OpenCL C 1.2
  3. Is AMD potentially risky? (Threadripper)

    Will try in an hour and let you know
  4. Is AMD potentially risky? (Threadripper)

    It's Abit confusing, the thing is by default openCL tick box will use your GPU not CPU, if you want OpenCL to be ran on CPU , there was a flag you need to put in your houdini.env which I don't remember
  5. Is AMD potentially risky? (Threadripper)

    Are you on linux or windows, on windows openCL drivers is installed out of the box, but on ubuntu you need to install them seperately
  6. Is AMD potentially risky? (Threadripper)

    OpenCL does work on these CPUs, and it would made gain, I just noticed that the grain solver is a perfect example for GPU, unfortunetly it is not the best solution for big farms, as not everybody has a GPU farm, next to their CPU farm.
  7. Is AMD potentially risky? (Threadripper)

    I agree with you, there are lots of different types of tasks, I also didn`t expect everybody to ran the entire tasks, as it would take 2 3 days to complete the task. I have also done some i7 vs slower but dual socket xeon pyro simulation tests for 200 frames, I7 was at frame 100 where dual xeon was at frame 50, but things turn around once voxel numbers increase and dual xeon would finish the 200 frames almost 30 ahead of a single I7. In the end you would save time in a finished cache. I am a big fan of redshift also, but I don`t do render for freelance. IMHO ,in the end it comes to the price and possible future optimizations on softwares ability to multi-thread better.
  8. Is AMD potentially risky? (Threadripper)

    hey guys, i was going to post a link here too, but I see that its already shared. To be honest Grain solver is a disaster on any CPU and definitely would not lunch it on CPU if a GPU is available. From experience I can say that Flip will scale as well as Pyro. 1950X has an average speed per core , so I don`t expect it to shine on smaller tasks also, however there is an FEM simulation in there with a some sop solver involved, although I believe pcOpen would perform a lot better than an attribute transfer. I can probably speed up this setup another %30 with lots of compile sops where possible, but yet again it will be limited to sop operators. However the purpose of the Benchmark is to simulate a production environment. The goal is how efficient a 1950X would be if you were to deliver to the client all the way to the renders as a freelancer, This CPU is a waste in a studio environment as an artist machine. Diorn, I am however curious to see those numbers on all the tasks that are completed I can also try a setup of some complex SOP operators one with and without compile sop to see the diffrence
  9. cracking effect

    do a shatter geo like in the sidefx tutorial, then pack them based on connectivity create an object to define places to crack transfer a custom attribute to the object with a falloff, like f@crack = 1; or sth create some random normals with attribute randomize in a vop use displace along normals to move the pieces, so connect the this custom attribute you transfered to displace along normals amount input that should get you started with a basic setup. But this is a diamond so you would see the already shattered object even if it was not broken so right after the shaterring, store their rest attribute and after the animated object type drop a wrangle and run it for interior faces only float moved = @rest-@P; if(moved = 0) removepoint(0,@ptnum); then fuse the whole thing back to together
  10. FLIP Energy transfer?

    you can do this after simulation also drop a wrangle, connect the same cache with a 1 frame offset to second input vector oldspeed = point(1,"v",@id); \\get the previous frame point velocity vector float speed1 = length2(@v); \\ measure current speed float speed2 = length2(oldspeed); \\ measure previous speed f@ratio = abs(speed1/speed2); \\ get the change ratio basically, if the ratio is 1 then speed hasn`t changed and vice versa, or sth like that
  11. Scaling packed Objects with VEX

    Jeff Wagner said that's the only way at the moment
  12. I am on the same boat, been all over the internet, so far no luck, anyone ? vdb morph only works with SDF, I am almost on the way to fill up a FLIP container which will help to extract some vels but it will be extremely dodgy
  13. RBD constraint come back after removing

    in recent builds, since when I am not sure, the SOP overwrite in glue network has a python expression which checks for time dependency on the incoming network, for some reason if your Glue Network is time dependant, this will force DOP to fetch in the GLUE every frame, caused me a big headache, until I found out the issue.
  14. Best approach for cloth ?

    Hey Seb; thnx for the file; I have the same issue, I cant get the constarints moving the cloth object from wires, I attached my example file. any ideas ? FEMConst.hipnc
  15. Must have done something wrong then, I will check
×