One of the topics discussed recently in my class was Spherical Geometry. By definition, it's nearly identical to planar, with some distinction. We used a third party program along with 3dsmax to study Euclidean and hyperbolic geometry, respectively. Then the assignment was to create our own unique tessellations on a sphere. We were able to seek out geometric assistance through 3rd party applications or plugins if necessary, but the end result needed to be imported into 3dsmax for final presentation.
Well, I didn't actually use any 3rd party software for my presentation; all of the tessellations I created in this image were done directly in Max, however I did take inspiration from tessellations and panels created by people in other applications. I used a free 3dsmax plugin called "Populate" to panel some of the spheres with my own original shapes, while most of the others were simply done using the Graphite Modeling and re-topology tools in 3dsmax 2013. This was well within the rules of the assignment, as long as the resulting model was exportable as .obj, and could be used universally in earlier versions of 3dsMax.
I'm sure you will be able to recognize some of these different tessellations, but hopefully you will see some topology here that is unique as well. Here is the wireframe clay render if anyone is interested in examining the underlying topology flow.
Oops. I'm sorry, I thought you had posted your comment under a different image of mine, so the render time I quoted in my first reply isn't correct. This image took almost 5 hours to render, not 20 min. However, the setup for this one was nearly the same as the one I thought you were talking about anyway. PMC image sampler was used for this one too, but the large polycount on this image really extended my average graphics card to the max, so it took a longer time to render in Octane.
I've been trying to get decent AND fast renders for AGES! And I think Octane is the perfect solution. It does seem a teeeeny bit complicated- nothing I can't figure out though. However, it eats my graphics card. I want to see if I can SLI another one in there. I think that might solve the problem.
Anyway, thanks for your response. May I ask where you learned all this from? Did you figure it out on your own, find some nice tutorials anywhere? I've fiddled around with it on my own and learned a great deal but I still feel like I'm missing something. Also, what graphics card do you have?
Are you referring to where I learned how to use Octane? I pretty much just downloaded the demo like yourself, and after just briefly looking at the user manual, gave it a go. It's really simple compared to some other render engines for the applications I use, like 3dsmax. MentalRay and Vray, by comparison, require a degree in physics to use. I like Octane for the simplicity of it's settings, and once you get used to the node-based workflow, it's really a pleasure to use.
Yes, yes, and very much agreed. The reason I like OctaneRender so much is because it is NOT like trying to get a decent render out of Maya-mentalray. It's so easy and largely intuitive. Also FAST, which I like. But I feel like there might be a lot more to it that what I was able to figure out on my own. I wasn't even aware there was a user manual. I'll definitely have to take a look. Thanks.
Ah, I purchased the software almost immediately after trying it, so that's prob why you haven't seen the manual yet; it's only available to registered users. I recommend purchasing, because there are no free render engines based on the GPU (fast) out there. I looked for years. There are a few free GPU engines, but they aren't nearly as robust, and then there are some free unbiased engines, like Luxrender, which are very good, but extremely slow by comparison. So judging by what you want, Octane is the solution. It definitely was for me.
I am fairly well certain I want to purchase. It fulfills all my needs. :3 It's fast, superior, and relatively easy to get the hang of. X3 I foresee it becoming a huge part of my workflow.
Awesome. It's really been indispensably huge part of my workflow now too. Keep in touch, and let me know if you need any help once you buy it. Can't wait to see what you come up with next, using Octane.
Thank you. There wasn't anything too special really about the way it was set up. I set it up in the typical Octane fashion, with HDRI environment map, using the PMC kernel. Once I positioned the camera the way I wanted with DOF, it's just like taking a virtual photograph at that point. I did set the scene to render up to 10000 samples, but this scene didn't take much. I got this after only 3500 samples (roughly 20min render time on my graphics card), at which point I simply stopped the render from adding any more samples, and saved the image. I did adjust the ISO and exposure a little in the image sampler before saving the image, just to brighten the results a bit, but what you see here is pretty much the raw render. I only needed Photoshop to convert the PNG file to JPG for upload here.
I've been trying to get decent AND fast renders for AGES! And I think Octane is the perfect solution. It does seem a teeeeny bit complicated- nothing I can't figure out though. However, it eats my graphics card.
Anyway, thanks for your response.
Thanks again.