10 reasons why NOT to use Blender for paid architectural visualisation – 7/10.

The lack of a quick and efficient UVW mapping tool

On most of the Blender forums the visitors could read that Blender built-in UVW mapping  features are among the best.
Well, that could be true in the field of custom modeling when someone have to unwrap a special and unique model, but it is definitely not true for archviz mapping.

Why?

In an archviz scene a 3d modeler have to deal with hundreds, thousands of ‘simple’ models. A good tool would offer the opportunity to assign the same UVW coordinates for multiple models at the same time, but with high level of customizing  later; the opportunity to give exact  UVW coordinates with resizing (numeric), positioning, rotating, scaling, tiling, etc.
Although Blender offers ‘texture space’ mapping (SHIFT+T), it has very limited functionality, compared to the UVW modifier in 3ds Max (and even those limited functions are not working properly in Cycles).

I tried to make some workarounds like transferring UVW layouts, but it is just not there yet (unfortunately).
Blender should offer an UVW modifier what is capable to offer all the necessary ‘simple’ UVW  mapping ways (planar, box, cylindrical, sphere, etc.) with the support of texture channels, tile sizes, mapping gizmos, etc.

 

I contact power users & developers

In the last few days I started to contact Blender users specialized on archviz.
I’m newbie in Blender and I will be minimum for a year.
I need feedback from users who live from archviz and know all the workarounds and weaknesses.
The development of Blender should be more focused;  at the moment it is a nice swiss knife for me.
Has a tons of features, none of them replaces the industry standard packages.
I deeply believe  – after these weeks – that the most easy ‘breakout point’ for Blender is archviz.
It needs the smallest effort to turn it to be able to compete with the big boys.
And almost no one do archviz as a hobby, it is clearly ‘pro’ grade job.
Which means the improvements could be clearly declared.

Contact: vr.builder (at) yahoo.com

10 reasons why NOT to use Blender for paid architectural visualisation – 6/10.

Speed issues

Dear Visitor!
Before starting a debate, first read this and this.
Thanks.

Let me to be more specific:

1. Slow GUI in general
Blender uses OpenGL for the GUI. It results good things and bad things.
The good: it has the same GUI on all platforms.
The bad and more important: the responsiveness of the GUI depends on your GPU.
What does it mean in practice?
Continue reading

10 reasons why NOT to use Blender for paid architectural visualisation – 5/10.

Dear Visitor!
Before starting a debate, first read this and this.
Thanks.

Data exchange

Importing DWG files isn’t supported (by trunk); with DXF files you have to be lucky or make serious preparations before importing (it shouldn’t be an issue, because I used to do it for Max, too, but still you have to be lucky to feed Blender with DXF).
Blender also cannot handle PSD files as far as I know, what means that your pipeline with PS, Premiere, After Effects will not be the same.

Recommended script: http://pythonide.blogspot.hu/2009/04/dwg-support-for-blender.html  (haven’t tried it yet)

10 reasons why NOT to use Blender for paid architectural visualisation – 4/10.

Dear Visitor!
Before starting a debate, first read this and this.
Thanks.

Layer system

Blender gives you only 20 layers, with no useful visual features compared to Max. I think I don’t have to say how necessary is for a bigger project to have an organized scene, and in Max by default it is done by layers.
I don’t say it is impossible in Blender (it is definitely not), but you will miss the ‘Layer manager’ of  Max and its functions in Blender.
Continue reading

10 reasons why NOT to use Blender for paid architectural visualisation – 3/10.

Dear Visitor!
Before starting a debate, first read this and this.
Thanks.

Blender has serious stability issues

This opinion based on 3-4 weeks of usage – Blender is not stable, at least not on my computer. It took me back to the ‘not so good’ old times, when one single app was able to get the whole system halted.
Max is far more reliable, if we can state this about an app, which freezes more than anything else in my standard work-flow (Autodesk guys should do something for their money).
Let me to note something: i saw a lot of videos tutorials from Blender pro users. They save like hell in every few minutes and this tells me that not my computer is the reason for stability issues.
Continue reading

10 reasons why NOT to use Blender for paid architectural visualisation – 2/10.

Dear Visitor!
Before starting a debate, first read this and this.
Thanks.

Array-dupliframe-whatever – meet a weird and unefficient method for multiplying objects

Yeah, I know it could sound terrible for hardcore Blender users (sorry, guys), but I spent half of my day with guessing how can I make something really simple.
So I think it worth to be among the TOP10 of the things in the ‘Why not Blender…’ section; it is simple crazy.
Max guys: you will hate it:)
I hate it.
Fortunately it is not so huge efficiency loss compared to the former post (about the missing 2D shapes/drawing tools), so don’t give up; it could be done.
Continue reading