OpenSimWorld is the directory of 3D Virtual Worlds based on OpenSimulator and connected through the HyperGrid. Learn More
New Members
CaleCoban, Sahibchaz, EvaStark, Chrisrenoir, WadePopstar, Cagna, Taelkaline, Shawnkmaloney, Doris, Pedrin, Moomoo, AnnieHope, EstefanyaBlack, Nalani, Elvis07, Sausalita, ShadowWindswept, VelcorckLafarck, KehlRazor, DallasWinsletLikes
Starting some X-mas decor on sim. xmas tree u see there was partially built on blender.
Liked by: 
Comments
I forgot saying this tree is my 1st upload I did on .glb format, possible now with this latest FS version - upload now is super fast. idk about graphic lag or perfomance/stability on opensim though.. any one knows anything about it?
like(0)
Got this answer from DeepSeek AI:
.glb x dae collada? Which one is the best?
Excellent question! The short answer is: **Yes, for the vast majority of users and use cases, the new .glb support is a significant improvement and is objectively better than the old .dae Collada format.**
Here’s a detailed breakdown of why:
### The Champion: GLB (.glb)
**GLB** is the binary file format representation of **glTF** (GL Transmission Format). Think of glTF as the "JPEG of the 3D world," designed to be a streamlined, efficient, and modern format for the web and real-time applications.
**Advantages of GLB:**
1. **All-in-One File:** This is the biggest practical advantage. A .glb file bundles the 3D model geometry, materials, textures, and even animations into a single, neat file. No more worrying about lost texture paths or juggling multiple files (.dae, .png, .jpg, etc.).
2. **Smaller File Size:** Being a binary format, .glb files are typically much smaller than their .dae counterparts, which are text-based XML files. This means faster upload times and less burden on the simulator's asset servers.
3. **Faster Upload & Processing:** The smaller size and efficient structure lead to quicker uploads from your computer and faster processing by the viewer once it's in-world.
4. **Modern Material System:** glTF natively supports a modern PBR (Physically-Based Rendering) workflow. This allows for much more realistic materials with accurate metallic, roughness, and normal maps, which can make content look significantly better under modern rendering engines.
5. **Less User Error:** The single-file nature eliminates the most common problem with .dae uploads: broken textures because the viewer couldn't find the image files on your hard drive.
6. **Industry Standard:** glTF/GLB is the standard format for the web, real-time applications, AR/VR, and is supported by virtually all modern 3D creation tools (Blender, Maya, 3ds Max, etc.).
### The Legacy Workhorse: Collada (.dae)
**Collada** was a pioneering open format that served the metaverse well for many years, but it shows its age.
**Disadvantages of .dae:**
1. **Multiple Files:** You must keep and manage a folder containing the .dae file and all its associated texture images. If you move or rename anything, the upload breaks.
2. **Larger File Size:** The XML text format is verbose and results in larger files compared to GLB.
3. **Slower Processing:** The viewer has to read the XML, then locate, load, and assemble all the separate texture files, which is a slower process.
4. **Outdated Material System:** Its material system is more complex and less aligned with modern PBR pipelines, often leading to inconsistencies and "workarounds" when importing to a real-time engine like OpenSim/SL.
### Side-by-Side Comparison
| Feature | GLB (.glb) | Collada (.dae) | Winner |
| :--- | :--- | :--- | :--- |
| **File Structure** | Single, self-contained file | Multiple files (.dae + textures) | **GLB** |
| **File Size** | Smaller (Binary) | Larger (Text-based XML) | **GLB** |
| **Upload Speed** | Faster | Slower | **GLB** |
| **Ease of Use** | Much easier, less error-prone | Prone to texture path errors | **GLB** |
| **Materials** | Modern PBR (Metallic/Roughness) | Legacy/Complex | **GLB** |
| **Reliability** | High | Moderate (due to user error) | **GLB** |
| **Legacy Support** | New, but growing | Universal in older content | **.dae** (for now) |
### Are There Any Reasons to Still Use .dae?
For now, a few:
* **Legacy Workflows:** If you have a complex, scripted build process that outputs .dae and you aren't ready to update it.
* **Specific Features:** In very rare cases, there might be a specific technical feature of the Collada importer in Firestorm that isn't fully replicated in the new GLB importer *yet*. However, the GLB importer is the new focus and will quickly surpass it.
* **Rigged Mesh Upload:** The initial GLB support in Firestorm is primarily for static mesh. While glTF supports skeletons and animations, the full workflow for rigged mesh upload might still be maturing. For complex avatar attachments, you might temporarily still need to use .dae. **Check the latest Firestorm release notes for the current status on this.**
### Conclusion and Recommendation
**You should switch to using .glb for your mesh uploads in OpenSim immediately.**
The transition to .glb in Firestorm is a massive leap forward. It simplifies the entire content creation pipeline, reduces errors, improves performance, and unlocks better visual quality with modern PBR materials.
**How to start:**
1. When exporting from Blender or another 3D tool, choose **glTF Binary (.glb)**.
2. In the Firestorm upload dialog, select **GLB** as the file type.
3. Enjoy a faster, smoother, and more reliable upload experience.
The era of wrestling with lost textures is finally coming to an end. This is one of the most significant quality-of-life improvements for creators in years.
like(0)
.glb x dae collada? Which one is the best?
Excellent question! The short answer is: **Yes, for the vast majority of users and use cases, the new .glb support is a significant improvement and is objectively better than the old .dae Collada format.**
Here’s a detailed breakdown of why:
### The Champion: GLB (.glb)
**GLB** is the binary file format representation of **glTF** (GL Transmission Format). Think of glTF as the "JPEG of the 3D world," designed to be a streamlined, efficient, and modern format for the web and real-time applications.
**Advantages of GLB:**
1. **All-in-One File:** This is the biggest practical advantage. A .glb file bundles the 3D model geometry, materials, textures, and even animations into a single, neat file. No more worrying about lost texture paths or juggling multiple files (.dae, .png, .jpg, etc.).
2. **Smaller File Size:** Being a binary format, .glb files are typically much smaller than their .dae counterparts, which are text-based XML files. This means faster upload times and less burden on the simulator's asset servers.
3. **Faster Upload & Processing:** The smaller size and efficient structure lead to quicker uploads from your computer and faster processing by the viewer once it's in-world.
4. **Modern Material System:** glTF natively supports a modern PBR (Physically-Based Rendering) workflow. This allows for much more realistic materials with accurate metallic, roughness, and normal maps, which can make content look significantly better under modern rendering engines.
5. **Less User Error:** The single-file nature eliminates the most common problem with .dae uploads: broken textures because the viewer couldn't find the image files on your hard drive.
6. **Industry Standard:** glTF/GLB is the standard format for the web, real-time applications, AR/VR, and is supported by virtually all modern 3D creation tools (Blender, Maya, 3ds Max, etc.).
### The Legacy Workhorse: Collada (.dae)
**Collada** was a pioneering open format that served the metaverse well for many years, but it shows its age.
**Disadvantages of .dae:**
1. **Multiple Files:** You must keep and manage a folder containing the .dae file and all its associated texture images. If you move or rename anything, the upload breaks.
2. **Larger File Size:** The XML text format is verbose and results in larger files compared to GLB.
3. **Slower Processing:** The viewer has to read the XML, then locate, load, and assemble all the separate texture files, which is a slower process.
4. **Outdated Material System:** Its material system is more complex and less aligned with modern PBR pipelines, often leading to inconsistencies and "workarounds" when importing to a real-time engine like OpenSim/SL.
### Side-by-Side Comparison
| Feature | GLB (.glb) | Collada (.dae) | Winner |
| :--- | :--- | :--- | :--- |
| **File Structure** | Single, self-contained file | Multiple files (.dae + textures) | **GLB** |
| **File Size** | Smaller (Binary) | Larger (Text-based XML) | **GLB** |
| **Upload Speed** | Faster | Slower | **GLB** |
| **Ease of Use** | Much easier, less error-prone | Prone to texture path errors | **GLB** |
| **Materials** | Modern PBR (Metallic/Roughness) | Legacy/Complex | **GLB** |
| **Reliability** | High | Moderate (due to user error) | **GLB** |
| **Legacy Support** | New, but growing | Universal in older content | **.dae** (for now) |
### Are There Any Reasons to Still Use .dae?
For now, a few:
* **Legacy Workflows:** If you have a complex, scripted build process that outputs .dae and you aren't ready to update it.
* **Specific Features:** In very rare cases, there might be a specific technical feature of the Collada importer in Firestorm that isn't fully replicated in the new GLB importer *yet*. However, the GLB importer is the new focus and will quickly surpass it.
* **Rigged Mesh Upload:** The initial GLB support in Firestorm is primarily for static mesh. While glTF supports skeletons and animations, the full workflow for rigged mesh upload might still be maturing. For complex avatar attachments, you might temporarily still need to use .dae. **Check the latest Firestorm release notes for the current status on this.**
### Conclusion and Recommendation
**You should switch to using .glb for your mesh uploads in OpenSim immediately.**
The transition to .glb in Firestorm is a massive leap forward. It simplifies the entire content creation pipeline, reduces errors, improves performance, and unlocks better visual quality with modern PBR materials.
**How to start:**
1. When exporting from Blender or another 3D tool, choose **glTF Binary (.glb)**.
2. In the Firestorm upload dialog, select **GLB** as the file type.
3. Enjoy a faster, smoother, and more reliable upload experience.
The era of wrestling with lost textures is finally coming to an end. This is one of the most significant quality-of-life improvements for creators in years.