I’m currently having some problems while importing assets from Softimage 2010 (crosswalk 4.1) within Unity 2.6 pro.
I use the FBX format.
Always : the texture(s) don’t appear on my object, I have to set the parameter “swap UV” of the FBX importer on TRUE.
Sometimes : even with the parameter active, the textures don’t show, even if the materials are good assigned (I see the different diffuse colours) and have the textures applied to them.
Have somebody already had something like this ?
Any idea ?
First of all, thanks for the reply and screenshot. My settings are the same ‘defaults’ as far as I can tell.
Could you explain what ‘workflow’ you’re following?
For now I model and texture in Softimage, keeping everything inside the Softimage project. That means scenes, textures, exported FBX files etc.
From there I copy the FBX files and textures into a new Unity project. Unity will see all files when started, and materials will show the textures. But not on the models, unless the ‘swap UV’ is ticked. But even then not all models will show the texture. In Unity the materials do show the texture in the ‘property’ window. All objects have one UV set btw.
It might all be just beginners error…
I hope this helps,
rob
p.s. Looking at Unity’s workflow, would it be useful to move the Softimage project structure into a unity project? So Unity will kepp up with changes?
for what I’ve seen with XSI, is that you mostly have to use the swap button when you export a model with a single UV, if you export a model containing 2 UV, it will load them on the correct channel(like a diffuse UV and lightmap UV)
there is a way to setup the render tree in a way that with a single UV XSI will load export teh mesh in the correct Channnel, but teh swap Uv from unity is far the easiest way
For the texture not applied directly at import , well I everytime load them in unity before load the mesh, eventually saving your texture and mesh in same directory.
I am on XSI 7.01 and crosswalk 4.0 by the way , but i dont think they mess up too much with the new version XD, so it should still work the same.
Just try to esport a mesh with 2UV an dsee if they come at the right channel in Unity
Just to wrap my head around this.
Do people export with textures converted to tiff and embedded in the file, or do they use the textures as is, so they can still change them in PS and see the update happen in Unity?
I’m testing with some basic shapes.
First of all, every export with the CW/FBX exporter gives me an UV error. It seems fine though when getting it into Unity.
I also saw that with non-organic objects I really have to turn on the normal calculation to get it look good.
With some basic shapes it seems to behave, will have a look at my basic scene again.
Just to off the thread question:
-what’s the scale in Unity? Is 1 unit 1 meter? In Softimage I use 1 unit = 10cm. So I have to set the FXB value in Unity to 0.1 if I want the same size.
I have a couple of extra one regarding camera’s, but that will be a new thread
personnaly i dont care the scale so much , you can set up a unit to work with within XSI and stick with that for all your model, and in import fbx setting in unity eventually scale to 1 (important if i remember for using physics in unity…)as they will come to 0.1 or the like from XSI.
the error with the texture support is perfectly normal since if you freeze your model XSI get rid of it and then fbx exporter complain about it but it doesnt matter at all so you can live with it ^^.
for normal things hmm the exporter simply look like it doesnt keep them at all(need to try that once more by the way myself too)
Sorry for responding so late, I just saw my mail notification ^^
Since my post I have resolved my problem with a “trick”, so it enabled me to continue my project.
For the explanations :
It showed up that the objet that was causing me so much troubles had multiples materials on it.
I tried to export a test obect with multiple materials an the problem happened again.
So, my fix was to seperate my cluster individualy in differents mesh, and export all them together in one fbx instead of one mesh with multiples materials.
I will not modify the object anymore, but if someone have some answers for me on this kind of “bug” it would be usefull.
Ive been using XSI to make games and unity was fine with crosswalk 3.1. Once Autodesk bought out XSI they ruined the FBX exporter and it never worked correctly anymore with Unity. None of the newer crosswalks worked either so I refuse to give any of them a try. If people say the new 4.0 is working then maybe ill believe them but otherwise dont fix what isnt broken.
Having the same problems - Unfold Meshes from Softimage2010 turned randomly black in Unity scene-
(with Crosswalk 4.1)
So what I do now to fix it:
Make a copy of your Softimage scene you will use to Unity export only.
Create a copy of your shader. Delete everything but diffuse. (especially Dirtmap what tend to make textures appear black as well) You will re-assign bump, opacity, etc. later in Unity. The point now is just fixing the texture blackness when import.
Triangulate your model
And like Giyomu told elsewhere, “swap UV” must be on all the time.
… and Textures are not black anymore.
Spent nights with these bloody black textures as well, so I hope it helps.
I’m having all sorts of problems with getting my meshes out of Softimage 2010 and into Unity. DAE format doesn’t work at all; the model doesn’t even import. FBX works, but the UV’s are not present. But OBJ works, including the UV’s.