Using Cloud Assets (Stored on Bitbybit Servers)

When to Use Cloud Assets

If you work with 3D models or other assets created in external software packages, Bitbybit's cloud asset feature allows you to upload these files to our servers. This makes them accessible from any browser where you're logged into your account and integrates them directly with your Bitbybit projects.

A cloud asset is a file of a cloud project: you add it under the project's Files, and every script of that project can load it by its title or by its file name. Uploading Cloud Assets shows how. A project kept in this browser has Files too, of any type, kept in this browser only, and they come to the cloud when the project moves there: see Files of a project.

Common Use Cases for Cloud Assets:

• Importing Existing 3D Models: Bring your 3D models (e.g., from Blender, SketchUp, SolidWorks) into Bitbybit to use in your scripts.
• Cross-Device Access: Access your uploaded assets from any computer or browser simply by logging into your Bitbybit account.
• Public Portfolio: When you make a project public, its scripts and their files can be opened by everyone on the internet. This can be a great way to build a public portfolio of your 3D work directly on our platform.
• Integrating with Parametric Models: Combine your imported 3D models with parametrically generated geometry created within Bitbybit, all in a single environment.
• Game Development: For advanced users creating games on our platform, cloud assets can serve as your game asset library (characters, props, environments), which you can load dynamically as your game logic dictates.
• Data Visualization & More: While 3D models are a primary focus, you can also upload other file types as cloud assets:
  • Data Files: Import data in .json or .csv format and parse it within your scripts to create dynamic data visualizations.
  • Texture Images: Upload image files (e.g., .jpg, .png) to use as textures for materials in your 3D scenes.

This section will guide you through understanding and utilizing cloud assets.

Important Things to Know About Cloud Assets

Access Control and Sharing

Understanding access control for your cloud assets is crucial:

• Whoever can open the project can read its files: A project's scripts load its files when they run, so whoever can open the project can download them too. A Public project's files can be read by anyone on the internet; a Silver community or Gold community project's files by the members of that community.
• Protecting Private Assets: A project stays Private until you change its visibility. To keep files private, keep them in a private project, and share a script that needs nothing private from a project of its own.
• A file's address: Copy the file address beside a file copies a link that downloads it. Anyone you give the link to can download the file, whatever the project's visibility.
• Right to Share: If you choose to make your projects (and thus their assets) public, ensure you have the legal right to share those assets. If you are unsure about the licensing or ownership of an asset, do not upload it to our platform or publish it.

Publishing Your Projects explains each visibility. Please review our Terms and Conditions for detailed information on asset usage and sharing.

Advice for 3D Designers and Architects

• Recommended Format for Web: glTF/GLB: While Bitbybit supports importing CAD files like STEP, if you are importing complex 3D models (especially those with materials and textures) for web display, we generally recommend exporting them to glTF (.gltf) or GLB (.glb) format from your original design software.

  • Optimized for Web: glTF is a format specifically designed for efficient transmission and loading of 3D scenes and models on the web.
  • Faster Loading: It typically loads faster than raw CAD files. As CAD files, such as STEP need meshing to be applied.
  • Material & Texture Support: glTF is excellent at preserving materials, textures, and PBR (Physically Based Rendering) properties, meaning your model should look very similar to how it appeared in your CAD software, or even better when enhanced with Bitbybit's lighting and rendering.
  • GLB (Binary glTF): The .glb format is even more optimized as it packages all data (JSON, binary geometry, textures) into a single binary file, usually resulting in a smaller file size.
  • You can further enhance the look of your imported models by creating skyboxes, lights, and shadows within your Bitbybit scripts.

• BIM Models (IFC): Upload .ifc files like any other asset and open them with the IFC API, which reads IFC4, IFC4X3 and IFC2X3 files with their storeys, elements, materials, properties and quantities:

  const file = await bitbybit.asset.getFile({ fileName: "house.ifc" });
  const model = await bitbybit.ifc.model.read({ data: await file.arrayBuffer() });
  const recipe = await bitbybit.ifc.geometry.recipe({ model });
  const solids = await bitbybit.manifold.recipes.build({ recipe, adjustZtoY: true });
  await bitbybit.draw.drawAnyAsync({ entity: solids });

  Each solid comes back with its element's IFC class, name and GlobalId, so it can be picked, coloured or listed. The model can also be changed and written back as IFC, or turned into exact shapes and STEP. The IFC package page covers the whole API, which is new and may still change.

• STEP or IGES Considerations: Importing .step or .iges files can be beneficial for their precision and potentially smaller file sizes for raw geometry.

  • Downside: A STEP file has to be read by the CAD kernel and meshed before it can be drawn, which takes longer than loading a glTF file, the more so for a large assembly.

Choosing the right format and understanding these considerations will help you achieve the best results when working with cloud assets on our platform.