Found 5 posts.
Search results Show results as topic list.
Houdini Lounge » OSX 10.11.2 good to go for H15?
- pockets
- 5 posts
- Offline
Houdini Lounge » OSX 10.11.2 good to go for H15?
- pockets
- 5 posts
- Offline
If it makes you feel any better, Maya 2016 immediately crashes in Viewport 2.0 mode under Win10 with new Nvidia 1070 cards from both Asus and eVGA if we set one of our scenes to view textures, with Maya set to use OpenGL. It doesn't crash when set to DirectX but then the textures don't show up at all. I've got a Gigabyte or other vendor in my machine and though Maya 2016 is terribly unstable in general I don't have the graphics related crashes.
Houdini Lounge » OSX 10.11.2 good to go for H15?
- pockets
- 5 posts
- Offline
twod
AMD's really stepped up their game with OpenGL lately…
Do you mean for Windows (or linux)? I know on paper I've wanted to go AMD but been gunshy of driver issues. When I spec'd the 5820K + 780Ti I really wanted to get either an r290 or r295x2 for the potential OpenCL boost but blinked and went with the “safe” bet of a fairly fast Nvidia board.
I've held off building another system for at home, instead being temporarily satisfied with my GTX equipped laptop and my eye towards spending discretionary cash on car parts but if I was to build another desktop at home I'd go AMD if I could just feel comfortable with the driver situation.
Houdini Lounge » OSX 10.11.2 good to go for H15?
- pockets
- 5 posts
- Offline
twod
It's frustrating from this side of the table, too. Somewhat baffling too.
Yeah, and it's hard having been an Apple advocate, because from a user experience standpoint I prefer the OS to anything else. This is pretty dynamite hardware too, even if it's a couple years old now, it's still a touch faster on the renders than that 6-core Haswell-E consumer/enthusiast i7.
My youngest brother works for Apple and my mom works for AMD and I get to be the downer at Christmas talking about how their respective companies make my life difficult right now, because neither one takes professional graphics seriously
Houdini Lounge » OSX 10.11.2 good to go for H15?
- pockets
- 5 posts
- Offline
I just updated hoping that Alembic performance wouldn't still be in the toilet but it looks like this latest El Cap hasn't solved the issue.
I swapped boxes with another artist, going from a 5820K + 780Ti running Win7 to a Late 2013 Mac Pro, with Xeon and dual FirePro D500 and it has been painful, mainly due to abysmal performance and stability with Alembics, particularly where cameras are concerned.
Lots of double busy pointers at the end of processing the geometry (both stopwatch and beachball) where even my quad-core i7 + 860M GTX laptop would just update the display. And if I save out looking through the Alembic camera I get a fatal crash loading the file again (I'll have to check if this is still the case after updating to the latest El Cap (*)). Rendering with multiple geo samples also induces a crash.
I thought I was safe exporting the camera and lens information to clip files and read these in to a new camera but basically looking at the Alembic geometry through an actual camera, and not a novel perspective view, incurs a wait and lots of busy mouse doing pretty much anything.
In every way this box is an upgrade yet for the first time in more than a decade I'm paranoid at any moment I'm going to get a crash or freeze or just something that takes longer than if I was to just do it on my laptop.
So now I have to wait until we can budget for a new PC build and this “trashcan” will end up being a completely overkill editorial machine
edit: (*) upping geo samples to “2” with alembic geometry turned on still results in a Mantra crash unless I add an Unpack SOP.
I swapped boxes with another artist, going from a 5820K + 780Ti running Win7 to a Late 2013 Mac Pro, with Xeon and dual FirePro D500 and it has been painful, mainly due to abysmal performance and stability with Alembics, particularly where cameras are concerned.
Lots of double busy pointers at the end of processing the geometry (both stopwatch and beachball) where even my quad-core i7 + 860M GTX laptop would just update the display. And if I save out looking through the Alembic camera I get a fatal crash loading the file again (I'll have to check if this is still the case after updating to the latest El Cap (*)). Rendering with multiple geo samples also induces a crash.
I thought I was safe exporting the camera and lens information to clip files and read these in to a new camera but basically looking at the Alembic geometry through an actual camera, and not a novel perspective view, incurs a wait and lots of busy mouse doing pretty much anything.
In every way this box is an upgrade yet for the first time in more than a decade I'm paranoid at any moment I'm going to get a crash or freeze or just something that takes longer than if I was to just do it on my laptop.
So now I have to wait until we can budget for a new PC build and this “trashcan” will end up being a completely overkill editorial machine
edit: (*) upping geo samples to “2” with alembic geometry turned on still results in a Mantra crash unless I add an Unpack SOP.
Edited by - 2015年12月15日 17:04:52
-
- Quick Links