Browse Search Popular Register Upload Rules User list Login:
Search:
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?
Attraction would make it orbit itself a bit, though, which I do not want. Thanks for the suggestions though.
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?
Welp, just updated this thing. Been a long time. But I made it more realistic.
But why is its center of mass.. There. Given the actual concentration of the matter, it should be fine.
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.
Lmao I didn't even know there was a rule regarding alts tbh, but in hindsight it should've been obvious. Are the saves safe at least?
Fair. Also I did read the rules. I must've either missed it or maybe it wasn't on the save but rather on the 'complete list' which I didn't look into.
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.
If not are there any mods out there that do this?
Trust me I know. Algodoo ran out of memory multiple times while making this. I did get rid of any exact duplicates though.
You can turn off air if you want the system to form faster, however doing this means that some parts may get flinged off into infinity.
ah yes, cringe. that was me at this time. nice.
Wow, this is really well made!
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!
So I've been having an issue of late where my game will randomly run out of memory once I go above a few thousand objects (Which happens more often than you'd think when trying to simulate particle dynamics or making charts/art not meant to be unpaused). and I want to ask a couple questions:

First of all, I don't know how to save as PHN rather than PHZ, as the game suggests (Which would at least allow me to pick up where I left off after restarting the game)

Secondly, I also noticed by opening the console at startup that the game only seems to allocate 85.5 MiB of VRAM to itself even though my computer has 8 GB dedicated RAM available. So I'd actually prefer if there's a way to make the game just allocate more RAM to itself so I don't have to deal with it in the first place. (Ideally, also using the actual dedicated RAM of my PC rather than VRAM)
I don't think I'll ever really post regularly again. I'll just occasionally post things I think are cool.
previous | 1 … 20 21 22 | next