176 results found

1. Face Occlusion Asset Not Available

   Hey everyone.

   I was going through the documentation and noticed that the Face Occlusion asset is not available in the Asset Library anymore. So either the documentation is outdated or there's actually an error in the library.

   Here is the documentation link:
   https://developers.snap.com/lens-studio/features/ar-tracking/face/face-templates/face-occlusion

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. The Snapchat UI Preview in LS is outdated

   There's new icons in the middle right of the UI and the call to action for branded lenses is now underneath the camera button. Scan is obviously gone for YEARS already so i would appreciate an update there.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Iraq has a large and growing community of talented Lens Creators and millions of active Snapchat users. Every day, creators in Iraq publish

   Iraq has a large and growing community of talented Lens Creators and millions of active Snapchat users. Every day, creators in Iraq publish high-quality AR Lenses that entertain people around the world, yet they still cannot access the same monetization opportunities available in many other countries.

   Creativity has no borders. If creators in supported countries can earn from their work, Iraqi creators deserve the same opportunity. We invest our time, skills, and passion into building experiences that bring value to the Snapchat community.

   We respectfully ask Snapchat to include Iraq in the Lens Creator Rewards and Lens+ payout programs. Supporting Iraqi creators would inspire innovation, grow the AR ecosystem, and reward thousands of talented developers who are ready to contribute even more.

   Please give Iraqi creators the opportunity to build, create, and earn—just like creators in other supported countries.

   SupportIraqiCreators #Snapchat #LensStudio #ARCreators #LensCreatorRewards

   Iraq has a large and growing community of talented Lens Creators and millions of active Snapchat users. Every day, creators in Iraq publish high-quality AR Lenses that entertain people around the world, yet they still cannot access the same monetization opportunities available in many other countries.

   Creativity has no borders. If creators in supported countries can earn from their work, Iraqi creators deserve the same opportunity. We invest our time, skills, and passion into building experiences that bring value to the Snapchat community.

   We respectfully ask Snapchat to include Iraq in the Lens Creator Rewards and Lens+ payout programs. Supporting… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Hide occlusion objects in phone Spectator mode

   Right now in Spectator mode with your phone, if worldmesh or hands are set with an occlusion material they just show black, please just dont render them in spectator pov.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Allow more than 25 mb of remote assets for audio track assets.

   Allow more than 25 mb of remote assets per project for audio track assets.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Downloading videos straight to PC via cable

   As the title says, it would be significantly faster and more convenient to transfer videos directly from Spectacles to a folder on a computer, without having to go through additional steps or mobile workflows.

   For creators, developers, and content producers, direct PC access would greatly improve productivity, speed up editing pipelines, and simplify file management. It would make exporting, archiving, and processing footage much more efficient, especially when handling large amounts of content.

   A simple drag-and-drop workflow or a desktop transfer option would be a huge quality-of-life improvement for the entire Spectacles community.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. make a first-party, Adjustable, behind the head, head strap for the Specs so it can be ready on release day as an optional accessory.

   Hear me out: make a first-party, Adjustable, behind the head, head strap for the Specs so it can be ready on release day as an optional accessory.

   I firmly believe front heavy AR Smartgoggles like this should have a optional head strap to both support some of the front weight off your nose,

   But to also prevent the Smartgoggles from sliding down your nose or even falling off completely when leaning forward from various task.

   I own INMO Air3 Smartgoggles which has a similar form factor and front weight bearing design. So this is a suggestion from my experience.

   I think this is something to consider and not overlook. Because nose pad alone isnt a good solution in my opinion.

   Hear me out: make a first-party, Adjustable, behind the head, head strap for the Specs so it can be ready on release day as an optional accessory.

   I firmly believe front heavy AR Smartgoggles like this should have a optional head strap to both support some of the front weight off your nose,

   But to also prevent the Smartgoggles from sliding down your nose or even falling off completely when leaning forward from various task.

   I own INMO Air3 Smartgoggles which has a similar form factor and front weight bearing design. So this is a suggestion from my experience.

   I… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Increase SnapML limite size for CameraKit Lens use.

   Ny goal is touse two character skin ML in the same project (See the Disney Avatar Lens as reference)

   https://youtube.com/shorts/2B4Bw1y06c0?si=K3omapIlwi7SaTag

   But we are facing a problem,
   1. Limit is 10mb and 1 character ML is 7mb
   2. We tried to import dynamically Prefab or MLAsset but API restrict us
   3. Switching Lens technic wont allow us to use both Male and Female character in teh same lens...

   So we're stuck with limitation amde for mobole while we are running this on Mac Mini AR Mirror...

   •  

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Shader Graph UX Improvements

   Version: Lens Studio 5.15 (latest Spectacles compatible as of writing)

   Feature requests:

   • Batch auto-creation and wiring of input nodes with matching type based on the empty input sockets of a processing node (such as custom code).

   Documentation on:
   - the compilation life cycles of nodes
   - the way ss_graph are stored in cache
   - how updates to their contents are saved and guidelines for source control.

   • Auto layout of nodes in the graph or some approach to prevent overlaps.

   • Error translation layer for the logger, as current error messages can hard to decipher.

   Bugs / Oddities:

   • If an input node is wired to a processing node that's fed into the shader graph output, then renaming it will cause freezes and cursor movement midway through.

   • Autofill of input node 'Title' based on 'script name'

   • Custom code nodes do not support early returns, unclear if bug or current limitation.

   Version: Lens Studio 5.15 (latest Spectacles compatible as of writing)

   Feature requests:

   • Batch auto-creation and wiring of input nodes with matching type based on the empty input sockets of a processing node (such as custom code).

   Documentation on:
   - the compilation life cycles of nodes
   - the way ss_graph are stored in cache
   - how updates to their contents are saved and guidelines for source control.

   • Auto layout of nodes in the graph or some approach to prevent overlaps.

   • Error translation layer for the logger, as current error messages can hard to decipher.

   Bugs / Oddities:

   • If an input node… more
   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Bug: Custom Code node compilation breaks with comments after inputs

    When a comment is typed on the same line as an input in Custom Code nodes, the compilation throws an error in the logger.

    •  

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Visual Scripting workflow issues in Lens Studio 5

    After testing Lens Studio 5 and building 5+ lenses using only Visual Scripting, I have run into a few workflow issues that slow down development and make debugging harder. Would be amazing if these can be looked into.

    • Texture Array inputs for example or a SceneObject Input lose their contents after renaming

    If I create a Texture Array input in the Visual Script graph, name it something like “TexArray1”, and fill the array, changing the input name later clears the array contents. Same happens with a Sceneobject input. the assigned object dissapears after a name change.

    It would be much better if renaming the input kept the existing array items.

    • Pasted nodes appear in random positions

    When copying and pasting connected nodes in the graph, the pasted nodes often appear far away or in unexpected places.

    It would be helpful if pasted nodes appeared near the mouse pointer, or directly underneath the original selection.

    • Copy and paste does not always preserve connections

    When copying and pasting a group of connected nodes, the pasted version often loses connections, especially when subgraphs are part of the selection.

    If the subgraph was created by the user, connections inside the subgraph can also disconnect. This makes it tedious because every pasted subgraph has to be checked for missing links.

    Cut and paste seems to preserve connections more reliably than copy and paste.

    • Creating subgraphs from selected nodes can crash Lens Studio

    If I select a group of connected nodes and right-click to create a subgraph, Lens Studio sometimes crashes.

    This seems more likely when a Tap Event or similar trigger node is included in the selection. It is not always clear what causes the crash.

    An error message in the log window would be helpful instead of a full crash.

    • Node inputs and outputs feel too easy to disconnect by accident

    Inputs and outputs feel quite sensitive. Clicking anywhere on a node body, instead of only on the node header, can sometimes start unwanted phantom connections.

    There are also times where the mouse is idle over a node, and one accidental click disconnects an input or output.

    This is especially frustrating because Command/Ctrl Z often does not undo the disconnection.

    • Undo and redo are unreliable

    Command/Ctrl Z and Ctrl Y do not always undo or redo the most recent action.

    For example, undo might revert a rename, but not undo the action I just performed. This happens often when moving grouped nodes, copying and pasting, or when pasted nodes accidentally land inside a group.

    In these cases, undo sometimes does nothing.

    • Runtime errors are hard to trace back to the broken node

    When an error appears like this:

    03:09:25 TypeError: cannot read property 'getComponent' of undefined
    Stack trace:
    getScreenTransform@Empty Script Graph.lsscript
    executionnode745@Empty Script Graph.lsscript:2978
    executionnode660@Empty Script Graph.lsscript:2967
    executionnode657@Empty Script Graph.lsscript:2959

    It is hard to diagnose because the .lsscript file is binary, so the line numbers are not readable or easy to inspect.

    It would be much easier if the node, input, or output causing the error turned red in the graph. This would make debugging more visual and help users go straight to the issue.

    Sometimes the problem is as simple as a missing Scene Object connection, but it takes much longer to find than it should.

    • Finally Would be good to have subgraph variables. At the moment global variables can be read in a subgraph. It would be great if variables in a subgraph are not affected by global variables.

    After testing Lens Studio 5 and building 5+ lenses using only Visual Scripting, I have run into a few workflow issues that slow down development and make debugging harder. Would be amazing if these can be looked into.

    • Texture Array inputs for example or a SceneObject Input lose their contents after renaming

    If I create a Texture Array input in the Visual Script graph, name it something like “TexArray1”, and fill the array, changing the input name later clears the array contents. Same happens with a Sceneobject input. the assigned object dissapears after a name change.

    It would be much… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. New Visual Scripting nodes.

    It's great using the visual script graph but these nodes would be great to have.

    • A working version of WaitforSeconds subgraph

    • DoOnce node

    • Do N node

    • a node that sends an execute / trigger remotely instead of having long connection lines in the graph

    • Index Generator, with ability to take a number range like 0 - 5 etc and output a loop output, shuffle the numbers and output or random output

    • Option picker for numbers, boolean, arrays, vec2,vec3,vec4 - allows input of these types and can expand the input like sequence node but then allow the user to have an index that can select one of these inputs.

    It's great using the visual script graph but these nodes would be great to have.

    • A working version of WaitforSeconds subgraph

    • DoOnce node

    • Do N node

    • a node that sends an execute / trigger remotely instead of having long connection lines in the graph

    • Index Generator, with ability to take a number range like 0 - 5 etc and output a loop output, shuffle the numbers and output or random output

    • Option picker for numbers, boolean, arrays, vec2,vec3,vec4 - allows input of these types and can expand the input like sequence node but then allow the user to have an… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Introduce variable fonts

    https://fonts.google.com/knowledge/introducing_type/introducing_variable_fonts

    This would be really nice as most web fonts transition to these and will save lens space.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Face Swap Potential Bug

    I think there's a bug with the new version of Face Swap asset (1.3.3) where the Wait for Result option doesn't behave as expected. Even with it still on and the "Swap On" set to manual, it triggers the result to output.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. More Support for Lens Games

    Hello Snap team,

    As a Snapchat game developer, I spend a lot of time and effort creating fun, interactive games for users. However, I have noticed that when my games are enrolled in Lens+, they often receive fewer uses and shares compared to when they are available outside Lens+.
    Game Lenses require significant development time, programming, testing, and creative design. They are very different from beauty Lenses or AI-based Lenses, so I believe they should have a separate reward system or a different calculation model that better reflects the effort behind them.
    This would be a great way to support and encourage game developers who are helping grow the Snapchat gaming experience and bringing more interactive content to the platform.

    Thank you for considering this suggestion.

    Hello Snap team,

    As a Snapchat game developer, I spend a lot of time and effort creating fun, interactive games for users. However, I have noticed that when my games are enrolled in Lens+, they often receive fewer uses and shares compared to when they are available outside Lens+.
    Game Lenses require significant development time, programming, testing, and creative design. They are very different from beauty Lenses or AI-based Lenses, so I believe they should have a separate reward system or a different calculation model that better reflects the effort behind them.
    This would be a great way to support… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Support for SPZ format Gaussians

    Would love to request native support for the .spz format for Gaussian Splats in Lens Studio in addition to .ply. SPZ is rapidly becoming an emerging industry standard with platforms and tools like Niantic Scanniverse and Marble Worlds adopting it for more optimized storage, faster loading, and better streaming workflows. Native SPZ support inside Lens Studio would greatly improve interoperability, reduce conversion friction, and make it much easier for creators to bring real world Gaussian captures directly into Spectacles and SnapAR experiences

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Feature Request: Dedicated Lens Studio IDE for Spectacles

    Developing for Spectacles within a mobile-first IDE creates unnecessary friction. Many mobile features are redundant or broken on the device, while essential Spectacles functions lack native integration.
    Key Issues
    • Feature Redundancy: Tools like Segmentation remain visible in the UI despite being unsupported, leading to developer confusion.
    • Lack of Native Parity: "Device Tracking - Surface Mode" doesn't work natively for Spectacles; we shouldn't need a separate placement package for a core spatial feature.
    • API Fragmentation: The shared API list is cluttered with mobile-only methods, making it difficult to identify Spectacles-compatible logic.
    Proposed Solution
    I am requesting a Spectacles-specific version of Lens Studio (or a dedicated "Native Specs Mode") that includes:
    1. A Streamlined UI: Automatically hides all non-functional mobile features.
    2. Native Surface Support: Built-in surface placement that works out-of-the-box for world-locked content.
    3. Dedicated Documentation: A standalone API reference strictly for Spectacles-supported features.
    At this stage, Spectacles development has evolved enough to deserve its own native environment and optimized workflow.

    Developing for Spectacles within a mobile-first IDE creates unnecessary friction. Many mobile features are redundant or broken on the device, while essential Spectacles functions lack native integration.
    Key Issues
    • Feature Redundancy: Tools like Segmentation remain visible in the UI despite being unsupported, leading to developer confusion.
    • Lack of Native Parity: "Device Tracking - Surface Mode" doesn't work natively for Spectacles; we shouldn't need a separate placement package for a core spatial feature.
    • API Fragmentation: The shared API list is cluttered with mobile-only methods, making it difficult to identify Spectacles-compatible logic.
    Proposed Solution
    I am requesting a Spectacles-specific… more

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Matcap Shader Error

    Hi, I believe there's an error with the matcap reflection node available in the shader editor. When the camera rotates in the Z axis, the reflections rotate as well, which I believe shouldn't happen.

    I think the error is in line 25:
    vec3 right = normalize(cross(forward, system.getCameraUp()));

    I believe it should be
    vec3 right = normalize(cross(forward, vec3(0.0, 1.0, 0.0)));

    because otherwise the camera up vector changes when the camera rotates

    •  

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Multiple Scenes

    Lens Studio would benefit enormously from true multi-scene support for game and app development workflows.

    Right now, larger projects are forced into one giant scene or awkward prefab-based workarounds. There was a Scene Manager system in the past, but it relied on scene-sized prefabs, was difficult to maintain, and has since been deprecated. For developers trying to build games or more complex interactive experiences, proper scenes would be a major quality-of-life improvement.

    Why scenes matter

    1. Clean restarts / state resets
       Reloading a scene is one of the simplest ways to reset gameplay state. Without scenes, developers often need to manually reset every variable, timer, spawned object, enemy state, UI state, etc. That becomes messy fast.

    2. Better project organization
       Separate scenes for:

    Main menu
    Tutorial
    Gameplay
    Pause menu
    Results screen
    Different maps / levels
    Testing environments

    This keeps projects cleaner and easier to maintain.

    1. Loading & performance optimization
       Only load what is needed. A menu scene should not need gameplay assets loaded. A small tutorial scene should not carry a full boss fight’s content in memory.

    2. Team collaboration / Git workflows
       Multiple developers working in one project can work on different scenes rather than constantly touching the same master scene file and causing merge conflicts.

    3. Multiple levels / experiences
       Some experiences naturally need multiple spaces or levels. While dynamic instantiation is useful, forcing everything into runtime spawning is often slower to build, harder to debug, and less intuitive than authoring levels directly.

    4. Faster iteration & testing
       Jump directly into a combat test scene, UI sandbox, or performance benchmark scene without loading the whole project.

    About persistent data between scenes

    A concern raised is “how do you know what carries over?”

    That is already solved in many engines:

    Default behavior: scene-local data is destroyed on load
    Optional persistent/global objects for intentional carryover
    Explicit saved state systems
    Developer-controlled scene transitions

    This is a feature, not a problem. Many developers want scene changes to clear state by default.

    Suggested implementation
    Additive or single-load scene options
    Persistent global manager objects
    Async scene loading
    Scene transition callbacks
    Build settings / scene order list
    Editor play-from-selected-scene support

    Lens Studio would benefit enormously from true multi-scene support for game and app development workflows.

    Right now, larger projects are forced into one giant scene or awkward prefab-based workarounds. There was a Scene Manager system in the past, but it relied on scene-sized prefabs, was difficult to maintain, and has since been deprecated. For developers trying to build games or more complex interactive experiences, proper scenes would be a major quality-of-life improvement.

    Why scenes matter

    1. Clean restarts / state resets
       Reloading a scene is one of the simplest ways to reset gameplay state. Without scenes, developers often need to manually… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Material Blend Modes Resources

    I've been struggling with the large choice of BlendModes, particularly how they affect the final look of the materials accross different devices, particularly 2024 Spectacles. I’d love to make an empirical tutorial on them, but because the Lens Scripting API documentation currently doesn't provide information on their exact expressions https://developers.snap.com/lens-studio/api/lens-scripting/enums/Built-In , I’d run the risk of providing inaccurate or confusing information.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating