This is completely unrelated to the scene, however I've encountered this one extremely annoying issue for so long now:
>Is cutting an object up so that i can change the color of each segment so that i can texture it
>Suddenly, the console spams "freeing up memory" and half the items i just cut dissappear!
Based on the console thing, Im 99.999% sure that its because algodoo doesn't have enough memory, and in that case, how exactly do I give algodoo more memory to work with?
Its fun to play around with but i noticed it also distorts objects that aren't moving when you add a new object with the collision layer. May i ask why that is?
Heh, I figured that. I made it by starting the right shape (from the intersection point), then once i looped around (clockwise) I did the top shape (counterclockwise) and when i reached the bottom I did the bottom shape clockwise again.
Great simulation! Although I tried to select the habitable zone display to remove it as it kind of cluttered the screen a bit but it just selected the background. Do you (or anyone else who may stumble across this comment) know how to select it?
I know this is april fools but I believe this is your most recent save. Is it possible to remove (through console commands) the limit to how far you can zoom in/out and/or extend sliders (such as showing negative attraction in the materials menu) or adding sliders (Adhesion slider)?
Asking cause it'd make things a bit more convienient for me when making to-scale (1M = 1AU) saves of space in the zooming case, and for the others it'd just be nice to have a more convienient way to mess with those properties.
PS, the big bricks beneath the dome towers are slightly taller than the grid implied I should have there because for some reason the stone falls a tiny bit when unpaused. If anyone knows how to fix that, that'd be great. Thanks!