Now for those wanting the easy way out (my prefered way I try to reduce button clicking to a dull roar) the cheapest and most flawless solution I found that had a price tag attached unfortunately its the iclone3D exchange if you use blender and that your good to go as they have in fact installed a very good unreal engine exporter (based off the dev tools of course)

I have an old version of iclone 3D exchange 2. Will this work or do I need a newer version?
Thanks

Thanks, will look into it

mrjoyce wrote:


Hi Mike, Milkshape 3D will export in FBX format

I found it to be a nasty piece of software which i wont use ..

urbanlamb wrote:


Lol! Yes, like all software it requires a certain degree of application but personally I have found it much more intuitive and easier to use than Blender and better at low polygon modelling so - you takes your choice.

Unfortunately, only the Pipeline version makes exports in FBX

http://www.reallusion.com/iclone/3dx/3dx_matrix.aspx

Its not hit and miss for me I have been using it exclusively in fact every asset on the gallery has been run through the exporter in Iclone I hesitate to create a tutorial on this because its promoting iclone and so I dont know if muvizu would want it on their site, but I would imagine the pro version would work I upgraded to pipeline so can't say for sure as I do a lot of game engine stuff and its got excellent integration for both unreal and unity even if you use maya or 3dsmax its actually faster to run the exports through here for unreal engine etc.

I can create a tutorial but it would be for the pipeline version I think they removed this from the other versions its a very powerful tool so I would not be surprised if its not limited to pipeline

basically use the unreal configuration and remove the merge opacity from alpha channels (you want that to stay intact) uncheck the support for the skeletons and animations it will throw and exception error at this point as the meshes should be without this and leave it on cm unless you want a massive object.

You can then add all missing maps etc and export you will have to build collision into the model first using your 3d modelling software and have everything properly mapped out and ready to accept the maps.

I have found the pipeline works flawlessly for muvizu, unreal, unity and anything else I tried.

Anyhow if i get time I will create a tutorial but it will not be in the wiki or uploaded via muvizu it will be on my channel only and I guess I can put a link on the forum but since iclone is a competitor I dont think it would be accepted here (logically I would say no as well if i were to moderate it so )


also if your experiencing issues its likely on the muvizu end I have found zero issues from the exporter end they have all been something that relates to muvizu however on my last set of assets I made I found any bugs gone from muvizu so it should work 99.9999% of the time however you need to worry about the integrity of the model and understand the udk collission etc in order to set the model up correctly
edited by urbanlamb on 28/11/2013

Hi snoopylino,

The error message you are getting means that your fbx contains something that is not licenced for Muvizu:Play+ (to state the obvious )

FBX can contain a lot of different type of things, such as lights, characters, animations and cameras. Muvizu:Play+ only supports static mesh objects for import. Most 3D modelling packages will include things like lights and cameras in the scene by default and FBX will, by default export these as well. In blender there is an option to export 'only the selected items' so you can select the model you want and only export that. Have a look in your FBX exporter and see if there is a similar option but if not take a closer look at the scene and try to delete anything except the object you want to export.

Snoopylino -also be aware of the limitations of the trial version (see below) and it is worth knowing that the cheaper pro version of 3dxchange allows you to export OBJ files which can then be converted into FBX files using the free autodesk converter.

Can only export 15 times and If you export 1 character with 3 motions in one FBX file, you will spend 4 export times
































edited by toonarama on 29/11/2013

snoopy I would not spend money on this if your using blender because the obj format export from 3dxechange into the autodesk converter will result in the removal of any of the maps etc so your wasting your money. You will end up with an object that is identical to if you exported from blender to muvizu. The only benefit of having this exchange is to finish the work on the object.

blender -> muvizu will result in the same thing

The purpose of the unreal fbx export options are to keep the information intact for muvizu to interpret and if there is no unreal support in the pro version then save your money unless you have intention to use the 3Dexchange for iclone movies.