PDA

View Full Version : RAC 2010 - fascias used as ridge tiles will not stretch



ws
2009-06-23, 11:20 AM
Another annoying little problem I've found with RAC 2010 is that on many existing upgraded projects, where I have used a fascia with a ridge tile profile on a dormer roof, the ridge tile has been shrunk back to the extent of the dormer roof before it was Joined to the main roof.

Attempting to stretch the ridge tile back to its full extent produces random lengths or even shortens it.

It does not happen on every single dormer (possibly just copied roofs?) but I have seen it in several projects now and it is definitely something new in 2010.

Remaking the ridges seems to make no difference.

iankids
2009-06-23, 11:31 AM
Hi William,

Given that it is not on every roof, is there something in the underlying structure of how the roofs were created which might give rise to it?

Were the roofs with the problems fully sketched (i.e. Valleys etc created as sketch lines) or were they a smaller roof which was then joined to the main roof with the join roof tool? I could imagine that if it was the latter that the underlying code might read the roof as the orginal sketch area.

This is purely a guess on my part and may have no bearing on problem at all.

Cheers,


Ian

ws
2009-06-23, 11:48 AM
Hi Ian,

yes, I think that is what is happening.

Revit is restricting the 'ridge' to the extent of the roof before it was Joined to the main roof.

Dragging the end of the ridge profile produces erratic jumps in length.

This also affects gutters as well.

Starting a new project I have been unable to replicate this so far and so I am not sure if it only affects upgraded projects.

iankids
2009-06-23, 11:56 AM
Hi Ian,

yes, I think that is what is happening.

Revit is restricting the 'ridge' to the extent of the roof before it was Joined to the main roof.

Dragging the end of the ridge profile produces erratic jumps in length.

This also affects gutters as well.

Starting a new project I have been unable to replicate this so far and so I am not sure if it only affects upgraded projects.


I too am having other "strange" problems with upgraded files.

I have a project which was started in 2009 and a few days back I decided to bite the bullet and bring one paying job over to 2010. I now find that having created the toposurface in a seperate file in 2010 it crashes they whole shebang when I try to link it to the upgraded model file.

As a work around, I recreated the toposurface in 2009, upgraded(???) to 2010 and then linked them.

Hopefully WU1 sorts out a few of these bugs.

Cheers,

Ian