#Can't open in Quicklook if Scene has SetActiveOnClick component after 3.37.11 exp update
1 messages · Page 1 of 1 (latest)
Thanks for reaching out @wicked karma
Please read through the following and share the information requested. This will help us to better assist you.
Description
Describe the issue that you're seeing. Please be as detailed as possible e.g. is this issue happening in Unity or Blender, which Needle Engine version are you using, do you see any errors in the Editor or Browser console, etc.
Information:
- If you're using Unity click the menu item Needle Engine/Report a Bug/Copy Project Info to Clipboard. Please share the results below.
- Please provide code snippets using Discord Code Blocks
- Have you contacted Needle through another channel or just through Discord?
Thanks for submitting!
💡 Did you know that we now also have a forum with AI support? Join now with your discord account!
The issue seems to be from set active on click component. Removing it from scene made quicklook work
Can't open in Quicklook if Scene has SetActiveOnClick component after 3.37.11 exp update
Can you please report a bug as the console log suggested? We have done a number of improvements to USDZ generation but it seems there have been a few regressions.
If you send in a bug report I can look at it
Already sent the bug report. My guess is it's happening when an go has more than one set activate on click component in it
Hi, can you try again with the latest patch release version 3.37.12-alpha.1 (you can update by clicking Install again in Unity on ExportInfo)
Will try it on Monday and update
I updated to latest version 3.37.12-exp and the issue still there. When i click open in quicklook i get this error.
Does this work on latest now? Otherwise would be great if you could report a new bug
Not fixed still getting the same error in 3.37.13-exp. Uploaded a new bug report
it was working fine, something broke it in the recent updates i guess
No, I haven't tried the image tracking in needle engine so far
Thank you!
Hey @wicked karma this was a regression on our end affecting how Sprites that were never enabled in the scene were treated on export. Will be fixed in the next release. Sorry for the regression
Thanks for the update
This issue is fixed. Thanks a lot