0

Limits on material and texture counts

Theanine

July 13, 2017 01:10

None

Follow

Is there a hard limit on how many materials and textures a model can have?

 

I'm trying to upload a very large, complex model with 11 materials, each with its own texture maps. The upload keeps failing if I add the textures in the Material Editor. If I don't add any textures and just upload it as is, it uploads OK but now it has no textures.

The textures are nothing out of the ordinary, just regular square PNGs with resolutions that are multiples-of-2. So that leads me to believe that I'm just simply adding too many of them, Sansar maybe doesn't like too many materials?

It would be nice if the material editor could be opened after the model was already uploaded, because then I could just try adding the textures after the successful upload, and avoid this Upload Failed error altogether.

8 comments

• 0
  
  Gindipple July 13, 2017 01:18

  Is it multiples of 2 or 4?

  I was told 4, of course that's a inherent multiple of 2 so I don't know if which is right

  Also go check the deeply hidden logs in your Temp dir.

   

• 0
  
  Theanine July 13, 2017 01:21

  "Power of 2" is the common terminology.

  Well I just managed to make something change. I had periods (.) in the names of some of the materials, and after removing them it's actually giving me a slightly more detailed error now: "Unable to load texture resource Albedo Map." Before, it was just saying Upload Failed.

  My textures do not have any periods in them though. The only non-letter characters are underscores.

  This is a dump of the error log:

  <18:16:30.769> [Build] Child process failed (3)
  <18:16:30.771> [Build.TaskExe] args: -resourceFolder C:\Users\Peter\AppData\Local\Temp\Sansar\Import\BF\RF\ -inputFile C:\Users\Peter\AppData\Local\Temp\Sansar\Import\BF\material-res\76e031d0ebb0e872d370deb122a3fd79
  <18:16:30.771> [Build.TaskExe] stdout :
  <18:16:30.771> [Build.TaskExe] stderr : <18:16:29.570> [ImportMaterial] LoadingC:\Users\Peter\AppData\Local\Temp\Sansar\Import\BF\material-res\76e031d0ebb0e872d370deb122a3fd79

  <18:16:30.824> [Build] Child process failed (4)
  <18:16:30.833> [Build.TaskExe] args: -resourceFolder C:\Users\Peter\AppData\Local\Temp\Sansar\Import\BF\RF\ -inputFile C:\Users\Peter\AppData\Local\Temp\Sansar\Import\BF\material-res\42a0e655cca02f2ecc2a04c3ed03090c <18:16:30.840> [Build] Child process failed (10)

  <18:16:30.850> [Build.TaskExe] stdout :
  <18:16:30.850> [Build.TaskExe] stderr : <18:16:29.592> [ImportMaterial] LoadingC:\Users\Peter\AppData\Local\Temp\Sansar\Import\BF\material-res\42a0e655cca02f2ecc2a04c3ed03090c

  <18:16:30.851> [Build.TaskExe] args: -resourceFolder C:\Users\Peter\AppData\Local\Temp\Sansar\Import\BF\RF\ -inputFile C:\Users\Peter\AppData\Local\Temp\Sansar\Import\BF\material-res\1fca21bc6e029439eb0e768e3d7c8fc9
  <18:16:30.851> [Build.TaskExe] stdout :
  <18:16:30.852> [Build.TaskExe] stderr : <18:16:29.665> [ImportMaterial] LoadingC:\Users\Peter\AppData\Local\Temp\Sansar\Import\BF\material-res\1fca21bc6e029439eb0e768e3d7c8fc9
  <18:16:29.829> [ResourceLoader] No version of resource could be found; last version tried = f9c2323a16c6478e7f3cc6a9bddff2db.Texture-Resource.v9a8d4bbd19b4cd55.payload.v0.noVariants
  <18:16:29.829> [ImportMaterial] Unable to load texture resource Albedo Map

   I really hope I can get this resolved soon because this is a model I was hoping to enter in the Creator Challenge.

  Edited by Theanine July 13, 2017 01:24
• 0
  
  Theanine July 13, 2017 05:03

  So I guess I answered my own question. I split the complex model into 4 different pieces, each with only 3-4 materials. These uploaded fine. Textures appear in-world as they should.

  If any of you encounter issues with uploading models with a lot of materials, try splitting it up into pieces. It looks like Sansar just doesn't like too many materials on a single model. Don't know if that's by design or just a bug,

  Fortunately Sansar actually respects the pivot / origin point of models that was saved in the FBX. This makes it easy to align the different pieces perfectly together. Second Life didn't do this, from what I remember - it forced the pivot point to always be the exact center of the model regardless of what the origin was in Blender. That made it a nightmare to align different model pieces together in SL, but in Sansar it's a breeze. Just copy/paste the XYZ coordinates of one model to another - if they had the same origin point in Blender, they will become perfectly aligned in Sansar.

• 0
  
  Tyler Scarborough July 13, 2017 06:52

  Tested with 20 + individual textures,  lowest size was 256 highest was 4096, i didn't try higher, anything larger is huge

• 0
  
  Tyler Scarborough July 13, 2017 06:53

  https://atlas.sansar.com/experiences/tylerscarborough/dynamic-evolution-development-experience

• 1
  
  Theanine July 13, 2017 07:02

  So you were able to use over 20 textures on a single model? I must have just encountered some random bug then.

  My textures were all between 512x512 and 1024x1024. It's good to know Sansar supports up to 4096x4096. That'll be very useful for certain things, like large terrain.

  But yeah, anything higher than 4096 is overkill.

• 0
  
  Bruce Patton July 13, 2017 22:57

  What does error 'Child process failed' mean ?

• 0
  
  Tyler Scarborough July 14, 2017 05:01

  @Theanine

   

  yeah. I was going to test with more... My textures i used for the 20 Texture test were 256's  I'm curious if higher resolution images would cause problems on upload