HUGE file size because of... schedules???

[KalvinK]

Hi, I hope this is the right place to post this, sorry if not to the mods.

I've followed all steps I could find for reducing file size, but my empty template file is still 220,000KB. I'll be using nearly 1GB per every 2 projects in that case (with one backup), a bit too much indeed. My embedded library is 37MB and I'm trying to trim that down, but I'm more concerned with the remaining 183,000KB. I started deleting things willy-nilly in a saved version of the template and found that deleting all of my schedules brings MASSIVE reductions in the file. Deleting them reduced my file size by 130,000KB, over half of the file. Most of the schedules I have in there are very basic door and window schedules, many adapted from the out-of-box ArchiCAD template. This basic square footage schedule (below) clears up nearly 10,000KB in my file when I delete it. Does anyone have an idea as to why my schedules might be using so much file storage? I'm bewildered.

Kalvin

Operating system used: Windows

[JeffH]

Do you have a lot of info already placed on your plans/model that is being scheduled, in your template file?

Deleting all schedules reduced my Larger project template from 53,764kb (52.5mb) down to 49,913kb (48.7mb)

The only things that appear on any schedule when a new project is created are 2 walls.  nothing else is pre-created in plan/model.  

[KalvinK]

Jeff,

Unfortunately no, the template file has virtually nothing in it. There is nothing in the model. It's weird.

[KalvinK]

Jeff, I should add however, that I have drawn plans in the template file prior and have now deleted everything out of it. While I was developing my template, I did one project at a time so that I didn't have to keep on sending updates back to a separate template file. I probably made like 3 or 4 residential projects in here before setting it aside and using it as a proper template. I'd bet that is significant to my issue. I just didn't think it would be this hard to clear unwanted data out of the file now. Open and repair does very little for me.

[Lingwisyer]

Might you have schedules that have not regenerated since the last project, and hence contain legacy information?

[Scott Boyd Turner]

Kalvin,

you should start a template by editing one of the Graphisoft templates and bring in views / attributes /schedules etc you need rather than starting from previous file otherwise you tend to get significant bloat as you've discovered.

Scott

[KalvinK]

Lingwisyer,

I just regenerated all schedules, no legacy information appears to be retained; however, this is almost certainly what is occurring. Your comment made me realize that the schedules I use the most frequently are the schedules that contribute the most to the bloat in my file size. However, all of them are completely empty and up-to-date now. And I've unchecked "store in project" on all of my views. I just wish there was a way that I could manually force the file to let go of that legacy information... But I might just have to start from scratch and tediously import everything...

[KalvinK]

Scott,

In a perfect world, yes that'd be the way to do it. However that would have been extremely impractical for me at the time. I've seen mods in this forum say that creating a template the way I did is a fine approach to use. But now it seems the situation may be beyond fixing and I'll have to start a new file and meticulously import everything like you are suggesting.

[runxel]

If even "Open & Repair" does not seem to help somethings deeply off indeed.

I'd just sent the file in with the support. They can check it or will send it to Budapest directly for deeper investigation. Might help the devs, too, to explore potential bugs.

[KalvinK]

Perhaps I'll do that.

With no viable fix, I started importing everything into a new template file this morning. It's a pain and might take a half or full days' worth of work, but it'll be worth it. At my worst the file was 250,000KB. It's looking like I'm going to be able to get it down to 60,000. Should save a lot of money on file storage in the future...

Once I'm done, I might send my "identical" files to support to show them the issues I experienced. Who knows if they'll investigate, but at least I can let them know about it.