Im working on a backpack mesh in blender. I am using the IMVU Blender toolkit. I am using the attachment tool from the toolkit.
ive been following the material naming convention in blender where i name my materials like: name [ID].
my intended workflow is as follows:
i want to create an empty open backback which i upload as a derivable.
i then want to make a series of props such as books etc, which i can then derive from my original mesh and upload a separate mesh of JUST the props. which fit inside the backpack.
this way i can make different versions of the backpack and derive from the original empty one as often as i like.
My issue is that, when i upload the props in a separate import, one of the materials unassigns and the submesh displays as pure white.
Steps to recreate the issue in IMVU Studio are:
1) Import FBX of just the backpack
2) Set up FBX
3) Uncheck overwrite meshes
4) Assign MESH ID as 77 (cuz i like 7's)
5) Review and Import
5) Confirm no errors, GREAT!
6) Import FBX of just the props
7) Set up FBX
8) Uncheck overwrite meshes
9) Assign MESH ID as 78
10) check material assignment is not conflicting with existing materials
11) Review and import
upon following these steps, one of the submeshes starts to display as white.
I have attached screenshots of my issue, but if further information is required, i can provide it. Out of good faith i am also willing to share my IMVU Blender FBX files, in case anyone wants to recreate the issue (blah blah blah DMCA warning).
note: When importing everything all together, there is no error. That is: whether i import it as 2 separate meshes, or combine the two and import as one mesh, there are no issues as long as it is done in the same import step. If i import in 2 steps rather than import all at once, that is where the issue arises.
Thank you in advance,
Richi
0 Votes
7 Comments
Sorted by
C
Communityposted
3 months ago
Admin
Posted by “FlexFactor” on March 12, 2024.
[Archived]
oh awesome! i will test on studio soon, my current work-around was to just do the uploading on classic, i submitted on classic then tested the props by editing on studio, as well as deriving from the bag in studio, and it seemed to work that way for both. I will mark ur answer as best, and will try to attempt this next time i run into the issue.
once again thank you for your time in looking into this, very much appreciated!
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Drosselmeyer” on March 12, 2024.
[Archived]
Just to keep up on the status of this post. Yes, this is a bug and we have a ticket going on it. I did find a work around for @FlexFactor's issue specifically and that was to save, close and reopen the project between FBX imports.
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Drosselmeyer” on March 12, 2024.
[Archived]
I have your files and will have a look. Thanks @FlexFactor !
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “FlexFactor” on March 12, 2024.
[Archived]
Hello and thank you for your response.
Im sad to hear that it is a known issue :(
I will zip the files now and email them.
To clarify, i do not save the draft. I first import one mesh, then immediately import the other mesh while my project is still unsaved.
For the second part of your assessment: In blender if i take the two meshes and join them into one mesh and export as fbx -> import into studio it works
OR
if i export both the meshes as seperate objects in ONE fbx file, it works as well
You will see what i mean when you check the files in the zip.
Thank you for looking into this.
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “FlexFactor” on March 12, 2024.
[Archived]
yes in step 10 of my process i make sure the material ID's dont conflict, and in blender i have all my material ID's as separate and distinct, from one another
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Drosselmeyer” on March 12, 2024.
[Archived]
Hmm. Hi @FlexFactor, The issue of white materials has been plaguing us, sorry to say. I will bring this to the attention of the engineer who would know best. If you would, it would be great to have the FBXs and textures, don't need the Blender files at this time. You can send them zipped up to studio@imvu.com. We will only use your files to reproduce the issue in-house.
Just so I am clear, this only happens if you import the contents-of-backpack FBX into a saved draft of the backpack-only project?
That is if you derive a new attachment product and import both contents-of-backpack and backpack-only FBXs in one go it works fine?
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “jazzKat” on March 10, 2024.
[Archived]
If you import two meshes from separate FBX files this tends to happen, so make sure the materials assigned to the SECOND mesh are DIFFERENT to the first. If Studio sees that same Mat ID used more than once it tends to whiteout.
0 Votes
People who like this
Delete Comment
This post will be deleted permanently. Are you sure?
Posted by “FlexFactor” on March 08, 2024.
[Archived]Hello all,
Overview of my problem:
Im working on a backpack mesh in blender. I am using the IMVU Blender toolkit. I am using the attachment tool from the toolkit.
ive been following the material naming convention in blender where i name my materials like: name [ID].
my intended workflow is as follows:
i want to create an empty open backback which i upload as a derivable.
i then want to make a series of props such as books etc, which i can then derive from my original mesh and upload a separate mesh of JUST the props. which fit inside the backpack.
this way i can make different versions of the backpack and derive from the original empty one as often as i like.
My issue is that, when i upload the props in a separate import, one of the materials unassigns and the submesh displays as pure white.
Steps to recreate the issue in IMVU Studio are:
1) Import FBX of just the backpack
2) Set up FBX
3) Uncheck overwrite meshes
4) Assign MESH ID as 77 (cuz i like 7's)
5) Review and Import
5) Confirm no errors, GREAT!
6) Import FBX of just the props
7) Set up FBX
8) Uncheck overwrite meshes
9) Assign MESH ID as 78
10) check material assignment is not conflicting with existing materials
11) Review and import
upon following these steps, one of the submeshes starts to display as white.
I have attached screenshots of my issue, but if further information is required, i can provide it. Out of good faith i am also willing to share my IMVU Blender FBX files, in case anyone wants to recreate the issue (blah blah blah DMCA warning).
note: When importing everything all together, there is no error. That is: whether i import it as 2 separate meshes, or combine the two and import as one mesh, there are no issues as long as it is done in the same import step. If i import in 2 steps rather than import all at once, that is where the issue arises.
Thank you in advance,
Richi
0 Votes
7 Comments
Community posted 3 months ago Admin
Posted by “FlexFactor” on March 12, 2024.
[Archived]oh awesome! i will test on studio soon, my current work-around was to just do the uploading on classic, i submitted on classic then tested the props by editing on studio, as well as deriving from the bag in studio, and it seemed to work that way for both. I will mark ur answer as best, and will try to attempt this next time i run into the issue.
once again thank you for your time in looking into this, very much appreciated!
0 Votes
Community posted 3 months ago Admin
Posted by “Drosselmeyer” on March 12, 2024.
[Archived]Just to keep up on the status of this post. Yes, this is a bug and we have a ticket going on it. I did find a work around for @FlexFactor's issue specifically and that was to save, close and reopen the project between FBX imports.
0 Votes
Community posted 3 months ago Admin
Posted by “Drosselmeyer” on March 12, 2024.
[Archived]I have your files and will have a look. Thanks @FlexFactor !
0 Votes
Community posted 3 months ago Admin
Posted by “FlexFactor” on March 12, 2024.
[Archived]Hello and thank you for your response.
Im sad to hear that it is a known issue :(
I will zip the files now and email them.
To clarify, i do not save the draft. I first import one mesh, then immediately import the other mesh while my project is still unsaved.
For the second part of your assessment: In blender if i take the two meshes and join them into one mesh and export as fbx -> import into studio it works
OR
if i export both the meshes as seperate objects in ONE fbx file, it works as well
You will see what i mean when you check the files in the zip.
Thank you for looking into this.
0 Votes
Community posted 3 months ago Admin
Posted by “FlexFactor” on March 12, 2024.
[Archived]yes in step 10 of my process i make sure the material ID's dont conflict, and in blender i have all my material ID's as separate and distinct, from one another
0 Votes
Community posted 3 months ago Admin
Posted by “Drosselmeyer” on March 12, 2024.
[Archived]Hmm. Hi @FlexFactor, The issue of white materials has been plaguing us, sorry to say. I will bring this to the attention of the engineer who would know best. If you would, it would be great to have the FBXs and textures, don't need the Blender files at this time. You can send them zipped up to studio@imvu.com. We will only use your files to reproduce the issue in-house.
Just so I am clear, this only happens if you import the contents-of-backpack FBX into a saved draft of the backpack-only project?
That is if you derive a new attachment product and import both contents-of-backpack and backpack-only FBXs in one go it works fine?
0 Votes
Community posted 3 months ago Admin
Posted by “jazzKat” on March 10, 2024.
[Archived]If you import two meshes from separate FBX files this tends to happen, so make sure the materials assigned to the SECOND mesh are DIFFERENT to the first. If Studio sees that same Mat ID used more than once it tends to whiteout.
0 Votes