Long ago someone here shared the cheat sheet to use for number of sides but I cant find it on older pages, so like in example above
shape on left has 20, 16 and 12 sides for large medium and small details, changing the radius to align the segments and running boolean required minimum cleanup and subdivides ok. (Got this from previous posts)
On right I tried with 24, 20 and 16 thinking 4 being a magic number and it all fall apart for the smallest shape. I can make it work by lowering its sides and changing radius however it will not always be ideal to scale the parts if they dont match reference. I want to understand the maths behind choosing sides for intersecting cylindrical details. Thank you.
EDIT: I explored further and made it work, there are slight inaccuracies but not enough to impact normal map bake. Still need to figure out why certain number of sides work.
Thank you, I follow Frank's guide religiously however I am looking for that cheat sheet / trying to understand the number logic (20,16,12 sides) as shown in my post. It was shared very long ago and the images are not showing on older pages here.
Not sure what that is but it is usually about size of the cylinder (half the size, half the segment count) + experimenting. Not sure if that's maya or max but in blender we use screw modifier to be able to change segment counts to match other cylinders so we can try & fail easily.
Hey guys, im trying to get a clean typology here but i've tried a bunch of different approaches but im kinda stuck.
im trying to model these air vent things on a locker but i cant really figure out what the best approach is here.
ive watched a couple tutorials but they all do it differently and non really work for me, so it would be appreciated if somebody could lead me in the right direction :D
Hey folks, I am trying to model this Viper MK VII from Battlestar Galactica but I can't bring myself on how could I combine all these booleans together
I tried to make the topo line up with loops and stuff but it still turns out rather messy after clean up.
The rear also has to be empty to put the engines inside and I don't know if doing it the boolean way is wise or should have I made it all one piece ?
@Raphael_Bouch I dont know how it looks from reference images however when it comes to vehicles its best to have them in seprate parts as in real life unless you are doing super tight low poly with limited vert count budget.
Hi, sorry forgot to add the refs ^^' ; Well a simple google search and there you have it
You see aside from the "hood" at the rear and a few other parts all shapes seems to flow into each other seamlessly. I'm making a high poly mesh so I'd like to avoid any "smash that geo inside and no one will notice". Would be much more easier if it was a fire arm since those are made of hundreds simpler separate parts bolted together lol.
Hi folks, I've been practicing the ol' cutting a cube out of a cylinder, and thanks to @FrankPolygon's tutorials I have arrived at a place I'm very happy at. I then wanted to try a cube from a sphere, and I have figured a way to make it work for me. Would you mind just looking over it to see if it is the most optimal way of doing it?
Started with a quad sphere and offset extruded the cube.
Bevelled the edges that were selected in the first picture, and set the bevel to 2 segments, but used radial mitering.
Corners ended up like this
I used multi cut
and then deleted the centre of the two tris
smooths pretty well.
Would you do the same, or is there an easier approach? Many thanks in advance.
@christrom There's a bit of subtle pinching caused by the extra loop between the base of the square and the loop path on the surface of the sphere. Dissolving the loop and merging the corner vertices of the triangular quads should resolve the smoothing artifacts while also simplifying the mesh. (See the third and fourth examples below.)
If a high poly mesh subdivides cleanly and provides the desired level of surface quality then it's generally passable but whether or not a topology layout is optimal depends entirely on what the constraints are.
Subdivision modeling is often a balance of accuracy, efficiency, and quality. When something needs to be done quickly then it may make sense to sacrifice some accuracy or quality by using some less than ideal topology routing to connect new shapes to the existing geometry. In cases where accuracy or quality is more important then it often makes sense to spend a bit more time matching the shapes in the references and a bit more effort generating consistent quad grid topology.
The goal should be to find a sweet spot in the workflow that matches the desired level of shape accuracy and surface quality while also using the minimal amount of resources like time, geometry, etc.
Unlike basic cylinders, quad spheres produce a consistent grid topology. An easier approach would be to line up the edges in the grid with the intersecting square shape then extrude off the surface of the sphere and bevel the edges around the feature to create the support loops. This approach is quick but it does require adjusting the geometry density. Which can be somewhat limiting if the intersecting shape is in an odd location or is a different size that doesn't fit the existing grid.
If the quads are too large then it can be difficult to support the shapes when subdivision is applied. Especially when terminating the corner loops into a quad triangle to prevent the support loops from running out onto the surface of the sphere. It can be tempting to try and resolve this by connecting the corner vertex across the adjacent quad but this moves the pole further away from the supported area at the base of the intersection. Which tends to produce visible smoothing artifacts. Sometimes these smoothing artifacts can be minimized by softening the profile of the support loops but it's often better to just adjust the mesh density or topology to support the area around the shape intersection.
When the new shape falls between the existing edges of the quad grid then it creates a natural support loop path around the base of the intersection. It is possible to use the same bevel / chamfer operation to generate the support loops but there needs to be enough space between the center and outside edges of the loops. If the added support loop disrupts the segment spacing around the shape intersection then it can cause overlapping geometry or pinching artifacts.
These types of smoothing artifacts can generally be resolved by over and under scaling the intersecting shapes to provide more room between the base of the intersection and the outside support loop. It may also be possible to minimize the smoothing artifacts by softening the profile of the support loops but this generally won't work if there isn't enough room between the loops.
Which is why it often makes more sense to either place the inside support loop on it's own or remove the extra outside support loop manually with a loop dissolve. The existing geometry in the larger shape will act as it's own support for the outside of the shape intersection. With some careful planning and experimentation it should be possible to solve most of these basic topology flow issues during the block out phase.
Increasing the amount of geometry will make it possible to carry support loops across the surface of the sphere without causing artifacts. This is mostly useful when certain types of corner topology are a requirement but there can also be situations where a high quality surface is required and in those cases it does make sense to increase the amount of starting geometry. With this type of topology layout it's generally possible to sharpen the corners by sliding the outer edges closer to the corner. Just be careful to avoid causing any unintended surface deformation. Which can cause it's own type of smoothing artifact.
There are also some situations where alternate modeling workflows that use floaters may be an option. This thread has a few previous discussions that cover different uses for floaters and examples of different topology layouts for panel lines and through holes. Definitely worth the time to do a quick search and skim through a few of those examples.
Recap: When a quad sphere's grid lines up with the outline of surface features it's often possible to extrude directly off the surface. If the intersecting shapes aren't aligned with the grid then make sure there's enough geometry to create a consistent loop path around the intersecting shapes. Try to avoid unnecessary loop complexity whenever possibly by relying on the existing geometry as part of the support loops. Solve the major topology flow issues early in the block out and avoid pushing corner poles out into unsupported areas of the mesh. These same strategies will also work with negative shapes like cut outs and through holes.
Thanks again Frank. There really should be a tip button on here as you are giving away such valuble information for free. Have you ever considered a YouTube channel? You'd get loads of subscribers. I've worked into the original mesh and got rid of the extra support and it holds fine. I should have really thought about using the existing geometry in your cylinder example, as the last screenshot on here is doing very much the same thing. As long as the geometry is dense enough it really doesn't affect the silhouette. Thanks again, you should be charging for this! I would gladly pay.
Hey guys! First time posting here so I'm sorry if this has been asked and answered before buut I'm having a real hard time producing a good looking result cutting details into curved surfaces like so:
.
I've tried a few different methods, and haven't really come up with a satisfactory solution. Shape I'm going for has a slight horizontal arch that fades and flattens out the further up the vertical arch it goes, and then cutting details into said surface.
so I made a very rough boolean opeartion, after that I did manual cleanup for edge flow on open area for engine section just to give you an idea.
There are number of approaches you can take though,
You can try spline cage method for modelling this as one highpoly mesh, most commonly used for modelling cars.
However I would make a proper blockout of main shapes, run a boolean and split parts, clean the split parts making sure the border edges dont move and add details. This way it wont be "smash that geo inside"
I am sure you are using more reference images instead of that blueprint you shared as its really hard to read. I would suggest looking into scale modelling groups on Facebook for more break down photos of this model. That will greatly help in modelling.
Since its symetriacal design so model just one half as this will not overwhelm you. Remember there are no shortcuts, you gotta keep pushing pulling verts all day :D
@Thanez Hello!! thank you so much for resolve my question, I know I´m little bit a picky person jeje.
jaja don´t worry I can wait, and yeah for sure! I´m interested.
So Thanez let me share you another problem it suppossed to be easy but still I´m having problems… first I´m aware that I can resolve it with te boolean process that u already teach me but I think it could be more faster with the align working pivot.
I goal is to keep the planar and avoid to all cost non-planar geo.
The problem is if I take the front faces and I rotate them I got a lot of Non planar faces
2. So I use the working pivot in one of the edges and move the vertex along that direction in order to preserve the planar faces:
So one part its fixed the main problem is that te direction of the bottom vertex are not matched with the direction of the top vertex (I mean the diagonal direction created from the working pivot)
So I´ve used the same process but I know that it will not be ACCURATE.
Please tell how can I do it accurate, along the diagonal edge from the top in order to have all my faces Planar.
I'm gonna try and do a video this time because I usually spend something like 5-15 minutes modeling something to show you, but 40-50 minutes to write it all up to get my thoughts in there correctly, in order to avoid the norwenglish you'll soon be witness to.
When It's done processing on youtube, you can see it here:
While that's uploading I can point out how that resource you posted is really good. Those are some NEATO tricks I use constantly. They do work really well for him because the edges he's aligning all exist on a flat plane on the XY axis: In essence, he's working in 2d. Your edges are not on a flat plane, you're in 3d. When you try and force polygon 1 to be planar, you're at the same time affecting the vertices that make up the polygons next to it, shifting those polygons out of planarity. It's an issue.
Aaaand this took me 25 minutes instead of 55 minutes. I think I'll do this more in the future if it's helpful.
Hello!! Glad to reply my result of your first tip :)
so here is my example with the awesome help that you provide me about the boolean operation:
I´ve had implement the facet shading and it helps me a lot.
I can tell that in your example the final part its scalated in Z axis soo in that part naturally do u have nonplanar geo right? because you say in your first explination that "When you squish a circle like that, you make the edges of the polygons non-planar, revealing the fact that all quads are made of triangles. Turning on facets shading mode illustrates the issue perfectly. Here on the right, I stole your oval shape and remade the big part but without squishing it."
@SignalFlare07 Welcome to Polycount. Consider checking out the forum information and introduction thread.
This reply is a bit late but you're on the right track. Try to match the segments of the intersecting shapes and their support loops with the existing geometry of the underlying curvature. This will help prevent unintended surface deformation caused by support loops disrupting the curve's segment spacing. Use an iterative block out process to find how much geometry the lofted section needs to be able to support the smaller shapes.
A couple pages back there's some detailed write-ups that cover blocking out similar hard surface shapes. Here's a few links to those posts.
Extraneous support loops on curved surfaces can either be terminated in a well supported area or carried across the existing edges of the curve. Which option makes the most sense depends on the complexity of the shapes and the amount of geometry available. Increasing the amount of geometry in a curve will make it easier to carry the support loops but it can also reduce the overall editability. Which is why it's generally considered best practice to try and match the segments of intersecting shapes and resolve the major topology flow issues before adding lots of support loops.
Here's a few links to some write-ups that discuss routing support loops on curved surfaces.
There's a lot of different ways to approach the order of operations but an iterative block out process will make it a lot easier to solve some of these topology flow issues. Below is just one example of what that block out process could look like.
Start by blocking out the proportions then add chamfers and curves. Modifiers can be used to generate these features non-destructively. Which will make it easier to go back and adjust the segment count, without having to re-model individual sections of the mesh.
Define the lofted surface profile with very basic geometry and smooth it using subdivision or a bevel / chamfer modifier. Boolean operations can be used to cut out the rest of the shapes. Adjust the number of segments in the lofted surface and the radiused cut outs until most of the edges are aligned. The segment matching doesn't need to be perfect. Close enough is usually good enough.
It's generally fine to leave a few triangles in the mesh if they are well supported and aren't causing any visible smoothing artifacts. If the mesh needs to be resolved to all quads for a specific technical reason then go back through the block out process and adjust the density of the curvature and the placement of the intersecting shapes.
Clean up any stray geometry and adjust the topology flow. Try to maintain consistent segment spacing along the curved surface. Use basic loop cut, join through and edge dissolve operations to re-route the topology. Keep everything co-planar by sliding the edges along the surface when making manual loop adjustments. Cut in some additional loop paths to define the chamfered feature on the bottom and slide the remaining vertex upwards to create the triangular notch above it.
Clean up any remaining loop routing issues then add support loops by beveling / chamfering the highlighted edges. Most of the corner support loops on the rectangular pockets can be terminated in a triangular quad or merged down into triangles that are anchored to the adjacent vertex on the curved surface.
Recap: Block out the basic shapes first then use an iterative block out process to solve the topology flow issues before adding the support loops. Let the shapes define the loop flow paths. Match the segments of the intersecting shapes. Extra support loops can either be terminated in well supported areas or carried across the surface.
Hello guys, I have been stuck here for days and I can't figure it out. The topology doesn't look good no matter what I try. I have tried many things, but none of them worked.
Beginner here, how do I connect a five sided polygon to a four sided in C4D? I'm studying to make a bottle, and the outline is the correct shape but I can't figure out for the life of me how to connect these edges and get rid of non planar polygons? A huge thanks in advance to the forum!
Beginner here, how do I connect a five sided polygon to a four sided in C4D? I'm studying to make a bottle, and the outline is the correct shape but I can't figure out for the life of me how to connect these edges and get rid of non planar polygons? A huge thanks in advance to the forum!
You can use boolean. Step by step in Blender: Bevel the edges > duplicate the triangle and separate to new obj > origin triangle to corner (use 3d Cursor is ok also) > rotate and scale triangle > solid and finally boolean with cube…
Notice here when you rotate, use transform orientations by normal (create new custom if u like) and set pivot point to active, from here you can rotate or use shear tool. Hope this help…
Beginner here, how do I connect a five sided polygon to a four sided in C4D? I'm studying to make a bottle, and the outline is the correct shape but I can't figure out for the life of me how to connect these edges and get rid of non planar polygons? A huge thanks in advance to the forum!
You can use boolean. Step by step in Blender: Bevel the edges > duplicate the triangle and separate to new obj > origin triangle to corner (use 3d Cursor is ok also) > rotate and scale triangle > solid and finally boolean with cube…
Notice here when you rotate, use transform orientations by normal (create new custom if u like) and set pivot point to active, from here you can rotate or use shear tool. Hope this help…
Never thought of it, I will give it a try - thanks a lot!
Hey guys I´ve a very important question for Blender, How can u see in realtime your shading with non planar geometry. In 3ds max you can see this with these options: This is the result: soo in Blender these geo is non planar but you can´t see that in the default shading: If I apply a triangulate modifier it works I would like to know if there is another way to see that problem.
Hope you can help me Cheers I´m really frustrated for this problem
@FrankPolygon Thank you very much for the reply! Out of curiosity, what is the tool you're using to create the first boolean cutter? I've been attempting it using lattices but it doesn't come out quite right. Using Maya 2024 by the way.
@SignalFlare07 Glad the write-up was helpful. The lofted shape on the back of the receiver can be created with basic subdivision or with a series of bevel operations.
Here's what the subdivision approach could look like. Start with a basic cage mesh and refine the shape with subdivision preview enabled. Adjust the subdivision level up or down until the edges in the curve are roughly aligned with the rest of the boolean shapes. Using subdivision to create this surface profile is fast but there's limited control over where the segments fall. Making the cage mesh larger will spread out the edges and adding or moving edges in the cage mesh will bring the edges closer together but beyond that there's not a lot that can be done to accurately control the edge placement.
Here's what the bevel approach could look like. Start with the same basic cage mesh then bevel the center edge longitudinally to create the basic profile and segment spacing. Then select the perpendicular edge and bevel that to create the lofted curve and segment spacing. This approach provides a lot of control over the placement of the edge segments but does require a lot of trial and error when using destructive modeling tools.
It might also be possible to combine both approaches by using subdivision preview to create the basic cage mesh then turning the subdivision off and beveling the cage mesh to control the placement and shape of the lofted surface.
@FrankPolygon Holy crap you're awesome! Really appreciate you taking the time to do these writeups. Been getting more into hard surface modelling and the previous writeups you've done in the thread have been really helpful!
I'm looking for advice for Maya modeling - how the heck does one approach modeling a spool of cable?? Sweepmesh is great and all, but the whole modeling a helix, extracting a curve and then sweepmeshing thing results in a very clean artificial looking spool. I want some of strands to overlap and whatnot, but I've been researching for hours now and no results. I can't find any way to add some random noise to the curves or SOMETHING similar?
hey i have this problem i dont know how to fix it, please help me.
A few extra support loops should help a lot.
If you're going to use an n-gon heavy subdivision workflow, it really helps to have frequent and even loops and avoid dense bevels. Here's a twitter page to look at for inspiration if that's how you want to approach modelling,
I'm having a hard time getting this curved piece to look like my reference photo. I've worked on this one spot for about 3 hours, I've added support edges, creases and everything I can think of but I cant maintain my smooth curve
Hey, im tyring to make this droid from a concept art, can anyone help me with the base shape? This is what ive currently got, i dont know how to model the part where the "eye" is if anyone has advice thatd be great!
Replies
Hey all,
Long ago someone here shared the cheat sheet to use for number of sides but I cant find it on older pages, so like in example above
shape on left has 20, 16 and 12 sides for large medium and small details, changing the radius to align the segments and running boolean required minimum cleanup and subdivides ok. (Got this from previous posts)
On right I tried with 24, 20 and 16 thinking 4 being a magic number and it all fall apart for the smallest shape. I can make it work by lowering its sides and changing radius however it will not always be ideal to scale the parts if they dont match reference. I want to understand the maths behind choosing sides for intersecting cylindrical details. Thank you.
EDIT: I explored further and made it work, there are slight inaccuracies but not enough to impact normal map bake. Still need to figure out why certain number of sides work.
Here you go. The articles explaining segment matching:
https://www.artstation.com/blogs/frankpolygon/e72b/sub-d-modeling-cylinder-to-cylinder-intersections
https://polycount.com/discussion/comment/2772692/#Comment_2772692
https://polycount.com/discussion/comment/2772248/#Comment_2772248
Thank you, I follow Frank's guide religiously however I am looking for that cheat sheet / trying to understand the number logic (20,16,12 sides) as shown in my post. It was shared very long ago and the images are not showing on older pages here.
Not sure what that is but it is usually about size of the cylinder (half the size, half the segment count) + experimenting. Not sure if that's maya or max but in blender we use screw modifier to be able to change segment counts to match other cylinders so we can try & fail easily.
Hey guys, im trying to get a clean typology here but i've tried a bunch of different approaches but im kinda stuck.
im trying to model these air vent things on a locker but i cant really figure out what the best approach is here.
ive watched a couple tutorials but they all do it differently and non really work for me, so it would be appreciated if somebody could lead me in the right direction :D
thanks in andvance!
You just need a flat evenly spaced loop around the vent before connecting it back to a flat grid.
i'm sorry but im not sure if i understand... i tried but it turned out like this:
Maybe like so (all quads):
nothing wrong with that, you just need to make sure that you have the supporting loops at the right places and thikness would help too
Hey folks, I am trying to model this Viper MK VII from Battlestar Galactica but I can't bring myself on how could I combine all these booleans together
I tried to make the topo line up with loops and stuff but it still turns out rather messy after clean up.
The rear also has to be empty to put the engines inside and I don't know if doing it the boolean way is wise or should have I made it all one piece ?
Thanks in advance for any help !
@Raphael_Bouch I dont know how it looks from reference images however when it comes to vehicles its best to have them in seprate parts as in real life unless you are doing super tight low poly with limited vert count budget.
Hi, sorry forgot to add the refs ^^' ; Well a simple google search and there you have it
You see aside from the "hood" at the rear and a few other parts all shapes seems to flow into each other seamlessly. I'm making a high poly mesh so I'd like to avoid any "smash that geo inside and no one will notice". Would be much more easier if it was a fire arm since those are made of hundreds simpler separate parts bolted together lol.
Hi folks, I've been practicing the ol' cutting a cube out of a cylinder, and thanks to @FrankPolygon's tutorials I have arrived at a place I'm very happy at. I then wanted to try a cube from a sphere, and I have figured a way to make it work for me. Would you mind just looking over it to see if it is the most optimal way of doing it?
Started with a quad sphere and offset extruded the cube.
Bevelled the edges that were selected in the first picture, and set the bevel to 2 segments, but used radial mitering.
Corners ended up like this
I used multi cut
and then deleted the centre of the two tris
smooths pretty well.
Would you do the same, or is there an easier approach? Many thanks in advance.
@christrom There's a bit of subtle pinching caused by the extra loop between the base of the square and the loop path on the surface of the sphere. Dissolving the loop and merging the corner vertices of the triangular quads should resolve the smoothing artifacts while also simplifying the mesh. (See the third and fourth examples below.)
If a high poly mesh subdivides cleanly and provides the desired level of surface quality then it's generally passable but whether or not a topology layout is optimal depends entirely on what the constraints are.
Subdivision modeling is often a balance of accuracy, efficiency, and quality. When something needs to be done quickly then it may make sense to sacrifice some accuracy or quality by using some less than ideal topology routing to connect new shapes to the existing geometry. In cases where accuracy or quality is more important then it often makes sense to spend a bit more time matching the shapes in the references and a bit more effort generating consistent quad grid topology.
The goal should be to find a sweet spot in the workflow that matches the desired level of shape accuracy and surface quality while also using the minimal amount of resources like time, geometry, etc.
Unlike basic cylinders, quad spheres produce a consistent grid topology. An easier approach would be to line up the edges in the grid with the intersecting square shape then extrude off the surface of the sphere and bevel the edges around the feature to create the support loops. This approach is quick but it does require adjusting the geometry density. Which can be somewhat limiting if the intersecting shape is in an odd location or is a different size that doesn't fit the existing grid.
If the quads are too large then it can be difficult to support the shapes when subdivision is applied. Especially when terminating the corner loops into a quad triangle to prevent the support loops from running out onto the surface of the sphere. It can be tempting to try and resolve this by connecting the corner vertex across the adjacent quad but this moves the pole further away from the supported area at the base of the intersection. Which tends to produce visible smoothing artifacts. Sometimes these smoothing artifacts can be minimized by softening the profile of the support loops but it's often better to just adjust the mesh density or topology to support the area around the shape intersection.
When the new shape falls between the existing edges of the quad grid then it creates a natural support loop path around the base of the intersection. It is possible to use the same bevel / chamfer operation to generate the support loops but there needs to be enough space between the center and outside edges of the loops. If the added support loop disrupts the segment spacing around the shape intersection then it can cause overlapping geometry or pinching artifacts.
These types of smoothing artifacts can generally be resolved by over and under scaling the intersecting shapes to provide more room between the base of the intersection and the outside support loop. It may also be possible to minimize the smoothing artifacts by softening the profile of the support loops but this generally won't work if there isn't enough room between the loops.
Which is why it often makes more sense to either place the inside support loop on it's own or remove the extra outside support loop manually with a loop dissolve. The existing geometry in the larger shape will act as it's own support for the outside of the shape intersection. With some careful planning and experimentation it should be possible to solve most of these basic topology flow issues during the block out phase.
Increasing the amount of geometry will make it possible to carry support loops across the surface of the sphere without causing artifacts. This is mostly useful when certain types of corner topology are a requirement but there can also be situations where a high quality surface is required and in those cases it does make sense to increase the amount of starting geometry. With this type of topology layout it's generally possible to sharpen the corners by sliding the outer edges closer to the corner. Just be careful to avoid causing any unintended surface deformation. Which can cause it's own type of smoothing artifact.
There are also some situations where alternate modeling workflows that use floaters may be an option. This thread has a few previous discussions that cover different uses for floaters and examples of different topology layouts for panel lines and through holes. Definitely worth the time to do a quick search and skim through a few of those examples.
Recap: When a quad sphere's grid lines up with the outline of surface features it's often possible to extrude directly off the surface. If the intersecting shapes aren't aligned with the grid then make sure there's enough geometry to create a consistent loop path around the intersecting shapes. Try to avoid unnecessary loop complexity whenever possibly by relying on the existing geometry as part of the support loops. Solve the major topology flow issues early in the block out and avoid pushing corner poles out into unsupported areas of the mesh. These same strategies will also work with negative shapes like cut outs and through holes.
Thanks again Frank. There really should be a tip button on here as you are giving away such valuble information for free. Have you ever considered a YouTube channel? You'd get loads of subscribers. I've worked into the original mesh and got rid of the extra support and it holds fine. I should have really thought about using the existing geometry in your cylinder example, as the last screenshot on here is doing very much the same thing. As long as the geometry is dense enough it really doesn't affect the silhouette. Thanks again, you should be charging for this! I would gladly pay.
Hey guys! First time posting here so I'm sorry if this has been asked and answered before buut I'm having a real hard time producing a good looking result cutting details into curved surfaces like so:
.
I've tried a few different methods, and haven't really come up with a satisfactory solution. Shape I'm going for has a slight horizontal arch that fades and flattens out the further up the vertical arch it goes, and then cutting details into said surface.
Homework done :) Thanks again Frank
Made a new attempt that I feel got a little closer but still feeling significant distortions around the corners of the inset details
so I made a very rough boolean opeartion, after that I did manual cleanup for edge flow on open area for engine section just to give you an idea.
There are number of approaches you can take though,
You can try spline cage method for modelling this as one highpoly mesh, most commonly used for modelling cars.
However I would make a proper blockout of main shapes, run a boolean and split parts, clean the split parts making sure the border edges dont move and add details. This way it wont be "smash that geo inside"
I am sure you are using more reference images instead of that blueprint you shared as its really hard to read. I would suggest looking into scale modelling groups on Facebook for more break down photos of this model. That will greatly help in modelling.
Since its symetriacal design so model just one half as this will not overwhelm you. Remember there are no shortcuts, you gotta keep pushing pulling verts all day :D
Hey, yeah that's what I ended up doing, thought you wouldn't reply ! :D
Thanks for the detailled explanation and taking your time to redo a model for me, +1 on you !
@Thanez Hello!! thank you so much for resolve my question, I know I´m little bit a picky person jeje.
jaja don´t worry I can wait, and yeah for sure! I´m interested.
So Thanez let me share you another problem it suppossed to be easy but still I´m having problems… first I´m aware that I can resolve it with te boolean process that u already teach me but I think it could be more faster with the align working pivot.
The problem is if I take the front faces and I rotate them I got a lot of Non planar faces
2. So I use the working pivot in one of the edges and move the vertex along that direction in order to preserve the planar faces:
So one part its fixed the main problem is that te direction of the bottom vertex are not matched with the direction of the top vertex (I mean the diagonal direction created from the working pivot)
So I´ve used the same process but I know that it will not be ACCURATE.
Please tell how can I do it accurate, along the diagonal edge from the top in order to have all my faces Planar.
This is my main resource
Files:
Thanx for the help.
cheers everyone
Hey buddy, glad you're back :)
I'm gonna try and do a video this time because I usually spend something like 5-15 minutes modeling something to show you, but 40-50 minutes to write it all up to get my thoughts in there correctly, in order to avoid the norwenglish you'll soon be witness to.
When It's done processing on youtube, you can see it here:
While that's uploading I can point out how that resource you posted is really good. Those are some NEATO tricks I use constantly. They do work really well for him because the edges he's aligning all exist on a flat plane on the XY axis: In essence, he's working in 2d. Your edges are not on a flat plane, you're in 3d. When you try and force polygon 1 to be planar, you're at the same time affecting the vertices that make up the polygons next to it, shifting those polygons out of planarity. It's an issue.
Aaaand this took me 25 minutes instead of 55 minutes. I think I'll do this more in the future if it's helpful.
Edit:
Here's that previous model I promised to upload: Octavio some sort of squished oval cone transition or something.max
And if you're at all interested, here's today's model:
Octavio planar problem del to.max
@Thanez
Hello!! Glad to reply my result of your first tip :)
so here is my example with the awesome help that you provide me about the boolean operation:
I´ve had implement the facet shading and it helps me a lot.
I can tell that in your example the final part its scalated in Z axis soo in that part naturally do u have nonplanar geo right? because you say in your first explination that "When you squish a circle like that, you make the edges of the polygons non-planar, revealing the fact that all quads are made of triangles. Turning on facets shading mode illustrates the issue perfectly. Here on the right, I stole your oval shape and remade the big part but without squishing it."
Cheers 🤗
Beginner here, how do I connect a five sided polygon to a four sided in C4D? I'm studying to make a bottle, and the outline is the correct shape but I can't figure out for the life of me how to connect these edges and get rid of non planar polygons? A huge thanks in advance to the forum!
This is the result:
soo in Blender these geo is non planar but you can´t see that in the default shading:
If I apply a triangulate modifier it works
I would like to know if there is another way to see that problem.
Hope you can help me
Cheers
I´m really frustrated for this problem
I've been attempting it using lattices but it doesn't come out quite right. Using Maya 2024 by the way.
It might also be possible to combine both approaches by using subdivision preview to create the basic cage mesh then turning the subdivision off and beveling the cage mesh to control the placement and shape of the lofted surface.
A few extra support loops should help a lot.
If you're going to use an n-gon heavy subdivision workflow, it really helps to have frequent and even loops and avoid dense bevels. Here's a twitter page to look at for inspiration if that's how you want to approach modelling,