Howto fill out the missing surfaces?!

[EEriksson]

Hi guys,

I dont know about you, but I've been struggeling with missing surfaces ever since the addin for revit arrived.
I've allways remodelled in revit when they appeared, but now they appeard when I was modelling in ModelIT when I cut a zone in half. Basically my entire floor in 2 zones are now missing surfaces. They total at about 4000 m2 of missing surfaces.
Now what would be the easiest way of adding the floor to the room??
The rooms are fairly large and have complicated geometry so redrawing them is the last thing that I want to do.

Any suggestions?

Thanks

Erik

[Bunsen Honeydew]

Are you sure there's not a hole in the floor? We found that importing a model from Revit put holes in every ceiling.

[PCully]

Hi Erik,

I've heard of this occasionally but never been able to reproduce here. Would it be possible for you to upload the Revit file (or the <VE> cab after import from Revit) to our upload form http://upload.iesve.com/ and mark it FAO Phil with the reference "User Forum: How To fill out the missing surfaces?!"

This way I can hopefully reproduce and get the development team to take a look. If the surfaces are missing in the same way they can be missing when you import from Revit then I don't think there is any way you'll be able to manually correct this without redrawing the room or reimporting? What you could try would be to import the Revit gbXML to a new project in <VE>, strip out all the other rooms then export the large room as a GEM from ModelIT, import this GEM to the main project and you should find you can replace the corrupted room and *hopefully* you will be able to split this version of the room without losing surfaces (sometimes export/import as GEM can make geometry more robust, I have no idea why!).

Bunsen Honeydew re: the holes in ceilings - this is when the upper limit of the room in Revit is not bounded by a ceiling or roof. This is covered in the modelling white paper.

Phil

[EEriksson]

Phil, I'll send you my model. This error occurred when I was modelling in VE. It did not appear when the model was transfered to VE from Revit. Allthough I dont know if the import from Revit did something to the geometry which could have triggered this error.

However I solved the problem by figuring out a number of things:
First, I can use the "draw partitions" tool to cut zones in half in their z-axis if I flip them 90 degrees. That seemed to close them up good, so I just extended the room again, and then when I tried to put them back in their place VE kept screaming about intersections, but if I turned intersections off and then placed the zone in the correct place and then turned them on again and did a model check for intersections it didnt report any. =)

The whole concept of using the "draw partitions" tool, deleting the "bad" room that have a missing surface and then extending the other part of the room so it meets the original shape of it works splendid when fighting missing surfaces.

However I have one remark that has to do with moving rooms, when using the model endpoint snap it doesnt always snap to the EXACT spot, it sometimes (like 1 of 2 cases) miss the endpoint with 0,0001 meter or so... which causes new intersections to occur... its like the move command is exact down to 0,00 and the intersection check is exact down to 0,000001.

Puh, I hope you can make sense out of that, it kind of took the 20+ hours to figure out...

Phil, I'll try to export and import a gem file, however I dont want it to remove the zones that are bad, I want to fix them, beacuse it will be to hard to redraw them again.

I'll send you the model and you will see for yourself.

Thanks

[EEriksson]

Hey Phil,

I cant send you the model because the form keeps complaining about my phone number and it doesnt give me any hints of what it would like instead.

/Erik

[PCully]

it probably looks for a UK number, sorry. Just add a dummy number with 11 digits or use the IES Glasgow office phone number 01419458500 and add your telephone number on the details section (it's only for a record anyway so not too important in this case)

Phil