Announcement

Collapse
No announcement yet.

Before and after

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Emcs07
    replied
    Originally posted by vlado View Post
    Unfortunately no. But you'll probably be able to test this in one way or another soon.
    That's interesting! Can you elaborate a bit more or is it still in the planning stages? (I am assuming you mean an option for EDU users)

    Originally posted by vlado View Post
    I think we solved most of the issues now; the 3ds Max builds are done and once they are on the site, we'll focus on the Maya builds.

    Best regards,
    Vlado
    Fantastic news, you guys are so diligent!

    Leave a comment:


  • vlado
    replied
    Originally posted by Emcs07 View Post
    I was wondering if this change will be a part of the update for VRay 2.5 (2.4?) for Maya? It would be amazing.
    Unfortunately no. But you'll probably be able to test this in one way or another soon.

    (By the way, how is that version going, is that bug still being a pain?)
    I think we solved most of the issues now; the 3ds Max builds are done and once they are on the site, we'll focus on the Maya builds.

    Best regards,
    Vlado

    Leave a comment:


  • dariofx
    replied
    Yes, we are also eagerly awaiting the next official release of Vray for Maya. Any updates?

    Leave a comment:


  • Emcs07
    replied
    I was wondering if this change will be a part of the update for VRay 2.5 (2.4?) for Maya? It would be amazing.


    (By the way, how is that version going, is that bug still being a pain?)

    Leave a comment:


  • Morbid Angel
    replied
    yeah I was almost at the panic mode there for a few minutes, turned out just before I left last night, I upped the fur count value, I meant to put in 150,000 but ended up with 1,500,000 Ram went through the roof, look changed I was like Nooooooo!

    Leave a comment:


  • vlado
    replied
    Ok then

    Best regards,
    Vlado

    Leave a comment:


  • Morbid Angel
    replied
    False alarm...there was an extra 0 in one place...made things waay too crazy, all good!

    Leave a comment:


  • Morbid Angel
    replied
    Soooooo, I just turned off the HT on one of my machines...and the fur look is drastically different from when the HT is on....I'm still checking but looks like there is a major issue there

    Leave a comment:


  • Morbid Angel
    replied
    This explains why it works on my main workstation better then on another one, one has HT off the other does not.

    Leave a comment:


  • Zach Gray
    replied
    Originally posted by vlado View Post
    Zach, just tried your file with v18, 50000 hairs and no problems at all - renders in 18s
    Vlado
    I've been in touch with Joe. It's a machine specific bug, probably due to multi-core stuff. (The v17 and v18 shave versions were trying to track down the bug) I've tested it on another machine, and it works great. Disabling hyperthreading also makes it work, but he's trying to track down the root cause.

    This is the machine with the trouble for the sake of interest:

    System Manufacturer Hewlett-Packard
    System Model HP Workstation z620
    System Type x64-based PC
    Processor Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz, 2301 Mhz, 6 Core(s),
    12 Logical Processor(s)
    Processor Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz, 2301 Mhz, 6 Core(s),
    12 Logical Processor(s)
    Last edited by Zach Gray; 21-01-2013, 05:39 PM.

    Leave a comment:


  • vlado
    replied
    Originally posted by Zach Gray View Post
    ..............
    Zach, just tried your file with v18, 50000 hairs and no problems at all - renders in 18s

    Best regards,
    Vlado

    Leave a comment:


  • Morbid Angel
    replied
    yeah since v16 I can have multiple shave nodes in one scene and multiple maya's with shave running...so things are getting better...hopefully.

    Leave a comment:


  • Zach Gray
    replied
    Originally posted by Morbid Angel View Post
    This means the problem still exists?
    I had posted a solution to the problem related to hyperthreading, but Joe got in touch with me and said that wasn't the real fix, so I pulled my post so I wouldn't confuse anyone else who might be having the problem. I think he's found where the crasher is, and is actively working on the fix. .17 didn't fix it completely, but fixed some other stability stuff as far as I know.

    Leave a comment:


  • bazuka
    replied
    FYI

    joe has just rlsed v17

    cheers

    Leave a comment:


  • Morbid Angel
    replied
    Originally posted by Zach Gray View Post
    ..............
    This means the problem still exists?

    Leave a comment:

Working...
X