Got something against RH making a living?
you need the base price of lw, od toolset, various other plugins and then you have to buy the documentation as well.
Do you get free driving lessons when you buy a car? Training in the culinary arts when you buy a cooker? A course in carpentry when you buy a saw ad a drill? Nope. Manufacturers of tools/machines document the specific operational parts and controls of their products within the context of the practice for which they're designed to be used.
If the answer to your question is not obvious to you, I think we've found the reason why you need every last step spelled out for you.
Those kind of statements are, in my experience, usually either placeholders for late-breaking items that you haven't been able to get a straight answer about from engineers, or - less commonly - items that are just boringly obvious.Sometimes the LW manual is a little too much like "Button xE5vb90 activates function xE5vb90", to my taste.
the LW manual is a little too much like "Button xE5vb90 activates function xE5vb90"
they took away the old renderer we all knew how to use, thus eliminating what would have been the transition period.
Its a while back now, but I seem to recall this was mentioned during 2018 beta, and part of what was communicated was the fact that because the geometry system in layout was being replaced, that there would have to be extensive rewrites to the old rendering system so as the (old) renderer could actually sample those surfaces. This would have added a good deal of extra work (recall, it was already aiming to be LW 2016), so you can imagine trying to wrangle all that on top of the new stuff. There was also the fact that, it would have meant maintaining 2 whole sets of everything... material nodes, lights, so you'd have had old version conductor, new version conductor... old version area light, new version area light... And if you'd mixed them up wrong in a single scene, you'd either get a messy render, or lots of back, or crashes.
I suspect that alone would have made the transition far harder for most folks, than the way it was done in the end.
I think that depencies, impact/capabities or limitations are relevant topics for a reference manual because they can depend on specific software.Yeah... it reads like stereo instructions, cos that's kind of what it is. How to operate the EQ switches is explained, but why you'd want to isnt. That's not product knowledge, its knowledge of the field (and its practicioners) the product is aimed towards.
Funny this comes up this morning. Just last evening I discussed this with someone in senior management. Here is part of my email:Just take a look at our grandchildren´s way of using gadgets that lands up in their hands where the apps are extremely easy to use and are updated with new and faster inventions all the time, from morphs to wigs, from particles splits, liquid and fire. These kids are all more focused in the creative process and would never accept swallowing problems that developers or production teams couldn't solve before the apps were released.