It is not possible in the current version of IdeaSpace, but I keep the idea in my mind.
It would help if you could send me the log file (/storage/logs/laravel.log), because there is no reason why the thumbnail generation should fail. And it would help to make IdeaSpace better. Thanks!
I am currently investigating the issue. I uploaded an image with 32MB without any problem. In another test I uploaded 15 image files where the smallest had 1.2MB and the largest 9MB. My server has 8GB of RAM.
Thanks for the log file, it says the issue is a memory error when the images are being resized.
I will come back to you.
@poVoq I am aware of these developments and the networked-aframe component and indeed, there could be a VR learning theme. Currently I don't have enough time to work on such a theme but it is definitely possible!
@poVoq I just tested the raycaster attribute without 5001 value but it is still extending beyond the elements.
It is not an issue using a Samsung GearVR, but I look into this issue.
Do you have the same issue in this theme? - https://www.ideaspacevr.org/theme-preview/ideaspace-360-photo-tour-pro
UPDATE: I tested the theme with A-Frame 0.8.2 and it truncates the laser line. I will test a bit more and update the theme and let you know.
Do you have access to log files from your webhost to get more details of the HTTP ERROR 500?
If you add /index.php to your domain, do you see something? If yes, there is an issue with mod_rewrite and nice URLs.
Does your webhost meet the IdeaSpaceVR requirements: https://www.ideaspacevr.org/documentation
So you could log in and uploaded a photosphere?
Are the DB connection settings still the same? You can take a look in config/database.php. Did you check the php logs? Did you check the IdeaSpaceVR logs in storage/logs/laravel.log?
@Aditya10115175 You have to implement the audio feature. I am using A-Frame as the js library https://aframe.io/
@Aditya10115175 If you have command line access, you would execute php artisan cache:clear
@WeddingDJ Ok, you should also delete all files in storage/framework/cache/*, storage/framework/sessions/* and storage/framework/views/* - it could be that this solves your issue.
@Aditya10115175 I need to see the whole laravel.log, you could upload it here.
For the database settings. I guess you use a MySQL database. You can just compare your MySQL settings with the settings in the database.php file. Make sure that host is 'localhost" (if running on the same server it is ok), that the database, username and password are still the same.
You said some time ago you change the data address, which data address?
I removed your database.php images as this information must stay private.