02-03-2017 12:05 AM
02-03-2017 02:05 AM
02-03-2017 04:31 AM
02-03-2017 04:54 AM
kojack said:
The grid itself has a resolution. Let's say the default is 256x256x256. I'm not sure what it really is, but something like that. With a distance and colour it might take 8 bytes per grid point. That means a full layer takes 128MB of ram. You could fill that with 1 huge cube stamp or a million tiny stamps, the result is the same.
Every time you click the increase resolution button, the grid doubles on each axis, which makes it take 8 times the memory. One click and you have a 1GB grid (512x512x512). Another click and it's 8GB of ram. Another and it's 64GB.
(These numbers are just a guess, I don't know how many bytes per point it really used. 8 seems reasonable)
02-03-2017 06:50 AM
P3nT4gR4m said:
kojack said:
The grid itself has a resolution. Let's say the default is 256x256x256. I'm not sure what it really is, but something like that. With a distance and colour it might take 8 bytes per grid point. That means a full layer takes 128MB of ram. You could fill that with 1 huge cube stamp or a million tiny stamps, the result is the same.
Every time you click the increase resolution button, the grid doubles on each axis, which makes it take 8 times the memory. One click and you have a 1GB grid (512x512x512). Another click and it's 8GB of ram. Another and it's 64GB.
(These numbers are just a guess, I don't know how many bytes per point it really used. 8 seems reasonable)
I was under the impression that the number of spaces in the grid stays constant but the sculpted volume is subdivided. That's why the bounding box shrinks when you hit the res button. Maybe not. Maybe a dev could clarify?
02-03-2017 12:28 PM