Hi all,
Those who have been here for the last couple of months surely noticed that I've been very active with krpano, especially with the 3D possibilities. But up to a couple of weeks ago, I did not have any experience in building a real tour and my focus was more on building small extentions for krpano to make tour building more accessible.
Thanks to these experiments I have had contact with some really nice people and had a chance to exchange ideas, share experiences and learn from eachother.
In one of those contacts, we explored how krpano could handle a larger 3D model. The model was a photogrammetry scan of a ruin and provided in glb format.
Some data:
- vertices: 482.736
- faces: 413.744
- glb size: 14.6Mb excl textures
- textures: 6x8K textures (total: 65Mb)
Wireframe:
So I started building a tour simular to the one online now at https://www.ruineaggstein.at/en/castle-ruin/360-degree-tour. As I didnt want to put 30+ panos as hotspots on the map so I looked up the most interesting points and came across 2 reference points:
I really like the style of the second one. Cirlces and numbers - looks like my annotations plugin
In the end, I decided to go for the content of the first one, mapping all points (1-16) on the 3D model with the annotations plugin. Looking back, it may have been too much (it is a bit distracting when you open the 3D model the first time).
Some observations:
- krpano is really good at handling these files. And when using 8K textures, the obj always loaded fast (at least locally), and in the browser, the most time is spent re-mapping the textures to the model when loading the scene. With 4K, this goes a lot faster so I opted for that resolution in the final tour
- The converted obj file is about 60mb and baked textures for the day/sunset views are 4K and 20Mb in total. Especially the obj file format is a lot more bandwidth to transfer...
- building tours is hard work with krpano! Organising the panos, linking them together, find a good way to navigate... I underestimated all aspects of the workflow
- while eating my own dogfood with the annotations, I found many things that could be improved so I did those along the way - an update is coming soon (adjustable colors, some workflow improvements, ...)
- Building the menu from scratch was also a challenge, but I'm happy with the result.
- I still miss some key features for these types of tours, more specifically an easy way to link the panorama's to the model/depthmap and a nice transition from the model to that panorama. if anyone has any tips/tricks, do reach out...
- I need to pay more attention to mobile when creating the tour (menu needs a good mobile version, could also load different versions of the models when using mobile to save bandwidth, ...)
All in all this was a very nice learning experience. Special thanks to Sebastian from https://360studios.at/ for the mentoring and providing the models/pano's.
And if you are curious: here is the tour:
https://krpano.kri-soft.be/aggstein/
Screenshot:
Would love to hear your feedback!?
gr,
Kristof