Floor Levels Not Showing Up In Analysis Drop Down Menu

[Anonymous]

Hey all!  I'm using the Insight 360 daylighting workflow for Revit 2017, and everything was working well until I couldn't select certain floors in my model all of a sudden.  One day I could select them, the next day they don't show up in the floor selection drop down.  The floors and their associated levels still exist in the model. See images below.

If I add a new level, and associate a floor to it, the level shows up.  If I associate a floor back to the level that disappeared, it still doesn't show up in the analysis dropdown.  This is all in a detached model with no worksets, phases, or design options.

If you're interested in taking a look a the model, let me know in a reply or email me directly and I'll send you a link (jdunn@eskewdumezripple.com).

Thanks all!

[stephanie.egger]

Hey @Anonymous!

If you want to go ahead and send me a link I can take a look at things 🙂

insight360.support@autodesk.com

-Stephanie

[hamza_sarout]

I am having the same problem, was there a solution for this issue?

The levels are in the project, there are rooms bounded by walls and from a linked model, but insight is not recognizing all the levels.

[scheerd]

Glad to help.  I haven't heard if there was a solution to the previous issue report.

Can you send me the model to david.scheer@autodesk.com?

David

[hamza_sarout]

Thank you David. I have managed to figure it out. it seems that insight does not recognize floors coming from linked models to generate its analysis grid; it is counter intuitive because it is already using the geometry and its associated data to calculate light levels. I had to create duplicate floors in the native model in order for the floors to appear in the drop down list in LAR. 

the other issue that I might have to face is how rooms from linked models and rooms from the native model are populated in the generated schedule. Do you know something about that?

[Anonymous]

Hmmmm, I can't recall if we had linked models in the model we were experiencing this issue in.  I'm at ZGF in Portland now, but I'll check back with the old team and have them followup.

Jacob Dunn

[rds3000]

Ah yes indeed, linked models.

Here's how it works for Lighting:

Lighting needs to access Floors and Rooms and Levels and to save data about them with the model.  Although we can access information about Floors and Rooms in a linked model, we can't generate schedules for Lighting results, so we don't use them to generate analysis surfaces or results.

However, all of the geometry in linked models is used to create the geometry for the analysis engine, so if you look at the Lighting Analysis Model View, this is what will be exported to analyze light for the analysis points that we do generate from Floors and Rooms and Levels in the main host model.

So when running Lighting, be sure that the Floors, Levels and Rooms are in the main host model.

Check the Lighting Analysis Model view for all geometry that will affect light in the model.  

In future releases, we will be able to generate analysis points from Floors on shared Levels, but it's more difficult to use Rooms in shared models, as we use Room parameters to report results in the Room schedule, and we can't modify the parameters of Rooms in the linked model, which is how we store data with the model as well.  We would have to create a new, standalone UI and data management system to do that independently of the Revit parameters.

Since we don't read Rooms and Floors in the linked model, it's safe to add copies of them to the main host model.

David

[Anonymous]

I'm having the same problem although it's with a native (non-linked) Revit model. In the lighting analysis drop-down menu only F1 and C1 show up. There definitely is a F2 level (been using it all along). 

Any ideas? 

Thanks,
Matt

[rds3000]

Hi Matt.

Since all Levels with Floors in the Host document that are Visible in the '_Lighting Analysis Model View' will show up in the Levels list, it's likely that there are no Floors associated with F2.  We see this fairly often that the Floors are associated with a different Level, but show up at the proper elevation due to an offset.

Best way to check is to Duplicate the _Lighting Analysis Model View, then show only Floors (VG > all off but Floors), then select the Floors that appear to be on F2 and see if the Level association is correct.

One other option is that the Floors have a Slab Shape Editor applied to them (Shape Editing tools like Modify Sub-Elements).  We currently don't handle non-planar Floors. We occasionally see this on regular interior Floors due to an inadvertent click of that button even though no points were really modified.  If you don't need the Floor to be sloped, click 'Reset Shape' to remove the Slab Shape Editor.

David

[Anonymous]

Ah, for some reason (due to my relative inexperience with Revit I'm sure) the second floor is associated with C1 level, with an offset. That was the other option available in the list. 

New analysis running now but I'm expecting it to work.

Thanks much for your help.

Matt

[rds3000]

Great!

Ideally you'd move the Floor to the Level at it's elevation.  

It generally works well, but you might get some odd results if the Rooms are not associated with the same Level as the Floor.

d

[tgibbons1]

Hi folks,

Former coworker of JDunn actually.  I'm still struggling with this issue - after probably 2+ years.  I've tried everything - just today am working in a model that will not refresh any new levels I've added.  The level in question is not linked from a consultant model, it's on an active workset that's not hidden, I've associated the floor geometries to the new level and created a new room associated with the new level, checked that the new room is included in the daylight analysis in the schedule, I've closed Revit, made a new local file, moved the levels to and from a scope box - all to no avail.  I've read through the above comments pretty thoroughly but let me know if there's something I'm missing.  

I would assume there are folks still having this issue.  It's as if the analysis doesn't ping the model to look for new levels - as if the only options for analyses are set in stone once you open the tool for the first time? 

Can someone from Autodesk get with the COTS team for Revit and identify how the levels get populated in that particular table?  

Thanks,

Tom

[rds3000]

Hi Tom.

Looks like you're doing everything right.

I'm able to debug in the Lighting source code, so I'd be glad to look at the model, which is the only way we'll be able to track this one down.  I never got the model from JD from ZGF for the previous issue, so hopefully we can help that situation too.

Please send a link to scheer.3d@gmail.com.  

We will of course keep the project files totally confidential.

David

[rds3000]

Confirmed workaround for this issue (which will be fixed in the next release):

Due to some wonkiness in the back end code we use to filter and sort Levels, any Levels with the same elevation as one previously added to the list will not be added to the list.  Easy fix that will be in the next release,...so meanwhile...

To be sure a new Level will show up in the list, two things:

- Be sure there is a Floor associated with the Level

- Be sure the Level is at a slightly different Elevation than other Levels.  Normally I'll copy a Level offset an inch, then any Floors I move to it, I'll offset them an inch in the opposite direction.

David

[FutchaC]

I recently had a similar problem and I am using the latest version of Insight for Revit 2019. Insight had trouble to recognize a floor that was added later on. I had to create "fake" levels above with floors in order for that floor to be taken into account during the analysis.

[scheerd]

The last version of the addin implemented filtering for Design Options, and the previous version for Worksets.  In any case, if the Floor shows up in the '_InsightLighting Model View', its level should show up on the list for a new analysis.

If you check the _ILMView and still see the Floor and not the Level, please send me your model to insight360.support@autodesk.com.  If we missed something, we'l fix it.

David