Announcements
Welcome to the Revit Ideas Board! Before posting, please read the helpful tips here. Thank you for your Ideas!
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Render Absolute Photometry Correctly Out of the Box (LED Lighting)

Render Absolute Photometry Correctly Out of the Box (LED Lighting)

When LED light fixtures are used in Revit, the rendering engine does not properly interpret the IES file. It works correctly if you render in the cloud, but for some reason the out of the box render engine interprets the light as rainbow colors.

25 Comments
Anonymous
Not applicable

This has been an issue for at least the last 5 years.  Absolute photometry (ies files) will not work in Revit.  There is a known workaround that requires the user to edit the ies file but it would be nice to be able to use the original ies file.

Anonymous
Not applicable
Anonymous
Not applicable

I just tested an LED IES file in Revit 2017.1 and it still does not work.  Average Estimated Illuminance in the space is ZERO.  If I try to adjust the "Wattage/Efficacy", I get an "Invalid Input" error.

I do not see any difference in behavior from the previous version of Revit.Is there something I am missing here?  Are we doing something wrong?

Is there something I am missing here?  Are we doing something wrong?

 

~ Armand

Anonymous
Not applicable

To clarify the original problem:

Revit will not CALCULATE lighting levels when using an absolute photometry IES file.  This issue appears to have NOT been solved or implemented yet.

 

Armand

dplumb_BWBR
Advisor
The 2017.1 Webcast promised to post a link to the LED Light families. Where are they?
harlan_brumm
Autodesk
Status changed to: Gathering Support
 
Anonymous
Not applicable

This is not a new feature request, but a bug that needs to be fixed. 

 

All LED fixture ies files use absolute photometry, and nearly 100% of the fixtures specified on new projects are LED.  The lack of support for absolute photometry makes Revit absolutely useless for lighting calculations and rendering.

 

I know there is a "work around" but, lighting professionals should not have to take on the expense and liability of manually hacking each ies file used in a project to make them work with Revit's broken calculation engine.

 

Nate

tkendrick
Advocate

Man, I could have sworn, in some new features release recently, that it was promoted that absolute photometry support was finally added. 

gina.liu
Alumni

@Bfglunz Would you please upload the simplified project file of LED lighting fixture here? So that we could reproduce this bug. Thanks!

Anonymous
Not applicable

gina.liu, simply go to Lithonia.com and download any LED ies file.  Put that file into a light fixture family and set the light source to photometric web.  Bring the fixture into a 'space' in a project.  Check the space for average foot candles.  It will not calculate.  This is a completely separate issue from rendering - I am only talking about the lighting calculations.

Anonymous
Not applicable

@gina.liu it is a known bug. 

Report

gina.liu
Alumni

Please try rendering an IES lighting on R2017 or a newer release.

I've downloaded "2ACL2_20L_MVOLT_EZ1_LP850.ies" file from Lithonia.com, and assign it as the photometric web file of a lighting fixture, which has a photometric light distribution. The lighting render result is acceptable.

This "rainbow" issue happens to R2016 and older release, and we had fixed it into R2017 release.

Anonymous
Not applicable
The issue is not the rendering. This issue is about lighting calculations. Go back to the project you created, add a "space" (not a room), then put your fixture in that space. Now, check the properties of the space. Look for "Average Estimated Illuminance". With LED ies files in your light fixtures, you will see that you are getting ZERO. Try the same experiment, but this time go get an ies file for a fluorescent fixture, and you will see the difference, and the issue.
I agree, it renders correctly, but I need it to "calculate" correctly.
Armand
tkendrick
Advocate
Yes! This is correct! And this is the problem!
Anonymous
Not applicable

gina.liu, 

 

I am using Revit 2017.2

These are the problem I am having with the absolute photometry files:

 

1. Spaces are calculations are showing 0.0 fc.

Space with absolute IES.PNG

 

2. The Coefficient of Utilization is not calculating or not showing.

CU Not Calculating.PNG

 

 

3. Initial intensity is not set to Luminous Flux and does not pulling it from the IES file. The Luminous Flux cannot be edited manually because the Initial Intensity dialog box ceases to work when an absolute photometry file is used and will not take input.

Initial Intensity.PNG

 

The IES files I attempted to use from Focal Point are available here.

 

Thanks for looking into this issue.

Best Regards,
Nate

Bfglunz
Participant

Hi Gina,

 

Thank you for your attention to my original question.


It would appear that the rendering bug has been fixed in 2017.

 

Thank you on behalf of the community for this fix.


Best,
Ben

gina.liu
Alumni

Hi @Anonymous 

 

Thanks for explanation!

 

Regarding to issue 3, i have tried on Revit 2017.2 with following steps:

1, Download a lighting family file (Lighting_Fixture-Focal_Point-ID+3.5in-Downlight-Round-FLC3D_RT.rfa) from http://www.focalpointlights.com/products/downlight/id-35-downlight-flc3d-lc3.

2, Open Revit 2017.2, new a project, and create this lighting in this project.

3, Select this lighting, and open Type Properties dialog.

4, Scroll down and open Initial Intensity dialog.

5, For Luminous Flux, edit the default value 1000.00 lm, for example, change it to 1200.00 lm.

6, Click OK.

This value is allowed to edit on my machine, and i cannot reproduce what you described. See the screen shot below.

Please let me know whether my steps are correct or not, or is there any other setting i should turn on in the case you described?

 

Capture.PNG

 

Thanks,

Gina

jill_chen
Autodesk

Hi @Anonymous

 

We did a fix on the absolute photometry to support calculate the average illumination, and the preview build is available on Revit beta forum, welcome to try the new build and add any comments.

 

This specific thread on beta forum as following:

https://beta.autodesk.com/project/forum/thread.html?cap=cb0fd5af18bb49b791dfa3f5efc47a72&forid={41425d69-0196-4dda-a690-cfccfdb70e6d}&topid={E8F5194F-F2A7-478A-9F50-BF697A276899}

 

Anonymous
Not applicable

@jill_chenI cannot find the thread. Could you follow up on this? I  have been dealing with this problem for 8+ years and I know the solution very well.

 

Using specific formulas, Revit could calculate the lumen value based on the raw content of the IES file. You can do it manually on this website and it will give you the real lumen value which sometimes differs from what the manufacturer provides.

https://www.visual-3d.com/tools/photometricviewer/

 

In the same vein, Revit could auto-populate the initial lumen value by just reading the IES file. Most people don't realize this has to be entered manually, so many light families are inaccurate and just contain the default lumen values.

 

I've been doing lighting design and rendering in Revit for a while now, and there are many avenues for improvement.

jill_chen
Autodesk

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea  

Autodesk Design & Make Report