We're here to help! We just need a little bit of information...
What system are you using?
Have you downloaded the latest version of Lens Studio?
Is this issue causing Lens Studio to crash?
What system do you run Lens Studio on?
Follow the next steps to help us solve your issue:
Copy and paste this text into your TerminalCommand Window
open ~/Library/Preferences/Snap/Lens\ Studio/ %LOCALAPPDATA%\Snap\Lens Studio Copy Text
- Press ReturnEnter to run the command. The Lens Studio folder will automatically open
Prepare to upload your files: zip the "Log" Folder by right-clicking and choosing "compress."Locate the Log.txt file right above it.
Attach a screenshot of the issue:
What is this most relevant to?
Please enter a brief description of your issue:
Thanks for submitting this issue.
Unfortunately, it's likely due to the operating system or hardware you're using – since they don't meet the system requirements for Lens Studio.
Still, we hear you loud and clear, and are logging the issue in case there's ever a workaround we can provide!
Operating System: Windows 10 (64 bit); MacOS 10.11+
Hardware: Minimum of Intel Core i3 2.5Ghz or AMD Phenom II 2.6Ghz with 4 GB RAM; Intel HD Graphics 4000 / Nvidia GeForce 710 / AMD Radeon HD 6450 or better; screen resolution of 1280x768 or higher
We'll try to resolve this issue as soon as possible. Thanks for letting us know about it!
Keep an eye out for a followup email from us. We may have a couple more questions for you, or we might already have a solution to offer.
The issue is that the way the graph is setup the "Set VFX Property" node doesn't know what type the "life" property is so when you type 5 into the inspector it interprets it as the string "5". There are two good ways to get this working how you want:
Oh, I didn't know assets could be dropped into the graphs. That's good to know! Works like a charm :)
Thanks for your help!
Hey! Is it possible to drive a vfx value by text script?
I have a custom trigger and want it to drive a value in a vfx component
Yeah, something like this:
Thanks Josh :)
It seems like we need to use the specific script in that example for sendDataToVFX to access properties, it would be helpful if it was noted in the API documentation for vfx