Wooo! Wait for something like this for a log time! Please go on with this, will be very usefull for Maya user like me!
I'm doing my best so you can throw CREASE+ commands on most of your meshes, atm, like I said it's not perfect but the CORE thing is there no worry :pleased: Also, beta testers are in the 1st post list .
As explained in the "Surface-Based Asset Generation" thread the 'secret' for clean bevels/chamfers seem to be to inset each 'plane' of the mesh first. If we could get an 'Inset' modifier with a "by smoothing group" checkbox or if that is simply added to the chamfer/quad-chamfer modifiers we should be in the clear.
As explained in the "Surface-Based Asset Generation" thread the 'secret' for clean bevels/chamfers seem to be to inset each 'plane' of the mesh first. If we could get an 'Inset' modifier with a "by smoothing group" checkbox or if that is simply added to the chamfer/quad-chamfer modifiers we should be in the clear.
I'm aware of that, and I'm implementing a new feature with a different approach... Meanwhile there are the commands with lowercase "C" flag that allow cleanup of the mesh before bevel or crease and it's already more closer, even if tbh it's not as efficient as inset method... It's about time guys.
So we did some test in the studio here to try out some different pipelines, Artist are pretty happy but there were some issues (its normal i know)
-Short cuts seam to be wonky and crash stuff ( not sure yet if its because of the use with other scripts) -We had to restart many times to let the script work again, rehashing and stuff did not work. -Boolean did not work like expected, some artist could not choose between the different options Intersect, combine
We do however see a lot of potential in this script. together with the shapeshifter this is we are searching for. right now it would be a combination of 3 scripts to get the pipeline working ( i will write it out today to post here/or PM i think )
Again this is just after a quick look at it. but going in the right direction. very excited thanks
So we did some test in the studio here to try out some different pipelines, Artist are pretty happy but there were some issues (its normal i know)
-Short cuts seam to be wonky and crash stuff ( not sure yet if its because of the use with other scripts) -We had to restart many times to let the script work again, rehashing and stuff did not work. -Boolean did not work like expected, some artist could not choose between the different options Intersect, combine
We do however see a lot of potential in this script. together with the shapeshifter this is we are searching for. right now it would be a combination of 3 scripts to get the pipeline working ( i will write it out today to post here/or PM i think )
Again this is just after a quick look at it. but going in the right direction. very excited thanks
- Shortcuts? explain in more details -Getting errors? often it happens when you're in mouse drag mode and you're trying to call crease+ again on another selection. When you're done with mouse drag make sure you hit Q or W though -In fact the cycle boolean operation thing works only if you haven't done any action after boolean, if there is only one node after boolean operation and you try to change operation type, you won't be able to change it. Again precision, and reading the documentation save alot from these things.
Awesome work Waywo,really proud of how far you have gone !
And to give you guys even more good news,if you have ShapeShifter in your script directory Crease+ will let you use ShapeShifter as your bevel tool instead of the classic Maya bevel.You will be able to toggle both of them,of course
depends on what bevel you are referring to. Maya has in fact three different bevel. One of them is hidden. And to be honest I have no problem with speed atm
ramonkalros To add some info on what Baidhir said,you should keep in mind that any beveling tool in probably any 3D software will be slow or fast depending on the complexity of your mesh.Before setting such a workflow in stone doing some experimentations on how to overcome it's issues would probably be wiser,too.
Last time i tried bevels in Modo/Maya if the chamfer passed the hundreds segments they were both really slow ,and so was my computer so this might explain that.Thanks for putting me on the right track ^^"
perna Maya is definitely capable of that sadly.Applying 50-100 segments on a chamfer already starts killing the perfs depending on the object's complexity, so waiting 8 minutes for tweaking a chamfer almost sounds to good.But then again i have a relatively weak GPU and CPU so the issue might depend on that.
To add on what already have been said, you may not want in current production workflow to jump straight and bevel 2300 edges. Also there's your machine to take in consideration when it comes to heavy process like that.
it`s heavy process only for maya. Softimage have this nice algoritm 15 years. Maya can`t fix this in 2017 ver. This is stupid decision. This need in specific situation like extrude and bevel vectors shapes. for example - world or country maps. KIlling Softimage and imposed to work in Maya. Hate autodesk
Way: He's not saying to bevel 2300 edges though (even though in special cases you certainly will, like when working with text or other vector-based shapes). A bit of math... 8 minutes is 480 seconds. 2300/480 = 4.8 edges. That seems much too slow for any real-time chamfering.
Maybe Maya users are accustomed to that, but a Max user who likes to change parameters interactively will find that horrendous.
Sorry about contributing to the off-topic talk.
That's fine cause for the moment I can't go split them edges in the API lol.
OMG guys I'm working on the implementation of a new feature called "Node Baker" that will allows you to bake a boolean or bevel operation of your choice, so that you don't have to delete the entire history of your object, with this new feature (for version 2.0), the workflow of CREASE+ will be almost 'procedural' , Shout out to Bertmac, who gave me this idea through his feedbacks, and between it's already working!!! Also I can't wait to implement the Shape Shifter feature of my friend Fansub though it may be or may not be for version 2.0... There's many more features, will keep em secret for the moment ..
A quick warmup with CREASE+, here's what you can achieve in 20 minutes, without destroying your history, allowing adjustments and overrides at anytime. I used new features I'll talk about when the next version is release, and I promise It's Day and Night.
-It's always a smart move to clean your mesh as you go with Booleans, connecting 2 vertices on large Ngons is all you have to do in most cases. WHY? Because it doesn't matter if you use CREASE+ 's default bevel or Shape Shifter which will be supported, the more your mesh is fucked up the more both will have difficulties, doing that will just increase your chance a lot for getting a nice shiny edge from your hard edge bevel. Yet Shape Shifter is the most powerful bevel and will in plenty cases save you from doing that, but bear in mind that errors, notably on bevel outputted mesh can appear. On my post I used CREASE+ default bevel, all that was required is to connect a couple of verts.
-When your bevel width is not on point , and you're at the maximum value, you can clamp the value for bigger width in the channel Box and it just works, so no panic in case your beveled edge is as thin as a panama paper, just clamp! :chuffed:
Update Beta- tester List (in first post) . Now y'all gotta wait, I have some cool things to introduce in a Next version I will upload in just a Week prior to Beta Testing.
Hey, in reference to the "Maya's bevel is super slow", I just tried it on 3000 edges in Maya 2016, and it completed the bevel in around a second. So, not great, but definitely not 8 minutes. And the computer I tested on isn't great. Adjusting parameters isn't realtime, but it takes maybe 1/4 of a second to update as I change the options. (Except for changing segments, which takes longer depending on the number. Changing to 4 segments took maybe 4 seconds, and the other parameters slow accordingly)
Replies
indeed 3ds Max has quad chamfer!
Also, beta testers are in the 1st post list .
If we could get an 'Inset' modifier with a "by smoothing group" checkbox or if that is simply added to the chamfer/quad-chamfer modifiers we should be in the clear.
[noparse]https://www.youtube.com/watch?v=9nV9z4jpAQk
Old ASF Hell compared to Version 2.1
-Short cuts seam to be wonky and crash stuff ( not sure yet if its because of the use with other scripts)
-We had to restart many times to let the script work again, rehashing and stuff did not work.
-Boolean did not work like expected, some artist could not choose between the different options Intersect, combine
We do however see a lot of potential in this script. together with the shapeshifter this is we are searching for. right now it would be a combination of 3 scripts to get the pipeline working ( i will write it out today to post here/or PM i think )
Again this is just after a quick look at it. but going in the right direction. very excited thanks
-Getting errors? often it happens when you're in mouse drag mode and you're trying to call crease+ again on another selection. When you're done with mouse drag make sure you hit Q or W though
-In fact the cycle boolean operation thing works only if you haven't done any action after boolean, if there is only one node after boolean operation and you try to change operation type, you won't be able to change it. Again precision, and reading the documentation save alot from these things.
And to give you guys even more good news,if you have ShapeShifter in your script directory Crease+ will let you use ShapeShifter as your bevel tool instead of the classic Maya bevel.You will be able to toggle both of them,of course
perna Maya is definitely capable of that sadly.Applying 50-100 segments on a chamfer already starts killing the perfs depending on the object's complexity, so waiting 8 minutes for tweaking a chamfer almost sounds to good.But then again i have a relatively weak GPU and CPU so the issue might depend on that.
PS: Softimage is great.
-It's always a smart move to clean your mesh as you go with Booleans, connecting 2 vertices on large Ngons is all you have to do in most cases. WHY? Because it doesn't matter if you use CREASE+ 's default bevel or Shape Shifter which will be supported, the more your mesh is fucked up the more both will have difficulties, doing that will just increase your chance a lot for getting a nice shiny edge from your hard edge bevel. Yet Shape Shifter is the most powerful bevel and will in plenty cases save you from doing that, but bear in mind that errors, notably on bevel outputted mesh can appear. On my post I used CREASE+ default bevel, all that was required is to connect a couple of verts.
-When your bevel width is not on point , and you're at the maximum value, you can clamp the value for bigger width in the channel Box and it just works, so no panic in case your beveled edge is as thin as a panama paper, just clamp! :chuffed:
[noparse]https://youtu.be/li7dZDxY_pg
Seriously go see your private Message
Thank to the guy who made this happen, you're amazing :pleased: , first recap, another milestone !