Maze Grid Home Adult
MazebzOS_AVX2-1-0-0-260580347 SPECIAL release
Ok in this one I did something super special to the terrain floater.
I added spinners for size of the yellow selection box and xy is the bottom left hand coordinate to place it. You can now do borders super easy with a box at 0,0 and the size being 1 wide and 1024 long...or you can make perfect square parcels in moments all the same exact size.....picture below.
Thank you to all who have been tracing bugs keep it up!
THANKS TO RIO FENIX for the idea!
download at https://maze.bz/mazebzviewer.zip
Ok in this one I did something super special to the terrain floater.
I added spinners for size of the yellow selection box and xy is the bottom left hand coordinate to place it. You can now do borders super easy with a box at 0,0 and the size being 1 wide and 1024 long...or you can make perfect square parcels in moments all the same exact size.....picture below.
Thank you to all who have been tracing bugs keep it up!
THANKS TO RIO FENIX for the idea!
download at https://maze.bz/mazebzviewer.zip
 | Rio Fenix: Amazing job you being doing, Prince. Thank you very much for all your time and effort. ✨👏 2 months ago |
MazebzOS_AVX2-1-0-0-260590852 Terrain coordinate update
So this one again is special.
The terrain update is finally cleaned up, it just appears in the bulldozer tab. It properly lets one define the bottom left of the yellow selector then set its length and width, hit return it updates. It is so good. Perfect squares, perfect parcels of 256 or whatever. Move it so that the next one is perfect. Make perfect square borders of 1 meter around it all. Thanks again to Rio Fenix for the idea!See the pic.
https://maze.bz/mazebzviewer.zip
So this one again is special.
The terrain update is finally cleaned up, it just appears in the bulldozer tab. It properly lets one define the bottom left of the yellow selector then set its length and width, hit return it updates. It is so good. Perfect squares, perfect parcels of 256 or whatever. Move it so that the next one is perfect. Make perfect square borders of 1 meter around it all. Thanks again to Rio Fenix for the idea!See the pic.
https://maze.bz/mazebzviewer.zip
| | Rio Fenix: Thank you, Prince. For listening to me and resolving an issue that will benefit the entire community. 2 months ago |
MazebzOS_AVX2-1-0-0-260760312 BOM FIXED
I decided that BOM was sucking in firestorm ..heads not rezzing things like that. Can I hear an AMEN? I discovered that the viewer had toggles in it that would turn off BOM randomly. Was driving me crazy. Evox would be on then would look and it would be off again. The viewer was using some deprecated assumptions that BOM was not available everywhere and if it did not get a call back from the sim in time it would turn BOM off. I fixed it. https://maze.bz/mazebzviewer.zip
I decided that BOM was sucking in firestorm ..heads not rezzing things like that. Can I hear an AMEN? I discovered that the viewer had toggles in it that would turn off BOM randomly. Was driving me crazy. Evox would be on then would look and it would be off again. The viewer was using some deprecated assumptions that BOM was not available everywhere and if it did not get a call back from the sim in time it would turn BOM off. I fixed it. https://maze.bz/mazebzviewer.zip
| | Gentle Dragonheart: Thank you! Runs smoothly as with all of your viewer versions. Highly recommended for anyone needing a better running version of Firestorm, it literally solved all the issues I was having with PBR Fire... 29 days ago |
I JUST RELEASED ANOTHER UPDATE...I added the ability in vs 3.5 to inject the material AND Blinn Phong Textures into the glb being uploaded. I also cleared up a bug that was causing a crash after one loads around 30 items in one upload. I believe it may be infinite. PROVE ME WRONG! When one uploades the glb it comes textured, you drag the glb from contents into your inventory so that it hits the database proper! Looking for more bugs. Let me know if you find them enjoy! Items will be on display HERE though construction is underway : hop://maze.bz:7002/Mesh%20Museum/128/128/28
This program will allow you to upload any mesh, rigged mesh, or not up to around 1 gigs about 20 files or so at once using an oar file! It auto chunks large meshes automatically. The items in the picture were over 2 million verts. It makes a sane physics map for you also . So despite the high verts, well the physics load is a lot lower than what you get with the viewer. It also will let you list all your oar contents in a text file...and well import it into blender with all the textures and placement just like in world!!! :-) Below is the help menu. and below that the download link.
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
👍👍👍
Prince Amor✦ ▸ Maze Grid Home 2 days ago
...
I am proud to announce my release of OarConv Reimagined. This program will allow you to upload any mesh, rigged mesh, or not up to around 1 gigs about 20 files or so at once using an oar file! It auto chunks large meshes automatically. The items in the picture were over 2 million verts. It makes a sane physics map for you also . So despite the high verts, well the physics load is a lot lower than what you get with the viewer. It also will let you list all your oar contents in a text file...and well import it into blender with all the textures and placement just like in world!!! :-) Below is the help menu. and below that the download link.
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
This program will allow you to upload any mesh, rigged mesh, or not up to around 1 gigs about 20 files or so at once using an oar file! It auto chunks large meshes automatically. The items in the picture were over 2 million verts. It makes a sane physics map for you also . So despite the high verts, well the physics load is a lot lower than what you get with the viewer. It also will let you list all your oar contents in a text file...and well import it into blender with all the textures and placement just like in world!!! :-) Below is the help menu. and below that the download link.
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
👍👍👍
Prince Amor✦ ▸ Maze Grid Home 2 days ago
...
I am proud to announce my release of OarConv Reimagined. This program will allow you to upload any mesh, rigged mesh, or not up to around 1 gigs about 20 files or so at once using an oar file! It auto chunks large meshes automatically. The items in the picture were over 2 million verts. It makes a sane physics map for you also . So despite the high verts, well the physics load is a lot lower than what you get with the viewer. It also will let you list all your oar contents in a text file...and well import it into blender with all the textures and placement just like in world!!! :-) Below is the help menu. and below that the download link.
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
| | Spax Orion: For those of you who want REPLACEMENT monsters for your IMAGE GAME MACHINE... THIS IS WHERE YOU GET THEM! Thanks Prince! 2 days ago |
I am proud to announce my release of OarConv Reimagined. This program will allow you to upload any mesh, rigged mesh, or not up to around 1 gigs about 20 files or so at once using an oar file! It auto chunks large meshes automatically. The items in the picture were over 2 million verts. It makes a sane physics map for you also . So despite the high verts, well the physics load is a lot lower than what you get with the viewer. It also will let you list all your oar contents in a text file...and well import it into blender with all the textures and placement just like in world!!! :-) Below is the help menu. and below that the download link.
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
| | Speck: A well overdue utility, thank you Prince. 6 days ago |
Happy easter...Put out my Easter Sim added and adding tons through out the week of easter egs and the like...feel FREE to stop by and grab what you may need for it. It has gotten bigger every year.
| | Carmen Jewel Ever: Thanx Prince :) 17 days ago |
MAZE VIEWER MAJOR UPDATE KDU 8.0
I am extremely pleased and excited to announce that I have obtained a license (and yes for those of you that may know this, I confirmed it today for sharing with the community--which is YOU , as an amateur) for KDU. For those that don't know what that means...it is well-- some of you said firestorm still looks a bit better than my work..well it is because of OpenJpg having to be used in opensim. The story is extremely long, it falls like star wars..long ago in a galaxy far away..I don't mind chatting with you about it, though, so say hello if you want to. KDU is the texture library firestorm uses. I wrote them and got the license for 150 dollars! I also added a zoom to whatever object is selected for editing. While it is selected just choose ALT+Z or in Controls in prefs choose your own. In Blender (.) zooms to selected so I duplicated the idea. https://maze.bz/mazebzviewer.zip
I am extremely pleased and excited to announce that I have obtained a license (and yes for those of you that may know this, I confirmed it today for sharing with the community--which is YOU , as an amateur) for KDU. For those that don't know what that means...it is well-- some of you said firestorm still looks a bit better than my work..well it is because of OpenJpg having to be used in opensim. The story is extremely long, it falls like star wars..long ago in a galaxy far away..I don't mind chatting with you about it, though, so say hello if you want to. KDU is the texture library firestorm uses. I wrote them and got the license for 150 dollars! I also added a zoom to whatever object is selected for editing. While it is selected just choose ALT+Z or in Controls in prefs choose your own. In Blender (.) zooms to selected so I duplicated the idea. https://maze.bz/mazebzviewer.zip
Thats right another UPDATE 3.6 fixed up a weird bug where some LIDAR type meshes with more than one texture was being assigned only one texture. I fixed that right up. I say someone break this thing uploading 30 things at a time is really blowing my mind....
I JUST RELEASED ANOTHER UPDATE...I added the ability in vs 3.5 to inject the material AND Blinn Phong Textures into the glb being uploaded. I also cleared up a bug that was causing a crash after one loads around 30 items in one upload. I believe it may be infinite. PROVE ME WRONG! When one uploades the glb it comes textured, you drag the glb from contents into your inventory so that it hits the database proper! Looking for more bugs. Let me know if you find them enjoy! Items will be on display HERE though construction is underway : hop://maze.bz:7002/Mesh%20Museum/128/128/28
This program will allow you to upload any mesh, rigged mesh, or not up to around 1 gigs about 20 files or so at once using an oar file! It auto chunks large meshes automatically. The items in the picture were over 2 million verts. It makes a sane physics map for you also . So despite the high verts, well the physics load is a lot lower than what you get with the viewer. It also will let you list all your oar contents in a text file...and well import it into blender with all the textures and placement just like in world!!! :-) Below is the help menu. and below that the download link.
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
I JUST RELEASED ANOTHER UPDATE...I added the ability in vs 3.5 to inject the material AND Blinn Phong Textures into the glb being uploaded. I also cleared up a bug that was causing a crash after one loads around 30 items in one upload. I believe it may be infinite. PROVE ME WRONG! When one uploades the glb it comes textured, you drag the glb from contents into your inventory so that it hits the database proper! Looking for more bugs. Let me know if you find them enjoy! Items will be on display HERE though construction is underway : hop://maze.bz:7002/Mesh%20Museum/128/128/28
This program will allow you to upload any mesh, rigged mesh, or not up to around 1 gigs about 20 files or so at once using an oar file! It auto chunks large meshes automatically. The items in the picture were over 2 million verts. It makes a sane physics map for you also . So despite the high verts, well the physics load is a lot lower than what you get with the viewer. It also will let you list all your oar contents in a text file...and well import it into blender with all the textures and placement just like in world!!! :-) Below is the help menu. and below that the download link.
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
I just released an update...I added the ability in vs 3.3 to inject the material into the glb being uploaded. When one uploades the glb it comes textured, you drag the glb from contents into your inventory so that it hits the database proper! Looking for more bugs. Let me know if you find them enjoy!
This program will allow you to upload any mesh, rigged mesh, or not up to around 1 gigs about 20 files or so at once using an oar file! It auto chunks large meshes automatically. The items in the picture were over 2 million verts. It makes a sane physics map for you also . So despite the high verts, well the physics load is a lot lower than what you get with the viewer. It also will let you list all your oar contents in a text file...and well import it into blender with all the textures and placement just like in world!!! :-) Below is the help menu. and below that the download link.
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
👍👍👍
Prince Amor✦ ▸ Maze Grid Home 2 days ago
...
I am proud to announce my release of OarConv Reimagined. This program will allow you to upload any mesh, rigged mesh, or not up to around 1 gigs about 20 files or so at once using an oar file! It auto chunks large meshes automatically. The items in the picture were over 2 million verts. It makes a sane physics map for you also . So despite the high verts, well the physics load is a lot lower than what you get with the viewer. It also will let you list all your oar contents in a text file...and well import it into blender with all the textures and placement just like in world!!! :-) Below is the help menu. and below that the download link.
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
This program will allow you to upload any mesh, rigged mesh, or not up to around 1 gigs about 20 files or so at once using an oar file! It auto chunks large meshes automatically. The items in the picture were over 2 million verts. It makes a sane physics map for you also . So despite the high verts, well the physics load is a lot lower than what you get with the viewer. It also will let you list all your oar contents in a text file...and well import it into blender with all the textures and placement just like in world!!! :-) Below is the help menu. and below that the download link.
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
👍👍👍
Prince Amor✦ ▸ Maze Grid Home 2 days ago
...
I am proud to announce my release of OarConv Reimagined. This program will allow you to upload any mesh, rigged mesh, or not up to around 1 gigs about 20 files or so at once using an oar file! It auto chunks large meshes automatically. The items in the picture were over 2 million verts. It makes a sane physics map for you also . So despite the high verts, well the physics load is a lot lower than what you get with the viewer. It also will let you list all your oar contents in a text file...and well import it into blender with all the textures and placement just like in world!!! :-) Below is the help menu. and below that the download link.
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
I just released an update...I added the ability in vs 3.3 to inject the material into the glb being uploaded. When one uploades the glb it comes textured, you drag the glb from contents into your inventory so that it hits the database proper! Looking for more bugs. Let me know if you find them enjoy!
I am proud to announce my release of OarConv Reimagined. This program will allow you to upload any mesh, rigged mesh, or not up to around 1 gigs about 20 files or so at once using an oar file! It auto chunks large meshes automatically. The items in the picture were over 2 million verts. It makes a sane physics map for you also . So despite the high verts, well the physics load is a lot lower than what you get with the viewer. It also will let you list all your oar contents in a text file...and well import it into blender with all the textures and placement just like in world!!! :-) Below is the help menu. and below that the download link.
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
I am proud to announce my release of OarConv Reimagined. This program will allow you to upload any mesh, rigged mesh, or not up to around 1 gigs about 20 files or so at once using an oar file! It auto chunks large meshes automatically. The items in the picture were over 2 million verts. It makes a sane physics map for you also . So despite the high verts, well the physics load is a lot lower than what you get with the viewer. It also will let you list all your oar contents in a text file...and well import it into blender with all the textures and placement just like in world!!! :-) Below is the help menu. and below that the download link.
FILE
Open OAR File: open a packaged .oar archive.
Open OAR Folder: open an extracted OAR working folder.
Convert Data: export the loaded OAR using the format from Tools > Output Format. It reads the existing OAR object XML and companion assets, then writes converted output files to disk.
Convert Data does not create a new LLMesh object or save a replacement object XML. The XML already exists in the loaded OAR and is used as export input.
FILE MENU COMPATIBILITY
The converter is only supported for OARs produced by the actual simulator. Repacked or reverse-injected OARs created by this program are not backward-compatible with the converter and may fail if reopened through File > Open OAR File or File > Open OAR Folder and then converted again.
IMPORT
Step One: create blank.oar and prepare an extracted working folder for injection.
Inject Mesh: add one .dae, .gltf, or .glb model into an extracted OAR. Set location, scale, physics, rigging, and LODs here.
Pack Oar: repack the extracted folder into a final .oar archive.
TOOLS
Objects List: browse objects in the loaded OAR and export selected objects through the normal OAR export pipeline.
Objects List > Export: export one or more selected OAR objects into an output folder. Depending on format, the app may write the main file under Solids or Phantoms and may also create companion folders such as Textures, MTL, or BIN.
Objects List > Export does not create a standalone mesh inventory object. It converts from the object's existing OAR XML and asset data.
Output Format: choose DAE, OBJ, GLTF, GLB, FBX, or STL for export.
Settings: set ranges, shifts, terrain options, and folder prefixes.
INJECT MESH DIALOG FIELDS
Source model: the .dae, .gltf, or .glb file to insert.
Location X/Y/Z: the final placement of the inserted object in the target OAR region.
Current dimensions: read-only size of the source model after analysis.
Scale: uniform size multiplier. 1.0 keeps original size.
Physics: choose how collision data is generated. File mode uses a separate physics model.
Rigged: treat the source as a rigged or avatar-style model.
Include Joint Positions: keep joint position data when rigged import needs it.
Strip Joint Data: remove rigging data and force a static-style result.
LOD High/Medium/Low/Lowest: control each generated LOD level.
Mode: choose how each LOD is derived.
Target Tris: desired triangle count for that LOD when the selected mode uses a target.
Vertices: read-only estimate of vertex count for each generated LOD.
WORKFLOW: OAR TO BLENDER USING GLB
1. Open Tools > Output Format and select GLB.
2. Open the source OAR with File > Open OAR File or Open OAR Folder.
3. Run File > Convert Data.
4. Import the generated .glb files into Blender with File > Import > glTF 2.0.
WORKFLOW: BUILD A REPACKED OAR WITH MULTIPLE MODELS
1. Run Import > Step One once to create a blank working OAR.
2. Run Import > Inject Mesh once for each model you want to add.
3. Source files can be .glb, .gltf, or .dae. Rigged avatar-style models can use the Rigged and joint options.
4. Repeat Inject Mesh until all assets are placed.
5. Run Import > Pack Oar to write the final repacked archive.
PLEASE DO ENJOY!!!!ONLY IN OPENSIM!Feel free to report bugs and or other worthy insights. I have written the original makers of it but not gotten any replies so I do no tknow if they are around or not. It is legal opensource though. THe list of contributors is there. If anyone knows them tell them to say hello...
https://maze.bz/OARConv.html
By request of Deborah Faust I made it so the textures discarded messages is off by default bottom right. It really means nothing anyway that we can do about it. I do have the viewer set to discard things farther away so nothign to miss there either.
In preparation for my mesh injection oar machine fixed a bug with materials on high density meshes where the material slots of pbr would disappear when I edit them. See them here at landmark below.
Download is at https://maze.bz/mazebzviewer.zip
hop://maze.bz:7002/Medieval%20Desert%20Fortress%20Castle/1...
In preparation for my mesh injection oar machine fixed a bug with materials on high density meshes where the material slots of pbr would disappear when I edit them. See them here at landmark below.
Download is at https://maze.bz/mazebzviewer.zip
hop://maze.bz:7002/Medieval%20Desert%20Fortress%20Castle/1...
MazebzOS_AVX2-1-0-0-260650330 bug fix
I went about fixing a bug that was in the edit menus ui where link number and things like that were overlapping the tabs and what not. I fixed that up in this. More to come. Any requests make them
https://maze.bz/mazebzviewer.zip
I went about fixing a bug that was in the edit menus ui where link number and things like that were overlapping the tabs and what not. I fixed that up in this. More to come. Any requests make them
https://maze.bz/mazebzviewer.zip
I have found a solution to a bug created by last weeks nvidia driver upgrade.
1) go to AppData\Roaming\Mazebz Viewer_x64 (make sure you can see hidden files.
2) erase the folder of the user name you are trying to log in with.
3) log in. This will wipe your settings, but it will allow the viewer to boot properly with the new nvidia settings.
1) go to AppData\Roaming\Mazebz Viewer_x64 (make sure you can see hidden files.
2) erase the folder of the user name you are trying to log in with.
3) log in. This will wipe your settings, but it will allow the viewer to boot properly with the new nvidia settings.
Thank you for the new add morning glory
MazebzOS_AVX2-1-0-0-260540551 important for certificates
So I did this
From 2026-02-19 to now: added capped mesh upload fee retries and user-facing logging for missing uploader URLs; refreshed CA handling to download/pin curl’s bundle at build/runtime; kept KDU off and use openjpeg due to licensing/package gaps. Certs for firestorm seem to be locked into 2024!
I also made it retain home in the viewer rather than need the url from the simulator. Hoping to fix the issue where we can't get home.
https://maze.bz/mazebzviewer.zip
So I did this
From 2026-02-19 to now: added capped mesh upload fee retries and user-facing logging for missing uploader URLs; refreshed CA handling to download/pin curl’s bundle at build/runtime; kept KDU off and use openjpeg due to licensing/package gaps. Certs for firestorm seem to be locked into 2024!
I also made it retain home in the viewer rather than need the url from the simulator. Hoping to fix the issue where we can't get home.
https://maze.bz/mazebzviewer.zip