我建立了一個很小的室內設計檔案，但檔案內容卻異常的大，於是我清除了檔案內的所有物件，結果檔案依舊還是有560mb，這讓我很疑惑，究竟還有什麼東西是我還沒有發現的嗎? 請求各位的幫忙，謝謝。 以下是檔案內容。
hi,
deleting the elements in your modelling space is not enough, you need to purge your file.
component and materials are not automatically removed from your file when you erase / replace them.
When you save your file, Sketchup asks if you want to clean your file.
you can also fins this in the edit menu, just below the “delete all guides” (something like delete unused elements).
only this, the purge, will make your model weigh less.
oh wow, it’s truly empty. really odd.
purge doesn’t change a thing. you have an empty file that weigh half a Gb. it’s not normal.
@colin one file to dissect here. I have no idea why it’s so heavy…
很遺憾的，我已經使用了這個功能，也使用過cleanUP3，但檔案依然維持在550mb，我只是很好奇究竟是什麼東西佔據了檔案容量，甚至已經大到快接近完整檔案的一半了，若是能解決這個問題，或許可以讓以後的檔案不會這麼大。
It looks like you have used an extension called PBR_TEXTURE_TOOL
I think this has embedded 99 images into the data separate to the sketchup ones
(I recovered them here to check)
If you paste this into the ruby developer consoles it will delete them.
Make sure to backup BEFORE you run this and save again
model = Sketchup.active_model
if model.attribute_dictionaries['PBR_TEXTURE_TOOL']
model.attribute_dictionaries.delete('PBR_TEXTURE_TOOL')
puts "Successfully deleted 'PBR_TEXTURE_TOOL'."
#IMPORTANT: Save the model after running this to commit the change to disk
puts "Please save your file now to reclaim the disk space."
else
puts "Dictionary not found."
end
I got an error message but deleting the middle line (important: save…) solved it.
quite the diet there.
Yeah, that line should be a comment starting with the pound sign, else it is a syntax error.
可以詢問一下，這些檔案的實際位置會放在哪裡嗎?我想看看究竟是哪裡出了問題，因為我沒有使用PBR_TEXTURE_TOOL ，謝謝!!!
I can’t help with that unfortunately, all I can see is that is what the data has recorded it as. It could be a different extension that has done it which has used a different naming structure.
I could see others for thrupaint and enscape etc too
Found on Model Root: ‘temp’ with 1 keys.
Found on Model Root: ‘GeoReference’ with 7 keys.
Found on Model Root: ‘VRayInfo’ with 6 keys.
Found on Model Root: ‘VRayPlugins’ with 33 keys.
Found on Model Root: ‘GSU_ContributorsInfo’ with 2 keys.
Found on Model Root: ‘Enscape.EmbeddedSettings’ with 2 keys.
Found on Model Root: ‘DM_PB3’ with 1 keys.
Found on Model Root: ‘Enscape.EmbeddedEnscapeViews’ with 0 keys.
Found on Model Root: ‘yooox_s_updates’ with 1 keys.
Found on Model Root: ‘ProfileBuilder’ with 1 keys.
Found on Model Root: ‘FredoTools_ThruPaint’ with 778 keys.
Found on Model Root: ‘JointPushPull’ with 2 keys.
Found on Model Root: ‘PBR_TEXTURE_TOOL’ with 262 keys.
Found on Model Root: ‘lightening’ with 1 keys.
Found on Model Root: ‘Enscape.EmbeddedSettings*EnscapeAccountId_95d1e867-766c-446a-85e1-688711821a2c’ with 1 keys.
Found on Model Root: ‘dynamic_components_templates’ with 0 keys.
Found on Model Root: ‘pid_path_key_map’ with 0 keys.
Found on Model Root: ‘Rayscaper_Data’ with 0 keys.
So lots of extensions here, I’m sure you can work out by a process of elimination which you have installed and which might be causing that,
I was curious about this case, so I ran the model through nEVEn.
The geometry and texture inventories were both empty, but the extension database scan told a different story.
It found 734 MB of data stored under PBR_TEXTURE_TOOL, which matches what @Elmtec-Adam identified.
After a cleanup and rescan, the model dropped from 566 MB to 0.1 MB.
It’s an interesting reminder that large SketchUp files aren’t always caused by geometry or textures, extension metadata can sometimes be the culprit.
