3D Meshes tiny on import

[Brownfists]

Hi, I work as part of a small team and i'm giving Substance a go. Everything was going perfectly smoothly, I had got the 3D model one of the modellers produced into Substance and was working away easily enough.

The trouble started when I used Blender to map UVs and seams. When I go to link the 3D model again the 3D model is absolutely tiny. I have made no changes to the model other than to mark seams and unwrap to a UV. As Substance Designer does not support .blend files, I tried with both .fbx and .obj files and got the same annoying result each time.

For the record, I know next to nothing about 3D modelling, I have no interest either, I am an artist and that is all, so please no rambling answers about 3D modelling specifics, it's over my head. If it is a 3D modelling issue, just say so so that I can pass this back to the relevant person and moan at them about it.

Otherwise, is this a known issue? If so, is there a (simple) fix? Is this something i'm doing wrong in Substance? If so, how do I ♥♥♥♥♥♥ myself?

[wesm]

Hi,

It sounds like its just a matter of the scale being different between substance and blender. This is very common in terms of modeling as no 3D app uses the same scale systems most of the time. It can be a headache when you want to transfer models.

It's strange that it worked before, but when you reimported the mesh it become small. Typically, before export, its best to "freeze transforms." Each 3D app will call this something different, but it simple sets the scale to 0,0,0. It doesn't change the size of the model, but just zeros the scale. On export, you don't want to have values in the scale other than zero. It sounds like the scale has changed somehow in blender before export. The new transform is being reimported back to substance.

I would suggest that you freeze the transform before FBX export. If that doesn't work, you can send me the FBX and I will take a look. Please reference this post.

[e-mail].

CHeers,

Wes

[Brownfists]

Thanks, I appreciate the help, i'll give that a try and then email it to you if it doesn't work.

[Brownfists]

Having problems handing off substance files to the individual handling the Unity engine. I have exported an sbs with dependencies and archive and then published the sbsar file and handed both off to dropbox for integration into Unity. However, when the sbsar is opened in unity, there are no textures and the sbsar reads as empty. Sure enough, when I open the sbsar in Substance designer I am getting the same result, the graphs aren't loading in and the outputs in the navigation window all have a flame symbol next to them, sbs file still loads in correctly. Not sure what we're doing wrong and there doesn't appear to be anything about it anywhere else.

[Darknoodles]

When you export to FBX or OBJ, simply tick the "Apply Transform" button at export. All object that have not a scale of 1 will be set to one. Also, with FBX, you can set the Custom Scale to 100.

[wesm]

Originally posted by Brownfists:

Having problems handing off substance files to the individual handling the Unity engine. I have exported an sbs with dependencies and archive and then published the sbsar file and handed both off to dropbox for integration into Unity. However, when the sbsar is opened in unity, there are no textures and the sbsar reads as empty. Sure enough, when I open the sbsar in Substance designer I am getting the same result, the graphs aren't loading in and the outputs in the navigation window all have a flame symbol next to them, sbs file still loads in correctly. Not sure what we're doing wrong and there doesn't appear to be anything about it anywhere else.

Hi,

This does seem strange. By chance are the graph's computation set to No? If you select a graph and look under the Attributes, there is a Yes/No switch for computation. If its set to no, the graph is not included in the package.

Cheers,

Wes

[Brownfists]

Got it to export out in the end, but it took a few attempts. We didn't change anything whenever we exported it, it just seems a little hit or miss. I'm moving forward with some other models now so I will see how the pipeline goes and if I encounter the same issue again over the next few weeks, will let you know if it's a persistent problem

[wesm]

Originally posted by Brownfists:

Got it to export out in the end, but it took a few attempts. We didn't change anything whenever we exported it, it just seems a little hit or miss. I'm moving forward with some other models now so I will see how the pipeline goes and if I encounter the same issue again over the next few weeks, will let you know if it's a persistent problem

Ok, thanks. Please let us know.

Cheers,

Wes