In July 2020, I decided I wanted to get serious about photogrammetry. I first learned about photogrammetry at university in 2014, using 123D for mobile scanning. It was slow, buggy and poor quality. I didn't really think much of it until some time in 2019 when I tried it again, this time with a DSLR and Meshroom. I was unsuccessful because I didn't really know anything about photogrammetry, so my results were not good enough to use. But when I saw this video earlier this year, I was really amazed by the process and the results. I never considered doing it this way, but it made a lot of sense and I decided to start building a small, affordable set up to give it a shot.
Every week I see the same question on Reddit, Discord or even through my own website, asking what they should do if they want a career in the architectural visualisation industry. The answer is generally the same each time, because there are very few requirements to get into it. I wanted to write a post to hopefully answer the many questions in one place based on my own experience and from speaking to others working in archviz.
Corona is a big player in the ArchViz industry. It is safe to say that almost every artist has heard of Corona or used it at some point. The reason being, it's very good. I have known about Corona for years, but never given it much of a try until now, making it the third renderer I have used for ArchViz after VRay and FStorm. So, here are some of my thoughts on it in comparison to my favourite renderer at the moment, FStorm.
I've used VRay for rendering since the beginning. It was what we were taught to use in school and it was my renderer of choice when I started working freelance. Being such a popular render engine, I didn't even consider using anything else. I'd seen Corona, Octane and all of the other render engines, but I saw no reason to switch from VRay. That was until I discovered FStorm about two years ago. I joined the FStorm Facebook page and couldn't believe some of the renders that were being posted.