Mudbox SDK is really a fun to play with and it ables to code almost anything into mudbox. I remember I said in the past that mudbox would have not a good SDK. Have to say that I really loving mudbox sdk. I hope that this applink could be a interest option I have red from mudbox forums that is really needed feature and mudbox users want to find a good way to do it. I think that we can win some mudbox users it this workflow works well. One important thing about mudbox applink is that retopo workflow needs to work really well. Work I can create a document for Andrew to read, if he likes to add some of those features. And when we have clear picture how everything should Right now it's important that main functions work but we can start to collect info how to make applink api better. It only needs that some changes must be done 3d-coat applink api to support this. ![]() If not same layer it would create itĬ:\texture\mudbox_diffuse.tga = path of the textureĪnd if there is no mesh part in import.txt it would mean that it adds textures into active scene in 3d-coat otherwise adds new mesh and includes textures into it.īecause exporting specifics layers using mudbox is quite easy task to do. If same name layer already in 3d-coat it would only update that layer. = says that we want to import texture layer into 3d-coat It could work someway like this when 3d-coat reads import.txt: But I agreee that would be really dynamic workflow if we could About taking textures from mudbox to 3d-coat, applink seams not to support that yet. Just copy ApplinkCore.mp into your Mudbox/plugins/ folder. When you update scene later textures are updated automaticly. When you bring new textures into mudbox, you need to actually click all the layers that they show up in screen. If you want to test this version, you can find applink menu in File -> Send to 3D-Coat. Also 3d-coat -> mudbox workflow works but with meshes only no texture support yet. Displacement maps needs to create a sculpting layer. Displacement is not supported because I need to do it diffrently Right now what should work is to take obj object into 3d-coat and bring it back into mudbox with textures. But surely it will be done in the future. So I don't see any rush to include this feature into applink. And real benefit of fbx files are multi uvs and at the moment 3d-coat can't import multi uvs (when using fbx) Fbx is built into applink scriptĪlready but there is some small issues to be fixed still. ![]() License server model: Single License Server. Run the software and choose: License type: Use a network license. Setup & start license server (LMTOOLS.EXE) with LICENSE.DAT as license file. It's a real beta so there is a lot of issues. Change thishost in LICENSE.DAT to your host name. ![]() Here is the first beta version of mudbox applink. Please log any bug that you come across in this thread.Ĭlean up files option in case you choose wrong option and don't have 3DC open.įiels to support export back to mudbox now created automatically with correct contents.Įxport as voxel primitive overwrites the previous exported voxel primitive from mudbox and doesn't change the thumbnail.Įxport back to mudbox very flakey and then only possible for subscription advantage pack version but still flakeyĬlean up Files option will not delete the run.txt fileĪ crazy Cuda driver related error I still need to track down the source of. If andrew add's the ability to import textures this is already in the plugin waiting to be exposed, but right now there is little point in exposing that portion. The big rule is you MUST save your mud scene file before use as it needs this to get the directory your mud file is in to work. The file enclosed is the raw plugin so a manual install is needed (the details are outlined in the readme file.) An installer version will follow. This one is compield against the Mudbox 2011 SDK so will only work on mudbox 20 subscription advatange pack 64 Bit versions. The next time you start Mudbox, default settings are recreated in the same location.Andrew asked me to make a Mudbox plug-in to work with applink, so here's a beta for you to test out. Renaming the directory gives you the option of restoring your preferences if this process does not fix the issue. Either delete the directory, or rename it if you want to keep a copy (for example as /2013_backup/)./Users/username/Library/Application Support/Autodesk/Mudbox /.Locate the following directory (or directories):.(For example, if you have saved images in the \data\Stamps or \data\Stencils directories.) Tip: To ensure that Mudbox always runs smoothly, it can be particularly useful to remove your user preferences whenever you install a new hot fix, service pack, or updated version of Mudbox.īefore removing your preferences, check if you have saved any data in the affected directories, and create any backups that you require.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |