By Richie More<\/em><\/p>\n\n\n\n SOLIDWORKS Visualize facilitates export of complete project into glTF<\/strong> (Graphics Language Transmission Format) and glB<\/strong> (Binary variant) formats.<\/p>\n\n\n\n These files are either self-contained or refer to external assets which represent 3D geometry, appearances, scenes, and animations. glTF \/ glB<\/strong> files are mostly used in AR\/VR applications, native web applications such as displaying a 3D model on Website or attaching them to Microsoft Documents (Word \/ Power Point) for 3D Visualization.<\/p>\n\n\n\n What\u2019s New in SOLIDWORKS Visualize 2021 is the ability to export Visualize projects as Draco-glTF and Draco-glB. Draco Extension results in smaller (compressed) file size, thus results in small downloads and fast transfer of 3D data when used in AR\/VR applications, or Web Applications.<\/p>\n\n\n\n A. Procedure to Export Draco Files.<\/strong><\/p>\n\n\n\n Step 1<\/strong><\/em>\u2013 Open any project in Visualize 2021.<\/p>\n\n\n\n Step 2- <\/strong><\/em>Navigate to file > Export > Export Project.<\/p>\n\n\n\n Step 3-<\/em> <\/strong>From the drop down list, Select appropriate Draco format.<\/p>\n\n\n\n B. GLTF\/GLB vs Draco GLTF\/ Draco GLB<\/strong><\/p>\n\n\n\n As Draco extension extremely compresses the files, let us check the compression level with memory stats for the files exported.<\/p>\n\n\n\n As we can clearly observe, Draco extension highly compresses the exported files.<\/p>\n\n\n\n Visualize Project used \u2013 C:\\Users\\<username>\\Documents\\SOLIDWORKS Visualize Content\\Projects \\ Camaro.svpj<\/p>\n\n\n\n By Tor Iveroth<\/em><\/p>\n\n\n\n In order for an application to open a file from a SOLIDWORKS PDM file vault view, that file has to first become cached to the local disk. Caching a file refers to the automated process that copy the file from the archive server to the local file vault view folder on the client. Once the file is cached, the application will open the file.<\/p>\n\n\n\n This cache procedure normally happens when you need access to the physical file, for example, when you preview or open the file.<\/p>\n\n\n\n If the file has references to other files in the file vault, those references are cached at the same time. This ensures that all related files are available for the application to load them. For example, in order to open an assembly, the subassemblies and parts must be accessible.<\/p>\n\n\n\n If you create a user defined reference relationship between a PDF (and any other non-CAD file type) to a drawing or an assembly, then by default, when you preview or open that PDF all the file references will cache. The following example illustrates this:<\/p>\n\n\n\n 2. Run the \u2018Clear local cache\u2019 command on the folder so that the physical PDF and its referenced CAD files are not available in the local vault view.<\/p>\n\n\n\n 3. Double click the PDF to open the file. This will automatically cache the PDF file and the referenced assembly with child components.<\/p>\n\n\n\n 4. The same automatic reference cache happens by default when you preview the PDF file.<\/p>\n\n\n\n This means that opening a PDF file can take some time, as there are potentially hundreds of referenced files cached to the client at the same time.<\/p>\n\n\n\n As a PDF by itself often do not need the referenced CAD files in order to open in a PDF application or to preview, you can control how the referenced files should automatically cache when accessing the PDF.<\/p>\n\n\n\n To access these settings, log into the SOLIDWORKS PDM administration tool and expand the \u2018File Types\u2019 node. Right click on the \u2018PDF extension and select \u2018Properties\u2019. To manually cache the referenced files when you have enabled these options, use the \u2018Get Version\u2019 or \u2018Get Latest Version\u2019 command.<\/p>\n\n\n\n These examples show how you configure the reference cache options for the PDF file type. You can use same options on any other file types that have referenced files in the file vault.<\/p>\n\n\n\n We recommend that you use the reference cache options primarily on non-CAD file types that do not need the referenced files in order to load or preview.<\/p>\n\n\n\n Why does SOLIDWORKS\u00ae 2021 SP2 crash when saving as a STEP or EASM file?<\/strong><\/p>\n\n\n\n This behavior might occur because of a fault in SOLIDWORKS\u00ae 2020 SP2. To resolve this issue, download and run the hotfix file attached to Solution ID: S-078987<\/a><\/p>\n\n\n\n Why do I see the following warning? \u2018This file was created in SOLIDWORKS 2007 or earlier. The model contains Surface Fill and related features, which could contain \u2026\u2019 In the SOLIDWORKS\u00ae PDM software, how do I delete a workflow state that contains a SOLIDWORKS CAD BOM that is separate from the state of the parent assembly or drawing?<\/strong> For a single SOLIDWORKS\u00ae Plastics analysis, does an increase in the number of CPU core processors reduce the solve time?<\/strong><\/p>\n\n\n\n As of the release of SOLIDWORKS\u00ae Plastics 2021, tests show that a CPU with 16 core processors is the upper limit for reducing solve time. Fore more information, see Solution ID: S-078825<\/a><\/p>\n\n\n\n That\u2019s it for this month. Thanks for reading this edition of SOLIDWORKS Support News.<\/p>\n\n\n\n <\/p>\n\n\n\n![\"\"](\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/1-75.png\")
<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\nHow to avoid caching all assembly files when you open or preview PDF files with attached user defined references in SOLIDWORKS PDM. <\/strong><\/h2>\n\n\n\n
<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n
<\/a><\/p>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\nNoteworthy Solutions from the SOLIDWORKS Knowledge Base<\/strong><\/h1>\n\n\n\n
<\/strong>Files created in SOLIDWORKS\u00ae 2007 and earlier versions allowed use of unsupported surface fill technology. The software allowed faces that were not G2 continuous at the boundary. Later software versions resolve this issue. To get more information, see Solution Id: S-078980<\/a><\/p>\n\n\n\n
When a SOLIDWORKS\u00ae PDM workflow state has any files or named BOMs referencing that state, the state and the workflow of the state fail to delete. To get more information, see Solution Id: S-078870<\/a><\/p>\n\n\n\n