135 results found
-
Send a mail when Draft lens is ready
A mail is not send when a Draft lens is ready. This feature is used to quickly send out test links to clients. Would be nice to get a notification as there's none right now.
2 votesthanks for this feedback Danny -- we will review this and let you know if this is something we can execute!
-
Enhanced Lens Creator Rewards Insights
It would be great if Snapchat could integrate Lens Creator Rewards Insights directly within the app. Also, adding an option to filter Lens rewards by Qualified Poster, sorted from low to high, would significantly enhance the creator's experience. Currently, this functionality is unavailable.
2 votesThanks for this helpful feedback. We will definitely be looking into how to improve insights around creator rewards.
-
LAT - Project-wide asynchronous loading
I am running into LAT issues quite often, even on relatively simple lenses. I feel like the push for a low LAT is going to lead to lots of very low quality, simple lenses because maintaining a low-enough LAT introduces complexity into the project. Currently I will finish up a lens, turn it into a prefab, then use the scene manager to load it asynchronously. It works, but it leads to a very clunky developer experience because now I have to remember to apply my prefab changes and then disable the prefab again so that the scene manager is the…
2 votesHey Mike,
Your post has spurred important discussions, We will continue to update you as we find additional ways to improve LAT including reviewing your thoughts here.
Thanks
Raag
-
Favorite Assets and Most Used for the Asset Library
It's great that Lens Studio has so many assets but sometimes it is hard to find certain assets without remembering their full name. Or other times I would see something I want to try later but I day later I won't remember what it was. If we could favorite assets that would significantly help with that problem.
Another tab that would be also very helpful - most used assets so we don't have to look for the assets we use all the time.
2 votesThis is a good idea -- there are some challenges we will have to explore for personalization.
We will let you know as we consider the idea
-
1 on 1 mentorship program
Members of the community or even some SLN who want to improve their skills can apply to be matched with SLN members who are willing to mentor them and teach them skills in creating lenses for different criteria. Some focus areas can be creating for engagement or for advanced technical innovation. If resources are available, we can do networking with everyone involved, etc.
2 votesWe love this idea for 1:1 mentorship opportunities. It's something that would take some time for our team to develop. We will consider this in the future!
-
Shadows Support For Bitmoji
So I think this has been requested multiple times on discord as well but yeah native option on 3D Bitmojis would add more detail to the experiences. Thanks to the new Inspect Preview I was able to see all the render mesh visuals of the bitmoji being added to the scene so I quickly wrote one script to navigate through and enable shadows dynamically through it but that way also didn't work coz I guess the mesh data wasn't available however I was able to change out the materials tho. Shadow and material options would be great properties to expose…
2 votesHey Krunal!
Excited to say that we should have a fix coming in the next version that will allow this to work!
Thanks
-
Organize My Lenses Dashboard
Currently my work is spread across multiple accounts on the My Lenses Dashboard, including a bunch of early work before we went to the lens folder system. I'm also still a part of many organizations that I built a professional effect for, but I'm no longer working for that client. It would be nice to be able to clean up my dashboard, move lenses from a legacy account into my new one and leave organizations that I'm no longer a part of.
2 votes -
Custom Code Node Errors + Code Height
When writing a custom code for a shader, the errors don't appear automatically. You need to click on another node and then click back on the code node so you can see the error.
Changing the "height" parameter so you can see more lines of code is not working either.
2 votes -
Custom Code Node Typing Suggestions
When writing a custom code node in LS 5.0, the suggestions are not very smart.
For example, in LS for, if you want to get a normal vector you could type "system.normal" and it would suggest automatically "system.getSurfaceNormalWorldSpace".
In LS 5.0 that doesn't happen, you need to type the exact same thing as the API.
My suggestion is to make it a little bit smarter like it used to be in LS 5 ;)
Cheers,
Caio2 votes -
Lens Studio 5.0 digital goods
I really appreciate the new features and updates in Lens Studio 5.0. I would like to offer a suggestion that could be highly beneficial for all creators.
You should add digital goods to Lens Studio 5.0 as soon as possible. Adding digital goods will provide significant benefits to many creators. It will help enhance their creativity and monetization opportunities.
I have personally earned a significant amount using digital goods, totaling 100,000+ coins. Therefore, I strongly urge you to make digital goods available in the next version of Lens Studio 5.0 as soon as possible.
Thank you.
2 votesCurrently adding digital goods to lens studio 5.0 is in the backlog but we do not have any timeline at this time.
In the meantime, we ask that you use Lens Studio 4.55 for any ILDG lenses at this time
-
Top Lenses (Top Posted Lenses)
Hi Team,
I am writing to suggest an enhancement to the new 'Post' metrics in the My-Lenses section. It would be incredibly beneficial to have an option in the dropdown menu for 'Top Posted Lenses'. This feature would allow users to easily identify which lenses are being posted the most. (See image as reference)
/Baruch
2 votesThank you for this feedback. it is an interesting idea that we have put into backlog for review.
-
Physics Overlap/Collision Events Include Triangle Hit Info
Currently the only way to get triangle hit information is from raycasting. This creates a convoluted code flow when trying to ascertain the hit triangle from an overlap or collision event, because both a raycast needs triggered and a check needs to happen to ascertain if the raycast hit mesh is the expected mesh
2 votesHey Blake,
We have identified this note pertains to our Lens Core engine.
We are currently slated to other priorities but we have taken this note and we will revisit periodically.
Thanks!
-
Physics Overlap Events include Contact Information
Currently only Physics Collide events include contact information. This makes it difficult to write custom collision responses for when using non-BodyComponents.
2 votesHey Blake,
We have identified this note pertains to our Lens Core engine.
We are currently slated to other priorities but we have taken this note and we will revisit periodically.
Thanks!
-
DepthTextureProvider is accessible via script
Currently DepthTextureProvider is not accessible via script, causing the need to have a blit operation to a rendertexture with packed floats in order to get high precision depth data to use in script.
2 votes -
2 votes
We are continuously working on improving the models that we are using for our generative AI capabilities.
Lens Studio 5.0 is just getting started and we are excited as we continue to watch it grow!
-
Scroll horizontally in Hierarchy panel
When there are lots of child SceneObjects, the Scene Hierarchy window needs to be really wide to be able to see them. It would be ideal if it could scroll horizontally!
1 vote -
Generating MarkerAssets on runtime
Creating Image Markers from Texture Assets in real-time could add some really cool functionality to lenses, both in Spectacles and on mobile.
For example, the 'Stand Out Object Segmentation' could be used to generate an image that can then be tracked to.
1 vote -
Add a 3D 'mannequin' to the Interactive Preview scenes
It would help a bunch to have a realistic 3D body in the Interactive scenes, so the 3D body tracking can pick it up. This would help with testing real-world situations where the body tracking might be used in combination with world tracking.
1 vote -
Fix: getComponent(SomeClass.getTypeName()) bug
getComponent(SomeClass.getTypeName()) seems to not be checking the numbers after the colon ":" in the getTypeName() string!
When the string is the same before the colon for multiple components on the same SceneObject, it can return the wrong component. Been running into this a couple times and it took a while to figure out what the issue was.
1 vote -
Changing Inspector values with arrow keys should be relative
Changing Inspector values using arrow keys with multiple SceneObjects selected should increase/decrease relatively, instead of overwriting all object's values.
For example, transforming SceneObjects should be a relative distance on top of their original positions.
1 vote
- Don't see your idea?