Anuncios

The Autodesk Community Forums has a new look. Read more about what's changed on the Community Announcements board.

GL
Contributor
602 Vistas, 4 Respuestas

Linework in Layout Shifts when Zoomed Out

I am having an issue with the appearance of linework appearance in layout. When zoomed out, some linework appears broken and inconsistent (see highlighted pic below). When I zoom in, it shows correctly (also below). The polyline in question is at the same Z=0 elevation as the rest of the linework (with exception of some surfaces but not linework). This happens in another file as well, that doesn't have any C3D pipes or linework. I have tried to explode the affected polylines and it doesn't fix the issue. Please note that everything prints correctly. I have attached the file. Thanks everyone for your help. 

 

GL_1-1632405732759.png

GL_2-1632405785173.png

 

Valentin-WSP
en respuesta a: GL

@GL ,

 

Consider this link:



Please select the "Accept as Solution" button if my post solves your issue or answers your question.


Emilio Valentin
pendean
en respuesta a: GL

In addition to other posts... your file has missing shape files that might be affecting your linework, and it does contain errors (as might the XREFs not included)

pendean_0-1632407846758.png

 

And your file does contain C3D pipe content

pendean_1-1632407934347.png

 

 

GL
Contributor
en respuesta a: pendean

That's strange that you are finding errors and I am not. I have run "audit" and recovered the file, and no errors found. For the shape files, these are the result of a surveyor sending my stuff converted from Land Desktop. Thanks for the feedback!


@pendean wrote:

In addition to other posts... your file has missing shape files that might be affecting your linework, and it does contain errors (as might the XREFs not included)

pendean_0-1632407846758.png

 

And your file does contain C3D pipe content

pendean_1-1632407934347.png

 

 


 

GL
Contributor
en respuesta a: Valentin-WSP

Thank you thank you thank you! The WHIPARC variable was causing this issue. Set = 0 and all fixed!

 


@Valentin-WSP wrote:

@GL ,

 

Consider this link: