quick profile problem

[Anonymous]

Whenever I generate the quick profile command from one of the xs lines in
the enclosed drawing, the profile appears fine. But then if I qsave, the
profile disappears.

Thanks,
Drew Burgasser
CAD Masters, Inc.
www.cadmasters.com

[Anonymous]

Sorry - c3d2007, sp1

"Drew Burgasser" wrote in message
news:5213272@discussion.autodesk.com...
Whenever I generate the quick profile command from one of the xs lines in
the enclosed drawing, the profile appears fine. But then if I qsave, the
profile disappears.

Thanks,
Drew Burgasser
CAD Masters, Inc.
www.cadmasters.com

[Anonymous]

Drew Burgasser wrote:
> Whenever I generate the quick profile command from one of the xs
> lines in the enclosed drawing, the profile appears fine. But then if
> I qsave, the profile disappears.

Drew,

This is as designed and documented. Quick Profiles are temporary
objects. From the help for Creating Quick Profiles:

"Quick profiles are only created temporarily and are removed when you
save or close the document or exit Autodesk Civil 3D. To create a
profile that you can use again, you must create an alignment at the
location of interest and use it to create a standard profile."

--
Himanshu Gohel. Civil 3D Team, Autodesk, Inc.
Autodesk Civil 3D Product Information: http://www.autodesk.com/civil3d

[Anonymous]

Here I thought 2007 had a nice new feature!!!!!!!!
So you are taking a pretty nice feature and making it temporary.....IT IS WAY TO NICE OF A FEATURE not to be permanent.....this is someting that needs to be CHANGED..

I cant imagine how many cases I could use this without having to go through the entire process of creating a alingment everytime..Saving loads of time and money
Thre are times you just need a simple profile of the ground...not a entire alingment design..


Customer Vote #1 to get this changed!!!!!!!!!!

[Anonymous]

Ahh, I see. Thanks.

I can see this as being frustrating for our users as we train them to qsave
often.

Thanks,
Drew Burgasser
CAD Masters, Inc.
www.cadmasters.com



"Himanshu Gohel" wrote in message
news:5214025@discussion.autodesk.com...
Drew Burgasser wrote:
> Whenever I generate the quick profile command from one of the xs
> lines in the enclosed drawing, the profile appears fine. But then if
> I qsave, the profile disappears.

Drew,

This is as designed and documented. Quick Profiles are temporary
objects. From the help for Creating Quick Profiles:

"Quick profiles are only created temporarily and are removed when you
save or close the document or exit Autodesk Civil 3D. To create a
profile that you can use again, you must create an alignment at the
location of interest and use it to create a standard profile."

--
Himanshu Gohel. Civil 3D Team, Autodesk, Inc.
Autodesk Civil 3D Product Information: http://www.autodesk.com/civil3d

[Anonymous]

I personally do not see a problem here. Even in the 2006 version, I would
make an alignment (with profile) & call it NOVICE (for want of a real name)
and just drag it around the plan as I saw fit. What is the difference?

Worked real nice and easy.

Bill

[Anonymous]

You can just explode it and use it if you want. That's what I do for short profiles.

[Anonymous]

Obviously the quick profile bug isn't corected in Civil3D 2008 version. I have the same problem. When Civil makes profile of 3dpoly, he takes 3d length for x axis of profile instead of 2d length as i shout be.

Please look at the atached file. In dwg file is 3dpoly from which xml. file was exported. If you look at the xml file, the distances on profile are in 3d (281th line in xml) and distances on alignment, from which it was created, are in 2d (11th line in xml).

[Matt.Anderson]

I don't have much use for Quick Profiles, beyond being Quick. I haven't exploded or exported them. If I need that data, I'll create an alignment.

I don't think I will create an alignment out of a 3d object to begin with - it kinda begs the question and as you noted seems to be the root of the problem. A 3d object has a long 3d Stationing as it goes up and down.

A defect - looks like it - the profile stationing should match the alignment stationing. It appears the profile stationing inversing includes the Z in determining the length, where the alignment stationing does not.

I would suggest not using a 3d object to define something intended to be flat.

[Civil3DReminders_com]

If remember correctly, the length issue is an as designed bug, so I doubt it will ever be fixed. The issue is that when Civil 3D creates the quick profile it rounds the elevation to the significant figures you have set (I don't recall which particular object setting it is). If you look at the xml file you will see all of the points are rounded 2 digits (approx.). To get a more accurate distance you have to increase the significant number. For short distances without a lot of vertices its not noticeable, but in the drawing you posted with lots of vertices it becomes really noticeable.

Christopher
http://civil-3d.blogspot.com/

[Anonymous]

I need to make a profile from conected 3d points and this is the only way to do it in Civil3D (as much as i know). To make a quick profile, export it to xml and then import it back again.
I also never use 3dpoly as a object that i make alignment out of. But in this case I do not use 3dpoly to make alignment but to make quick profile which exported and imported again creates that alignment. Problem isnt in alignment, it is ok, but in profile. Stationing from that profile is not the same as statining from alignment.

to ChristopherF:
elevation is not an issue here, and those decimal places arent the problem here, problem is in wrong x axis stationing. I dont see who would need that kind of stationing if that is designed bug ...or am i wrong.

[Civil3DReminders_com]

I explained it better in an older post (which I can't find), but it is an elevation and station problem caused by rounding. The higher the precision the closer the quick profile's station will be to the 3dpolyline's length.

Christopher
http://civil-3d.blogspot.com/

[Sinc]

>> The higher the precision the closer the quick profile's station will be to the 3dpolyline's length.

Exactly - that's the bug.

Stationing is not the same thing as a 3D-polyline's length. The 3D-Polyline's length is a 3D-distance, and stationing should use 2D distances.

[Anonymous]

i thing i know what post your are referring but i don't think that the case here. The difference is to large and that distance is to similar to 3d length to be that kind of bug. Well it seems that I'll have to write some code to get this the right way 🙂 ... Hope autodesk will correct this bug in near future.

btw. great blog you have 🙂

[Civil3DReminders_com]

Yep, I was wrong.