Here's my attempt at a render:




My focus was on the rim metal which is supposed to be a polished alloy aluminum with a ceramic glaze.

I made a quick room scene in MoI and render was done in Metropolis BiPT.

If I'm able to wait longer, I'll be able to take care of much of the noise.

And then there is this ... How close is this

Martin

Nice! A motorcycle with a hitch mount...

I could support an 10m-80m High-Sierra Screwdriver with an ATAS and 100 watts barefoot. ;-)

And do it in style!

Here is a unique object produced from a similar process.




This one started off as a Revolved-by-Rail cylinder made with a grid of 24x18 control points.
Some odd points were scaled in, while evens were scaled out to even the outside.
An inner circle was trimmed in the Z direction to 'gut' the inside shapes, then I used Twist.

Could be an old push-mower blade, or some kind of exhaust grate.

Here is a really nice render done by Ed Ferguson in KeyShot.

Looks clean, give Ed a pat on the back from me

Martin

Really nice. Reminds me that I don't know even half of the program's features or power.

C.

Hallo,
I have more simple and elegant way to make this kind of rim.

Check this video:
http://www.youtube.com/watch?v=OjRA4_fYGbs&feature=youtu.be

Thanks for the alternate method!

This underlying feature to NURBS surface design is what I was emphasizing: Don't forget that you can manipulate the surface structures.

...Moi3D is so versatile!

:)

No problem you have good tutorials, i learn some tips form them)

Hi Mike,

I finally found some time to go through your tutorial. I'm having a little issue with moving the nurb points. Take a look, there is no gradual transition between the points that have been moved and the the ones that are not. Did I miss something?

Hi beanworks, can you please post the 3DM model file when you have a question about a problem with a particular shape like this? That makes it a lot easier to dig into it and see what's going on, it's much harder to diagnose geometry issues just looking at one screenshot where you can't zoom in and rotate around, etc...

Is it possible that your surface was created from a curve that was made up of multiple segments instead of only one single smooth segment? If so that could make that kind of result, the segmentation is basically transferred into the surface that's created from such a curve. Usually in a case like that you can fix that up by running the Rebuild command on the curve before using it for construction:

http://moi3d.com/2.0/docs/moi_command_reference10.htm#rebuild

That tends to be the easiest way to convert a curve made up of multiple segmented pieces into just one single smooth segment.

- Michael

Haha, Yep, thats exactly what I did. You're awesome, thanks.

I'm so glad Beanworks - you spooked me! ;-)
Have fun!

Here is a neat interactive model of my sports rim (from Sketchfab.com)

Wait a minute or two for it to load then just click and drag to manipulate the model.

<iframe frameborder="0" height="700" width="800" src="http://skfb.ly/m4ji3hedca?autostart=1&transparent=1&autospin=0.1&controls=1"></iframe>

By Default tire is White!
So White on white there is nothing to view before you move the mouse!!!
And after click and move you see only the center of the rim!

Pilou, I set this up at my work, and it worked fine.

I just now tried it at home where my internet speed is slower.

It took it longer to load, maybe two minutes, and it moves very very slow because of my video card.

I noticed that all of the 'lighting' layers did not activate immediately.

It took the tire another 20 seconds before the rim, which was black, to become chrome.

I'm assuming this is 'Direct-X' operated.
This makes me wonder if users of Moi will have the same card-dependent performance issues when (and if) Michael adds material/UI view support for background reflection and more material and lighting options.

I may re-think using these interactive models if they're going to be slow for me to use at home... or I could allow them not to 'autostart'.

For me it's loaded in a few seconds (statistics say that is 500 kb file), so for the color that must be old config of Direct X etc... :)

Your looking at WebGL and what is rendering it will depend on the browser AND OS. My default Windows IE doesnt play it. WEBGL is nativley meant to run Open GL, but "2.0" I think, and alot of drivers dont run it or support it very well. Chrome and others use ANGEL to convert the OpenGL to DirectX.

There are many factors. My experience so far is Firefox runs the WebGL stuff the best, right out of the box. It worked on this particular model better than chrome. I didnt even try to load "ChromeFrame" on my IE to test it.

I would appreciate Microsoft to Enable WebGL but they have been against it for quite awhile. Maybe rightly so.

There is talk that Internet Explorer 11 looking to be released this month in Windows "Blue" has WebGL support signs built into it, but not implemented. I guess we'll see.