Optimising work is part of me. I hate repeating the same task again and again. We are using computers, that’s what they are good at, repeating a task for us. When it comes to work in a team, the workflow get even more important so that two different persons don’t overlap each other work or come back with always the same questions of “how you doing this?” or “where is this file?”. This is all good sense in theory, very far for being the norm in practice, at least from my experience, working mostly with architects and designers. Furthermore, as a freelance, months will pass without using a specific workflow, working on a different project with different software. Being able to look back at how we did something is a must if we don’t want to repeat the same mistake again.
On the Saydnaya project I was working on with Forensic Architecture for Amnesty International, we produce a series of interactive 360 panoramic views developed using the fresh WebVR. We didn’t get enough time to develop it in VR, although it is real-time 3D online in a browser, no plugin, no viewer needed. Pretty awesome stuff! Here is the workflow we used to get those 8 Interactive 360 Panoramic views online:
- Some of the 3d models were made with Rhino then exported to 3dsMax, most of the models were made only with 3dsMax avoiding any mistranslation between Rhino and 3dsMax, two very different modellers.
- All the texturing and lighting was done in 3dsMax, then baked to texture.
- Optimization was a big part of the process.. Models were exported in OBJ (only meshes) and optimised with MeshLab. Maps were optimized with Photoshop.
- Everything was tested in a sandbox in WebGL using MAMP as a Apache Local Server, Atom to edit the PhD and Python files.
If you are interested and would like more details, let me know in the comment below or via email.
What is WebVR? It is 3 things, see this Reddit post here for more details:
- WebVR is configuring the VR HMDs
- WebGL is about drawing in WebVR using mainly three.js
- HTML5 is the sandbox to play in.