The response to my rant about resisting unsupported changes to the 2010 UI has descended into name-calling. Yes, I’m as thick-skinned as anyone, but I draw the line at being labelled as a ‘borderline neurotic’ or a ‘conspiracy theorist’. Just because I’m paranoid, it doesn’t mean that everyone isn’t out to get me!
Any ‘real-world’ Revit user will tell you that there are certain features of the software that are guaranteed to evoke exasperation and a torrent of non-ASCII abuse (%&*£*, etc). ‘Surely, I tell my colleagues in Excitech Support, ‘it’s within the realm of possibility that these features were planted by a non-Autodesk espionage team.’ The reaction to my slightly unorthodox views? Contempt and scorn.
One such frustration is Revit lighting. Last year, it all began with the happy announcement of the inclusion of Mental Ray rendering and the ability to use manufacturer-based IES web distribution files for Revit Architecture 2009. The Revit consultants were all a little smug about the ease of achieving high-quality output that could rival our 3DS Max counterparts like Paul Grimston (although he’d never admit it) without knowing what every button does.
Anyway, I was more than happy to field a call from a Revit customer who was trying to achieve an accurate linear fluorescent uplighting effect. In the test file, instead of an even spread of light, there were hotspots everywhere.

As you’d imagine, it took less than 5 minutes and 400 mouse-clicks to wipe the smug ‘know-it-all’ grin off my face. This was a real problem.
My early efforts were futile. From downloading a manufacturer’s ‘strip light’ IES file to the desperate variation of random parameters within the lighting family: nothing worked.
Finally, I started to apply a more methodical approach and began to review the Type and Instance Parameters for the family.
In the Type Properties of the family, I saw the following parameters. Most were self-explanatory, but it was worth researching the Help system.
From the Help system, I ‘discovered’ that Emit from Light Length means the length of the line that represents the light source in a rendered image. So, this does affect the rendering and needs to be set to the length of the tube.
Light Source Symbol Size is apparently the radius of the representative symbol. According to the Help system, This parameter does not affect the light in a rendered image.
Changing these settings improved the output, but it was far from perfect.
Finally, I applied common sense. That elusive attribute told me that this was a linear light source and, in the absence of reflectors, there was a uniform spherical distribution around the fixture.
So I changed the Light Source Definition in the Family from Linear + Hemispherical to Linear + Spherical:
The result:

As you can see, this was a vast improvement on the original and a few hours after the initial enquiry (okay, maybe a bit more), the customer issue was resolved.
The moral to the story:
1. Read the user manual.
2. Consultants, much like the tools they use, are blessed with vast amounts of logic. The paradox is that common sense is often a last resort accompanied by the exclamation: ‘Surely it can’t be that obvious!’