When I 'setup' roofs I'm getting an error of "Object reference not set to an instance of an object" and it causes parts of room surfaces to be removed from my project tree and not associated with any floors, yet they can still be seen in the views.
Below is a screenshot after I've 'Hide all floors' and it's still showing these un-associated surfaces which are then causing more errors as essentially it's removing random walls and floors from the project tree.
Are you able to help me re-associate these surfaces please?
Hi Shane,
I've sent them over now.
Many thanks Adon, I have downloaded the files and will get back to you.
Shane Regan | Principle Building Performance Support EngineerHevacomp to OpenBuildings - A complete guide for every user | Bentley Communities
Hello Adon,
We have been investigating this matter in depth and the course of the issue appears to be due to how your roof has been traced. Please see image below where the roof at 28m encroaches over a portion of the irrelevant room adjacent to it. This has caused conflicts in the rooms below upon roof setup.
To resolve:
1. Delete Room 10.02
2. Delete roof section in Roof at 28m
3. Use the Roof at 27.5 to draw the entire roof for tenth floor. ie use the elevation setting below if you want the roof sections at 28m:
4. Complete the Setup roof option for this floor:
Hi Adon,
Just to follow on from that - if these are flat roofs then please note that you could also just change the surfaces in the project tree, this may actually be simpler in your case, ie as below:
Ok great thanks Shane,
Have you found out how to resolve the un-associated surfaces that got deleted from the project tree at all?
You are very welcome Adon.
Was this in relation to the other matter from Service Request 7001220989?
Yes part of that aswell but it occurred in the files I sent over for this post when I added the roof. the screenshots are in my original comment on this post.
Thanks for clarifying, I see what you mean. I have logged a defect for this matter so that our developers can view the underlying code. However this appears to just be a visual issue so for now the existing room data itself should be fine to proceed with and to run your calculations.