Jump to content

Gytis

Member
  • Posts

    393
  • Joined

  • Last visited

Posts posted by Gytis

  1. I I think it's a big mistake to not take advantage of Autosave.

    I strongly second this. I may be paranoid, but I autosave a backup copy to new location AND manually save my original file like gmm18 describes:

    I just hit the keyboard

    shortcut, Command(⌘)-S, often. I have incorporated it into my workflow,

    I don't even have to think about it, I just hit it, especially before and after

    a complex operation.

    I hatessess re-doing thingssess....

  2. The file size change is an important clue. As I had changed Document Prefs>Save VP Cache in order to retain renders, I increased the file size, but unexpectedly dramatically. With all VPs rendered it was over 1GB!

    The root problem is that though each VP is cropped to a close-up, the ENTIRE design layer is calculated THEN cropped, and it is quite a DL, less a model than an aggregate of all pieces/parts.

    I would recommend more rigorous and liberal use of layers and classes to isolate, control, and organize visibilities. I played around turning classes off and got much better results, i.e. quicker renders and much less memory usage. I'm not sure of your requirements, but I would put different assemblies on different layers (including an invisible "Reference/Derelict" which I include in every file to dump development stuff), while using classes more as you have, to control types of parts.

    IMHO, this is definitely the primary issue.

    HTH.

  3. I've looked at the file you posted, and have a few observations:

    • 868 MB=very large and unwieldy file
    • Some ways to minimize:
      • purge un-needed colinear vertices in polylines
      • use more symbols for repeated items (one definition=endless usages w/o memory penalty)
      • most importantly, create leaner file structure with DLVPs to reference files with standard elements

      I've been told there is no perceptible difference between For VP settings, I've been told there is no perceptible difference between "Shaded Polygon" and "Final Shaded Polygon" except the latter takes lots longer to render....

      [*]I don't know what the official recommended file size is, but I get the feeling that staying under 250 MB is a good idea. Personally I try to stay under 150 MB.

    I was able to render your D Rails Sheet, but it took f...o...r...e.....v...e.......r........

  4. UPDATE:

    Experimented with a stripped down file, same results. Forged ahead with original file, ignoring the issue, and suddenly I notice that SVPs are rendering as desired!

    Happiness, sort of. What was wrong? What "fixed" it? Will it occur again? I had been working on minor revisions, some on primary design layers, some on SVPs, VPs...

    I've always believed in the ghost in the machine.

  5. Frustration!

    Section viewports which previously had displayed attributes of original objects (i.e. hatches, fills, etc.) in the section plane no longer do, nor will no matter what I fiddle with.

    Other files, and earlier versions of troubled file are display correctly.

    Viewports are set to "none" class, and ALL settings are identical to functioning VPs. File has increased in complexity with DLVPs to external file, and several SVPs duplicated numerous times for details, a detailed 3D model pushing the file to nearly 100MB.

    Could any of this be the offending animal?

  6. Wow, Pat. You are the man! A space in front of "Fronts" was the wrench in the works.

    Thanks...you have ended a debilitating bout of intense confusion.

    How about this: how do you reference a database sub-row cell, e.g. B3.2? Seems to just read formula as text. I've played with various operators to no avail and can't find instructions....

  7. I don't know what I am doing incorrectly, but I cannot make an external call reference from a spreadsheet row in one worksheet to a database cell in a second worksheet. Both are in the same drawing/file, and I have followed the manual directions(I think...), as shown in grab. I am trying to reference the contents of cell E13 in Worksheet 'Fronts'.

×
×
  • Create New...