So far
198.901 polygons
112.483 vertices
Steam regulator and manometer added…
And some remarks about 3dsMax. In the last part of this blog I wrote "because above 400.000 polygons my 3dsMax gets slightly slower".
The amount of polygons have not been the reason for the rapid slow down. It was another phenomena. I could solve the issue but I do not know the exact reason for it.
In the end a problem appears which made working absolute impossible. The scene contained only one rivet with 144 polygons. I used the array function to duplicate it in a circle and in all of a sudden Max eats up all available memory, including the page file. I even had problems to start the task manager to terminate Max. And the file size increased dramatically too.
The solution was quite simple, even I do not understand the cause. If somebody can explain it to me, I would be very thankful!
I only had to select all items, which had been editable meshes, convert them to editable poly and back, problem gone, very low memory usage and dramatically smaller file size (823 MB before, 1.35 MB after).
Mick!
198.901 polygons
112.483 vertices
Steam regulator and manometer added…
And some remarks about 3dsMax. In the last part of this blog I wrote "because above 400.000 polygons my 3dsMax gets slightly slower".
The amount of polygons have not been the reason for the rapid slow down. It was another phenomena. I could solve the issue but I do not know the exact reason for it.
In the end a problem appears which made working absolute impossible. The scene contained only one rivet with 144 polygons. I used the array function to duplicate it in a circle and in all of a sudden Max eats up all available memory, including the page file. I even had problems to start the task manager to terminate Max. And the file size increased dramatically too.
The solution was quite simple, even I do not understand the cause. If somebody can explain it to me, I would be very thankful!
I only had to select all items, which had been editable meshes, convert them to editable poly and back, problem gone, very low memory usage and dramatically smaller file size (823 MB before, 1.35 MB after).
Mick!