I'm creating a scene that uses JavaScript to toggle the visibility of objects.
Collision settings remain on hidden objects.
This hasn't happened before.
What should I do?
Could you share a link to the scene with us, so we could take a closer look at the issue?
For now this issue can be solved, by appending ?webwalk=1392 suffix at the end of the URL (but before the hash (#), if there is any). This suffix will have to be added to the URLs until the next Shapespark release.
Thank you for your reply. The above solution works fine.
Just to be sure, could you please provide a list of suffixes?
There is only one suffix that should be applied to solve this problem.
For example, if you have a URL like: https://demo.shapespark.com/demo/ you simply add ?webwalk=1392 at the end: https://demo.shapespark.com/demo/?webwalk=1392.
If the URL ends with #autoplay then you should add the suffix before the hash: https://demo.shapespark.com/demo/?webwalk=1392#autoplay.
Even when I load each scene’s index.html from a parent iframe tag with ?webwalk=1392 appended, the ?webwalk=1392 functionality does not seem to work. Why is that?
<script>
document.addEventListener( "DOMContentLoaded", function() {
var _ele = document.querySelector( "#iframe_content" );
var type_str = new URLSearchParams( window.location.search ).get( "type" );
var path_str = "./data/" + type_str + "/index.html?type=" + type_str + "&webwalk=1392";
_ele.src = path_str;
} );
</script>
?webwalk=1392 will only work if the source URL is pointing to the Shapespark cloud. If you have a scene bundle hosted somewhere on your own server, it won’t work, you would have to wait for the next Shapespark release and create a new bundle after that.
Is the issue described above expected to be resolved in the next release?
Hello, yes, sorry for the delay.
It’s possible that we will have a new release in January, but if not then in February for sure.
Hi, this bug has been fixed in today’s Shapespark release (3.6.0).