Is there a way to disable the sheet preview when you hover over the drawing tab?

[tim_newsome]

Is there a way to disable the sheet preview when you hover over the drawing tab?

I have an extensive set of construction plans. Each scope of work is its own DWG. i.e. Grading sheets = Grading Plans.dwg, Utility sheets = Utility Plans.dwg. As I am working every time my cursor goes up into the ribbon, AutoCAD shows me the plan views for that DWG. It is a consistent disruption.

[BlackBox]

Is there a way to disable the sheet preview when you hover over the drawing tab?


Consider the FILETABPREVIEW sysvar.



I have an extensive set of construction plans. Each scope of work is its own DWG. i.e. Grading sheets = Grading Plans.dwg, Utility sheets = Utility Plans.dwg. As I am working every time my cursor goes up into the ribbon, AutoCAD shows me the plan views for that DWG. It is a consistent disruption.


Consider using single-Layout sheet drawings (for plot), with a single XREF in each for that scope of work, and Layer States to control the resultant plot output.

You do the design work in the XREF, labeling in the XREF or in the sheet (depending on how Viewports do or do not overlap, align with centerlines, etc), so the sheet drawings are just for plotting.

Yes, it's more drawings... Yes, it can be more efficient to print them all to PDF *IF* you print via Core Console in parallel, instead of printing them via PUBLISH in series.

HTH

[PaulLi_apa]

I don't know of a way to disable the sheet preview completely.
@BlackBox referred to FILETABPREVIEW system variable.
When you hover over the drawing tabs:
With a 1 setting it will show thumbnails:
110079
With a 0 setting it will still show a list:
110078

- - - Updated - - -

found this thread that provides one more system variable that will at least disable the loading of the layouts:https://forums.autodesk.com/t5/autocad-forum/autocad-how-to-turn-off-file-tab-hover-preview/m-p/6347588/highlight/true#M126228
FILETABTHUMBHOVER: controls what happens next, when you hover one of the thumbnails.. Disabling it prevents loading the modelspace or layoout you hovered over..
So set FILETABTHUMBHOVER to 0

[tedg]

Consider using single-Layout sheet drawings (for plot), with a single XREF in each for that scope of work, and Layer States to control the resultant plot output.

You do the design work in the XREF, labeling in the XREF or in the sheet (depending on how Viewports do or do not overlap, align with centerlines, etc), so the sheet drawings are just for plotting.

Yes, it's more drawings... Yes, it can be more efficient to print them all to PDF *IF* you print via Core Console in parallel, instead of printing them via PUBLISH in series.

HTH

Yes BB, that's pretty much what our company does, and we use SSM and publish, which is awesome. We are an A/E design company and this works great for buildings and structures.

I do know that our "Civil" C3D folks like to keep the same type of sheets in one file with multiple layouts, this helps with plan-profile data and such (at least that is what I am told), but they limit it to like 4 sheets.
Which still works great with SSM, because you are plotting layouts from the SSM.

[BlackBox]

Yes BB, that's pretty much what our company does, and we use SSM and publish, which is awesome. We are an A/E design company and this works great for buildings and structures.

I do know that our "Civil" C3D folks like to keep the same type of sheets in one file with multiple layouts, this helps with plan-profile data and such (at least that is what I am told), but they limit it to like 4 sheets.
Which still works great with SSM, because you are plotting layouts from the SSM.

PUBLISH - regardless of using SSM or manually invoking the Command - plots drawings in series (one-at-a-time).

Plotting via Core Console, plots multiple drawings individually in parallel (all at same time).


As example, say it takes 30 seconds to plot a single drawing, all drawings take the same amount of time to plot, and you have 10 drawings in your plan set... PUBLISH takes +/- 300 seconds (5 mins)... Core Console takes +/- 30 seconds to achieve the same result.

Please take from this what you like. :beer: