@poVoq I see. So there is no issue with clicking the navigation element in Daydream VR but rather a "visual irritation" for the user regarding the pointer line which suddenly "jumps" from infinite z-distance to the intersection of a navigation element.
The reason why it intersects and truncates even before hitting the navigation element is that I wrap the navigation element in a hidden circle which is closer to the camera than the actual visual elements. I need to encapsulate the visual elements otherwise the mouseenter and mouseleave events from A-Frame are not consistently triggered.
I agree that a laser pointer with a dot at the end of the line would be perfect. In Gear VR in Oculus Home the laser pointer renders as a white dot on an element as well. Your idea of having an invisible sphere would in theory work, but not with the current raycaster / laser-controls components in A-Frame, I think.. I saw the crawling cursor component but did not look into it how it is implemented.
What would work is to hide the current raycaster line and attach a white small sphere at the intersection point of any element and hide the white sphere when intersecting at a fixed distance (eg. don't show the sphere if intersecting at z >= 5000). The raycaster returns an intersection event containing x, y, z coordinates where it intersects with an element. I will add this as a feature request in github for all themes.
I just find the line (with your comment) , change it and....... It Works!!!!
Thank you a lot.
By the way learn about codecs and conversion, unfortunately H265 seems not being supported and there is not control in reproduction.
More things to be done.
Thank you again.
Did you check the memory_limit value if you dump your php configuration with phpinfo()?
If you use the Photosphere Viewer theme you can configure the image quality in themes/photosphere-viewer/functions.php. It is set to 75 per default. You could lower this value in order to reduce memory consumption.
Some configuration in your system does not allow PHP to allocate more memory. According to your log it looks like that 132120576 Bytes is the maximum and the additional 33554433 bytes for resizing the image cannot be allocated.
You could try to configure the memory_limit = -1 so PHP would take what it needs.
@freseco Yes you could create the user manually, and you will need some settings in the settings table too. Ideally you reinstall IdeaSpace with your working DB settings. If not these two files show you which values you have to insert into the user and settings DB tables: