size of TSW files
Posted: Tue Apr 21, 2020 9:17 pm
Hello
I want to ask if you are dealing with big files generated by TSW.
I don't have such complex assemblies but my files are growing up to 25-30 MB.
Personally, I don't consider 30 MB to be such a big size for a computer file but compared to other simple TSW files which has a few KB, it is a big file.
Despite of my pretty powerful computer (HP Z 820 workstation, 2 x Intel Xeon 2.20 GHz, 32 GB RAM, NVIDIA Quadro K5000 4096 MB with all drivers installed in Win 10 Pro 64 bit), the software is very slow with this kind of files (the TSW graphics settings are in "advanced mode" and the Task manager performance graphs of CPU / Memory / GPU do not grow over 40-50% utilization of respective components)
The pan / zoom / rotate actions results in non-smooth movements of the geometry on the screen even in "shading mode". In "realistic rendering" things happens even worse.
When I zoom in and I don't have a lot of details on the screen, the movement becomes smoother.
With this kind of files the "save" command takes a long time to finish.
Before TSW I worked in CATIA on the same computer, with the same or even more complex type of assemblies but without any graphical problems.
What can lead to such big files in this software?
How must I design to avoid such problems - I only have a few months experience in TSW.
If you want I can upload somewhere one or two of this files.
Thank you!
I want to ask if you are dealing with big files generated by TSW.
I don't have such complex assemblies but my files are growing up to 25-30 MB.
Personally, I don't consider 30 MB to be such a big size for a computer file but compared to other simple TSW files which has a few KB, it is a big file.
Despite of my pretty powerful computer (HP Z 820 workstation, 2 x Intel Xeon 2.20 GHz, 32 GB RAM, NVIDIA Quadro K5000 4096 MB with all drivers installed in Win 10 Pro 64 bit), the software is very slow with this kind of files (the TSW graphics settings are in "advanced mode" and the Task manager performance graphs of CPU / Memory / GPU do not grow over 40-50% utilization of respective components)
The pan / zoom / rotate actions results in non-smooth movements of the geometry on the screen even in "shading mode". In "realistic rendering" things happens even worse.
When I zoom in and I don't have a lot of details on the screen, the movement becomes smoother.
With this kind of files the "save" command takes a long time to finish.
Before TSW I worked in CATIA on the same computer, with the same or even more complex type of assemblies but without any graphical problems.
What can lead to such big files in this software?
How must I design to avoid such problems - I only have a few months experience in TSW.
If you want I can upload somewhere one or two of this files.
Thank you!