2+ years later and I'm the only one who has responded to this. I can't believe I'm the only one this is happenning to. I now have a detailed corridor model of a multi-family project which, until an hour ago, has been working great. Modifying the corridor via assemblies, regions, profiles, whatever, has been an ongoing process for the past 2 months. Doing the same thing today, and I'm now getting the Surface to only sometimes change with the corridor revisions...and most of those times it is incorrect. It started out as just affecting one baseline, but now others have jumped on the band wagon.
This corridor and surface are important pieces to my plan production sheets which are all labeled (based on a surface this one is pasted into) and ready for submittal. If I can't get this surface to update properly, well, it won't be a good thing.
In this image, I have selected the corridor so it can be seen vs the Tin lines. Note that there is no longer any corridor region along the street going to the right. I removed this regions due to the surface not reflecting a change in the Assembly being used. Yet the surface remains showing as if the original assembly were still in use.
So short of removing the Surface and rebuilding it, any ideas floating around?
You should've tried the SOP, Save, Close, Restart. This appears to have kicked it back into submission.
Oh, this was in 2012, SP1, btw.
OK, Jeff, QUIT talking to yourself. Yesterday thru today I was experiencing a similar situation after I changed to different assemblies, etc. I am using 2013 and I definitely ALWAYS use the save, close, restart as my first as my first remedy. I must be in a different zone because SOP is not appearing on my screen.
Access a broad range of knowledge to help get the most out of your products and services.