Trying to create custom button shapes as per below tutorial in MD Ver 8, I am getting this error. can any one tell me where I did wrong.
https://www.youtube.com/watch?v=HjFJcvs5TaE
CD PROJEKT®, Cyberpunk®, Cyberpunk 2077® are registered trademarks of CD PROJEKT S.A.
© 2021 CD PROJEKT S.A. All rights reserved. All other copyrights and trademarks are the property of their respective owners.
Trying to create custom button shapes as per below tutorial in MD Ver 8, I am getting this error. can any one tell me where I did wrong.
https://www.youtube.com/watch?v=HjFJcvs5TaE
Hi Angle
Thanks for your help and explanation.
- In the video link - " How to create a custom button in CLO3D" the button is made in CLO3D itself (exported as OBJ and created a Custom Button in CLO).
In MD manual not much explanation about Custom button making.
Thanks
I finally got the tutorial to work, for me, Gupta. Take it slow, double-check each setting and imitate exactly what was done, and it works. There are some things that aren't explicitly said in the tutorial, like making sure the button is parallel to the ground, and facing the correct direction, making sure the export to obj scale is in mm, etc. But here's my results:
It still needs a bit of tweaking, example the 'thread' length thing, but it does work.
@Rosemary - Thanks for your help, Now It works for a simple square or circle, exported as mm scale. I don't know where I made wrong previously (Followed same steps as in video tutorial) Its time for me to experiment more on these. Once again Thanks.
I think in that video the thing the leave out as an entire step relative to buttons made in modelling apps, is that the orientation of the swizzle between software's is crucial as is the world unit-less space.
[ post link about swizzle orientation between software's ]
I find the best remedy is to look at an existing MD button model by unpacking it (unzip a MD button file) and opening that file up in your modelling software to look at the mesh groups that are in a MD button. That will immediately indicate the correct MD offset (set start thread length) for the button relative to the 0,0,0 (x,y,z) swizzle plane in your modelling app. When you then export this from your modeling software, you need to ensure both your model and unit space between software's is matched so the axis's on the swizzle and model work at the same orientation, or that when you import the button shown in their video step retains the same [positive] x,y,z axis. That will remedy the problem with hard modeled buttons. Look at the color of your swizzle in your 3D modelling app (green, red, blue) which is the standard for axis orientation between all software's and you can match that 3D screen view and model to MD's gizmo colored axis relative to the floor plane. That is absolutely crucial.
My advice would be if you are making many custom buttons that you look at the mesh groups in a .btn file type and explore it's insertion point, unit-less scale, and bounding collision volumes. If you adhere to those norms you can custom load any object as a new button, then save it as a new library component.
That way you can load any new type of button and 100% automate the process in your app so the buttons save ready for use in MD.
Note insertion point (0,0,0) of the button, the axis (positive) direction is based on matching the same export axis vector orientation to work with MD's button files. If you follow this you will be able to create many custom buttons that work in MD. You can even automate the packing into a zipped button file that you simply rename the extension, so you can take this to into bulk automation for library creation of new buttons avoiding most of the steps in MD.
Automate the entire workflow into packing buttons for use in MD. Start with some clean geometry, then add in all that additional random surface textural material detail.
Simply use procedural math's node graphs to dial up any design variant, shape, curvature, or boolean additive or subtractive symmetry.
Such that one template file allows you to output (batch) a new design every few seconds into a .zip packed MD compatible library file.
Apply the node graph procedural texture to the base mesh model and boom a new finished button design in under 60 seconds ready to use.
Decorate using vector artwork generated by procedural nodes and project the geometry back to the base button form surfaces in real-time as you work.
Create a 1001 new CG buttons in an afternoon. Blender is a great tool for button automation into MD.
Button building (see digital samples above and in render - pink arrows) is relatively simple to do, what I do find for garments is that it is good to generate all the scales and variants for a single decorative surface or shape design in one batch so they match as a set of library trims. For most garments this is a factor when selecting button type, as you may want to include it in various functional forms. Taking the time to build your Digital CG button creation tool then allows you to choose the shank, or type of button function, without the penalty of limiting library choice. Plus it's a lot of textural fun to explore designs. Shell, metal, ceramic, enamel, leather, wood, plastic, bakelite, etc.
Angel Angel - Thank you very much for valuable information
My pleasure,
And for all those whom wonder how to make paralyzingly detailed CG simulated fabrics to go with your detailed buttons > try using software that weaves every single strand of brocade type yarn into a digital 3D simulation you can bake down into an image and depth map.
[ Video link to the amazing Silk Now software weaving application ]
A historical learning tool, but also an artisans virtual development software into CG test proofing a woven design or a CG texture textile.
https://silknow.eu/
https://silknow.eu/virtualLoom-v0.91b/
[ Video link #2 to the amazing Silk Now software ]
As simple as loading your artwork and using drag and drop to define weaving.
The future is wow and >> now ! <<
:-)
Intriguing possibilities, Angel! Seems best with good contrast/low color count pics.
Yes, good for making the final silk label tag found in the garment > as the text in woven tag labels needs to be reduced down into the weave pixels that this software does so well.Also useful for those woven logotype trims you see.
If you combine the base weave 3D model with matching depth scale grey maps and additional yarn textures onto the 3D model with some random noise added in then you can take it a lot further. As you can stroke the center of the tube for the yarn, it gives you a nurb for a complex weave model - so you can dump the tube surface in the model they use for yarn and throw in your own custom twisted random hair strands with strays, then it really starts to pop before you bake textures down.
It's taking me a while to figure out which settings give a result I like, but I'm getting there. Added in the normals map generated from the same texture. It helps pop the image nicely.
My fabrics aren't nearly as good as your's. All that CG work experience, I guess. *grin*
Hi Angel Angel - Thanks for you valuable comments and explanations. One request - Please Please donot delete Posts - They carry valuable information to everyone and Thanks for sharing your works
Thanks
:-)
Procedural decorative everything > button making in the blink of an eye.
I perhaps need to make some more custom avatars with shoes trimmed with buttons + bells on them ... and hair sets with ear rings and necklaces. Automated this is actually really easy to do, as it's only a few steps.
( Above ) to fit shoes, hair and accessories to your avatar or custom avatar > Select Avatar > CTRL+Alt+shift+T > Avatar Accessory Maker (Accessories (*.acc) Modal). And drop on your custom accessories. It's that easy.
And to whack in a custom button .... an easy process. (Just get those x,y,z, swizzle axis right and off you go - see my tip on using a MD library base button to get that scale and orientation correct )
Below Registering custom button into library. Materials > Button > Register Button . Straight in - no drama.
Ping, twang, yank, any custom button directly into your library in seconds. Py batch script out of blender and you can drop 1001 algorithm driven procedural decorative buttons in an afternoon.
:-)
Hi Angel Angel,
i am new to this software. trying to create different buttons but not clear. is it possible to create a video and upload the link here.
Thank You
Please sign in to leave a comment.