Motiva has announced the release of Layama, a new tool that creates 360-degree tours in just a few clicks. The aim of Layama is to produce 360 tours that do not compromise on rendering quality or require high-end machines to run in the way that Real-time VR does while adding more natural navigation and camera movement that does away with clickable hot-spots. The project is rendered and automatically output to a website that can be hosted on the user’s own servers. You can try an example out below.
Layama is compatible with 3DS Max (V-Ray and Corona render engines only), Unreal Engine and Blender (Cycles and Eevee). A Cinema 4D compatible version is planned for release in the future. The website that Layama produces should run on any modern browser, including mobiles.
At launch, Layama was released for the promo price of €120, rising by €1 per day until it reaches the final price of of €180. Find out more and see examples on Motiva’s website.
Interactive Layama demo – use your mouse to try it out
Now that’s a neat software!
Unfortunately it’s just mono 360, no stereo. I was hoping for an alternative to VRto.me, which gets expensive fast, especially if you want to host it on your own server. But it does support VR headsets. We end up making our own stereo viewers for the flexibility and to add depth support for hotspots and the laser pointer.
I think they will implement stereo at some point in the near future 🙂
Seems it’s on their very early stage, no trial version, no tutorials, not a lot of samples?
It was released 3 days ago, video tutorials are being recorded right now 😉
The best software I’ve found for this is Yulio (https://www.yulio.com/)
It’s a bit pricey, but is perfect for architects wanted to do good 360 VR
I’ve had the chance to talk to their Product Owner and they have a lot of really innovative features coming up!
Looks good, I hope it comes the stereo soon.
I bought it just yesterday and all the antivirus are saying that’s a trojan
looks promising but fishy
What AV are you using? we’ll try to contact them to whitelist it. Usually that kind of fake detections are caused by the antidebugging systems, since the AV cannot debug the code it raises an heuristic warning.