Sharing: how does your a-scene look like?

đź’¬ Chit chat
1

Just a fun comparison between 8th Wallers…

I’m working on a project for a museum, and our a-scene looks like this:

  <a-scene
    loading-localization
    xrextras-loading
    pipeline-additions
    update-tracker
    images-360
    model-viewer
    pool__imagetarget="mixin: imagetarget; size: 3; dynamic: false"
    camera-feed-delegator
    xrextras-runtime-error
    xrextras-gesture-detector
    renderer="colorManagement:true; webgl2: true"
    xrweb="disableWorldTracking: true"
  >

Our custom components:

  • loading-localization: for translating (and redesigning) all the loading pages.
  • pipeline-additions: added QR code reading.
  • update-tracker: constantly checking a hash code for the latest release, prompting the user to reload the page if anything happens.
  • images-360: starts a 360 view.
  • model-viewer: adds a 3D model inside a-camera to always keep the model static on the screen.
  • pool__imagetarget: We have around 70 image targets but only three image target entities that we (re)use.
  • camera-feed-delegator: listens to events triggered by image targets and QR codes, delegating which entities or components should be triggered based on manifest files that describe all targets in the museum.
2

for me model-viewer & images 360 wrap in one components to be button switch
other is good

3

And what other components do you have for your a-scene? :slight_smile: