@optimaforever said:

was wondering if there was any problem with this approach of modelling.

I'd say it's all up to your preferences. The excess loops you're talking about can be annoying and resource consuming indeed. Since you can't prevent them from appearing, the only possible approach is the one you described and it's totally ok

@box said:

Errm, that would be a white whale. But then you norgies eat whale. So maybe it's a lightly grilled whale.

...I'm off now to pickle a koala for my breakfast.

Got me dead

Rather than using sandpaper you could scramble it with sand in a box(not tested though - the plastic might snap :/)

Count me in

@pilou said:

@unknownuser said:

Also, to achieve the exact thing from the photo, you need to either use subD starting with a simple cube or manually make 1/6 of the sphere(think of the sphere as a cube)

As said on my previous post!

Oh, my bad

Also, to achieve the exact thing from the photo, you need to either use subD starting with a simple cube or manually make 1/6 of the sphere(think of the sphere as a cube)

@bryan k said:

Well it looks great. Why not go ahead and finish the exterior?

Haven't modeled anything for a while... I hope to be able to continue soon. I'm planning to rework the rear wheel arches so they match the front. Also I remember the last thing I did was I punched a hole on the sideskirt for a muffler. For the rest I'm looking for contributors

@marvsweden said:

Thanks for a magnificent plugin.
I've run into a problem with internal faces and/or edges connected to more than two faces after scaling down my model. Now I can't find a way to clean it up. Got any ideas on how to proceed? I've used Solid Inspector which thinks everything's OK. I checked with section cuts without finding any internal faces. I tried scaling the mesh up alot but SubD still thinks something's wrong. Are there any other tools or tricks to find out why SubD gives that error message? SubD can't resolve the error itself and I don't find any problem with the mesh.

Here's some discussion from another thread that might help:

@zaharistoyanov said:

@hsrhdrehre5654654 said:

Also, in my case, i need to use Artisan instead of SubD because with SubD i keep getting invisible "edges touching more than two faces" and it wont let me to subd.

With Artisan, smooth as hell. So i will say that Artisan is more flexible when dealing with geometry. I just needed to discard subd because it was making me to waste even more time, instead of the opposite..

Been there! Here's what happens - sometimes you repeat edges to close some gaps and a new face overlaps the already existing one next to the gap(sorry, I'm on another PC so I can't show an example). So you get the old face, the overlapping one on top of it and the closed gap next to them - all in all 3 faces. That's a problem that always needs fixing. I can remember having issues with it even with Artisan and Loop. I'd also guess rendering would be a pain in the rear end

@thomthom said:

Yea, it doesn't work well unless it's a planar joint.

There is actually a feature in OpenSubdiv that takes this into account. The outer set of faces are not displayed, but taken into account when subdividing. I've yet to try it out though - I' not so convinced how usable that workflow would be.

Sounds promising! Damn, I always forget about the oncoming OpenSubdiv implementation

@thomthom said:

You apply crease to the corner vertices - that avoids the rounding.

In SUbD v2 there is a new default subdivision mode that will keep corners sharp. (Can be change off course.)

I've been modelling this car with using mirrored components to create symmetry:
[attachment=3:3jayf6gc]<!-- ia3 -->2016-04-16_13h52_32.png<!-- ia3 -->[/attachment:3jayf6gc]

Corners - ok. But the whole edge between the two components appears as creased and you can't un-crease it because it's a contour

[attachment=2:3jayf6gc]<!-- ia2 -->ControlMesh.png<!-- ia2 -->[/attachment:3jayf6gc]

[attachment=1:3jayf6gc]<!-- ia1 -->SubDividedInHalves.png<!-- ia1 -->[/attachment:3jayf6gc]

[attachment=0:3jayf6gc]<!-- ia0 -->SubDividedAsOne.png<!-- ia0 -->[/attachment:3jayf6gc]

So one approach could be to treat everything inside a group/component as one solid just for the sake of a smooth transition. In the given case - group the two halves(without having them exploded) and then apply SubD. Instead of giving the "nested group" error, this could be used to treat the two pieces as one and get the edge between them flowing like the other loops