Civil 3D Headache....again.

[ACADuser]

My cross sections (generated in MS) are not showing FG surfaces.  I have tried plotting single sections, multiple sections, etc. and can't get the FG surface to show.  Same problem when the min/max elevation range In the create section vew dialogue is set to values that include the FG surfaces.  Attached is a screen grab showing what I am getting.

[Joe-Bouza]

Not sure I understand you question but do the sample lines include FG?

[ACADuser]

Yes, I have sampled several sources (see attached).

Odd thing is the FG surface shows up in the corridor section editor.

[ACADuser]

Ok, after my previous post I went back to the drawing and the "Section Sources" dialog was still open.  Instead of clicking cancel I clicked on the "Apply" buttom.  What do you know - the darn FG lines appear in the sections.  FYI these surfaces had already been added as a sample source.

Is there something that would cause a "disconnect" between the section views and sampled sources ?

[bscott]

Something to check.....your fg surface style.  See the attached pic.

[Joe-Bouza]

Nice graphics, Bryan - Is that the latest release of Snagit?

[BrianHailey]

That setting is for if you want to see your surface in the corridor section editor. As far as I know, it does not have anything to do with sections created via sample lines. (Could be wrong, it's happened before. And as I don't have C3D on this computer to test it, I probably am.)

[bscott]

Joe- besides always providing help.....always one to bring a smile to one's face!

Brian, no, I think you are correct, now that I think more about it.  There is something I am remembering back from C3d 2008 that I ran into this and it ended up being a setting of some sort similar to that.  It had to do with a surface, or corridor display setting on the actual part itself (surface or corridor), so that when you turned it on, your data would then show up in your sections.  I know the darn thing is in there somewhere, I just can't remember where.

Of course, this may not be the issue at all, but at least it can be ruled out once I find it.  I'll keep digging- I remember it was kind of burried within (as with everything C3d).