Jump to content
[[Template core/front/profile/profileHeader is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

Community Reputation

6 Neutral

About Diorn

  • Rank

Personal Information

  • Name
    Dorin Croitoru
  1. A Geometry Object For Each File On Disk

    Trying to get this tool working on H18.5, would really need it for my current project with lots of imports. Unfortunately i'm stuck with this error: Traceback (most recent call last): File "geofolder-to-RsProxy-Import", line 108, in <module> File "geofolder-to-RsProxy-Import", line 91, in createSubnetOfFileNodes IndexError: tuple index out of range Any idea how i might fix this?
  2. A Geometry Object For Each File On Disk

    Just wanted to thank you for this very clever approach to making a tool
  3. Digging up this old thread to ask if it is possible to recover a gallery category or item accidentally deleted with wrong mouse click?
  4. Is AMD potentially risky? (Threadripper)

    Hi, well there is no black and white answer, this is my personal conclusion from the benchmarks we did so far. Both are a good choice and will do a fine job. if you do cpu rendering and a lot of sim work, especially pyro, then go for the TR for a bit of a trade off to sop work and sigle thread ops, the reverse is true for 7900x, being a a bit slower in some types of sims but faster in sop operations and almost head to head in grains and flip wih tr, the diferences are about 25% either way for sops vs pyro, but for cpu rendering TR is the winner by far. Plase take into consideration the overclocking aspect as the final conclusion is based on the highest clock speeds for both cpus. Also please take note of the motherboard you are choosing as it will and may impact performance, overclock scores or future ram upgrade capacity. Ram speed has also impacted scores, get at least 3000mhz ram. ps- for comp work you will also find that software is mostly singlethreaded, though you can try to juggle deadline software to better acces all the threads available on a multi core cpu.
  5. Is AMD potentially risky? (Threadripper)

    Speed performance seems totally reasonable with OCL and if i can bypass the RAM capacity with your suggestion that's a sure win! I'm eager to try out a cloth grain based sim knowing this now... And I wonder if I can apply the same process for a larger Pyro sim with OCL... I'll make sure to send the results to SideFX, Thanks Marty
  6. Is AMD potentially risky? (Threadripper)

    I think i ran most tests 2 times but yeah, OCL on GPU seems to improve Grain results immensly, a good question would be how much gpu RAM is neccessary for your average type grain sim situation. If you wish to make another type of grain Sim i can run it... PS: On this particular station i am running 4x GTX 1080, but is OCL using all cards or only one? @marty any info about this? Judging by ram usage during the sim, it is just 1 card... the ram usage went up 30% during this sim, so that would be aprox 2.4 gb V-ram for 700k points
  7. Is AMD potentially risky? (Threadripper)

    Hi, didn't get to it but i'm pretty certain it's a short matter of time before we see support for both of them...
  8. Is AMD potentially risky? (Threadripper)

    Thank you! updated the scores spreadsheet...
  9. Is AMD potentially risky? (Threadripper)

    cool guys, thanks. Regards,
  10. Is AMD potentially risky? (Threadripper)

    I got open CL for CPU to turn on at the office of a studio i work for, on the i7 6950x, was indeed as simple as setting the ENV file, this would not work at home on the 7900x. i'll try to run the grain benchmark from VFX ARABIA, all i have to do with oCL set for CPU, is turn on all the OCL ticks inside the DOP network, correct? here are the numbers for the Grains scene from VFX Arabia, res 0.01: No oCL -12:16 CPU oCL -08:04 40% faster than no OCL GPU oCL -06:15 63.7% faster than no OCL (gtx 1080)
  11. Is AMD potentially risky? (Threadripper)

    Yup we are moving closer and closer to proper multi-threadding support for sure! Just was not convinced if it is right around the corner or not so I personally made a bit of a trade-off for now
  12. Is AMD potentially risky? (Threadripper)

    Sure no problem, will post the results, i'll run it a couple of times to see if the numbers stay consistent. One mention though: i will not let it go to the mantra rendering. Can't keep my workstation unavailable for a few days at a moment and we already have cinebench scores and some mantra tests. Speaking as a freelancer,and especially from this position, CPU rendering is not an option for me, i would not want the hassle of online renderfarms and i am trying to keep my setup compact, hence one workstation for all things, from modeling texturing to rendering to comp. I could not afford to leave freelance jobs to render for on CPU on a single computer this is why Redshift is highly preferable for me. This is my current production environment. I did work in a facility where i had to take care of a 30 PC vray render farm (running on backburner) and i am glad those days are over for the types of jobs i like to work on. So i will only post the numbers up untill the Mantra tasks for now. As a personal opinion/conclusion to the other tests we had on this thread, as i previously stated it is more important to decide what are your personal needs, for an effects TD i would say TR is a win no question. Again speaking as a generalist freelancer the jobs i do are varried and i cannot guarantee i'll do Pyro all year or flip or even heay sim stuff. Still it is comforting to see lower res sims go fast on the intel, so this means faster RnD with the expense of leaving it to compute more for the final rez sim once and when I get there. I'm really interested for any more under the hood or behind the scenes info you have about this stuff and those SOPs setups you mention sound interesting, so far i've fund this thread very educating and it is good to find out more about how Houdini works. Also the benchmark scene you posted is really interesting to learn from especially the deadline management of the rops, so i am grateful for that!
  13. Is AMD potentially risky? (Threadripper)

    Deadline is great and i never used it like this - but i am running the test right now, i am not entirely sure this is such a universal benchmark. my I9 has finished chewing on all the sim-based tasks, with the only ones left being 3 mantra ones (wich supposedly will take a few days to render?) so again it looks to me like it is is a mostly CPU rendering test. Still no grain, liquid (with proper meshing setup), complex sops opperations with no simming involved, or FEM. So i am preparing a FEM benchmark next...
  14. Is AMD potentially risky? (Threadripper)

    yes this was supposed to be a more single threadded collection of use cases (i'm sure the methodology can be improved), i'll update the running spreadsheet. Thank you for running the test! in related news, mr Timucin Ozger, lead FX TD for MPC, has kindly provided a through benchmarking scene file with the bonus of having a Deadline implementation: Link to the SideFX forums post: https://www.sidefx.com/forum/topic/51730/
  15. Is AMD potentially risky? (Threadripper)

    Yes, at 4.8 it was actually asking for more current than i was giving it for it to become stable under load. But more current would mean larger temps at 4.8ghz i was getting auto throttling from the CPU hardware fail-safe mechanisms. 8 cores at 4.7 and 2 at 4.6 runs indeed hot, but no throttling and no instability so far for renders or sims or any other of the benchmarks, and some of them run hotter(90+) some of them run cold (70+). PS: if you don't mind, and have the time, could you please try out my sops/Bullet benchmark on your machines? @Beatnutz still around for some more tests?