Hello everyone! Im trying to include my GLB to an Spatial.io scene on Unity and I cant. I was readin

For open brush you may need to use OBJ files if exporting from medium directly to open brush.  

[Checking my notes, recently tested]
Works for Medium directly to Open Brush 

Mesh format (first screen): 
[Vertex Colors | Textures+Uvs] = Textures and UVs 

Second Screen:
Texture size* (see below)
Normal Map space [OBJ | Tangent] = Object (required)
Type [TGA | PNG] = Must be PNG, TGA files will fail
Export Format [OBJ | FBX] = Object** 

** I don't think FBX (as delivered by medium works), I seem to remember the version which medium exports isn't supported. There's a couple of FBX standards and medium uses the old one.  Something about binary headers..

*In open brush the texture size cap has been removed (at least for desktops, but likely universally).  If your scene has a lot of textures, those can add up in memory pretty fast.  I know you can do 2048, for instance, pretty sure 4096 works, vaguely remember that 8192 was too much, but not 100% on that. This will impact export speed.  If it's just one sculpt being dropped in, then that's likely less of an issue on the open brush side, although haven't explored this specifically with the quest.

Additional comments:  Direct exports from medium tend to come in rather bleached.   The best practical solution is to export from medium to an intermediary software if you want to do things like retain metalness/gloss.   From there, ideally export as a GLB, although FBX may or may not be supported (see above).  

For FBX and OBJ, the textures must be in the same folder as the asset (not a subfolder).  This may require modification depending on the export program.  

Using intermediary software is where it gets really tricky.  For instance you may need to start off right away with vertexes, and the required format is going to very with that program. The exports from the third program have to be in the correct structure to work.   Additionally complicating things is that that glbs have to be compliant with the current standard within pretty tight ranges to be brought in.

Incidentally, a correctly formatted animation in GLB should be readable by open brush's pathing system.  

Exporting has its own quirks (mostly due to external shader support, exporting with models may or may not work, etc), but also in some cases due to naming structure requirements and group handling. Import success is pretty much on a program by program basis.   

OBJ+Textures seems to work pretty universally, if you just want to get a model in.  If you want to bring other things along you'll have to poke at it.   There's a lot of software out there.  Was starting on documenting some functional pipelines, but that's really time consuming so didn't get too far along with that.

For open brush you may need to use OBJ files if exporting from medium directly to open brush.  

[Checking my notes, recently tested]
Works for Medium directly to Open Brush 

Mesh format (first screen): 
[Vertex Colors | Textures+Uvs] = Textures and UVs 

Second Screen:
Texture size* (see below)
Normal Map space [OBJ | Tangent] = Object (required)
Type [TGA | PNG] = Must be PNG, TGA files will fail
Export Format [OBJ | FBX] = Object** 

** I don't think FBX (as delivered by medium works), I seem to remember the version which medium exports isn't supported. There's a couple of FBX standards and medium uses the old one.  Something about binary headers..

*In open brush the texture size cap has been removed (at least for desktops, but likely universally).  If your scene has a lot of textures, those can add up in memory pretty fast.  I know you can do 2048, for instance, pretty sure 4096 works, vaguely remember that 8192 was too much, but not 100% on that. This will impact export speed.  If it's just one sculpt being dropped in, then that's likely less of an issue on the open brush side, although haven't explored this specifically with the quest.

Additional comments:  Direct exports from medium tend to come in rather bleached.   The best practical solution is to export from medium to an intermediary software if you want to do things like retain metalness/gloss.   From there, ideally export as a GLB, although FBX may or may not be supported (see above).  

For FBX and OBJ, the textures must be in the same folder as the asset (not a subfolder).  This may require modification depending on the export program.  

Using intermediary software is where it gets really tricky.  For instance you may need to start off right away with vertexes, and the required format is going to very with that program. The exports from the third program have to be in the correct structure to work.   Additionally complicating things is that that glbs have to be compliant with the current standard within pretty tight ranges to be brought in.

Incidentally, a correctly formatted animation in GLB should be readable by open brush's pathing system.  

Exporting has its own quirks (mostly due to external shader support, exporting with models may or may not work, etc), but also in some cases due to naming structure requirements and group handling. Import success is pretty much on a program by program basis.   

OBJ+Textures seems to work pretty universally, if you just want to get a model in.  If you want to bring other things along you'll have to poke at it.   There's a lot of software out there.  Was starting on documenting some functional pipelines, but that's really time consuming so didn't get too far along with that.