Daryl Dunlap

Daryl Dunlap

About Me

Not Specified


My Tutorials

obj-image Intermediate
Redshift4H | Instancing | Intermediate
obj-image Beginner
Redshift4H | Instancing | Beginner

Recent Forum Posts

Amd ProRender integration? Jan. 15, 2019, 9:15 a.m.

Solaris is not a Mantra GPU - it is simply a highly customized Hydra port. USD is the future - you get a scenegraph that resolves directly on the GPU, and thus, a storage format (USD) that can be rendered directly on the GPU (Hydra).

Redshift showed what can be done on the GPU, in terms of speed and production workflow support. The fact still remains, if you look at VRay, and the over 10 years head start they had in the GPU rendering research/development sector, it should be clear, just how extremely difficult it is to author a Production GPU renderer. ChaosGroup should absolutely own this GPU rendering market, hands down.

Look, AMD creates GPU's for a living and authored their own GPU Rendering API (Radeon Rays), and their GPU Renderer is crap (ProRender) - that's how hard it is to make a Production GPU renderer. Same thing for nVidia, they created a GPU Rendering API (Optix), released it for free and someone rolled that into a Product (FurryBall) - failed miserably, and famously crashed while running live at Siggraph. nVidia created another GPU Rendering API (RTX), but, this time with hardware acceleration, but no one knows how it will perform - as everyone has to rewrite their Engines under CUDA to get access to that hardware acceleration, to even see how it performs in Production scenarios.

SideFX team is very smart - like, I dont even know who to compare them too, they are in their own league, as far as bringing innovation to market. I'd be pleasantly surprised if they could roll their own Production GPU renderer.

Hard Gun Modeling Tools Project Jan. 1, 2019, 1:39 p.m.

Anyway you could make this work like Topobuild? Where its interactive and doesnt create extra Nodes?

CopyToPoints vs Instance OBJ node with High Point counts Nov. 6, 2018, 9:42 a.m.

Thanks so much Sean - this mystery has been solved. I was hoping I was missing something, and indeed it was that option on the ForEach EndBlock (which should be enabled by default!).